Child pages
  • Identity
Skip to end of metadata
Go to start of metadata

element

How to use it

repeatable?

notes

rules

 

<entityId>

Use how? Where are we putting LC Control no. and/or VIAF ID?
 Do those go in <source>?

no

Not going to use since viaf ids, etc. will go in the sources,

optional

 

<entityType>

"person", corporateBody', "family"

no

 

required

 

<nameEntry>

text of name, see <part>

yes

Don't use preferred entry. 

Create a new entry for direct order names using local type (applies to personal names)

required if applicable

 

<nameEntry>@scriptCode

ISO 15924 four-letter code "Latn"--Let's avoid using non-Roman scripts.

yes

For this project everything will be Latn

locally required

 

<nameEntry>@xml:lang

Three-letter ISO 639-2 language code

yes

Do we need to repeat this if it is the same as the declared language in the control? We will use it "to be more precise"

locally required

 

<nameEntryParallel>

 

yes

 

required if applicable

 

<nameEntryParallel>@scriptCode

ISO 15924 four-letter code "Latn"--Let's avoid using non-Roman scripts.

yes

 

locally required if using<nameEntryParallel>

 

<nameEntryParallel>@xml:lang

Three-letter ISO 639-2 language code

yes

 

locally required if using<nameEntryParallel>

 

-<part>

Dump the entire name in one <part> or multiple <part> for @localType="surname"
 and "forename" and "dates"(1xx $d in MARC authority record)? Do we need to bother if we are always using <existDates>? 

I recommend we limit ourselves to one <part> and only include dates in existDates.-MR

yes

Do we want to use parts in the same way as MARC subfields? 

Dividing parts more useful for corp names.  

Problem with putting it all in one is that you can't go back. 

What is the value add? 

For now we will use it like MARC subfields and examine if this is beneficial. 

Relator term will not be used (ex. collector)

Punctuation will be included (like MARC ISBD), although it is tempting to not use.

locally restricted to one <part>

 

-<useDates>

Don't use this for birth-death dates but for when the version of the name was used.

yes

 

optional

 

<dateRange> or <dateSet> or <date>

 

yes

 

locally required if using
<useDates>

 

<fromDate>

Use @standardDate?

yes

 

required within <dateRange>

 

<toDate>

Use @standardDate?

yes

 

required within <dateRange>

 

-<authorizedForm>

"DLC", "VIAF", "AACR2". We don't want to require this because it would preclude encoding alternative forms.-MR

yes

You can use authorized form, alternative form or nothing.

Refers to authorization body (LCSH, VIAF)  

Will need to come back to this.

locally required if applicable

 

-<alternativeForm>

"DLC:x400", "VIAF:x400", "AACR2"

yes

 

optional

 

-<descriptiveNote>

 

yes

Where or When do we feel compelled to use this?

optional

 

  • No labels