Spreadsheet v 1.0 Crosswalk
To view the most recent spreadsheet ingest documentation, please visit the Spreadsheet v 2.0 Crosswalk guide. You can still use v1.0 spreadsheet templates to ingest content into the repository but we will not be updating templates or the metadata transform document for v1.0. If you need to add a metadata field to your template, you will need to switch to version 2.0.
The spreadsheet ingest templates are built using the MODS metadata standard.
Spreadsheet Metadata Guide
Column title: the header text at the top of the template spreadsheet
MODS form label: the field label on the CTDA MODS form
MODS Element: the element in the MODS standard the column title will populate
Use: How the MODS element should be used in describing your object.
M/LM: the field can have multiple values separated by pipes
Column title | MODS form label | MODS Element | Use |
|---|---|---|---|
Binary_file | N/A | N/A | Enter the complete file name, including file extension, of the object you are describing. This object should be uploaded to the CTDA servers before uploading your spreadsheet into the Spreadsheet Ingest Module. |
nonSort | Initial Article | <nonSort> | Non-sorting characters at the beginning of a title. Examples: The, An, A |
Label (Required) | N/A | N/A | Label element used by the system. This value should match title column |
Title (Required) | Title | <title> | Title of the object you are describing. If your object has more than one title, separate the titles using the pipe "|" symbol and see the instructions for Title_Type below. |
| Title_Type | Title Type | <titleInfo type=" "> | Denote if your object has more than one title in this column Accepted values: abbreviated, translated, alternative, uniform |
Sub_Title | Subtitle | <subTitle> | If your object has a subtitle, enter it in this element. |
| Supplied | Did you give this object its title? | <titleInfo supplied="yes"> | Select "yes" when the title information has been supplied from an external source, not from the resource. |
Creator_Contributor_Information_Name_Type | Name Type | <name type=" "> | Indicates what type of name is recorded in the Creator/Contributor element Accepted values: personal, corporate, conference, family |
| Creator_Contributor_authority | Creator Name Authority | <name authority=" "> | Record the name of the authoritative list used for the name of the creator of the object, if applicable, e.g. authority="naf". The Library of Congress maintains a list of authority files: Name and Title Authority Source Codes. |
| Creator_Contributor_authority_valueURI | Creator Name Authority URI | <name valueURI=" "> | A URI uniquely identifying the vocabulary from which the controlled term for the name entered into the Contributor/Creator element. |
Creator_Contributor_Information_Contributor_Creator | Creator/Contributor | <namePart> | The name of a person, organization, or event (conference, meeting, etc.) associated in some way with the resource. |
| Creator_Contributer_Information_Role_Type | <role type=" "> | Indicates whether the role is expressed in a coded or textual form. Accepted values: code, text | |
| Creator_Contributor_Information_Role_Type_Authority | <role authority=" "> | The preferred controlled vocabulary for Roles is Marc Relator Terms list. If you use a role from the controlled vocabulary, you should enter marcrelator into this column. You can also enter local if you are using a local role term. | |
Creator_Contributor_Information_Role | Role | The relationship of the Creator/Contributor recorded in name to the object you are describing. | |
| Type_of_Resource | |||
Genre | Genre | <genre> | A term to designate a category characterizing a particular style, form, or content of your object. |
| Genre_authority | <genre authority=" "> | Record the name of the authoritative list used for the term used in the Genre element. The preferred controlled vocabulary for Genre Terms is the Getty's Art and Architecture Thesaurus. | |
| Genre_authority_valueURI | <genre valueURI=" "> | A URI uniquely identifying the vocabulary from which the controlled term for the genre term, entered into the Genre element. | |
Origin_Information_SingleDate | Enter a Single Date | <dateIssued> | The date your object was published, released, or issued. Dates should be in the YYYY-MM-DD, YYYY-MM, or YYYY format depending on the date information of your object. Example: 2001-12-26 If applicable, you should use one of the following qualifiers for your date:
The qualifier should appear after the date separated by the pipe “|” symbol Example: 2001-12-26|questionable |
Origin_Information_dateRange | Enter a Date Range | <dateIssued> | The date range your object was published, released, or issued. Dates should be in the YYYY-MM-DD, YYYY-MM, or YYYY format depending on the date information of your object. Each date in the range MUST be separated by the pipe "|" symbol. Example: 1967-01-03|1967-02-03 If applicable, you should use one of the following qualifiers for your date:
The qualifier should appear after the date separated by the pipe "|" symbol for EACH date in the range: Example: 1967|approximate|1990|approximate |
Origin_Information | Information on Origin, Place of Publication, Publisher | Enter the place of publication and the publisher of your object if applicable. You MUST enter BOTH the place and publisher, separated by the pipe "|" symbol. Example: New York|Scholastic Inc. | |
| Frequency | <frequency> | Frequency of the publication of your object. Applies to serial type objects like newspapers. Terms to use in this element can be found on the MARC Frequency of Issue Term List. | |
| Frequency_authority | <frequency authority=" "> | The code of the authority used to populate the <frequency> element. | |
| Issuance | <issuance> | Used to describe how your object is issued. Accepted values: monographic, single unit, multipart monograph, continuing, serial, integrating resource | |
Digital Format | Digital Format | <internetMediaType> | Choose the file format of your object from the dropdown list. |
Digital Origin | Digital Origin | <digitalOrigin> | Choose either "born digital" or "reformatted digital" from the dropdown list. |
| Medium | <form> | Describe the physical presentation of your object, including physical form or medium of the resource. This element should be used to characterize the resource itself, not the content of your object, which should be entered into the <genre> element. | |
| Extent | <extent> | Describe the physical extent of your object. | |
| Reformatting_Quality | <reformattingQuality> | Describe the purpose and quality of the format of your object. Accepted values: access, preservation, replacement | |
| Language | <languageTerm> | Enter the language in which your object is expressed. | |
| Language_Term_type | <languageTerm type=" "> | Enter the format of the content in the <languageTerm> element above. Accepted values: text, code | |
| Language_Term_authority | <languageTerm authority= " "> | Enter the authority used for the content in the <languageTerm type=" "> element above. The recommended authority for language codes is ISO 639-2b. | |
Description | Description | <abstract> | A summary or description of your object. |
Held by | Held by | <note type="ownership"> | Choose the name of your institution from the dropdown list |
| Note_Type | <note type=" "> | The note type for the content in the <note> element below. Review the list of note types here. | |
| Note | <note> | Use the note field to capture information that is not encoded in another MODS field on this list. | |
| Source_Note | <note type="source"> | ||
Subject_topic | Topic | <topic> | A term or phrase denoting the primary topic of your object. You can enter multiple entries into this cell. Separate each entry with the pipe “|” symbol. Example: Dogs|Cats |
| Subject_Topic_authority | <topic authority=" "> | Enter the authority used to populate the contents in the "Subject_topic" column. The name or acronym for the authority should be entered in lower case, i.e. fast. The recommended authority for topic terms is FAST. | |
| Subject_Topic_authority_valueURI | <topic authorityURI=" "> | Enter the URI of the authority used to populate the content in the "Subject_topic" columns | |
| Subject_Topic_valueURI | <topic valueURI=" "> | Enter the value URI from the authority used to populate the contents in the "Subject_topic" column, | |
Subject_Geographic | Place | <geographic> | Enter the geographic subject terms used to describe your object. You can enter multiple entries into this cell. Separate each entry with the pipe “|” symbol. Example: Hartford (Conn.)|Providence (R.I.) |
| Subject_Geographic_authority | <geographic authority=" "> | Enter the authority used to populate the contents in the "Subject_geographic" column. The name or acronym for the authority should be entered in lower case, i.e. tgn. The recommended authority for geographic terms is TGN. | |
| Subject_Geographic_authority_valueURI | <geographic authorityURI=" "> | Enter the URI of the authority used to populate the content in the "Subject_geographic" columns | |
| Subject_Geographic_valueURI | <geographic valueURI=" "> | Enter the value URI from the authority used to populate the contents in the "Subject_geographic" column. | |
| Subject_Temporal | <temporal> | Enter terms to describe the coverage or chronological time period of your object. | |
Subject_Temporal_encoding | <temporal encoding=" "> | Enter the type of encoding for the format of the date used in the "Subject_Temporal" column. Best practice recommends using the w3cdtf encoding which uses the YYYY-MM-DD date format. | |
| Subject_Temporal_point | <temporal point=" "> | Enter the start and end points of the dates in the "Subject_Temporal" column. Only use for date ranges. | |
Subject_Name_Type | Name Subject, Name Type | Person, Corporate, Family, Confernece/meeting | |
| Subject_Name_authority | |||
| Subject_Name_authority_valueURI | |||
Subject_Name | Name | <name> | Doe, John. NASA. U.S.S. Constitution, etc. |
| Subject_Genre | <genre> | ||
| Subject_Genre_authority | <genre authority=" "> | ||
| Subject_Genre_authority_valueURI | |||
Cartographic_Coordinates | Coordinates | Geographic coordinates | |
Identifier | Identifiers, Type Local | <identifier> | Enter any identifiers associated with your object. For example, the unique file name of your object, a collection number, or an accession number. Separate multiple entries with the pipe “|” symbol Example: MS25|1993.2.34.jpg |
| Identifier_type | <identifier type=" "> | Enter the type of identifier for the content in the <identifier> element above. For identifiers that are local to your institution, use "local". | |
Rights | Rights | Rights statement | |
| Related_Item_Type | |||
| Related_Item_Title | |||
| Related_Item_Issuance | |||
| Access | |||
| Preferred_Citation | |||
| Record_Content_Source | |||
| Cataloging_Language_type | |||
| Cataloging_Language_authority | |||
| Cataloging_Language | |||
pid | N/A | WARNING!! Advanced users only. If you assign a pid to this object, enter it here. Typically used to ingest a compound object parent. You must be able to predict the pid that the system will generate for this field. Use the format: namespace:pid | |
parent_object | N/A | PID of the parent to which this new object belongs. Use namespace:pid format | |
| isSequenceNumber | Only used for book/newspaper/manuscript pages. Enter the order in which the pages should appear in the book/newspaper issue/manuscript. | ||
| dateIssued | Only used for newspaper issues. Dates should be in the YYYY-MM-DD or YYYY-MM. If the date is not entered in this format, the newspaper issue will not appear in the newspaper issue list as expected. | ||
parent_predicate | N/A | Choose from list: isMemberOfCollection for child objects isConstituentOf for compound objects isMemberOf for paged objects | |
Cmodel | N/A | The content model of the object, choose from the list:
|
Multi-Value Fields
In every multi-value field, values are separated by the pipe symbol “|” (that vertical line above the backslash on your keyboard). You can add as many values as you want in a multi-value field.
Some multi-value fields require you to add values and attributes in a particular order. See the “date range” field for example.
Some multi-value fields are “linked.” Multiple values in these fields must match in order. If there is a blank field in one of the columns, add two pipes next to each other.
In this example, John Smith (a personal name) is the creator, NASA (a corporate name) is the Contributor, and Jane Doe (a personal name) is the photographer.
Dropdown Lists
Some fields have drop down menus. Do not type content in these fields, please use the drop-down menu. Once you have one value in the field, you may use pull down and fill for multiple rows without using the drop-down again.
Terminology
In general conversation people incorrectly refer to an object’s “pid” as the “namespace:pid” pair separated by the colon. In reality the pid is only the second element after the colon. In this spreadsheet template, the column header “PID” actually requires the namespace:pid pair.