Aviary

<xs:element ref="abstract"/> 

<xs:element ref="note"/> 

<xs:element ref="tableOfContents"/> 

<xs:element ref="originInfo"/> 

<originInfo><dateIssued> 

<originInfo><dateCreated> 

<originInfo><dateCaptured> 

<originInfo><dateOther>  

1.  MODS puts all names in a repeated<name> with type of contribution indicated in <role>. It does not make the explicit distinction between creator and contributor in terms of primary vs. secondary roles. An application may wish to designate use of Creator or Contributor for all MODS names or use the role value to determine which DC element is used. 
2. MODS allows <name> subelements to be parsed: <namePart>, <displayForm>, <affiliation>, <role>, <description> MODS subelements should be concatenated in Dublin Core, separated by a space or other form of punctuation. 

<subject> 

<geographic> 

<temporal> 

<hierarchicalGeographic> 

<cartographics>   

<physicalDescription> 

<internetMediaType> 

<extent> 

<form> 

<xs:element ref="typeOfResource"/> 

<xs:element ref="genre"/> 

1. Use separate instances of Type for each MODS element value. 
2.  If converting MODS typeOfResource values to Dublin Core Resource Type values, see conversion details below. If MODS <genre> contains authority="dct", that may be used in dc:type and typeOfResource dropped. 

<xs:element ref="subject"/> 

<topic> 

<name> 

<occupation>  

<relatedItem> data is parsed into subelements in MODS (any MODS element may be used).  
Implementations may wish to consider the relatedItem type to determine mapping. If type="constituent", a full description may be given under relatedItem and conversion may result in an incomprehensible value. Alternatively, an application may wish to map only some elements under <relatedItem>, e.g., <titleInfo> and <identifier> or <location> if a full MODS description is given. 

For example, if giving a reference to a resource fully described in MODS relatedItem, one could use: <relatedItem><identifier> 
and/or title of a resource: <relatedItem><titleInfo><title> 

ASpace URL  

<recordInfo>

ZJ requested that we use this for the url from ArchivesSpace for that specific object.  

This is a unique identifier from the URL (of the finding aid). It is essentially the same as the resource URI found in the ASpace bulk upload templates. It is the URL without the domain name. Example: if the URL is https://collections.library.vanderbilt.edu/repositories/2/resources/2074 the Resource URI will be repositories/2 /resources/2074.   

<recordInfo>

<recordOrigin> 
"recordOrigin" is intended to show the origin, or provenance of the MODS record. This might include what methods were used to prepare it (machine generated or human prepared), or what transformations had been applied (i.e., the result of converting an existing MARC 21 record to MARCXML and to MODS). It can be free text or an institution may establish locally-controlled values for machine processing and consistency. There is no MARC equivalent to <recordOrigin>.