UWL MIG CONTENTdm Metadata Application Profile
Collection title: Sephardic Studies Collection of the University of Washington
CONTENTdm collection alias: p16786coll3

Table of contents

MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries

Combined property list

Use this order when configuring fields for the collection

KEY

For further information about compound objects and compound-object items, refer to Compound objects.

Field label Field order Text Ballads Oral histories Default Field configuration
Title 1 Record values - CO
Record values - CO-item
Record values - CO
Record values - CO-item
Record values - CO
Record values - CO-item
Record values
See details
Title (Translated) 2 n/a Record values - CO
n/a Record values
See details
Title (Non-Latin Script) 3 Record values - CO
n/a n/a Record values
See details
Title (ALA-LC Romanization) 4 Record values - CO
n/a n/a Record values
See details
Title (Harvard Romanization) 5 Record values - CO
n/a n/a Record values
See details
Interviewee 6 n/a n/a Record values - CO
Record values
See details
Interviewee Birthplace 7 n/a n/a Record values - CO
Record values
See details
Primary Performer 8 n/a Record values - CO
n/a Record values
See details
Performer 9 n/a Record values - CO
n/a Record values
See details
Performer Birthplace 10 n/a Record values - CO
n/a Record values
See details
Interviewer 11 n/a n/a Record values - CO
Record values
See details
Videographer 12 n/a n/a Record values - CO
Record values
See details
Author 13 Record values - CO
n/a n/a Record values
See details
Editor 14 Record values - CO
n/a n/a Record values
See details
Publisher 15 Record values - CO
n/a n/a Record values
See details
Publisher Location 16 Record values - CO
n/a n/a Record values
See details
Printer 17 Record values - CO
n/a n/a Record values
See details
Printer Location 18 Record values - CO
n/a n/a Record values
See details
Translator 19 Record values - CO
n/a n/a Record values
See details
Donor 20 Record values - CO
Record values - CO
Record values - CO
Record values
See details
Lender 21 Record values - CO
Record values - CO
Record values - CO
Record values
See details
Former Owner 22 Record values - CO
Record values - CO
Record values - CO
Record values
See details
Date (EDTF) 23 Record values - CO
Record values - CO
Record values - CO
Record values
See details
Date 24 Record values - CO
Record values - CO
Record values - CO
Record values
See details
Dates 25 Record values - CO
Record values - CO
Record values - CO
Record values
See details
Interviewee Biography 26 n/a n/a Record values - CO
Record values
See details
Notes 27 Record values - CO
Record values - CO
Record values - CO
Record values
See details
Subjects (LCSH) 28 Record values - CO
n/a Record values - CO
Record values
See details
Genre/Form (LCGFT) 29 Record values - CO
Record values - CO
Record values - CO
Record values
See details
Related OCLC Record 30 Record values - CO
n/a n/a Record values
See details
Object Type 31 Record values - CO
Record values - CO
Record values - CO
Record values
See details
Romancero Theme 32 n/a Record values - CO
n/a Record values
See details
Cross Reference 33 Record values - CO
Record values - CO
n/a Record values
See details
Individuals Discussed 34 n/a n/a Record values - CO
Record values
See details
Organizations Discussed 35 n/a n/a Record values - CO
Record values
See details
Geographic Coverage 36 n/a n/a Record values - CO
Record values
See details
Time Period Discussed 37 n/a n/a Record values - CO
Record values
See details
Index 38 n/a n/a Record values - CO
Record values
See details
Recording Location 39 n/a Record values - CO
Record values - CO
Record values
See details
Language 40 Record values - CO
Record values - CO
Record values - CO
Record values
See details
Digital Collection 41 Record values - CO
Record values - CO-item
Record values - CO
Record values - CO-item
Record values - CO
Record values - CO-item
Record values
See details
Sephardic Studies Accession Number (SSAN) 42 Record values - CO
Record values - CO
Record values - CO
Record values
See details
Restrictions 43 Record values - CO
Record values - CO
Record values - CO
Record values
See details
Rights URI 44 Record values - CO
Record values - CO
Record values - CO
Record values
See details
Ordering Information 45 Record values - CO
Record values - CO
Record values - CO
Record values
See details
Repository 46 Record values - CO
Record values - CO-item
Record values - CO
Record values - CO-item
Record values - CO
Record values - CO-item
Record values
See details
Repository Collection 47 Record values - CO
Record values - CO
Record values - CO
Record values
See details
Repository Collection Guide 48 Record values - CO
Record values - CO
Record values - CO
Record values
See details
Type 49 Record values - CO
Record values - CO-item
Record values - CO
Record values - CO-item
Record values - CO
Record values - CO-item
Record values
See details
Extent 50 n/a Record values - CO-item Record values - CO-item Record values
See details
Digital Format 51 Record values - CO-item Record values - CO-item Record values - CO-item Record values
See details
Original Format 52 n/a Record values - CO-item Record values - CO-item Record values
See details
Physical Description 53 Record values - CO
Record values - CO-item Record values - CO-item Record values
See details
Timecode Start 54 n/a Record values - CO-item Record values - CO-item Record values
See details
Digital Reproduction Information 55 Record values - CO
Record values - CO-item Record values - CO-item Record values
See details
Cataloging 56 Record values - CO
Record values - CO
Record values - CO
Record values
See details
Staff Notes 57 Record values - CO
Record values - CO
Record values - CO
Record values
See details
Institution 58 Record values - CO
Record values - CO
Record values - CO
Record values
See details
collectionPageCategory 59 Record values - CO
Record values - CO
Record values - CO
Record values
See details
Original File Name 60 Record values - CO-item Record values - CO-item Record values - CO-item Record values
See details
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries

Metadata creation guidance: Text > Compound objects and compound-object items

Text > Compound objects

Text > compound objects: Title
Property definition
  • A name for the resource.
Recording values
  • Find Unicode Title in Sephardic Studies Collection Master Catalog and revise according to the Aki Yerushalayim standard if needed. (Reference available here.)
  • Use a space, colon, space (" : ") to indicate the break between title and subtitle, even if no colon appears on title page.
  • Only Romanize the portion of the title that will be included in the Title field.
  • Following the title and colon, record a minimum of five words of the subtitle, followed by an ellipsis (“…”) if not recording the complete subtitle.
  • Subtitles should be lowercase, including the first word, except for proper nouns.
  • Names of languages are not capitalized in romanized Ladino (i.e.: Judeo Spanish is rendered as djudeo espanyol).
  • Do not romanize rashe tevot (Hebrew abbreviations).
  • Words of Hebrew-Aramaic origin should be romanized according to Aki Yerushalayim standards.
  • In cases where resources are printed in romanized Ladino, transcribe the title into this field exactly as it appears, even if it doesn’t conform to the Aki Yerushalayim standard.
  • All compound objects must have a title.
Examples / well-formed values
  • Pavlo i Virjinia : romanso
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Text > compound objects: Title (Non-Latin Script)
Property definition
  • A name for the resource in non-Latin script.
Recording values
  • Enter the Ladino title in Hebrew script as it appears on the title page.
  • Record title exactly as found, even with printer errors.
  • Roshe tevot (abbreviations) are considered part of the title and should be recorded.
  • Use a space, colon, space (" : ") to indicate the break between title and subtitle, even if no colon appears on title page.
  • Following the title and colon, record a minimum of five words of the subtitle, followed by an ellipsis (“…”) if not recording the complete subtitle.
  • In cases where resources are printed in Romanized Ladino, do not provide a value.
  • Optional: Record the subtitle as it appears in a matching MARC record verified by cataloging staff; record from the 245 subfield b.
  • Note: subtitles in 245 subfield b will be preceded by a colon (":"); parallel titles will be preceded by an equals sign (“=“) and should not be recorded.
  • Required for all compound objects.
Examples / well-formed values
  • פאב׳לו אי ב׳ירז׳יניאה: רומאנסו
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Text > compound objects: Title (ALA-LC Romanization)
Property definition
  • A non-Latin script title which has been Romanized according to the ALA-LC Romanization Tables.
Recording values
  • Search for Romanized title in LOC Ladino catalog.
  • If a potential match is found, confirm that it is the correct title. It may be helpful to review information included in the web display such as the publisher, printer, and publisher/printer locations.
  • Copy the Romanized title just as it appears in the LOC record, usually following the period after the author name.
  • When copying from LOC, retain this version: do not edit to match the Title value for the resource.
  • If no record exists, Romanize according to the ALA-LC Ladino romanization table.
  • When Romanizing a title, only include the portion transcribed in the Title field.
  • Note: Titles in the Library of Congress’ online Ladino catalog do not always conform to current ALA-LC romanization standards. Copy catalog those entries as-is into this field. If the title does not exist in the online catalog, romanize according to the ALA-LC standard.
  • Use space, colon, space (" : ") to indicate a break between title and subtitle, even if no colon appears on the title page.
  • Subtitles should be lowercase, including the first word, except for proper nouns.
  • Following the title and colon, record a minimum of five words of the subtitle, followed by an ellipsis (“…”) if not recording the complete subtitle.
  • Consult Hebraica Cataloging (pgs. 20-23) for instructions related to rashe tevot (Hebrew abbreviations).
  • Words of Hebrew-Aramaic origin should be romanized according to the ALA-LC Hebrew and Yiddish Romanization Table.
  • In cases where resources are printed in romanized Ladino, leave this field blank.
  • Required for all compound objects.
Examples / well-formed values
  • Pavlo y Virzhinyah : romanso
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Text > compound objects: Title (Harvard Romanization)
Property definition
  • A Ladino title in Hebrew script Romanized according to the Harvard Library standard.
Recording values
  • Search for the title in the Harvard Library HOLLIS online catalog.
  • When searching it helps to filter results by language and approximate year.
  • If a potentical match is found, copy the title just as it appears in the title field on HOLLIS.
  • If no record can be found, do not provide a value.
  • In cases where resources are printed in Romanized Ladino, do not provide a value.
  • Required for all compound objects if available.
Examples / well-formed values
  • Sefer ḥovat ha-levavot shaʻar ha-biṭaḥon en ladino
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Text > compound objects: Author
Property definition
  • The person or the corporate body responsible for the textual content.
Recording values
  • Search the Library of Congress Name Authority File via id.loc.gov for the author name (usually an individual).
  • If a potential match is found, confirm that it is the person associated with the resource: it may be helpful to review information included in the web display such as source(s) of information and occupation (for persons), and/or to follow the links provided for exact and/or closely matching concepts from other schemes.
  • Copy the name string for use just as it appears at the top of the page, above the URI(s), including dates.
  • If no record exists, Romanize the author name as it appears on the title page (or elsewhere if not on the title page) according to the ALA-LC Ladino romanization table.
  • When recording names without a match in the NAF, reuse the recorded form consistently when the same person or organization appears in the metadata for a different resource.
  • For a personal name like Alexander Ben Guiat, "Ben" is considered part of the first name and is transcribed as: "Guiat, Alexander Ben".
  • Separate multiple entries with a semicolon and space (“; “).
  • Order of values does not matter.
  • Author names usually appear on the title page after the following designations: el autor; kompuesto; por.
  • Required for all compound objects.
Examples / well-formed values
  • Saint-Pierre, Bernardin de, 1737-1814.
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Text > compound objects: Editor
Property definition
  • A person or corporate body responsible for editing the textual or other content of the resource.
Recording values
  • Search the Library of Congress Name Authority File via id.loc.gov for the editor name (usually an individual).
  • If a potential match is found, confirm that it is the person associated with the resource. It may be helpful to review information included in the web display such as source(s) of information and occupation (for persons), and/or to follow the links provided for exact and/or closely matching concepts from other schemes.
  • Copy the name string for use just as it appears at the top of the page, above the URI(s), including dates.
  • If no record exists, Romanize the editor name as it appears on the title page (or elsewhere if not on the title page) according to the ALA-LC Ladino romanization table.
  • Record personal names as "Lastname, Firstname".
  • When recording names without a match in the NAF, reuse the recorded form consistently when the same person or organization appears in the metadata for a different resource.
  • For a personal name like Alexander Ben Guiat, "Ben" is considered part of the first name and is transcribed as: "Guiat, Alexander Ben".
  • Separate multiple entries with a semicolon and space (“; “).
  • Order of values does not matter.
  • Editor names usually appear on title page after the following designations: editor.
Examples / well-formed values
  • Habib, Moiz
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Text > compound objects: Publisher
Property definition
  • A person or corporate body responsible for publishing the resource.
Recording values
  • Search the Library of Congress Name Authority File via id.loc.gov for the printer name (could be an individual or a corporate body).
  • If a potential match is found, confirm that it is the person or corporate body associated with the resource. It may be helpful to review information included in the web display such as source(s) of information and occupation (for persons), and/or to follow the links provided for exact and/or closely matching concepts from other schemes.
  • Copy the name string for use just as it appears at the top of the page, above the URI(s), including dates.
  • If no record exists, Romanize the publisher name as it appears on the title page (or elsewhere if not on the title page) according to the ALA-LC Ladino romanization table.
  • Record personal names as "Lastname, Firstname".
  • For a personal name like Alexander Ben Guiat, "Ben" is considered part of the first name and is transcribed as: "Guiat, Alexander Ben".
  • When recording names without a match in the NAF, reuse the recorded form consistently when the same person or organization appears in the metadata for a different resource.
  • Publisher names usually appear on the title page after the following designations: publikado por mano; publikado por.
  • Separate multiple entries with a semicolon and space (“; “).
  • Order of values does not matter.
Examples / well-formed values
  • Cherezli, Salomon Israel
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Text > compound objects: Publisher Location
Property definition
  • A location, usually a city, associated with the publisher of the resource.
Recording values
  • For metadata creation taking place outside the University of Washington Libraries (UWL) Cataloging and Metadata Services unit:
  • Enter a location associated with the publisher in natural language, providing sufficient information to disambiguate place names as needed.
  • As a rule, include more information rather than less.
  • For example, when providing the name of a city, also provide the state, region, and/or country name(s) as available.
  • If multiple publishers are associated with a resource, include the Publisher value to which the location corresponds in square brackets following.
  • UWL Cataloging staff will use this information to create a structured value.
  • Be sure to provide the value 'xyz' for the Cataloging property to indicate to cataloging staff that revision of the unstructured value is needed.
  • Separate multiple entries with a semicolon and space (“; “).
  • Order of values does not matter.

  • For UWL cataloging staff creating structured values:
  • Forms of the names should be derived from the Library of Congress Authority File.
  • Enter as follows:
  • Country--State or Province--City
  • Separate multiple entries with a semicolon and space (“; “).
  • Order of values does not matter.
  • If multiple publishers are associated with a resource, include the Publisher value to which the location corresponds in square brackets following.
Examples / well-formed values
  • [Natural-language values for review by cataloging staff:]
  • İzmir (Turkey)
  • Jerusalem, Israel [Cherezli, Salomon Israel]; Istanbul, Turkey [Joseph, Benjamin Ben]

  • [Structured values provided by cataloging staff:]
  • Turkey--Izmir
  • Jerusalem [Cherezli, Salomon Israel]; Turkey--Istanbul [Joseph, Benjamin Ben]
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Text > compound objects: Printer
Property definition
  • A person or corporate body responsible for printing the resource.
Recording values
  • Search the Library of Congress Name Authority File via id.loc.gov for the printer name (could be an individual or a corporate body).
  • If a potential match is found, confirm that it is the person or corporate body associated with the resource: it may be helpful to review information included in the web display such as source(s) of information and occupation (for persons), and/or to follow the links provided for exact and/or closely matching concepts from other schemes.
  • Copy the name string for use just as it appears at the top of the page, above the URI(s), including dates.
  • If no record exists, Romanize the printer name as it appears on the title page (or elsewhere if not on the title page) according to the ALA-LC Ladino romanization table.
  • Record personal names as "Lastname, Firstname".
  • For a personal name like Alexander Ben Guiat, "Ben" is considered part of the first name and is transcribed as: "Guiat, Alexander Ben".
  • Printer names usually appear on title page after the following designations: bi-defus; estamparia el; estampada; estampado en la estamparia; estampa; estamparor; emprimeria (also abbreviated to emp.); nidpas.
  • If entering multiple values for this property, separate each using a semicolon and space ("; "). Order of values does not matter.
Examples / well-formed values
  • Emprimeria Arditi
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Text > compound objects: Printer Location
Property definition
  • A location, usually a city, associated with the printer of the resource.
Recording values
  • For metadata creation taking place outside the University of Washington Libraries (UWL) Cataloging and Metadata Services unit:
  • Enter a location associated with the printer in natural language, providing sufficient information to disambiguate place names as needed.
  • As a rule, include more information rather than less.
  • For example, when providing the name of a city, also provide the state, region, and/or country name(s) as available.
  • If multiple printers are associated with a resource, include the Printer value to which the location corresponds in square brackets following.
  • UWL Cataloging staff will use this information to create a structured value.
  • Be sure to provide the value 'xyz' for the Cataloging property to indicate to cataloging staff that revision of the unstructured value is needed.
  • Separate multiple entries with a semicolon and space (“; “).
  • Order of values does not matter.

  • For UWL cataloging staff creating structured values:
  • Forms of the names should be derived from the Library of Congress Authority File.
  • Enter as follows:
  • Country--State or Province--City
  • Separate multiple entries with a semicolon and space (“; “).
  • Order of values does not matter.
  • If multiple printers are associated with a resource, include the Printer value to which the location corresponds in square brackets following.
Examples / well-formed values
  • [Natural-language values for review by cataloging staff:]
  • İzmir (Turkey)
  • Jerusalem, Israel [Cherezli, Salomon Israel]; Istanbul, Turkey [Joseph, Benjamin Ben]

  • [Structured values provided by cataloging staff:]
  • Turkey--Izmir
  • Jerusalem [Cherezli, Salomon Israel]; Turkey--Istanbul [Joseph, Benjamin Ben]
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Text > compound objects: Translator
Property definition
  • A person or corporate body responsible for translating the textual content of the resource from one language into another.
Recording values
  • When appropriate, search the Library of Congress Name Authority File via id.loc.gov for the translator name.
  • If a potential match is found, confirm that it is the person associated with the resource. It may be helpful to review information included in the web display such as source(s) of information and occupation (for persons), and/or to follow the links provided for exact and/or closely matching concepts from other schemes.
  • Copy the name string for use just as it appears at the top of the page, above the URI(s), including dates.
  • If no record exists, Romanize the translator name as it appears on the title page (or elsewhere if not on the title page) according to the ALA-LC Ladino romanization table.
  • Record personal names as "Lastname, Firstname".
  • For a personal name like Alexander Ben Guiat, "Ben" is considered part of the first name and is transcribed as: "Guiat, Alexander Ben".
  • When recording names without a match in the NAF, reuse the recorded form consistently when the same person or organization appears in the metadata for a different resource.
  • Translator names usually appear on title page after the following designations: adaptado; aranzhado; imitado; rezumido; reskrito; trezlador; trezladado; tradusio.
  • Separate multiple entries with a semicolon and space (“; “).
  • Order of values does not matter.
Examples / well-formed values
  • Guiat, Alexander Ben, 1869-1924.
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Text > compound objects: Donor
Property definition
  • A person or corporate body who donated a physical item to the University of Washington Libraries or an affiliated academic unit.
Recording values
  • Find donor name in Sephardic Studies Collection Master Catalog.
  • Contributor is considered a donor if the catalog notes that the item is property of Sephardic Studies.
  • When appropriate, search the Library of Congress Name Authority File via id.loc.gov for the donor name.
  • If a potential match is found, confirm that it is the person associated with the resource. It may be helpful to review information included in the web display such as source(s) of information and occupation (for persons), and/or to follow the links provided for exact and/or closely matching concepts from other schemes.
  • Copy the name string for use just as it appears at the top of the page, above the URI(s), including dates.
  • If no record exists, record personal names as "Lastname, Firstname".
  • When recording names without a match in the NAF, reuse the recorded form consistently when the same person or organization appears in the metadata for a different resource.
  • For a personal name like Alexander Ben Guiat, "Ben" is considered part of the first name and is transcribed as: "Guiat, Alexander Ben".
  • Separate multiple entries with a semicolon and space (“; “).
  • Order does not matter.
  • Either a donor or lender value must be provided for every compound object.
Examples / well-formed values
  • Azose, Isaac
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Text > compound objects: Lender
Property definition
  • A person or corporate body who lent a physical item to the University of Washington Libraries or an affiliated academic unit for creation of a digital surrogate.
Recording values
  • Find lender name in Sephardic Studies Collection Master Catalog.
  • Contributor is considered a lender if the catalog notes that item is still property of that individual.
  • When appropriate, search the Library of Congress Name Authority File via id.loc.gov for the lender name.
  • If a potential match is found, confirm that it is the person associated with the resource. It may be helpful to review information included in the web display such as source(s) of information and occupation (for persons), and/or to follow the links provided for exact and/or closely matching concepts from other schemes.
  • Copy the name string for use just as it appears at the top of the page, above the URI(s), including dates.
  • If no record exists, record personal names as "Lastname, Firstname".
  • When recording names without a match in the NAF, reuse the recorded form consistently when the same person or organization appears in the metadata for a different resource.
  • For a personal name like Alexander Ben Guiat, "Ben" is considered part of the first name and is transcribed as: "Guiat, Alexander Ben".
  • Separate multiple entries with a semicolon and space (“; “).
  • Order of values does not matter.
  • Either a lender or donor value must be provided for every compound object.
Examples / well-formed values
  • Maimon, Rabbi Solomon
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Text > compound objects: Former Owner
Property definition
  • A person or corporate body who previously owned a physical or digital resource.
Recording values
  • When searching for donor or lender in Sephardic Studies Collection Master Catalog, some contributions will be recorded as "Person A via Person B," or as "Person A / Person B."
  • In such a case, Person A is the former owner, and their name belongs in this field.
  • When appropriate, search the Library of Congress Name Authority File via id.loc.gov for the lender name.
  • If a potential match is found, confirm that it is the person associated with the resource. It may be helpful to review information included in the web display such as source(s) of information and occupation (for persons), and/or to follow the links provided for exact and/or closely matching concepts from other schemes.
  • Copy the name string for use just as it appears at the top of the page, above the URI(s), including dates.
  • If no record exists, record personal names as "Lastname, Firstname".
  • When recording names without a match in the NAF, reuse the recorded form consistently when the same person or organization appears in the metadata for a different resource.
  • For a personal name like Alexander Ben Guiat, "Ben" is considered part of the first name and is transcribed as: "Guiat, Alexander Ben".
  • Separate multiple entries with a semicolon and space (“; “).
  • Order of values does not matter.
Examples / well-formed values
  • Benezra, Henry
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Text > compound objects: Date (EDTF)
Property definition
  • Prominent date for the resource, such as the date of creation of the original resource.
Recording values
  • Values entered for this property are not visible in the public interface.

  • Reflects the date in the "Date" field.
  • Express all dates, including date ranges, using Library of Congress' Extended Date Time Format.
  • Creating well-formed values for resources in the Sephardic Studies Digital Collection may require first converting date values from lunar to Gregorian calendar systems.
  • The most recent version of the Library of Congress' summary of EDTF is available at https://www.loc.gov/standards/datetime/.
  • Six formats are recommended for values in Date, each corresponding to a specific EDTF format:
  • If the value of Date is YYYY, enter YYYY.
  • If the value of Date is YYYY?, enter YYYY?
  • If the value of Date is [month] DD, YYYY, enter YYYY-MM-DD.
  • If the value of Date is [month], YYYY, enter YYYY-MM.
  • If the value of Date is between YYYY and YYYY, enter YYYY/YYYY.
  • If the value of Date is between YYYY and YYYY?, enter YYYY?/YYYY?
  • If the value of Date is not any of the above, consult the EDTF spedification to determine the appropriate notation.
  • Date-Edtf value should agree with dates values entered in Date and Dates fields.
Examples / well-formed values
  • If the Date field = "1940" then Date EDTF = "1940"
  • If the Date field = "1910?" then Date EDTF = "1910?"
  • If Date field = "May 9, 2001" then Date EDTF = "2001-05-09"
  • If Date field = "January 2008" then Date EDTF = "2008-01"
  • If Date field = "between 1930 and 1939" then Date EDTF = "1930/1939"
  • If Date field = "between 1855 and 1999?" then Date EDTF = "1855?/1999?"
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Text > compound objects: Date
Property definition
  • Prominent date for the resource, such as the date of creation of the original resource.
Recording values
  • Enter the date (generally a year only) as reflected on the title page.
  • If only the lunar or Gregorian year is recorded, only enter that year. Do not convert between calendar systems.
  • If both Gregorian and lunar years are recorded, only enter the Gregorian year.
  • Do not enter chronograms.
  • If no date present on item, generate an estimate based on similar items in other collections: LOC Ladino catalog, Harvard University Library, and the National Library of Israel are viable options.
  • Required for all compound objects.
Examples / well-formed values
  • 5651 [example of lunar year]
  • 1923 [example of Gregorian year]
  • ca. 1900
  • not before 1900
  • after 1900 [example of estimate]
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Text > compound objects: Dates
Property definition
  • Prominent years for the resource, such as the date(s) of creation of the original resource; the expected value is a list of each and every pertinent year.
Recording values
  • Values entered for this property are not visible in the public interface.

  • Reflects the date in the "Date" field pertinent to the overall object.
  • Creating well-formed values for resources in the Sephardic Studies Digital Collection may require first converting date values from lunar to Gregorian calendar systems.
  • Enter the year or years only.
  • When the value of Date is YYYY, enter YYYY.
  • When the value of Date is YYYY?, enter an eleven year date range, five years on either side of the uncertain date.
  • When the value of Date is [month] DD, YYYY, enter the year only in the following format: YYYY.
  • When the value of Date is [month], YYYY, enter the year only in the following format: YYYY.
  • When the value of Date is between YYYY and YYYY, enter all years in the date range in the following format: YYYY YYYY YYYY etc.
  • When the value of Date is between YYYY and YYYY?, enter all years in the date range plus five years before the earliest date and five years after the latest date, in the following format: YYYY YYYY YYYY etc.
  • This field is indexed and enables date searching in CONTENTdm.
  • The Dates value should agree with date values entered in Date-Edtf and Date fields.
Examples / well-formed values
  • 1939
  • 1939?
  • 1939 1940 1941 1942 1943 1944 1945
  • 1934 1935 1936 1937 1938 1939 1940 1941 1942 1943 1944 1945 1946 1947 1948 1949 1950
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Text > compound objects: Notes
Property definition
  • An account of the resource.
Recording values
  • Enter any information of importance that is not represented elsewhere.
  • Prioritize information that might affect a user's understanding or use of the resource, such as missing pages or alternative titles not captured in the various title properties.
  • May include notes about property values taken from information provided by previous catalogers when these values cannot be found in the resource.
  • May include information about property values taken from alternative locations in the resource (other than title page, title page verso, etc.).
  • Start each distinct note entry on a new line.
  • When entering values in a spreadsheet, note that depending on the spreadsheet-editing application, CTRL + ENTER, ALT + ENTER, or another key combination can be used to enter a new line within a cell.
Examples / well-formed values
  • Title value taken from cover, title page missing from digitized volume.
  • Editor value taken from introduction.
  • Publisher location from previous cataloger.
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Text > compound objects: Subjects (LCSH)
Property definition
  • The topic of the resource.
Recording values
  • University of Washington Libraries (UWL) cataloging staff will provide a value or values for this property.
  • For metadata creation taking place outside the UWL Cataloging and Metadata Services unit:
  • Do not provide a value for this property.
  • Be sure to provide the value 'xyz' for the Cataloging property to indicate to cataloging staff that a value is needed.
  • For textual resources, be sure to record a staffNotes value which provides the needed information for UWL cataloging staff to perform subject analysis.
  • For details about the information needed by cataloging staff, contact the collection manager(s) or metadata liaison(s).
Examples / well-formed values
  • High holidays--Liturgy--Texts
  • Sacred songs
  • Bible. Ruth--Commentaries
  • Ladino language--Grammar--Textbooks
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Text > compound objects: Genre/Form (LCGFT)
Property definition
  • The genre or form of the resource, expressed using values selected from Library of Congress Genre/Form Terms.
Recording values
  • University of Washington Libraries (UWL) cataloging staff will provide a value or values for this property.
  • For metadata creation taking place outside the UWL Cataloging and Metadata Services unit:
  • Do not provide a value for this property.
  • Be sure to provide the value 'xyz' for the Cataloging property to indicate to cataloging staff that a value is needed.
  • For textual resources, be sure to use the Staff Notes property to provide an informal description which will provide cataloging staff with the information needed to provide genre and form terms.
  • For details about the information needed by cataloging staff, contact the collection manager(s) or metadata liaison(s).
Examples / well-formed values
  • Sacred works
  • Textbooks
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Text > compound objects: Related OCLC Record
Property definition
  • Number for an OCLC record related to the digital resource, for example, a record for a physical item from which the digital surrogate was created.
Recording values
  • University of Washington Libraries (UWL) cataloging staff will provide a value or values for this property if applicable.
  • For metadata creation taking place outside the University of Washington Libraries (UWL) Cataloging and Metadata Services unit:
  • Do not provide a value for this property.
  • Be sure to provide the value 'xyz' for the Cataloging property to indicate to cataloging staff that a value is needed if applicable.
  • When the resource does not use English, be sure to use the Staff Notes property to provide information which will allow cataloging staff to identify any related records.
  • For details about the information needed by cataloging staff, contact the collection manager(s) or metadata liaison(s).
  • For UWL cataloging staff:
  • Separate multiple values with a semicolon.
Examples / well-formed values
  • [Values provided by cataloging staff:]
  • 37917418
  • 27382728
  • 37917418; 27382728
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Text > compound objects: Object Type
Property definition
  • The nature or genre of the resource.
Recording values
  • Enter one of the following values:
  • book
  • newspaper
Examples / well-formed values
  • book
  • newspaper
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Text > compound objects: Cross Reference
Property definition
  • Information about other sources in which a description of or information about the resource may be found.
Recording values
  • Optional: Provide information about one or more sources which provide additional information about the resource.
Examples / well-formed values
  • RJEO 5a; AMP F7; MP 45; FLSJ IX, 45
  • RJEO - Benmayor, R. Romances judeo-españoles de Oriente: Nueva recolección. Musical transcriptions by Judith H. Mauleón. Madrid: Gredos, 1979.
  • AMP - Armistead, Samuel G., with the collaboration of Selma Margaretten, Paloma Montero, and Ana Valenciano and with musical transcriptions edited by Israel J. Katz. El romancero judeo-español en el Archivo Menéndez Pidal (Catálogo-índice de romances y canciones) (Catálogo-índice de romances y canciones ) 3 vols. Madrid: Catedra-Seminario Menéndez Pidal, 1977, 387; 393; 358 pp. http://bit.ly/1NMq6Pt
  • MP - Menéndez Pidal, Ramón. “Catálogo del romancero judío-español,"" Cultura Española, 4 (1906), 1045–1077; 5 (1907), 161–199. http://bit.ly/1NT9xPL
  • FLSJ - Armistead, Samuel G. and Joseph H. Silverman. Folk Literature of the Sephardic Jews. Series in eight volumes. Catalog online at: http://www.sephardifolklit.org/
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Text > compound objects: Language
Property definition
  • A language of the resource.
Recording values
  • Enter language names, fully spelled out, as they appear in the ISO 639 Code Tables "Language Name(s)" column. Note that Ladino is listed as such, and not as Judeo-Spanish or Judezmo.
  • Do not enter languages that only appear on the title page or final pages (i.e. in advertisements).
  • For Aramaic-language resources, simply enter "Aramaic".
  • Separate multiple values using a semicolon and space (“; “).
  • Order of values does not matter.
  • Required for all compound objects where applicable.
Examples / well-formed values
  • Ladino
  • Hebrew
  • Ladino; Hebrew
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Text > compound objects: Digital Collection
Property definition
  • Name of the digital collection.
Recording values
  • Enter the following value:
  • Sephardic Studies Digital Collection at the University of Washington
  • Required for all compound objects.
Examples / well-formed values
  • Sephardic Studies Digital Collection at the University of Washington
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Text > compound objects: Sephardic Studies Accession Number (SSAN)
Property definition
  • A number assigned to each resource in the Sephardic Studies Digital Collection Master Catalog; each resource's number is unique in the Catalog.
Recording values
  • Find the item in Sephardic Studies Collection Master Catalog in column AX (File Name) and enter its corresponding number here.
  • Required for all compound objects.
Examples / well-formed values
  • ST00495
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Text > compound objects: Restrictions
Property definition
  • Any restrictions on the use of a resource.
Recording values
  • Required for all compound objects.
  • Enter the following value:
  • To inquire about permissions, contact sephstud@uw.edu. Please cite the Sephardic Studies Accession Number.
Examples / well-formed values
  • To inquire about permissions, contact sephstud@uw.edu. Please cite the Sephardic Studies Accession Number.
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Text > compound objects: Rights URI
Property definition
  • URI that dereferences to a rights statement.
Recording values
Examples / well-formed values
  • http://rightsstatements.org/vocab/CNE/1.0/
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Text > compound objects: Ordering Information
Property definition
  • Instructions for ordering.
Recording values
  • Enter the following value:
  • Reproductions are not available for order.
Examples / well-formed values
  • Reproductions are not available for order.
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Text > compound objects: Repository
Property definition
  • The institution holding the resource.
Recording values
  • This value will be entered by University of Washington Libraries Special Collections Staff following transfer of collection resources.
  • Value will be as follows:
  • University of Washington Libraries. Special Collections
Examples / well-formed values
  • University of Washington Libraries. Special Collections
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Text > compound objects: Repository Collection
Property definition
  • Collection to which the original resource is a part.
Recording values
  • Where applicable, this value will be entered by University of Washington Libraries Special Collections Staff following transfer of collection resources.
  • Where a finding aid for an archival collection including the resource exists, the value will be constructed using the collection name and accession number given there.
Examples / well-formed values
  • 🚧 🚧 🚧
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Text > compound objects: Repository Collection Guide
Property definition
  • URI to an EAD finding aid.
Recording values
  • Where applicable, this value will be entered by University of Washington Libraries Special Collections Staff following transfer of collection resources.
  • Where a finding aid for an archival collection including the resource exists, the value will be the Ark URL for this finding aid in ArchivesWest.
Examples / well-formed values
  • 🚧 🚧 🚧
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Text > compound objects: Type
Property definition
  • Describes the nature or genre of the content of the resource.
Recording values
  • Values entered for this property are not visible in the public interface.

  • Values for this property must come from the DCMI Type Vocabulary.
  • For textual-resource compound objects, provide the following value:
  • Text
Examples / well-formed values
  • Text
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Text > compound objects: Physical Description
Property definition
  • Description of the physical attributes of the original medium in which data, sound, images, etc., are stored; the carrier; may include an extent statement.
Recording values
  • For textual resources, Physical Description is recorded at the compound-object level.
  • If information is available, provide a description of the physical resource from which the digital surrogate (compound object) was created.
  • If information is available, include both the number of pages and a measurement for the volume.

  • Recording number of pages:
  • For pages numbered with Roman or Arabic numerals, record the number of the final page in either Roman or Arabic numerals followed by “pages”.
  • When a volume includes both Roman- and Arabic-numbered pages, provide the roman numeral followed by a comma and space (“, “), the Arabic numeral followed by a space, and “pages”.
  • If pages are not numbered, record a number of pages in Arabic numerals followed by a space (“ “) and “pages”.
  • Optionally, record an unnumbered page count before or after an Arabic- and/or Roman-numbered page count, separating with a comma and space (“, “).

  • Recording physical dimensions:
  • Add this information following page information, separating with a comma and space (“, “).
  • Record the height of the volume in centimeters.
  • Record the height using Arabic numerals.
  • Use a space and “cm” (no following punctuation) after the numeral(s) (“ cm”).
Examples / well-formed values
  • xi pages, 25 cm
  • 25 pages, 25 cm
  • xi, 25 pages, 25 cm
  • 15 unnumbered pages, 30 cm
  • xi, 25 pages, 15 unnumbered pages, 30 cm
  • 2 unnumbered pages, 300 pages, 35 cm
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Text > compound objects: Digital Reproduction Information
Property definition
  • Description of the digital conversion process, date scanned, etc.
Recording values
  • If available, provide details regarding the digitization of the text.
  • For texts, digital reproduction details are assumed to be the same or similar for all compound-object items (pages), so information should be recorded at the compound-object level.
Examples / well-formed values
  • Scanned from original text or image at 400 dpi, saved in TIFF format, resized and enhanced using Adobe Photoshop, and imported as JPEG2000 using Contentdm software's JPEG2000 Extension. 2006.
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Text > compound objects: Cataloging
Property definition
  • Messages for local catalogers.
Recording values
  • Values entered for this property are not visible in the public interface.

  • For metadata creation taking place outside the UWL Cataloging and Metadata Services unit:
  • Enter "xyz" to request the creation and/or review of values for one or more of the following fields by UWL cataloging staff:

  • Subjects (LCSH)
  • Genre/Form (LCGFT)
  • Related OCLC Record
  • Geographic Coverage
  • Interviewee Birthplace
  • Performer Birthplace
  • Recording Location
  • Printer Location
  • Publisher Location
Examples / well-formed values
  • xyz
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Text > compound objects: Staff Notes
Property definition
  • Notes for staff only, notes of an administrative nature.
Recording values
  • Values entered for this property are not visible in the public interface.

  • Staff Notes values are hidden in the public CONTENTdm interface.
  • These values will be used by University of Washington Libraries (UWL) cataloging staff to assign controlled values for the following fields for textual resources.

  • For books, catalogers may supply values for:
  • Subjects (LCSH)
  • Genre/Form (LCGFT)
  • Related OCLC Record
  • Printer Location
  • Publisher Location

  • For ephemera, catalogers may supply values for:
  • Subjects (LCSH)
  • Genre/Form (LCGFT)

  • To facilitate cataloging of books:
  • Briefly summarize the genre, subject, and intended use.
  • Descriptions of novels should briefly summarize the arc of the story.
  • For religious texts, such as prayer books and bibles, note for which Jewish holiday and/or ritual they are used.
  • Note if the work is a translation, and the author and language of the original text.

  • To facilitate cataloging of ephemera:
  • Record any relevant information characterizing the resource which isn’t included in values for any other metadata field.
  • Translate non-English text or terminology to aid cataloging staff in metadata creation.

  • Required for all textual-resource compound objects which will require subject or genre/form analysis from UWL cataloging staff.
Examples / well-formed values
  • For books:
  • A Ladino translation of the French novel "Paul et Virginie" by Bernardin de Saint-Pierre (1737-1814). This short love story, set in the 18th century on a French island, tells of a man a woman separated by distance and circumstance, never to be united before their untimely deaths.
  • This is a parallel Hebrew-Ladino translation of the Book of Ruth with corresponding commentary in Ladino. The Book of Ruth is part of the Old Testament found in the section known as Ketuvim (Writings). It is traditionally read on the Jewish holiday of Shavuot (Feast of Weeks).

  • For ephemera:
  • This is a wedding certificate decorated with a floral pattern behind a picture of a menorah (Jewish candelabra) and an open book with the words “Siman Tov u-Mazal Tov,” a Hebrew phrase often used to congratulate a couple on their wedding.
  • The Ladino text in this cigarette advertisement reads “A high-quality product.”
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Text > compound objects: Institution
Property definition
  • Information for the purpose of facilitating browsing in the University of Washington Libraries Digital Collections online interface.
Recording values
  • Values entered for this property are not visible in the public interface.

  • Use the following value:
  • special collections
Examples / well-formed values
  • special collections
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Text > compound objects: collectionPageCategory
Property definition
  • A category for the resource, for use in presenting resources by category on a collection landing page.
Recording values
  • Values entered for this property are not visible in the public interface.

  • Provide the category within which the resource should be presented on the collection landing page.
Examples / well-formed values
  • Novelesque Ballad - Various subjects
  • Institutional Publications
  • Ephemera
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries

Text > Compound-object items

Text > compound-object items: Title
Property definition
  • A name for the resource.
Recording values
  • Every page must have a title.
  • Provide the page number as the item title.
  • Where there is no pagination, a description of the page contents may be used as an item title.
  • Use sentence-case capitalization.
  • Do not spell out page numbers, use numerals.
  • All compound-object items must have a title.

  • In some cases, Hebrew letters may be used to mark pagination on alternating pages.
  • In these cases, provide a page number in Arabic numerals even though it is not marked on the page.
  • For pages where pagination is indicated using a Hebrew letter, provide this in parentheses following the Arabic numeral(s).
  • For pages without any pagination in this case (usually the pages facing those marked with a Hebrew letter), enter "(unnumbered)" following the Arabic numeral(s).
Examples / well-formed values
  • Cover
  • Inside cover
  • Title page
  • Publisher's introduction
  • Page 1
  • Page 2
  • Blank page

  • Page 2 (ב)
  • Page 3 (unnumbered)
  • Page 4 (ג)
  • Page 5 (unnumbered)
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Text > compound-object items: Digital Collection
Property definition
  • Name of the digital collection.
Recording values
  • Enter the following value:
  • Sephardic Studies Digital Collection at the University of Washington
  • Required for all compound-object items.
Examples / well-formed values
  • Sephardic Studies Digital Collection at the University of Washington
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Text > compound-object items: Repository
Property definition
  • The institution holding the resource.
Recording values
  • This value will be entered by University of Washington Libraries Special Collections Staff following transfer of collection resources.
  • Value will be as follows:
  • University of Washington Libraries. Special Collections
Examples / well-formed values
  • University of Washington Libraries. Special Collections
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Text > compound-object items: Type
Property definition
  • Describes the nature or genre of the content of the resource.
Recording values
  • Values entered for this property are not visible in the public interface.

  • Values for this property must come from the DCMI Type Vocabulary.
  • For image-file compound-object items (digitized pages), provide one or both of the following values depending on content:
  • Text
  • StillImage

  • Separate multiple entries with a semicolon and space (“; “).
  • Order of values does not matter.
Examples / well-formed values
  • Text
  • StillImage
  • StillImage; Text
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Text > compound-object items: Digital Format
Property definition
  • File format of a digital resource.
Recording values
  • Enter the file format of the file representing the compound-object item--that is, the access item.
  • This should be the format of the file given as a value for the digitalFileName property.
  • Use media types listed at http://www.iana.org/assignments/media-types/index.html.
  • For audio WAVE files, enter "audio/wav".
Examples / well-formed values
  • audio/mpeg
  • image/jpeg
  • application/pdf
  • text/plain
  • video/mp4
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Text > compound-object items: Original File Name
Property definition
  • The complete name including file extension of a digital file representing a resource to be described by one or more property/value pairs in CONTENTdm.
Recording values
  • Values entered for this property are not visible in the public interface.

  • When entering values in a metadata spreadsheet, each row will include values describing a resource--either a compound object, compound-object item, or standalone object.
  • Each row describing either a compound-object item or a standalone object must include a filename provided as a value for this property.
  • Enter the filename of the image file for the page described in the spreadsheet row.
Examples / well-formed values
  • ST-001.jpg
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries

Metadata creation guidance: Ballads > Compound objects and compound-object items

Ballads > Compound objects

Ballads > compound objects: Title
Property definition
  • A name for the resource.
Recording values
  • Construct as follows:
  • Audio: [song title]
  • (Do not enter square brackets around the song title.)
  • Romanize song titles according to the Aki Yerushalayim standard. (Reference available here.)
  • All compound objects must have a title.
Examples / well-formed values
  • Audio: Alavar kero al Dyo
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Ballads > compound objects: Title (Translated)
Property definition
  • A name for the resource created by translating an existing title.
Recording values
  • Translate the song title.
  • Use title-case capitalization.
  • Do not use a period at the end of the translated title.
Examples / well-formed values
  • The Abduction of Helen of Troy
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Ballads > compound objects: Primary Performer
Property definition
  • A primary performer who is seen, heard, or otherwise prominently featured in the resource.
Recording values
  • Provide the name of the primary singer featured in the recording.
  • When appropriate, search the Library of Congress Name Authority File via id.loc.gov for the name of the singer.
  • If a potential match is found, confirm that it is the person associated with the resource. It may be helpful to review information included in the web display such as source(s) of information and occupation (for persons), and/or to follow the links provided for exact and/or closely matching concepts from other schemes.
  • Copy the name string for use just as it appears at the top of the page, above the URI(s), including dates.
  • If no record exists, record personal names as "Lastname, Firstname".
  • When recording names without a match in the NAF, reuse the recorded form consistently when the same person or organization appears in the metadata for a different resource.
  • For a personal name like Alexander Ben Guiat, "Ben" is considered part of the first name and is transcribed as: "Guiat, Alexander Ben".
  • Separate multiple entries with a semicolon and space (“; “).
  • Order of values does not matter.
Examples / well-formed values
  • Azose, Jack
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Ballads > compound objects: Performer
Property definition
  • A performer who is seen, heard, or otherwise featured in the resource.
Recording values
  • Provide the names of other people who may be heard performing in the recording.
  • This can include singers or other performers.
  • When appropriate, search the Library of Congress Name Authority File via id.loc.gov for the name of a performer who may be heard in the song recording.
  • If a potential match is found, confirm that it is the person associated with the resource. It may be helpful to review information included in the web display such as source(s) of information and occupation (for persons), and/or to follow the links provided for exact and/or closely matching concepts from other schemes.
  • Copy the name string for use just as it appears at the top of the page, above the URI(s), including dates.
  • If no record exists, record personal names as "Lastname, Firstname".
  • When recording names without a match in the NAF, reuse the recorded form consistently when the same person or organization appears in the metadata for a different resource.
  • For a personal name like Alexander Ben Guiat, "Ben" is considered part of the first name and is transcribed as: "Guiat, Alexander Ben".
  • Separate multiple entries with a semicolon and space (“; “).
  • Order of values does not matter.
Examples / well-formed values
  • Azose, Louise
  • Azose, Jack; Azose, Louise
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Ballads > compound objects: Performer Birthplace
Property definition
  • The place of birth of a primary performer featured in a resource.
Recording values
  • For metadata creation taking place outside the University of Washington Libraries (UWL) Cataloging and Metadata Services unit:
  • Enter a performer birthplace in natural language, providing sufficient information to disambiguate place names as needed.
  • As a rule, include more information rather than less.
  • For example, when providing the name of a city, also provide the state, region, and/or country name(s) as available.
  • UWL Cataloging staff will use this information to create a structured value.
  • Be sure to provide the value 'xyz' for the Cataloging property to indicate to cataloging staff that revision of the unstructured value is needed.
  • Separate multiple entries with a semicolon and space (“; “).
  • Order of values does not matter.
  • If multiple performers are associated with a resource, include the Performer or Primary Performer value to which the birthplace corresponds in square brackets following.

  • For UWL cataloging staff creating structured values:
  • Forms of the names should be derived from the Library of Congress Authority File.
  • Enter as follows:
  • Country--State or Province--City
  • Separate multiple entries with a semicolon and space (“; “).
  • Order of values does not matter.
  • If multiple performers are associated with a resource, include the Performer or Primary Performer value to which the birthplace corresponds in square brackets following.
Examples / well-formed values
  • [Natural-language values for review by cataloging staff:]
  • Ortaköy (Istanbul, Turkey)

  • [Structured values provided by cataloging staff:]
  • Turkey--Istanbul
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Ballads > compound objects: Donor
Property definition
  • A person or corporate body who donated a physical item to the University of Washington Libraries or an affiliated academic unit.
Recording values
  • Find donor name in Sephardic Studies Collection Master Catalog; the item may be recorded on the Ladino Audio Archive tab.
  • Check both the main collection tab and Ladino Audio Archive tab for the correct file.
  • Contributor is considered a donor if the catalog notes that the item is property of Sephardic Studies.
  • When appropriate, search the Library of Congress Name Authority File via id.loc.gov for the donor name.
  • If a potential match is found, confirm that it is the person associated with the resource. It may be helpful to review information included in the web display such as source(s) of information and occupation (for persons), and/or to follow the links provided for exact and/or closely matching concepts from other schemes.
  • Copy the name string for use just as it appears at the top of the page, above the URI(s), including dates.
  • If no record exists, record personal names as "Lastname, Firstname".
  • When recording names without a match in the NAF, reuse the recorded form consistently when the same person or organization appears in the metadata for a different resource.
  • For a personal name like Alexander Ben Guiat, "Ben" is considered part of the first name and is transcribed as: "Guiat, Alexander Ben".
  • Separate multiple entries with a semicolon and space (“; “).
  • Order does not matter.
  • Either a donor or lender value must be provided for every compound object.
Examples / well-formed values
  • Azose, Isaac
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Ballads > compound objects: Lender
Property definition
  • A person or corporate body who lent a physical item to the University of Washington Libraries or an affiliated academic unit for creation of a digital surrogate.
Recording values
  • Find lender name in Sephardic Studies Collection Master Catalog; the item may be recorded on the Ladino Audio Archive tab.
  • Check both the main collection tab and Ladino Audio Archive tab for the correct file.
  • Contributor is considered a lender if the catalog notes that item is still property of that individual.
  • When appropriate, search the Library of Congress Name Authority File via id.loc.gov for the lender name.
  • If a potential match is found, confirm that it is the person associated with the resource. It may be helpful to review information included in the web display such as source(s) of information and occupation (for persons), and/or to follow the links provided for exact and/or closely matching concepts from other schemes.
  • Copy the name string for use just as it appears at the top of the page, above the URI(s), including dates.
  • If no record exists, record personal names as "Lastname, Firstname".
  • When recording names without a match in the NAF, reuse the recorded form consistently when the same person or organization appears in the metadata for a different resource.
  • For a personal name like Alexander Ben Guiat, "Ben" is considered part of the first name and is transcribed as: "Guiat, Alexander Ben".
  • Separate multiple entries with a semicolon and space (“; “).
  • Order of values does not matter.
  • Either a lender or donor value must be provided for every compound object.
Examples / well-formed values
  • Maimon, Rabbi Solomon
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Ballads > compound objects: Former Owner
Property definition
  • A person or corporate body who previously owned a physical or digital resource.
Recording values
  • When searching for donor or lender in Sephardic Studies Collection Master Catalog, some contributions will be recorded as "Person A via Person B," or as "Person A / Person B."
  • In such a case, Person A is the former owner, and their name belongs in this field.
  • When appropriate, search the Library of Congress Name Authority File via id.loc.gov for the lender name.
  • If a potential match is found, confirm that it is the person associated with the resource. It may be helpful to review information included in the web display such as source(s) of information and occupation (for persons), and/or to follow the links provided for exact and/or closely matching concepts from other schemes.
  • Copy the name string for use just as it appears at the top of the page, above the URI(s), including dates.
  • If no record exists, record personal names as "Lastname, Firstname".
  • When recording names without a match in the NAF, reuse the recorded form consistently when the same person or organization appears in the metadata for a different resource.
  • For a personal name like Alexander Ben Guiat, "Ben" is considered part of the first name and is transcribed as: "Guiat, Alexander Ben".
  • Separate multiple entries with a semicolon and space (“; “).
  • Order of values does not matter.
Examples / well-formed values
  • Benezra, Henry
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Ballads > compound objects: Date (EDTF)
Property definition
  • Prominent date for the resource, such as the date of creation of the original resource.
Recording values
  • Values entered for this property are not visible in the public interface.

  • Reflects the date in the "Date" field.
  • Express all dates, including date ranges, using Library of Congress' Extended Date Time Format.
  • Creating well-formed values for resources in the Sephardic Studies Digital Collection may require first converting date values from lunar to Gregorian calendar systems.
  • The most recent version of the Library of Congress' summary of EDTF is available at https://www.loc.gov/standards/datetime/.
  • Six formats are recommended for values in Date, each corresponding to a specific EDTF format:
  • If the value of Date is YYYY, enter YYYY.
  • If the value of Date is YYYY?, enter YYYY?
  • If the value of Date is [month] DD, YYYY, enter YYYY-MM-DD.
  • If the value of Date is [month], YYYY, enter YYYY-MM.
  • If the value of Date is between YYYY and YYYY, enter YYYY/YYYY.
  • If the value of Date is between YYYY and YYYY?, enter YYYY?/YYYY?
  • If the value of Date is not any of the above, consult the EDTF spedification to determine the appropriate notation.
  • Date-Edtf value should agree with dates values entered in Date and Dates fields.
Examples / well-formed values
  • If the Date field = "1940" then Date EDTF = "1940"
  • If the Date field = "1910?" then Date EDTF = "1910?"
  • If Date field = "May 9, 2001" then Date EDTF = "2001-05-09"
  • If Date field = "January 2008" then Date EDTF = "2008-01"
  • If Date field = "between 1930 and 1939" then Date EDTF = "1930/1939"
  • If Date field = "between 1855 and 1999?" then Date EDTF = "1855?/1999?"
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Ballads > compound objects: Date
Property definition
  • Prominent date for the resource, such as the date of creation of the original resource.
Recording values
  • Enter the date on which the recording was made.
  • Use a YYYY-MM-DD format if month and day information is available.
  • Use a YYYY-MM or YYYY format if month and/or day information is not available.
Examples / well-formed values
  • 2020-03-15
  • 2019-04
  • 2018
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Ballads > compound objects: Dates
Property definition
  • Prominent years for the resource, such as the date(s) of creation of the original resource; the expected value is a list of each and every pertinent year.
Recording values
  • Values entered for this property are not visible in the public interface.

  • Reflects the date in the "Date" field pertinent to the overall object.
  • Creating well-formed values for resources in the Sephardic Studies Digital Collection may require first converting date values from lunar to Gregorian calendar systems.
  • Enter the year or years only.
  • When the value of Date is YYYY, enter YYYY.
  • When the value of Date is YYYY?, enter an eleven year date range, five years on either side of the uncertain date.
  • When the value of Date is [month] DD, YYYY, enter the year only in the following format: YYYY.
  • When the value of Date is [month], YYYY, enter the year only in the following format: YYYY.
  • When the value of Date is between YYYY and YYYY, enter all years in the date range in the following format: YYYY YYYY YYYY etc.
  • When the value of Date is between YYYY and YYYY?, enter all years in the date range plus five years before the earliest date and five years after the latest date, in the following format: YYYY YYYY YYYY etc.
  • This field is indexed and enables date searching in CONTENTdm.
  • The Dates value should agree with date values entered in Date-Edtf and Date fields.
Examples / well-formed values
  • 1939
  • 1939?
  • 1939 1940 1941 1942 1943 1944 1945
  • 1934 1935 1936 1937 1938 1939 1940 1941 1942 1943 1944 1945 1946 1947 1948 1949 1950
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Ballads > compound objects: Notes
Property definition
  • An account of the resource.
Recording values
  • Enter any information of importance that is not represented elsewhere.
  • When reusing existing metadata, only the place name will be included the value for Recording Location.
  • Any additional information present in existing metadata which will not be used in the Recording Location value may be included here.
  • For example, adapt existing value “Seattle, in her home” as:
  • Recording Location: Seattle, Washington, USA
  • Notes: Recorded in the home of [name].
  • Start each distinct note entry on a new line.
  • When entering values in a spreadsheet, note that depending on the spreadsheet-editing application, CTRL + ENTER, ALT + ENTER, or another key combination can be used to enter a new line within a cell.
Examples / well-formed values
  • Song from father's pizmonim manuscript.
  • Uniquely Sephardic in origin. Given its subject matter, this ballad has been transmitted both orally and in written form, in Pesach hagaddahs. The only extant versions are from the Eastern tradition and one version from Crypto Portuguese Jews. Thus, an earlier version must have existed among Peninsular Jews. There is no evidence of its existence among non-Jews.
  • Recorded in the home of Jack Azose.
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Ballads > compound objects: Genre/Form (LCGFT)
Property definition
  • The genre or form of the resource, expressed using values selected from Library of Congress Genre/Form Terms.
Recording values
  • University of Washington Libraries (UWL) cataloging staff will provide a value or values for this property.
  • For metadata creation taking place outside the UWL Cataloging and Metadata Services unit:
  • Do not provide a value for this property.
  • Be sure to provide the value 'xyz' for the Cataloging property to indicate to cataloging staff that a value is needed.
Examples / well-formed values
  • Ballads
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Ballads > compound objects: Object Type
Property definition
  • The nature or genre of the resource.
Recording values
  • Enter the following value:
  • ballads
Examples / well-formed values
  • ballads
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Ballads > compound objects: Romancero Theme
Property definition
  • A translation of the song's thematic classification, printed in Spanish on pages 219-221 of "Romances judeo-españoles de Oriente: nueva recolección."
Recording values
Examples / well-formed values
  • Capture and seduction by taking aboard ship
  • Girl enticed into boat and abducted; Capture by luring; Capture and seduction by taking aboard ship; Apple tree as symbol of seduction
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Ballads > compound objects: Cross Reference
Property definition
  • Information about other sources in which a description of or information about the resource may be found.
Recording values
  • Provide any references to other Sephardic ballad collections given for this ballad as it is described in "Romances judeo-españoles de Oriente : nueva recolección".
  • Locate the song in "Romances judeo-españoles de Oriente: nueva recolección" by Rina Benmayor and Judith H. Mauleón.

  • Copy the list of cross references--including the resource (or an abbreviation denoting a resource) and numeric page number--which appears after the word "bibliographia."
  • Include full titles for each abbreviation.
  • Separate multiple values with a semicolon and space ("; ").

  • Resource abbreviations are as follows:
  • AMP - Armistead, Samuel G., with the collaboration of Selma Margaretten, Paloma Montero, and Ana Valenciano and with musical transcriptions edited by Israel J. Katz. El romancero judeo-español en el Archivo Menéndez Pidal (Catálogo-índice de romances y canciones) (Catálogo-índice de romances y canciones ) 3 vols. Madrid: Catedra-Seminario Menéndez Pidal, 1977, 387; 393; 358 pp. bit.ly/1NMq6Pt
  • Attias - Attias, Moshe, 1972. Romancero sefardí: romanzas y cantes populares en judeo-espanol. 2nd ed. Jerusalem: Ben-Zewi Institute, 1961, 350 pp.
  • FLSJ - Armistead, Samuel G. and Joseph H. Silverman. Folk Literature of the Sephardic Jews. Series in eight volumes. Catalog online at: http://www.sephardifolklit.org/
  • Larrea - Larrea, Palacín, Arcadio de. Romances de Tetuán, 2 vols. Madrid: C.S.I.C., 1952, 351; 377 pp.
  • MP - Menéndez Pidal, Ramón. “Catálogo del romancero judío-español,"" Cultura Española, 4 (1906), 1045–1077; 5 (1907), 161–199. bit.ly/1NT9xPL
  • RJEO - Benmayor, R. Romances judeo-españoles de Oriente: Nueva recolección. Musical transcriptions by Judith H. Mauleón. Madrid: Gredos, 1979.
Examples / well-formed values
  • RJEO 5a; AMP F7; MP 45; FLSJ IX, 45
  • RJEO - Benmayor, R. Romances judeo-españoles de Oriente: Nueva recolección. Musical transcriptions by Judith H. Mauleón. Madrid: Gredos, 1979.
  • AMP - Armistead, Samuel G., with the collaboration of Selma Margaretten, Paloma Montero, and Ana Valenciano and with musical transcriptions edited by Israel J. Katz. El romancero judeo-español en el Archivo Menéndez Pidal (Catálogo-índice de romances y canciones) (Catálogo-índice de romances y canciones ) 3 vols. Madrid: Catedra-Seminario Menéndez Pidal, 1977, 387; 393; 358 pp. http://bit.ly/1NMq6Pt
  • MP - Menéndez Pidal, Ramón. “Catálogo del romancero judío-español,"" Cultura Española, 4 (1906), 1045–1077; 5 (1907), 161–199. http://bit.ly/1NT9xPL
  • FLSJ - Armistead, Samuel G. and Joseph H. Silverman. Folk Literature of the Sephardic Jews. Series in eight volumes. Catalog online at: http://www.sephardifolklit.org/
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Ballads > compound objects: Recording Location
Property definition
  • A location, usually a city, where a resource was recorded.
Recording values
  • For metadata creation taking place outside the University of Washington Libraries (UWL) Cataloging and Metadata Services unit:
  • Enter a recording location in natural language, providing sufficient information to disambiguate place names as needed.
  • As a rule, include more information rather than less.
  • For example, when providing the name of a city, also provide the state, region, and/or country name(s) as available.
  • UWL Cataloging staff will use this information to create a structured value.
  • Be sure to provide the value 'xyz' for the Cataloging property to indicate to cataloging staff that revision of the unstructured value is needed.
  • Separate multiple entries with a semicolon and space (“; “).
  • Order of values does not matter.
  • When reusing existing metadata, include only the place name in the value for Recording Location.
  • Add any other relevant information as a value for the Notes property.
  • For example, adapt existing value “Seattle, in her home” as:
  • Recording Location: Seattle, Washington, USA
  • Notes: Recorded in the home of [name].

  • For UWL cataloging staff creating structured values:
  • Forms of the names should be derived from the Library of Congress Authority File.
  • Enter as follows:
  • Country--State or Province--City
  • Separate multiple entries with a semicolon and space (“; “).
  • Order of values does not matter.
Examples / well-formed values
  • [Natural-language values for review by cataloging staff:]
  • Seattle, WA, USA

  • [Structured values provided by cataloging staff:]
  • United States--Washington (State)--Seattle
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Ballads > compound objects: Language
Property definition
  • A language of the resource.
Recording values
  • Enter language names, fully spelled out, as they appear in the ISO 639 Code Tables "Language Name(s)" column. Note that Ladino is listed as such, and not as Judeo-Spanish or Judezmo.
  • For Aramaic-language resources, simply enter "Aramaic".
  • Separate multiple values using a semicolon and space (“; “).
  • Order of values does not matter.
  • Required for all compound objects.
Examples / well-formed values
  • English
  • Spanish
  • English; Spanish
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Ballads > compound objects: Digital Collection
Property definition
  • Name of the digital collection.
Recording values
  • Enter the following value:
  • Sephardic Studies Digital Collection at the University of Washington
  • Required for all compound objects.
Examples / well-formed values
  • Sephardic Studies Digital Collection at the University of Washington
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Ballads > compound objects: Sephardic Studies Accession Number (SSAN)
Property definition
  • A number assigned to each resource in the Sephardic Studies Digital Collection Master Catalog; each resource's number is unique in the Catalog.
Recording values
  • Find the item in Sephardic Studies Collection Master Catalog in column AX (File Name) and enter its corresponding number here.
  • If a match is not found, search the Sephardic Studies Collection Master Catalog's Ladino Audio Archive tab in column P (Digitized File Name) and enter its corresponding number here.
  • Required for all compound objects.
Examples / well-formed values
  • LAA0003
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Ballads > compound objects: Restrictions
Property definition
  • Any restrictions on the use of a resource.
Recording values
  • Required for all compound objects.
  • Enter the following value:
  • To inquire about permissions, contact sephstud@uw.edu. Please cite the Sephardic Studies Accession Number.
Examples / well-formed values
  • To inquire about permissions, contact sephstud@uw.edu. Please cite the Sephardic Studies Accession Number.
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Ballads > compound objects: Rights URI
Property definition
  • URI that dereferences to a rights statement.
Recording values
Examples / well-formed values
  • http://rightsstatements.org/vocab/CNE/1.0/
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Ballads > compound objects: Ordering Information
Property definition
  • Instructions for ordering.
Recording values
  • Enter the following value:
  • Reproductions are not available for order.
Examples / well-formed values
  • Reproductions are not available for order.
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Ballads > compound objects: Repository
Property definition
  • The institution holding the resource.
Recording values
  • This value will be entered by University of Washington Libraries Special Collections Staff following transfer of collection resources.
  • Value will be as follows:
  • University of Washington Libraries. Special Collections
Examples / well-formed values
  • University of Washington Libraries. Special Collections
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Ballads > compound objects: Repository Collection
Property definition
  • Collection to which the original resource is a part.
Recording values
  • Where applicable, this value will be entered by University of Washington Libraries Special Collections Staff following transfer of collection resources.
  • Where a finding aid for an archival collection including the resource exists, the value will be constructed using the collection name and accession number given there.
Examples / well-formed values
  • 🚧 🚧 🚧
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Ballads > compound objects: Repository Collection Guide
Property definition
  • URI to an EAD finding aid.
Recording values
  • Where applicable, this value will be entered by University of Washington Libraries Special Collections Staff following transfer of collection resources.
  • Where a finding aid for an archival collection including the resource exists, the value will be the Ark URL for this finding aid in ArchivesWest.
Examples / well-formed values
  • 🚧 🚧 🚧
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Ballads > compound objects: Type
Property definition
  • Describes the nature or genre of the content of the resource.
Recording values
  • Values entered for this property are not visible in the public interface.

  • Values for this property must come from the DCMI Type Vocabulary.
  • For ballad, and oral history compound objects, provide the following value:
  • Sound
Examples / well-formed values
  • Sound
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Ballads > compound objects: Cataloging
Property definition
  • Messages for local catalogers.
Recording values
  • Values entered for this property are not visible in the public interface.

  • For metadata creation taking place outside the UWL Cataloging and Metadata Services unit:
  • Enter "xyz" to request the creation and/or review of values for one or more of the following fields by UWL cataloging staff:

  • Subjects (LCSH)
  • Genre/Form (LCGFT)
  • Related OCLC Record
  • Geographic Coverage
  • Interviewee Birthplace
  • Performer Birthplace
  • Recording Location
  • Printer Location
  • Publisher Location
Examples / well-formed values
  • xyz
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Ballads > compound objects: Staff Notes
Property definition
  • Notes for staff only, notes of an administrative nature.
Recording values
  • Values entered for this property are not visible in the public interface.

  • Staff Notes values are hidden in the public CONTENTdm interface.
  • These values will be used by University of Washington Libraries (UWL) cataloging staff to assign controlled values for the following fields for ballad recordings:
  • Genre/Form (LCGFT)
  • Performer Birthplace
  • Recording Location

  • Staff notes should not be necessary for UWL catalogers entering structured values for ballad recordings.
  • Other staff notes may be entered as needed.
Examples / well-formed values
  • N/A
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Ballads > compound objects: Institution
Property definition
  • Information for the purpose of facilitating browsing in the University of Washington Libraries Digital Collections online interface.
Recording values
  • Values entered for this property are not visible in the public interface.

  • Use the following value:
  • special collections
Examples / well-formed values
  • special collections
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Ballads > compound objects: collectionPageCategory
Property definition
  • A category for the resource, for use in presenting resources by category on a collection landing page.
Recording values
  • Values entered for this property are not visible in the public interface.

  • Provide the category within which the resource should be presented on the collection landing page.
Examples / well-formed values
  • Novelesque Ballad - Various subjects
  • Institutional Publications
  • Ephemera
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries

Ballads > Compound-object items

Ballads > compound-object items: Title
Property definition
  • A name for the resource.
Recording values
  • Construct as follows for audio-file (.mp3/.wav/etc.) items:
  • [song title] - audio
  • Enter the song title romanized according to Aki Yerushalayim.
  • Construct as follows for image-file (.jpg) items which are images of singers:
  • Image of [singer name], singer
  • Provide the singer name in natural order.
  • Construct as follows for image-file (.pdf) items which are digitized sheet music:
  • Musical Transcription: [song title]
  • (Do not enter square brackets around song titles or singer names.)
  • All compound-object items--audio files and image files--must have a title.
Examples / well-formed values
  • La Muerte del Duque de Gandía (í-a) - audio
  • Image of Bohora Cornell (Coronel), singer
  • Musical Transcription: La Muerte del Duque de Gandí
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Ballads > compound-object items: Digital Collection
Property definition
  • Name of the digital collection.
Recording values
  • Enter the following value:
  • Sephardic Studies Digital Collection at the University of Washington
  • Required for all compound-object items.
Examples / well-formed values
  • Sephardic Studies Digital Collection at the University of Washington
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Ballads > compound-object items: Repository
Property definition
  • The institution holding the resource.
Recording values
  • This value will be entered by University of Washington Libraries Special Collections Staff following transfer of collection resources.
  • Value will be as follows:
  • University of Washington Libraries. Special Collections
Examples / well-formed values
  • University of Washington Libraries. Special Collections
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Ballads > compound-object items: Type
Property definition
  • Describes the nature or genre of the content of the resource.
Recording values
  • Values entered for this property are not visible in the public interface.

  • For audio-file compound-object items (ballad recordings), provide the following value:
  • Sound
  • For image-file compound-object items which are performer photographs, provide the following value:
  • StillImage
  • For image-file compound-object items which are digitized sheet music, provide the following value:
  • Image
Examples / well-formed values
  • Sound
  • StillImage
  • Image
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Ballads > compound-object items: Extent
Property definition
  • Size or duration of the resource.
Recording values
  • For audio files, enter the runtime of the digital access file.
  • Format runtime as HH:MM:SS.
Examples / well-formed values
  • 00:12:58
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Ballads > compound-object items: Digital Format
Property definition
  • File format of a digital resource.
Recording values
  • Enter the file format of the file representing the compound-object item--that is, the access item.
  • This should be the format of the file given as a value for the digitalFileName property.
  • Use media types listed at http://www.iana.org/assignments/media-types/index.html.
  • For audio WAVE files, enter "audio/wav".
Examples / well-formed values
  • audio/mpeg
  • image/jpeg
  • application/pdf
  • text/plain
  • video/mp4
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Ballads > compound-object items: Original Format
Property definition
  • File format, physical medium, and/or dimensions of the original resource.
Recording values
  • Values for Original Format must be taken from the RDA Carrier Type vocabulary.
  • For ballad recordings, enter one of the following values depending on which compound-object item you are describing.
  • For audio file items:
  • audiocassette
  • For image files (singer photos) and digitized sheet music:
  • sheet
Examples / well-formed values
  • audiocassette
  • sheet
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Ballads > compound-object items: Physical Description
Property definition
  • Description of the physical attributes of the original medium in which data, sound, images, etc., are stored; the carrier; may include an extent statement.
Recording values
  • For ballad recordings, Physical Description is recorded at the compound-object-item level.
  • If information is available, provide a description of the physical resource from which the digital surrogate (compound-object item) was created.

  • For audio-file items (song recordings), if information is available, provide a runtime for the analog media from which the audio file was created.
  • Format runtime as HH:MM:SS.

  • For image-file items (photographs of performers, digitized sheet music), if information is available, provide a measurement or measurements of the physical media from which image files were created.

  • For photographs of performers, if information is available, record the height and width of the photo in centimeters, excluding any frame or mount, using Arabic numerals.
  • Use a space and “cm” (no following punctuation) after the measurements (“ cm”), to record as:
  • [height] x [width] cm

  • For sheet music, if information is available, record the height of the sheet or volume in centimeters.
  • Record the height using Arabic numerals.
  • Use a space and “cm” (no following punctuation) after the numeral(s) (“ cm”), to record as:
  • [height] cm
Examples / well-formed values
  • 00:32:23
  • 10 x 15 cm
  • 28 cm
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Ballads > compound-object items: Timecode Start
Property definition
  • When an audio file has been created from a portion of a longer original recording, the time at which the audio file's content begins in the original recording.
Recording values
  • If information is available, provide the timecode at which the clip included in the audio file begins.
  • Only applicable for compound-object audio files, when an audio file has been created from a portion of a longer original recording.
  • Record using the format HH:MM:SS.
Examples / well-formed values
  • 00:34:32
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Ballads > compound-object items: Digital Reproduction Information
Property definition
  • Description of the digital conversion process, date scanned, etc.
Recording values
  • If available and applicable, provide details regarding the digitization of ballad compound-object items (singer photo, audio file, etc.).
Examples / well-formed values
  • Sample rate: 96KHz. Bit depth: 24. Issues encountered: Repaired several faulty splices. Date of transfer: 2019-01-04. Applicable conservation treatments: Baked and repaired several splices. De-noise and de-hum (iZotrope RX5).
  • Digital, stereo. Copied from analog recording to compact disc. Converted to 24 bit/48kHz Broadcast WAV format files by University of Washington Libraries in 2010.
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Ballads > compound-object items: Original File Name
Property definition
  • The complete name including file extension of a digital file representing a resource to be described by one or more property/value pairs in CONTENTdm.
Recording values
  • Values entered for this property are not visible in the public interface.

  • When entering values in a metadata spreadsheet, each row will include values describing a resource--either a compound object, compound-object item, or standalone object.
  • Each row describing either a compound-object item or a standalone object must include a filename provided as a value for this property.
  • For ballads, compound-object items will either be audio files, image files (photographs) of a singer, or musical transcriptions (image or PDF files).
  • For oral histories, compound-object items will either be audio files, image files (photographs) of an interviewee, or transcripts (PDF files).
Examples / well-formed values
  • 86_El_Robo_de_Elena.mp3
  • Estrea_Chiprut.jpg
  • La_Muerte_del_Duque_de_Gandía.pdf
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries

Metadata creation guidance: Oral histories > Compound objects and compound-object items

Oral histories > Compound objects

Oral histories > compound objects: Title
Property definition
  • A name for the resource.
Recording values
  • Construct as follows:
  • [interviewee name] interview
  • Provide the interviewee name in natural order.
  • (Do not enter square brackets around the interviewee name.)
  • All compound objects must have a title.
Examples / well-formed values
  • Solomon Maimon interview
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Oral histories > compound objects: Interviewee
Property definition
  • A person interviewed.
Recording values
  • Provide the name of the interviewee.
  • When appropriate, search the Library of Congress Name Authority File via id.loc.gov for the interviewee name.
  • If a potential match is found, confirm that it is the person associated with the resource. It may be helpful to review information included in the web display such as source(s) of information and occupation (for persons), and/or to follow the links provided for exact and/or closely matching concepts from other schemes.
  • Copy the name string for use just as it appears at the top of the page, above the URI(s), including dates.
  • If no record exists, record personal names as "Lastname, Firstname".
  • When recording names without a match in the NAF, reuse the recorded form consistently when the same person or organization appears in the metadata for a different resource.
  • For a personal name like Alexander Ben Guiat, "Ben" is considered part of the first name and is transcribed as: "Guiat, Alexander Ben".
  • Separate multiple entries with a semicolon and space (“; “).
  • Order of values does not matter.
Examples / well-formed values
  • Maimon, Solomon
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Oral histories > compound objects: Interviewee Birthplace
Property definition
  • The place of birth of a person interviewed.
Recording values
  • For metadata creation taking place outside the University of Washington Libraries (UWL) Cataloging and Metadata Services unit:
  • Enter the place of birth of the interviewee in natural language, providing sufficient information to disambiguate place names as needed.
  • As a rule, include more information rather than less.
  • For example, when providing the name of a city, also provide the state, region, and/or country name(s) as available.
  • UWL Cataloging staff will use this information to create a structured value.
  • Separate multiple entries with a semicolon and space (“; “).
  • Order of values does not matter.
  • If multiple interviewees are associated with a resource, include the Interviewee value to which the birthplace corresponds in square brackets following.
  • Be sure to provide the value 'xyz' for the Cataloging property to indicate to cataloging staff that revision of the unstructured value is needed.

  • For UWL cataloging staff creating structured values:
  • Forms of the names should be derived from the Library of Congress Authority File.
  • Enter as follows:
  • Country--State or Province--City
  • Separate multiple entries with a semicolon and space (“; “).
  • Order of values does not matter.
  • If multiple interviewees are associated with a resource, include the Interviewee value to which the birthplace corresponds in square brackets following.
Examples / well-formed values
  • [Natural-language values for review by cataloging staff:]
  • Seattle, Washington, United States
  • Thessaloniki, Greece [Naar, Albert]; Istanbul, Turkey [Saltiel, Jack]

  • [Structured values provided by cataloging staff:]
  • United States--Washington (State)--Seattle
  • Greece--Thessalonike [Naar, Albert]; Turkey--Istanbul [Saltiel, Jack]
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Oral histories > compound objects: Interviewer
Property definition
  • The person who interviewed the interviewee.
Recording values
  • Provide the name of the interviewer.
  • When appropriate, search the Library of Congress Name Authority File via id.loc.gov for the interviewer name.
  • If a potential match is found, confirm that it is the person associated with the resource. It may be helpful to review information included in the web display such as source(s) of information and occupation (for persons), and/or to follow the links provided for exact and/or closely matching concepts from other schemes.
  • Copy the name string for use just as it appears at the top of the page, above the URI(s), including dates.
  • If no record exists, record personal names as "Lastname, Firstname".
  • When recording names without a match in the NAF, reuse the recorded form consistently when the same person or organization appears in the metadata for a different resource.
  • For a personal name like Alexander Ben Guiat, "Ben" is considered part of the first name and is transcribed as: "Guiat, Alexander Ben".
  • Separate multiple entries with a semicolon and space (“; “).
  • Order of values does not matter.
Examples / well-formed values
  • Droker, Howard
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Oral histories > compound objects: Videographer
Property definition
  • A person who created the video recording.
Recording values
  • Provide the name of the videographer--the person who created the video recording.
  • When appropriate, search the Library of Congress Name Authority File via id.loc.gov for the videographer name.
  • If a potential match is found, confirm that it is the person associated with the resource. It may be helpful to review information included in the web display such as source(s) of information and occupation (for persons), and/or to follow the links provided for exact and/or closely matching concepts from other schemes.
  • Copy the name string for use just as it appears at the top of the page, above the URI(s), including dates.
  • If no record exists, Record personal names as "Lastname, Firstname".
  • For a personal name like Alexander Ben Guiat, "Ben" is considered part of the first name and is transcribed as: "Guiat, Alexander Ben".
  • When recording names without a match in the NAF, reuse the recorded form consistently when the same person or organization appears in the metadata for a different resource.
  • Separate multiple entries with a semicolon and space (“; “).
  • Order of values does not matter.
Examples / well-formed values
  • Meyers, Richard D.
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Oral histories > compound objects: Donor
Property definition
  • A person or corporate body who donated a physical item to the University of Washington Libraries or an affiliated academic unit.
Recording values
  • Find donor name in Sephardic Studies Collection Master Catalog; the item may be recorded on the Ladino Audio Archive tab.
  • Check both the main collection tab and Ladino Audio Archive tab for the correct file.
  • Contributor is considered a donor if the catalog notes that the item is property of Sephardic Studies.
  • When appropriate, search the Library of Congress Name Authority File via id.loc.gov for the donor name.
  • If a potential match is found, confirm that it is the person associated with the resource. It may be helpful to review information included in the web display such as source(s) of information and occupation (for persons), and/or to follow the links provided for exact and/or closely matching concepts from other schemes.
  • Copy the name string for use just as it appears at the top of the page, above the URI(s), including dates.
  • If no record exists, record personal names as "Lastname, Firstname".
  • When recording names without a match in the NAF, reuse the recorded form consistently when the same person or organization appears in the metadata for a different resource.
  • For a personal name like Alexander Ben Guiat, "Ben" is considered part of the first name and is transcribed as: "Guiat, Alexander Ben".
  • Separate multiple entries with a semicolon and space (“; “).
  • Order does not matter.
  • Either a donor or lender value must be provided for every compound object.
Examples / well-formed values
  • Azose, Isaac
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Oral histories > compound objects: Lender
Property definition
  • A person or corporate body who lent a physical item to the University of Washington Libraries or an affiliated academic unit for creation of a digital surrogate.
Recording values
  • Find lender name in Sephardic Studies Collection Master Catalog; the item may be recorded on the Ladino Audio Archive tab.
  • Check both the main collection tab and Ladino Audio Archive tab for the correct file.
  • Contributor is considered a lender if the catalog notes that item is still property of that individual.
  • When appropriate, search the Library of Congress Name Authority File via id.loc.gov for the lender name.
  • If a potential match is found, confirm that it is the person associated with the resource. It may be helpful to review information included in the web display such as source(s) of information and occupation (for persons), and/or to follow the links provided for exact and/or closely matching concepts from other schemes.
  • Copy the name string for use just as it appears at the top of the page, above the URI(s), including dates.
  • If no record exists, record personal names as "Lastname, Firstname".
  • When recording names without a match in the NAF, reuse the recorded form consistently when the same person or organization appears in the metadata for a different resource.
  • For a personal name like Alexander Ben Guiat, "Ben" is considered part of the first name and is transcribed as: "Guiat, Alexander Ben".
  • Separate multiple entries with a semicolon and space (“; “).
  • Order of values does not matter.
  • Either a lender or donor value must be provided for every compound object.
Examples / well-formed values
  • Maimon, Rabbi Solomon
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Oral histories > compound objects: Former Owner
Property definition
  • A person or corporate body who previously owned a physical or digital resource.
Recording values
  • When searching for donor or lender in Sephardic Studies Collection Master Catalog, some contributions will be recorded as "Person A via Person B," or as "Person A / Person B."
  • In such a case, Person A is the former owner, and their name belongs in this field.
  • When appropriate, search the Library of Congress Name Authority File via id.loc.gov for the lender name.
  • If a potential match is found, confirm that it is the person associated with the resource. It may be helpful to review information included in the web display such as source(s) of information and occupation (for persons), and/or to follow the links provided for exact and/or closely matching concepts from other schemes.
  • Copy the name string for use just as it appears at the top of the page, above the URI(s), including dates.
  • If no record exists, record personal names as "Lastname, Firstname".
  • When recording names without a match in the NAF, reuse the recorded form consistently when the same person or organization appears in the metadata for a different resource.
  • For a personal name like Alexander Ben Guiat, "Ben" is considered part of the first name and is transcribed as: "Guiat, Alexander Ben".
  • Separate multiple entries with a semicolon and space (“; “).
  • Order of values does not matter.
Examples / well-formed values
  • Benezra, Henry
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Oral histories > compound objects: Date (EDTF)
Property definition
  • Prominent date for the resource, such as the date of creation of the original resource.
Recording values
  • Values entered for this property are not visible in the public interface.

  • Reflects the date in the "Date" field.
  • Express all dates, including date ranges, using Library of Congress' Extended Date Time Format.
  • Creating well-formed values for resources in the Sephardic Studies Digital Collection may require first converting date values from lunar to Gregorian calendar systems.
  • The most recent version of the Library of Congress' summary of EDTF is available at https://www.loc.gov/standards/datetime/.
  • Six formats are recommended for values in Date, each corresponding to a specific EDTF format:
  • If the value of Date is YYYY, enter YYYY.
  • If the value of Date is YYYY?, enter YYYY?
  • If the value of Date is [month] DD, YYYY, enter YYYY-MM-DD.
  • If the value of Date is [month], YYYY, enter YYYY-MM.
  • If the value of Date is between YYYY and YYYY, enter YYYY/YYYY.
  • If the value of Date is between YYYY and YYYY?, enter YYYY?/YYYY?
  • If the value of Date is not any of the above, consult the EDTF spedification to determine the appropriate notation.
  • Date-Edtf value should agree with dates values entered in Date and Dates fields.
Examples / well-formed values
  • If the Date field = "1940" then Date EDTF = "1940"
  • If the Date field = "1910?" then Date EDTF = "1910?"
  • If Date field = "May 9, 2001" then Date EDTF = "2001-05-09"
  • If Date field = "January 2008" then Date EDTF = "2008-01"
  • If Date field = "between 1930 and 1939" then Date EDTF = "1930/1939"
  • If Date field = "between 1855 and 1999?" then Date EDTF = "1855?/1999?"
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Oral histories > compound objects: Date
Property definition
  • Prominent date for the resource, such as the date of creation of the original resource.
Recording values
  • Enter the date on which the interview was recorded.
  • Use a YYYY-MM-DD format if month and day information is available.
  • Use a YYYY-MM or YYYY format if month and/or day information is not available.
Examples / well-formed values
  • 2020-03-15
  • 2019-04
  • 2018
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Oral histories > compound objects: Dates
Property definition
  • Prominent years for the resource, such as the date(s) of creation of the original resource; the expected value is a list of each and every pertinent year.
Recording values
  • Values entered for this property are not visible in the public interface.

  • Reflects the date in the "Date" field pertinent to the overall object.
  • Creating well-formed values for resources in the Sephardic Studies Digital Collection may require first converting date values from lunar to Gregorian calendar systems.
  • Enter the year or years only.
  • When the value of Date is YYYY, enter YYYY.
  • When the value of Date is YYYY?, enter an eleven year date range, five years on either side of the uncertain date.
  • When the value of Date is [month] DD, YYYY, enter the year only in the following format: YYYY.
  • When the value of Date is [month], YYYY, enter the year only in the following format: YYYY.
  • When the value of Date is between YYYY and YYYY, enter all years in the date range in the following format: YYYY YYYY YYYY etc.
  • When the value of Date is between YYYY and YYYY?, enter all years in the date range plus five years before the earliest date and five years after the latest date, in the following format: YYYY YYYY YYYY etc.
  • This field is indexed and enables date searching in CONTENTdm.
  • The Dates value should agree with date values entered in Date-Edtf and Date fields.
Examples / well-formed values
  • 1939
  • 1939?
  • 1939 1940 1941 1942 1943 1944 1945
  • 1934 1935 1936 1937 1938 1939 1940 1941 1942 1943 1944 1945 1946 1947 1948 1949 1950
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Oral histories > compound objects: Interviewee Biography
Property definition
  • Biographical information about a person interviewed.
Recording values
  • Enter brief biographical information about the interviewee.
  • Provide primarily biographical information as mentioned in the interview and/or related to topics discussed in the interview.
Examples / well-formed values
  • Lela Abravanel was born in Salonica [Thessaloniki] Greece. She discusses her childhood in Las Kampanyas, a suburb of Salonica, and how she spoke French with her parents.
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Oral histories > compound objects: Notes
Property definition
  • An account of the resource.
Recording values
  • Enter any information of importance that is not represented elsewhere.
  • When reusing existing metadata, only the place name will be included the value for Recording Location.
  • Any additional information present in existing metadata which will not be used in the Recording Location value may be included here.
  • For example, adapt existing value “Seattle, in her home” as:
  • Recording Location: Seattle, Washington, USA
  • Notes: Recorded in the home of [name].
  • Start each distinct note entry on a new line.
  • When entering values in a spreadsheet, note that depending on the spreadsheet-editing application, CTRL + ENTER, ALT + ENTER, or another key combination can be used to enter a new line within a cell.
Examples / well-formed values
  • Rabbi Maimon discusses his education at Yeshiva University (00:05:30), his return to Seattle and installment as rabbi (00:10:50), and challenges faced by the Sephardic community in Seattle (00:10:12).
  • Recorded in the home of Rabbi Maimon.
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Oral histories > compound objects: Subjects (LCSH)
Property definition
  • The topic of the resource.
Recording values
  • University of Washington Libraries (UWL) cataloging staff will provide a value or values for this property.
  • For metadata creation taking place outside the UWL Cataloging and Metadata Services unit:
  • Do not provide a value for this property.
  • Be sure to provide the value 'xyz' for the Cataloging property to indicate to cataloging staff that a value is needed.
  • For oral histories, be sure to record a value for the Index property which provides needed information for UWL cataloging staff to perform subject analysis. Cataloging staff may also use transcripts for subject analysis.
  • For details about the information needed by cataloging staff, contact the collection manager(s) or metadata liaison(s).
Examples / well-formed values
  • Sephardim--Washington (State)--Interviews
  • Jews--Washington (State)--Interviews
  • Jews--Washington (State)--History
  • Temple de Hirsch (Seattle, Wash.)
  • Fish trade--Washington (State)--History
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Oral histories > compound objects: Genre/Form (LCGFT)
Property definition
  • The genre or form of the resource, expressed using values selected from Library of Congress Genre/Form Terms.
Recording values
  • University of Washington Libraries (UWL) cataloging staff will provide a value or values for this property.
  • For metadata creation taking place outside the UWL Cataloging and Metadata Services unit:
  • Do not provide a value for this property.
  • Be sure to provide the value 'xyz' for the Cataloging property to indicate to cataloging staff that a value is needed.
Examples / well-formed values
  • Oral histories
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Oral histories > compound objects: Object Type
Property definition
  • The nature or genre of the resource.
Recording values
  • Enter the following value:
  • oral histories
Examples / well-formed values
  • oral histories
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Oral histories > compound objects: Individuals Discussed
Property definition
  • Individuals given significant attention in the resource.
Recording values
  • Provide names of individuals given significant attention in the interview.
  • When appropriate, search the Library of Congress Name Authority File via id.loc.gov for the names of individuals discussed in the oral history.
  • If a potential match is found, confirm that it is the person associated with the resource. It may be helpful to review information included in the web display such as source(s) of information and occupation (for persons), and/or to follow the links provided for exact and/or closely matching concepts from other schemes.
  • Copy the name string for use just as it appears at the top of the page, above the URI(s), including dates.
  • If no record exists, record personal names as "Lastname, Firstname".
  • When recording names without a match in the NAF, reuse the recorded form consistently when the same person appears in the metadata for a different resource.
  • For a personal name like Alexander Ben Guiat, "Ben" is considered part of the first name and is transcribed as: "Guiat, Alexander Ben".
  • Separate multiple entries with a semicolon and space (“; “).
  • Order of values does not matter.
Examples / well-formed values
  • Adatto, Albert; Maimon, Bension
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Oral histories > compound objects: Organizations Discussed
Property definition
  • Organizations given significant attention in the resource.
Recording values
  • Provide the name or names of an organization or organizations given significant attention in the interview.
  • When appropriate, search the Library of Congress Name Authority File via id.loc.gov for the names of organizations discussed in the oral history.
  • If a potential match is found, confirm that it is the organization associated with the resource: it may be helpful to review information included in the web display such as source(s) of information, and/or to follow the links provided for exact and/or closely matching concepts from other schemes.
  • Copy the name string for use just as it appears at the top of the page, above the URI(s), including dates.
  • If no match is found, record an organization name.
  • When recording names without a match in the NAF, reuse the recorded form consistently when the same person appears in the metadata for a different resource.
  • Separate multiple entries with a semicolon and space (“; “).
  • Order of values does not matter.
Examples / well-formed values
  • Congregation Ezra Bessaroth
  • Congregation Ezra Bessaroth; Longacres Race Track
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Oral histories > compound objects: Geographic Coverage
Property definition
  • The spatial characteristics given significant attention in the resource.
Recording values
  • For metadata creation taking place outside the UWL Cataloging and Metadata Services unit:
  • Enter broad and local geographic locations given significant attention in the resource in natural language, providing sufficient information to disambiguate place names as needed.
  • As a rule, include more information rather than less.
  • For example, when providing the name of a city, also provide the state, region, and/or country name(s) as available.
  • Cataloging staff will use this information to create a structured value.
  • Separate multiple entries with a semicolon and space (“; “).

  • For UWL cataloging staff creating structured values:
  • Forms of the names should be derived from the Library of Congress Authority File.
  • Enter as follows:
  • Country--State or Province--City
  • For neighborhoods or other types of locales below the city level, enter an LCSH heading in the Subjects (LCSH) field.
  • Separate multiple entries with a semicolon and space (“; “).
Examples / well-formed values
  • [Natural-language values for review by cataloging staff:]
  • Tacoma, Washington, USA
  • Rhodes, Greece

  • [Structured values provided by cataloging staff:]
  • United States--Washington (State)--Tacoma
  • Greece--Rhodes
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Oral histories > compound objects: Time Period Discussed
Property definition
  • Representation of time periods given significant attention in the resource.
Recording values
  • Enter a period in time as needed.
  • If practical, enter the date using one of the following formats:
  • YYYY
  • YYYY?
  • [month spelled out] [day], YYYY
  • [month spelled out], YYYY
  • between YYYY and YYYY
  • between YYYY and YYYY?
  • When a date or date range is not practical, prefer an LCSH heading reprenting the time period.
  • When none of the options above are practical, enter the most practical representation of the time period.
Examples / well-formed values
  • 1964
  • between 1986 and 1990
  • Twentieth century
  • Nineteen forties
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Oral histories > compound objects: Index
Property definition
  • An abridged transcript, or list of contents, for the resource.
Recording values
  • Enter an abridged transcript or a list of contents.
  • Start each list entry on a new line preceded by a hyphen.
  • When entering index values in a spreadsheet, note that depending on the spreadsheet-editing application, CTRL + ENTER, ALT + ENTER, or another key combination can be used to enter a new line within a cell.
  • Non-English interviews do not need an index.
Examples / well-formed values
  • Topics presented in order of discussion on recording:
  • - More on civil rights and local activism.
  • - Phone rings in the background
  • - Made presentation to Jim Ellis.
  • - Federal case involving racism and employment opportunities.
  • - Nixon Administration.
  • - 1989 Supreme Court case about employment and racism.
  • - Had a series of mini strokes that forced me to retire.
  • - Narrator's comments about people he has talked to. Lists names. I'm not a journalist. This is an oral history. Intention is to create oral history of the whole city.
  • - Intention to publish. - Discusses the scope of the publication.
  • - Events in the 1960s precede the scope. - Discuss other potential subjects for the project.
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Oral histories > compound objects: Recording Location
Property definition
  • A location, usually a city, where a resource was recorded.
Recording values
  • For metadata creation taking place outside the University of Washington Libraries (UWL) Cataloging and Metadata Services unit:
  • Enter a recording location in natural language, providing sufficient information to disambiguate place names as needed.
  • As a rule, include more information rather than less.
  • For example, when providing the name of a city, also provide the state, region, and/or country name(s) as available.
  • UWL Cataloging staff will use this information to create a structured value.
  • Be sure to provide the value 'xyz' for the Cataloging property to indicate to cataloging staff that revision of the unstructured value is needed.
  • Separate multiple entries with a semicolon and space (“; “).
  • Order of values does not matter.
  • When reusing existing metadata, include only the place name in the value for Recording Location.
  • Add any other relevant information as a value for the Notes property.
  • For example, adapt existing value “Seattle, in her home” as:
  • Recording Location: Seattle, Washington, USA
  • Notes: Recorded in the home of [name].

  • For UWL cataloging staff creating structured values:
  • Forms of the names should be derived from the Library of Congress Authority File.
  • Enter as follows:
  • Country--State or Province--City
  • Separate multiple entries with a semicolon and space (“; “).
  • Order of values does not matter.
Examples / well-formed values
  • [Natural-language values for review by cataloging staff:]
  • Seattle, WA, USA

  • [Structured values provided by cataloging staff:]
  • United States--Washington (State)--Seattle
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Oral histories > compound objects: Language
Property definition
  • A language of the resource.
Recording values
  • Enter language names, fully spelled out, as they appear in the ISO 639 Code Tables "Language Name(s)" column. Note that Ladino is listed as such, and not as Judeo-Spanish or Judezmo.
  • For Aramaic-language resources, simply enter "Aramaic".
  • Separate multiple values using a semicolon and space (“; “).
  • Order of values does not matter.
  • Required for all compound objects.
Examples / well-formed values
  • English
  • Spanish
  • English; Spanish
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Oral histories > compound objects: Digital Collection
Property definition
  • Name of the digital collection.
Recording values
  • Enter the following value:
  • Sephardic Studies Digital Collection at the University of Washington
  • Required for all compound objects.
Examples / well-formed values
  • Sephardic Studies Digital Collection at the University of Washington
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Oral histories > compound objects: Sephardic Studies Accession Number (SSAN)
Property definition
  • A number assigned to each resource in the Sephardic Studies Digital Collection Master Catalog; each resource's number is unique in the Catalog.
Recording values
  • Find the item in Sephardic Studies Collection Master Catalog in column AX (File Name) and enter its corresponding number here.
  • If a match is not found, search the Sephardic Studies Collection Master Catalog's Ladino Audio Archive tab in column P (Digitized File Name) and enter its corresponding number here.
  • Required for all compound objects.
Examples / well-formed values
  • LAA0003
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Oral histories > compound objects: Restrictions
Property definition
  • Any restrictions on the use of a resource.
Recording values
  • Required for all compound objects.
  • Enter the following value:
  • To inquire about permissions, contact sephstud@uw.edu. Please cite the Sephardic Studies Accession Number.
Examples / well-formed values
  • To inquire about permissions, contact sephstud@uw.edu. Please cite the Sephardic Studies Accession Number.
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Oral histories > compound objects: Rights URI
Property definition
  • URI that dereferences to a rights statement.
Recording values
Examples / well-formed values
  • http://rightsstatements.org/vocab/CNE/1.0/
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Oral histories > compound objects: Ordering Information
Property definition
  • Instructions for ordering.
Recording values
  • Enter the following value:
  • Reproductions are not available for order.
Examples / well-formed values
  • Reproductions are not available for order.
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Oral histories > compound objects: Repository
Property definition
  • The institution holding the resource.
Recording values
  • This value will be entered by University of Washington Libraries Special Collections Staff following transfer of collection resources.
  • Value will be as follows:
  • University of Washington Libraries. Special Collections
Examples / well-formed values
  • University of Washington Libraries. Special Collections
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Oral histories > compound objects: Repository Collection
Property definition
  • Collection to which the original resource is a part.
Recording values
  • Where applicable, this value will be entered by University of Washington Libraries Special Collections Staff following transfer of collection resources.
  • Where a finding aid for an archival collection including the resource exists, the value will be constructed using the collection name and accession number given there.
Examples / well-formed values
  • 🚧 🚧 🚧
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Oral histories > compound objects: Repository Collection Guide
Property definition
  • URI to an EAD finding aid.
Recording values
  • Where applicable, this value will be entered by University of Washington Libraries Special Collections Staff following transfer of collection resources.
  • Where a finding aid for an archival collection including the resource exists, the value will be the Ark URL for this finding aid in ArchivesWest.
Examples / well-formed values
  • 🚧 🚧 🚧
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Oral histories > compound objects: Type
Property definition
  • Describes the nature or genre of the content of the resource.
Recording values
  • Values entered for this property are not visible in the public interface.

  • Values for this property must come from the DCMI Type Vocabulary.
  • For ballad, and oral history compound objects, provide the following value:
  • Sound
Examples / well-formed values
  • Sound
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Oral histories > compound objects: Cataloging
Property definition
  • Messages for local catalogers.
Recording values
  • Values entered for this property are not visible in the public interface.

  • For metadata creation taking place outside the UWL Cataloging and Metadata Services unit:
  • Enter "xyz" to request the creation and/or review of values for one or more of the following fields by UWL cataloging staff:

  • Subjects (LCSH)
  • Genre/Form (LCGFT)
  • Related OCLC Record
  • Geographic Coverage
  • Interviewee Birthplace
  • Performer Birthplace
  • Recording Location
  • Printer Location
  • Publisher Location
Examples / well-formed values
  • xyz
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Oral histories > compound objects: Staff Notes
Property definition
  • Notes for staff only, notes of an administrative nature.
Recording values
  • Values entered for this property are not visible in the public interface.

  • Staff Notes values are hidden in the public CONTENTdm interface.
  • These values will be used by University of Washington Libraries (UWL) cataloging staff to assign controlled values for the following fields for oral histories:
  • Subjects (LCSH)
  • Genre/Form (LCGFT)
  • Geographic Coverage
  • Interviewee Birthplace
  • Recording Location

  • Add any available relevant information which is not given in Index, Notes, or other property values, which will assist UWL catalogers assigning values for Subjects (LCSH) and Geographic Coverage.
  • Catalogers will the use unstructured values provided for Interviewee Birthplace and Recording Location to create structured values for these fields, so Staff Notes will not be required for them.
Examples / well-formed values
  • Interviewee discusses time spent in Los Angeles in great detail.
  • Interviewee discusses experiences of religious discrimination in great detail.
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Oral histories > compound objects: Institution
Property definition
  • Information for the purpose of facilitating browsing in the University of Washington Libraries Digital Collections online interface.
Recording values
  • Values entered for this property are not visible in the public interface.

  • Use the following value:
  • special collections
Examples / well-formed values
  • special collections
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Oral histories > compound objects: collectionPageCategory
Property definition
  • A category for the resource, for use in presenting resources by category on a collection landing page.
Recording values
  • Values entered for this property are not visible in the public interface.

  • Provide the category within which the resource should be presented on the collection landing page.
Examples / well-formed values
  • Novelesque Ballad - Various subjects
  • Institutional Publications
  • Ephemera
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries

Oral histories > Compound-object items

Oral histories > compound-object items: Title
Property definition
  • A name for the resource.
Recording values
  • Construct as follows for audio file (.mp3/.wav/etc.) items which are interview recordings:
  • [interviewee name] interview, audio
  • Construct as follows for image-file (.jpg) items which are images of interviewees:
  • Image of [interviewee name]
  • Provide the interviewee name in natural order.
  • Construct as follows for image-file (.jpg) items which are interview transcripts:
  • [interviewee name] interview, transcript
  • All compound-object items--audio files and image files--must have a title.
Examples / well-formed values
  • Solomon Maimon interview, audio
  • Image of Solomon Maimon
  • Solomon Maimon interview, transcript
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Oral histories > compound-object items: Digital Collection
Property definition
  • Name of the digital collection.
Recording values
  • Enter the following value:
  • Sephardic Studies Digital Collection at the University of Washington
  • Required for all compound-object items.
Examples / well-formed values
  • Sephardic Studies Digital Collection at the University of Washington
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Oral histories > compound-object items: Repository
Property definition
  • The institution holding the resource.
Recording values
  • This value will be entered by University of Washington Libraries Special Collections Staff following transfer of collection resources.
  • Value will be as follows:
  • University of Washington Libraries. Special Collections
Examples / well-formed values
  • University of Washington Libraries. Special Collections
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Oral histories > compound-object items: Type
Property definition
  • Describes the nature or genre of the content of the resource.
Recording values
  • Values entered for this property are not visible in the public interface.

  • For audio-file compound-object items (interview recordings), provide the following value:
  • Sound
  • For image-file compound-object items which are interviewee photographs, provide the following value:
  • StillImage
  • For image-file compound-object items which are interview transcripts, provide the following value:
  • Text
Examples / well-formed values
  • Sound
  • StillImage
  • Text
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Oral histories > compound-object items: Extent
Property definition
  • Size or duration of the resource.
Recording values
  • For audio files, enter the runtime of the digital access file.
  • Format runtime as HH:MM:SS.
Examples / well-formed values
  • 00:12:58
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Oral histories > compound-object items: Digital Format
Property definition
  • File format of a digital resource.
Recording values
  • Enter the file format of the file representing the compound-object item--that is, the access item.
  • This should be the format of the file given as a value for the digitalFileName property.
  • Use media types listed at http://www.iana.org/assignments/media-types/index.html.
  • For audio WAVE files, enter "audio/wav".
Examples / well-formed values
  • audio/mpeg
  • image/jpeg
  • application/pdf
  • text/plain
  • video/mp4
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Oral histories > compound-object items: Original Format
Property definition
  • File format, physical medium, and/or dimensions of the original resource.
Recording values
  • Values for Original Format must be taken from the RDA Carrier Type vocabulary.
  • For oral histories, enter one of the following values depending on which compound-object item you are describing.
  • For audio file items and for transcripts (.pdf or other document file formats):
  • online resource
  • For image files (interviewee photos):
  • sheet
Examples / well-formed values
  • online resource
  • sheet
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Oral histories > compound-object items: Physical Description
Property definition
  • Description of the physical attributes of the original medium in which data, sound, images, etc., are stored; the carrier; may include an extent statement.
Recording values
  • For oral histories, Physical Description is recorded at the compound-object-item level.
  • For SSDC oral history audio files and transcript files which are born-digital, do not record a Physical Description value.

  • For image-file items (photographs of interviewees), if information is available, provide a measurement or measurements of the physical media from which image files were created.
  • For photographs of interviewees, if information is available, record the height and width of the photo in centimeters, excluding any frame or mount, using Arabic numerals.
  • Use a space and “cm” (no following punctuation) after the measurements (“ cm”), to record as:
  • [height] x [width] cm
Examples / well-formed values
  • 10 x 15 cm
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Oral histories > compound-object items: Timecode Start
Property definition
  • When an audio file has been created from a portion of a longer original recording, the time at which the audio file's content begins in the original recording.
Recording values
  • If information is available, provide the timecode at which the clip included in the audio file begins.
  • Only applicable for compound-object audio files, when an audio file has been created from a portion of a longer original recording.
  • Record using the format HH:MM:SS.
Examples / well-formed values
  • 00:34:32
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Oral histories > compound-object items: Digital Reproduction Information
Property definition
  • Description of the digital conversion process, date scanned, etc.
Recording values
  • If available and applicable, provide details regarding the digitization of oral history compound-object items (interviewee photos, audio file, etc.).
Examples / well-formed values
  • Sample rate: 96KHz. Bit depth: 24. Issues encountered: Repaired several faulty splices. Date of transfer: 2019-01-04. Applicable conservation treatments: Baked and repaired several splices. De-noise and de-hum (iZotrope RX5).
  • Digital, stereo. Copied from analog recording to compact disc. Converted to 24 bit/48kHz Broadcast WAV format files by University of Washington Libraries in 2010.
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Oral histories > compound-object items: Original File Name
Property definition
  • The complete name including file extension of a digital file representing a resource to be described by one or more property/value pairs in CONTENTdm.
Recording values
  • Values entered for this property are not visible in the public interface.

  • When entering values in a metadata spreadsheet, each row will include values describing a resource--either a compound object, compound-object item, or standalone object.
  • Each row describing either a compound-object item or a standalone object must include a filename provided as a value for this property.
  • For ballads, compound-object items will either be audio files, image files (photographs) of a singer, or musical transcriptions (image or PDF files).
  • For oral histories, compound-object items will either be audio files, image files (photographs) of an interviewee, or transcripts (PDF files).
Examples / well-formed values
  • interview_001_audio.mp3
  • interviewee_001_photo.jpg
  • interview_001_transcript.pdf
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries

Metadata creation guidance: Default > Standalone items

Default > standalone items: Title
Property definition
  • A name for the resource.
Recording values
  • Find Unicode Title in Sephardic Studies Collection Master Catalog and revise according to the Aki Yerushalayim standard if needed. (Reference available here.)
  • Use a space, colon, space (" : ") to indicate the break between title and subtitle, even if no colon appears on title page.
  • Only Romanize the portion of the title that will be included in the Title field.
  • Following the title and colon, record a minimum of five words of the subtitle, followed by an ellipsis (“…”) if not recording the complete subtitle.
  • Subtitles should be lowercase, including the first word, except for proper nouns.
  • Names of languages are not capitalized in romanized Ladino (i.e.: Judeo Spanish is rendered as djudeo espanyol).
  • Do not romanize rashe tevot (Hebrew abbreviations).
  • Words of Hebrew-Aramaic origin should be romanized according to Aki Yerushalayim standards.
  • In cases where resources are printed in romanized Ladino, transcribe the title into this field exactly as it appears, even if it doesn’t conform to the Aki Yerushalayim standard.
  • All compound objects must have a title.
  • Construct as follows:
  • Audio: [song title]
  • (Do not enter square brackets around the song title.)
  • Romanize song titles according to the Aki Yerushalayim standard. (Reference available here.)
  • All compound objects must have a title.
  • Construct as follows:
  • [interviewee name] interview
  • Provide the interviewee name in natural order.
  • (Do not enter square brackets around the interviewee name.)
  • All compound objects must have a title.
  • Every page must have a title.
  • Provide the page number as the item title.
  • Where there is no pagination, a description of the page contents may be used as an item title.
  • Use sentence-case capitalization.
  • Do not spell out page numbers, use numerals.
  • All compound-object items must have a title.

  • In some cases, Hebrew letters may be used to mark pagination on alternating pages.
  • In these cases, provide a page number in Arabic numerals even though it is not marked on the page.
  • For pages where pagination is indicated using a Hebrew letter, provide this in parentheses following the Arabic numeral(s).
  • For pages without any pagination in this case (usually the pages facing those marked with a Hebrew letter), enter "(unnumbered)" following the Arabic numeral(s).
  • Construct as follows for audio-file (.mp3/.wav/etc.) items:
  • [song title] - audio
  • Enter the song title romanized according to Aki Yerushalayim.
  • Construct as follows for image-file (.jpg) items which are images of singers:
  • Image of [singer name], singer
  • Provide the singer name in natural order.
  • Construct as follows for image-file (.pdf) items which are digitized sheet music:
  • Musical Transcription: [song title]
  • (Do not enter square brackets around song titles or singer names.)
  • All compound-object items--audio files and image files--must have a title.
  • Construct as follows for audio file (.mp3/.wav/etc.) items which are interview recordings:
  • [interviewee name] interview, audio
  • Construct as follows for image-file (.jpg) items which are images of interviewees:
  • Image of [interviewee name]
  • Provide the interviewee name in natural order.
  • Construct as follows for image-file (.jpg) items which are interview transcripts:
  • [interviewee name] interview, transcript
  • All compound-object items--audio files and image files--must have a title.
Examples / well-formed values
  • Pavlo i Virjinia : romanso
  • Audio: Alavar kero al Dyo
  • Solomon Maimon interview
  • Cover
  • Inside cover
  • Title page
  • Publisher's introduction
  • Page 1
  • Page 2
  • Blank page

  • Page 2 (ב)
  • Page 3 (unnumbered)
  • Page 4 (ג)
  • Page 5 (unnumbered)
  • La Muerte del Duque de Gandía (í-a) - audio
  • Image of Bohora Cornell (Coronel), singer
  • Musical Transcription: La Muerte del Duque de Gandí
  • Solomon Maimon interview, audio
  • Image of Solomon Maimon
  • Solomon Maimon interview, transcript
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Default > standalone items: Title (Translated)
Property definition
  • A name for the resource created by translating an existing title.
Recording values
  • Translate the song title.
  • Use title-case capitalization.
  • Do not use a period at the end of the translated title.
Examples / well-formed values
  • The Abduction of Helen of Troy
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Default > standalone items: Title (Non-Latin Script)
Property definition
  • A name for the resource in non-Latin script.
Recording values
  • Enter the Ladino title of the resource in Hebrew script as it appears on the title page or other source of information.
  • Record title exactly as found, even with printer errors.
  • Roshe tevot (abbreviations) are considered part of the title and should be recorded.
  • Use a colon and space (": ") to indicate the break between title and subtitle, even if no colon appears on title page.
  • Following the title and colon, record a minimum of five words of the subtitle, followed by an ellipsis (“…”) if not recording the complete subtitle.
  • Optional: Record the subtitle as it appears in a matching MARC record verified by cataloging staff; record from the 245 subfield b.
  • Note: subtitles in 245 subfield b will be preceded by a colon (":"); parallel titles will be preceded by an equals sign (“=“) and should not be recorded.
  • Required for all compound objects.
Examples / well-formed values
  • פאב׳לו אי ב׳ירז׳יניאה: רומאנסו
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Default > standalone items: Title (ALA-LC Romanization)
Property definition
  • A non-Latin script title which has been Romanized according to the ALA-LC Romanization Tables.
Recording values
  • Search for Romanized title in LOC Ladino catalog.
  • If a potential match is found, confirm that it is the correct title. It may be helpful to review information included in the web display such as the publisher, printer, and publisher/printer locations.
  • Copy the Romanized title just as it appears in the LOC record, usually following the period after the author name.
  • When copying from LOC, retain this version: do not edit to match the Title value for the resource.
  • If no record exists, Romanize according to the ALA-LC Ladino romanization table.
  • When Romanizing a title, only include the portion transcribed in the Title field.
  • Note: Titles in the Library of Congress’ online Ladino catalog do not always conform to current ALA-LC romanization standards. Copy catalog those entries as-is into this field. If the title does not exist in the online catalog, romanize according to the ALA-LC standard.
  • Use space, colon, space (" : ") to indicate a break between title and subtitle, even if no colon appears on the title page.
  • Subtitles should be lowercase, including the first word, except for proper nouns.
  • Following the title and colon, record a minimum of five words of the subtitle, followed by an ellipsis (“…”) if not recording the complete subtitle.
  • Consult Hebraica Cataloging (pgs. 20-23) for instructions related to rashe tevot (Hebrew abbreviations).
  • Words of Hebrew-Aramaic origin should be romanized according to the ALA-LC Hebrew and Yiddish Romanization Table.
  • In cases where resources are printed in romanized Ladino, leave this field blank.
  • Required for all compound objects.
Examples / well-formed values
  • Pavlo y Virzhinyah : romanso
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Default > standalone items: Title (Harvard Romanization)
Property definition
  • A Ladino title in Hebrew script Romanized according to the Harvard Library standard.
Recording values
  • Search for the title in the Harvard Library HOLLIS online catalog.
  • When searching it helps to filter results by language and approximate year.
  • If a potentical match is found, copy the title just as it appears in the title field on HOLLIS.
  • If no record exists, do not create a Romanized title for this field.
  • Required for all standalone objects if available.
Examples / well-formed values
  • Sefer ḥovat ha-levavot shaʻar ha-biṭaḥon en ladino
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Default > standalone items: Interviewee
Property definition
  • A person interviewed.
Recording values
  • Provide the name of the interviewee.
  • When appropriate, search the Library of Congress Name Authority File via id.loc.gov for the interviewee name.
  • If a potential match is found, confirm that it is the person associated with the resource. It may be helpful to review information included in the web display such as source(s) of information and occupation (for persons), and/or to follow the links provided for exact and/or closely matching concepts from other schemes.
  • Copy the name string for use just as it appears at the top of the page, above the URI(s), including dates.
  • If no record exists, record personal names as "Lastname, Firstname".
  • When recording names without a match in the NAF, reuse the recorded form consistently when the same person or organization appears in the metadata for a different resource.
  • For a personal name like Alexander Ben Guiat, "Ben" is considered part of the first name and is transcribed as: "Guiat, Alexander Ben".
  • Separate multiple entries with a semicolon and space (“; “).
  • Order of values does not matter.
Examples / well-formed values
  • Maimon, Solomon
See also
Shareable link
MAP info | TOC | PROPERTY LIST
MIG Data Dictionaries
Default > standalone items: Interviewee Birthplace
Property definition
  • The place of birth of a person interviewed.
Recording values
  • For metadata creation taking place outside the University of Washington Libraries (UWL) Cataloging and Metadata Services unit:
  • Enter the place of birth of the interviewee in natural language, providing sufficient information to disambiguate place names as needed.
  • As a rule, include more information rather than less.
  • For example, when providing the name of a city, also provide the state, region, and/or country name(s) as available.
  • UWL Cataloging staff will use this information to create a structured value.
  • Separate multiple entries with a semicolon and space (“; “).
  • Order of values does not matter.
  • If multiple interviewees are associated with a resource, include the Interviewee value to which the birthplace corresponds in square brackets following.
  • Be sure to provide the value 'xyz' for the Cataloging property to indicate to cataloging staff that revision of the unstructured value is needed.

  • For UWL cataloging staff creating structured values:
  • Forms of the names should be derived from the Library of Congress Authority File.
  • Enter as follows:
  • Country--State or Province--City
  • Separate multiple entries with a semicolon and space (“; “).
  • Order of values does not matter.
  • If multiple interviewees are associated with a resource, include the Interviewee value to which the birthplace corresponds in square brackets following.
Examples / well-formed values
    See also
    Shareable link
    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries
    Default > standalone items: Primary Performer
    Property definition
    • A primary performer who is seen, heard, or otherwise prominently featured in the resource.
    Recording values
    • Provide the name of the primary singer featured in the recording.
    • When appropriate, search the Library of Congress Name Authority File via id.loc.gov for the name of the singer.
    • If a potential match is found, confirm that it is the person associated with the resource. It may be helpful to review information included in the web display such as source(s) of information and occupation (for persons), and/or to follow the links provided for exact and/or closely matching concepts from other schemes.
    • Copy the name string for use just as it appears at the top of the page, above the URI(s), including dates.
    • If no record exists, record personal names as "Lastname, Firstname".
    • When recording names without a match in the NAF, reuse the recorded form consistently when the same person or organization appears in the metadata for a different resource.
    • For a personal name like Alexander Ben Guiat, "Ben" is considered part of the first name and is transcribed as: "Guiat, Alexander Ben".
    • Separate multiple entries with a semicolon and space (“; “).
    • Order of values does not matter.
    Examples / well-formed values
    • Azose, Jack
    See also
    Shareable link
    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries
    Default > standalone items: Performer
    Property definition
    • A performer who is seen, heard, or otherwise featured in the resource.
    Recording values
    • Provide the names of other people who may be heard performing in the recording.
    • This can include singers or other performers.
    • When appropriate, search the Library of Congress Name Authority File via id.loc.gov for the name of a performer who may be heard in the song recording.
    • If a potential match is found, confirm that it is the person associated with the resource. It may be helpful to review information included in the web display such as source(s) of information and occupation (for persons), and/or to follow the links provided for exact and/or closely matching concepts from other schemes.
    • Copy the name string for use just as it appears at the top of the page, above the URI(s), including dates.
    • If no record exists, record personal names as "Lastname, Firstname".
    • When recording names without a match in the NAF, reuse the recorded form consistently when the same person or organization appears in the metadata for a different resource.
    • For a personal name like Alexander Ben Guiat, "Ben" is considered part of the first name and is transcribed as: "Guiat, Alexander Ben".
    • Separate multiple entries with a semicolon and space (“; “).
    • Order of values does not matter.
    Examples / well-formed values
    • Azose, Louise
    • Azose, Jack; Azose, Louise
    See also
    Shareable link
    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries
    Default > standalone items: Performer Birthplace
    Property definition
    • The place of birth of a primary performer featured in a resource.
    Recording values
    • For metadata creation taking place outside the University of Washington Libraries (UWL) Cataloging and Metadata Services unit:
    • Enter a performer birthplace in natural language, providing sufficient information to disambiguate place names as needed.
    • As a rule, include more information rather than less.
    • For example, when providing the name of a city, also provide the state, region, and/or country name(s) as available.
    • UWL Cataloging staff will use this information to create a structured value.
    • Be sure to provide the value 'xyz' for the Cataloging property to indicate to cataloging staff that revision of the unstructured value is needed.
    • Separate multiple entries with a semicolon and space (“; “).
    • Order of values does not matter.
    • If multiple performers are associated with a resource, include the Performer or Primary Performer value to which the birthplace corresponds in square brackets following.

    • For UWL cataloging staff creating structured values:
    • Forms of the names should be derived from the Library of Congress Authority File.
    • Enter as follows:
    • Country--State or Province--City
    • Separate multiple entries with a semicolon and space (“; “).
    • Order of values does not matter.
    • If multiple performers are associated with a resource, include the Performer or Primary Performer value to which the birthplace corresponds in square brackets following.
    Examples / well-formed values
    • [Natural-language values for review by cataloging staff:]
    • Ortaköy (Istanbul, Turkey)

    • [Structured values provided by cataloging staff:]
    • Turkey--Istanbul
    See also
    Shareable link
    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries
    Default > standalone items: Interviewer
    Property definition
    • The person who interviewed the interviewee.
    Recording values
    • Provide the name of the interviewer.
    • When appropriate, search the Library of Congress Name Authority File via id.loc.gov for the interviewer name.
    • If a potential match is found, confirm that it is the person associated with the resource. It may be helpful to review information included in the web display such as source(s) of information and occupation (for persons), and/or to follow the links provided for exact and/or closely matching concepts from other schemes.
    • Copy the name string for use just as it appears at the top of the page, above the URI(s), including dates.
    • If no record exists, record personal names as "Lastname, Firstname".
    • When recording names without a match in the NAF, reuse the recorded form consistently when the same person or organization appears in the metadata for a different resource.
    • For a personal name like Alexander Ben Guiat, "Ben" is considered part of the first name and is transcribed as: "Guiat, Alexander Ben".
    • Separate multiple entries with a semicolon and space (“; “).
    • Order of values does not matter.
    Examples / well-formed values
    • Droker, Howard
    See also
    Shareable link
    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries
    Default > standalone items: Videographer
    Property definition
    • A person who created the video recording.
    Recording values
    • Provide the name of the videographer--the person who created the video recording.
    • When appropriate, search the Library of Congress Name Authority File via id.loc.gov for the videographer name.
    • If a potential match is found, confirm that it is the person associated with the resource. It may be helpful to review information included in the web display such as source(s) of information and occupation (for persons), and/or to follow the links provided for exact and/or closely matching concepts from other schemes.
    • Copy the name string for use just as it appears at the top of the page, above the URI(s), including dates.
    • If no record exists, Record personal names as "Lastname, Firstname".
    • For a personal name like Alexander Ben Guiat, "Ben" is considered part of the first name and is transcribed as: "Guiat, Alexander Ben".
    • When recording names without a match in the NAF, reuse the recorded form consistently when the same person or organization appears in the metadata for a different resource.
    • Separate multiple entries with a semicolon and space (“; “).
    • Order of values does not matter.
    Examples / well-formed values
    • Meyers, Richard D.
    See also
    Shareable link
    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries
    Default > standalone items: Author
    Property definition
    • The person or the corporate body responsible for the textual content.
    Recording values
    • Search the Library of Congress Name Authority File via id.loc.gov for the author name (usually an individual).
    • If a potential match is found, confirm that it is the person associated with the resource: it may be helpful to review information included in the web display such as source(s) of information and occupation (for persons), and/or to follow the links provided for exact and/or closely matching concepts from other schemes.
    • Copy the name string for use just as it appears at the top of the page, above the URI(s), including dates.
    • If no record exists, Romanize the author name as it appears on the title page (or elsewhere if not on the title page) according to the ALA-LC Ladino romanization table.
    • When recording names without a match in the NAF, reuse the recorded form consistently when the same person or organization appears in the metadata for a different resource.
    • For a personal name like Alexander Ben Guiat, "Ben" is considered part of the first name and is transcribed as: "Guiat, Alexander Ben".
    • Separate multiple entries with a semicolon and space (“; “).
    • Order of values does not matter.
    • Author names usually appear on the title page after the following designations: el autor; kompuesto; por.
    Examples / well-formed values
    • Saint-Pierre, Bernardin de, 1737-1814.
    See also
    Shareable link
    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries
    Default > standalone items: Editor
    Property definition
    • A person or corporate body responsible for editing the textual or other content of the resource.
    Recording values
    • Search the Library of Congress Name Authority File via id.loc.gov for the editor name (usually an individual).
    • If a potential match is found, confirm that it is the person associated with the resource: it may be helpful to review information included in the web display such as source(s) of information and occupation (for persons), and/or to follow the links provided for exact and/or closely matching concepts from other schemes.
    • Copy the name string for use just as it appears at the top of the page, above the URI(s), including dates.
    • If no record exists, Romanize the editor name as it appears on the title page (or elsewhere if not on the title page) according to the ALA-LC Ladino romanization table.
    • Record personal names as "Lastname, Firstname".
    • For a personal name like Alexander Ben Guiat, "Ben" is considered part of the first name and is transcribed as: "Guiat, Alexander Ben".
    • Editor names usually appear on a title page after the following designations: editor.
    • If entering multiple values for this property, separate each using a semicolon and space (“; “). Order of values does not matter.
    Examples / well-formed values
    • Habib, Moiz
    See also
    Shareable link
    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries
    Default > standalone items: Publisher
    Property definition
    • A person or corporate body responsible for publishing the resource.
    Recording values
    • Search the Library of Congress Name Authority File via id.loc.gov for the printer name (could be an individual or a corporate body).
    • If a potential match is found, confirm that it is the person or corporate body associated with the resource. It may be helpful to review information included in the web display such as source(s) of information and occupation (for persons), and/or to follow the links provided for exact and/or closely matching concepts from other schemes.
    • Copy the name string for use just as it appears at the top of the page, above the URI(s), including dates.
    • If no record exists, Romanize the publisher name as it appears on the title page (or elsewhere if not on the title page) according to the ALA-LC Ladino romanization table.
    • Record personal names as "Lastname, Firstname".
    • For a personal name like Alexander Ben Guiat, "Ben" is considered part of the first name and is transcribed as: "Guiat, Alexander Ben".
    • When recording names without a match in the NAF, reuse the recorded form consistently when the same person or organization appears in the metadata for a different resource.
    • Publisher names usually appear on the title page after the following designations: publikado por mano; publikado por.
    • Separate multiple entries with a semicolon and space (“; “).
    • Order of values does not matter.
    Examples / well-formed values
    • Cherezli, Salomon Israel
    See also
    Shareable link
    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries
    Default > standalone items: Publisher Location
    Property definition
    • A location, usually a city, associated with the publisher of the resource.
    Recording values
    • For metadata creation taking place outside the University of Washington Libraries (UWL) Cataloging and Metadata Services unit:
    • Enter a location associated with the publisher in natural language, providing sufficient information to disambiguate place names as needed.
    • As a rule, include more information rather than less.
    • For example, when providing the name of a city, also provide the state, region, and/or country name(s) as available.
    • If multiple publishers are associated with a resource, include the Publisher value to which the location corresponds in square brackets following.
    • UWL Cataloging staff will use this information to create a structured value.
    • Be sure to provide the value 'xyz' for the Cataloging property to indicate to cataloging staff that revision of the unstructured value is needed.
    • Separate multiple entries with a semicolon and space (“; “).
    • Order of values does not matter.

    • For UWL cataloging staff creating structured values:
    • Forms of the names should be derived from the Library of Congress Authority File.
    • Enter as follows:
    • Country--State or Province--City
    • Separate multiple entries with a semicolon and space (“; “).
    • Order of values does not matter.
    • If multiple publishers are associated with a resource, include the Publisher value to which the location corresponds in square brackets following.
    Examples / well-formed values
    • [Natural-language values for review by cataloging staff:]
    • İzmir (Turkey)
    • Jerusalem, Israel [Cherezli, Salomon Israel]; Istanbul, Turkey [Joseph, Benjamin Ben]

    • [Structured values provided by cataloging staff:]
    • Turkey--Izmir
    • Jerusalem [Cherezli, Salomon Israel]; Turkey--Istanbul [Joseph, Benjamin Ben]
    See also
    Shareable link
    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries
    Default > standalone items: Printer
    Property definition
    • A person or corporate body responsible for printing the resource.
    Recording values
    • Search the Library of Congress Name Authority File via id.loc.gov for the printer name (could be an individual or a corporate body).
    • If a potential match is found, confirm that it is the person or corporate body associated with the resource: it may be helpful to review information included in the web display such as source(s) of information and occupation (for persons), and/or to follow the links provided for exact and/or closely matching concepts from other schemes.
    • Copy the name string for use just as it appears at the top of the page, above the URI(s), including dates.
    • If no record exists, Romanize the printer name as it appears on the title page (or elsewhere if not on the title page) according to the ALA-LC Ladino romanization table.
    • Record personal names as "Lastname, Firstname".
    • For a personal name like Alexander Ben Guiat, "Ben" is considered part of the first name and is transcribed as: "Guiat, Alexander Ben".
    • Printer names usually appear on title page after the following designations: bi-defus; estamparia el; estampada; estampado en la estamparia; estampa; estamparor; emprimeria (also abbreviated to emp.); nidpas.
    • If entering multiple values for this property, separate each using a semicolon and space ("; "). Order of values does not matter.
    Examples / well-formed values
    • Emprimeria Arditi
    See also
    Shareable link
    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries
    Default > standalone items: Printer Location
    Property definition
    • A location, usually a city, associated with the printer of the resource.
    Recording values
    • For metadata creation taking place outside the University of Washington Libraries (UWL) Cataloging and Metadata Services unit:
    • Enter a location associated with the printer in natural language, providing sufficient information to disambiguate place names as needed.
    • As a rule, include more information rather than less.
    • For example, when providing the name of a city, also provide the state, region, and/or country name(s) as available.
    • If multiple printers are associated with a resource, include the Printer value to which the location corresponds in square brackets following.
    • UWL Cataloging staff will use this information to create a structured value.
    • Be sure to provide the value 'xyz' for the Cataloging property to indicate to cataloging staff that revision of the unstructured value is needed.
    • Separate multiple entries with a semicolon and space (“; “).
    • Order of values does not matter.

    • For UWL cataloging staff creating structured values:
    • Forms of the names should be derived from the Library of Congress Authority File.
    • Enter as follows:
    • Country--State or Province--City
    • Separate multiple entries with a semicolon and space (“; “).
    • Order of values does not matter.
    • If multiple printers are associated with a resource, include the Printer value to which the location corresponds in square brackets following.
    Examples / well-formed values
    • [Natural-language values for review by cataloging staff:]
    • İzmir (Turkey)
    • Jerusalem, Israel [Cherezli, Salomon Israel]; Istanbul, Turkey [Joseph, Benjamin Ben]

    • [Structured values provided by cataloging staff:]
    • Turkey--Izmir
    • Jerusalem [Cherezli, Salomon Israel]; Turkey--Istanbul [Joseph, Benjamin Ben]
    See also
    Shareable link
    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries
    Default > standalone items: Translator
    Property definition
    • A person or corporate body responsible for translating the textual content of the resource from one language into another.
    Recording values
    • Search the Library of Congress Name Authority File via id.loc.gov for the translator name.
    • If a potential match is found, confirm that it is the person associated with the resource: it may be helpful to review information included in the web display such as source(s) of information and occupation (for persons), and/or to follow the links provided for exact and/or closely matching concepts from other schemes.
    • Copy the name string for use just as it appears at the top of the page, above the URI(s), including dates.
    • If no record exists, Romanize the translator name as it appears on the title page (or elsewhere if not on the title page) according to the ALA-LC Ladino romanization table.
    • Record personal names as "Lastname, Firstname".
    • For a personal name like Alexander Ben Guiat, "Ben" is considered part of the first name and is transcribed as: "Guiat, Alexander Ben".
    • Translator names usually appear on title page after the following designations: adaptado; aranzhado; imitado; rezumido; reskrito; trezlador; trezladado; tradusio.
    • If entering multiple values for this property, separate each using a semicolon and space ("; "). Order of values does not matter.
    Examples / well-formed values
    • Guiat, Alexander Ben, 1869-1924.
    See also
    Shareable link
    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries
    Default > standalone items: Donor
    Property definition
    • A person or corporate body who donated a physical item to the University of Washington Libraries or an affiliated academic unit.
    Recording values
    • Find donor name in Sephardic Studies Collection Master Catalog.
    • Contributor is considered a donor if the catalog notes that the item is property of Sephardic Studies.
    • When appropriate, search the Library of Congress Name Authority File via id.loc.gov for the donor name.
    • If a potential match is found, confirm that it is the person associated with the resource: it may be helpful to review information included in the web display such as source(s) of information and occupation (for persons), and/or to follow the links provided for exact and/or closely matching concepts from other schemes.
    • Copy the name string for use just as it appears at the top of the page, above the URI(s), including dates.
    • If no record exists, record personal names as "Lastname, Firstname".
    • When recording names without a match in the NAF, reuse the recorded form consistently when the same person or organization appears in the metadata for a different resource.
    • For a personal name like Alexander Ben Guiat, "Ben" is considered part of the first name and is transcribed as: "Guiat, Alexander Ben".
    • Separate multiple entries with a semicolon and space (“; “).
    • Order does not matter.
    • Either a donor or lender value should be provided for every standalone object.
    Examples / well-formed values
    • Azose, Isaac
    See also
    Shareable link
    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries
    Default > standalone items: Lender
    Property definition
    • A person or corporate body who lent a physical item to the University of Washington Libraries or an affiliated academic unit for creation of a digital surrogate.
    Recording values
    • Find lender name in Sephardic Studies Collection Master Catalog.
    • Contributor is considered a lender if the catalog notes that item is still property of that individual.
    • When appropriate, search the Library of Congress Name Authority File via id.loc.gov for the lender name.
    • If a potential match is found, confirm that it is the person associated with the resource: it may be helpful to review information included in the web display such as source(s) of information and occupation (for persons), and/or to follow the links provided for exact and/or closely matching concepts from other schemes.
    • Copy the name string for use just as it appears at the top of the page, above the URI(s), including dates.
    • If no record exists, record personal names as "Lastname, Firstname".
    • For a personal name like Alexander Ben Guiat, "Ben" is considered part of the first name and is transcribed as: "Guiat, Alexander Ben".
    • If entering multiple values for this property, separate each using a semicolon and space ("; "). Order of values does not matter.
    • For every item, either a donor or lender must be credited.
    Examples / well-formed values
    • Maimon, Rabbi Solomon
    See also
    Shareable link
    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries
    Default > standalone items: Former Owner
    Property definition
    • A person or corporate body who previously owned a physical or digital resource.
    Recording values
    • When searching for donor or lender in Sephardic Studies Collection Master Catalog, some contributions will be recorded as "Person A via Person B." In that case, Person A is the former owner, and their name belongs in this field.
    • When appropriate, search the Library of Congress Name Authority File via id.loc.gov for the lender name.
    • If a potential match is found, confirm that it is the person associated with the resource: it may be helpful to review information included in the web display such as source(s) of information and occupation (for persons), and/or to follow the links provided for exact and/or closely matching concepts from other schemes.
    • Copy the name string for use just as it appears at the top of the page, above the URI(s), including dates.
    • If no record exists, record personal names as "Lastname, Firstname".
    • For a personal name like Alexander Ben Guiat, "Ben" is considered part of the first name and is transcribed as: "Guiat, Alexander Ben".
    • Separate multiple entries with a semicolon and space (“; “).
    • Order of values does not matter.
    Examples / well-formed values
    • Benezra, Henry
    See also
    Shareable link
    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries
    Default > standalone items: Date (EDTF)
    Property definition
    • Prominent date for the resource, such as the date of creation of the original resource.
    Recording values
    • Values entered for this property are not visible in the public interface.

    • Reflects the date in the "Date" field.
    • Express all dates, including date ranges, using Library of Congress' Extended Date Time Format.
    • Creating well-formed values for resources in the Sephardic Studies Digital Collection may require first converting date values from lunar to Gregorian calendar systems.
    • The most recent version of the Library of Congress' summary of EDTF is available at https://www.loc.gov/standards/datetime/.
    • Six formats are recommended for values in Date, each corresponding to a specific EDTF format:
    • If the value of Date is YYYY, enter YYYY.
    • If the value of Date is YYYY?, enter YYYY?
    • If the value of Date is [month] DD, YYYY, enter YYYY-MM-DD.
    • If the value of Date is [month], YYYY, enter YYYY-MM.
    • If the value of Date is between YYYY and YYYY, enter YYYY/YYYY.
    • If the value of Date is between YYYY and YYYY?, enter YYYY?/YYYY?
    • If the value of Date is not any of the above, consult the EDTF spedification to determine the appropriate notation.
    • Date-Edtf value should agree with dates values entered in Date and Dates fields.
    Examples / well-formed values
    • If the Date field = "1940" then Date EDTF = "1940"
    • If the Date field = "1910?" then Date EDTF = "1910?"
    • If Date field = "May 9, 2001" then Date EDTF = "2001-05-09"
    • If Date field = "January 2008" then Date EDTF = "2008-01"
    • If Date field = "between 1930 and 1939" then Date EDTF = "1930/1939"
    • If Date field = "between 1855 and 1999?" then Date EDTF = "1855?/1999?"
    See also
    Shareable link
    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries
    Default > standalone items: Date
    Property definition
    • Prominent date for the resource, such as the date of creation of the original resource.
    Recording values
    • Enter the date (generally a year only) as reflected on the title page.
    • If only the lunar or Gregorian year is recorded, only enter that year. Do not convert between calendar systems.
    • If both Gregorian and lunar years are recorded, only enter the Gregorian year.
    • Do not enter chronograms.
    • If no date present on item, generate an estimate based on similar items in other collections: LOC Ladino catalog, Harvard University Library, and the National Library of Israel are viable options.
    • Required for all standalone objects.
    Examples / well-formed values
    • 5651 [example of lunar year]
    • 1923 [example of Gregorian year]
    • ca. 1900
    • not before 1900
    • after 1900 [example of estimate]
    See also
    Shareable link
    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries
    Default > standalone items: Dates
    Property definition
    • Prominent years for the resource, such as the date(s) of creation of the original resource; the expected value is a list of each and every pertinent year.
    Recording values
    • Values entered for this property are not visible in the public interface.

    • Reflects the date in the "Date" field pertinent to the overall object.
    • Creating well-formed values for resources in the Sephardic Studies Digital Collection may require first converting date values from lunar to Gregorian calendar systems.
    • Enter the year or years only.
    • When the value of Date is YYYY, enter YYYY.
    • When the value of Date is YYYY?, enter an eleven year date range, five years on either side of the uncertain date.
    • When the value of Date is [month] DD, YYYY, enter the year only in the following format: YYYY.
    • When the value of Date is [month], YYYY, enter the year only in the following format: YYYY.
    • When the value of Date is between YYYY and YYYY, enter all years in the date range in the following format: YYYY YYYY YYYY etc.
    • When the value of Date is between YYYY and YYYY?, enter all years in the date range plus five years before the earliest date and five years after the latest date, in the following format: YYYY YYYY YYYY etc.
    • This field is indexed and enables date searching in CONTENTdm.
    • The Dates value should agree with date values entered in Date-Edtf and Date fields.
    Examples / well-formed values
    • 1939
    • 1939?
    • 1939 1940 1941 1942 1943 1944 1945
    • 1934 1935 1936 1937 1938 1939 1940 1941 1942 1943 1944 1945 1946 1947 1948 1949 1950
    See also
    Shareable link
    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries
    Default > standalone items: Interviewee Biography
    Property definition
    • Biographical information about a person interviewed.
    Recording values
    • Enter brief biographical information about the interviewee.
    • Provide primarily biographical information as mentioned in the interview and/or related to topics discussed in the interview.
    Examples / well-formed values
    • Lela Abravanel was born in Salonica [Thessaloniki] Greece. She discusses her childhood in Las Kampanyas, a suburb of Salonica, and how she spoke French with her parents.
    See also
    Shareable link
    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries
    Default > standalone items: Notes
    Property definition
    • An account of the resource.
    Recording values
    • Enter any information of importance that is not represented elsewhere.
    • Start each distinct note entry on a new line.
    • When entering values in a spreadsheet, note that depending on the spreadsheet-editing application, CTRL + ENTER, ALT + ENTER, or another key combination can be used to enter a new line within a cell.
    Examples / well-formed values
    • Title value taken from cover, title page missing from digitized volume.
    • Song from father's pizmonim manuscript.
    • Uniquely Sephardic in origin. Given its subject matter, this ballad has been transmitted both orally and in written form, in Pesach hagaddahs. The only extant versions are from the Eastern tradition and one version from Crypto Portuguese Jews. Thus, an earlier version must have existed among Peninsular Jews. There is no evidence of its existence among non-Jews.
    • Rabbi Maimon discusses his education at Yeshiva University (00:05:30), his return to Seattle and installment as rabbi (00:10:50), and challenges faced by the Sephardic community in Seattle (00:10:12).
    See also
    Shareable link
    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries
    Default > standalone items: Subjects (LCSH)
    Property definition
    • The topic of the resource.
    Recording values
    • University of Washington Libraries (UWL) cataloging staff will provide a value or values for this property.
    • For metadata creation taking place outside the UWL Cataloging and Metadata Services unit:
    • Do not provide a value for this property.
    • Be sure to provide the value 'xyz' for the Cataloging property to indicate to cataloging staff that a value is needed.
    • For textual resources, be sure to record a staffNotes value which provides the needed information for UWL cataloging staff to perform subject analysis.
    • For details about the information needed by cataloging staff, contact the collection manager(s) or metadata liaison(s).
    • University of Washington Libraries (UWL) cataloging staff will provide a value or values for this property.
    • For metadata creation taking place outside the UWL Cataloging and Metadata Services unit:
    • Do not provide a value for this property.
    • Be sure to provide the value 'xyz' for the Cataloging property to indicate to cataloging staff that a value is needed.
    • For oral histories, be sure to record a value for the Index property which provides needed information for UWL cataloging staff to perform subject analysis. Cataloging staff may also use transcripts for subject analysis.
    • For details about the information needed by cataloging staff, contact the collection manager(s) or metadata liaison(s).
    Examples / well-formed values
    • High holidays--Liturgy--Texts
    • Sacred songs
    • Bible. Ruth--Commentaries
    • Ladino language--Grammar--Textbooks
    • Sephardim--Washington (State)--Interviews
    • Jews--Washington (State)--Interviews
    • Jews--Washington (State)--History
    • Temple de Hirsch (Seattle, Wash.)
    • Fish trade--Washington (State)--History
    See also
    Shareable link
    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries
    Default > standalone items: Genre/Form (LCGFT)
    Property definition
    • The genre or form of the resource, expressed using values selected from Library of Congress Genre/Form Terms.
    Recording values
    • University of Washington Libraries (UWL) cataloging staff will provide a value or values for this property.
    • For metadata creation taking place outside the UWL Cataloging and Metadata Services unit:
    • Do not provide a value for this property.
    • Be sure to provide the value 'xyz' for the Cataloging property to indicate to cataloging staff that a value is needed.
    • When the resource does not use English, be sure to use the Staff Notes property to provide an informal description which will provide cataloging staff with the information needed to provide genre and form terms.
    • For details about the information needed by cataloging staff, contact the collection manager(s) or metadata liaison(s).
    • 📚 For review/input by cataloging staff

    • Use the following value taken from Library of Congress Genre/Form Terms:
    • Newsletters
    • 📚 For review/input by cataloging staff

    • Use the following value taken from Library of Congress Genre/Form Terms:
    • Photographs
    • 📚 For review/input by cataloging staff

    • Use the following value taken from Library of Congress Genre/Form Terms:
    • Records (Documents)
    Examples / well-formed values
    • Newsletters
    • Photographs
    • Records (Documents)
    See also
    Shareable link
    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries
    Default > standalone items: Related OCLC Record
    Property definition
    • Number for an OCLC record related to the digital resource, for example, a record for a physical item from which the digital surrogate was created.
    Recording values
    • University of Washington Libraries (UWL) cataloging staff will provide a value or values for this property if applicable.
    • For metadata creation taking place outside the University of Washington Libraries (UWL) Cataloging and Metadata Services unit:
    • Do not provide a value for this property.
    • Be sure to provide the value 'xyz' for the Cataloging property to indicate to cataloging staff that a value is needed if applicable.
    • When the resource does not use English, be sure to use the Staff Notes property to provide information which will allow cataloging staff to identify any related records.
    • For details about the information needed by cataloging staff, contact the collection manager(s) or metadata liaison(s).
    • For UWL cataloging staff:
    • Separate multiple values with a semicolon.
    Examples / well-formed values
    • [Values provided by cataloging staff:]
    • 37917418
    • 27382728
    • 37917418; 27382728
    See also
    Shareable link
    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries
    Default > standalone items: Object Type
    Property definition
    • The nature or genre of the resource.
    Recording values
    • Contact the collection manager(s) or metadata liaison(s) regarding appropriate Object Type values for standalone objects in the collection.
    Examples / well-formed values
    • book
    • newspaper
    • ballads
    • oral histories
    See also
    Shareable link
    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries
    Default > standalone items: Romancero Theme
    Property definition
    • A translation of the song's thematic classification, printed in Spanish on pages 219-221 of "Romances judeo-españoles de Oriente: nueva recolección."
    Recording values
    Examples / well-formed values
    • Capture and seduction by taking aboard ship
    • Girl enticed into boat and abducted; Capture by luring; Capture and seduction by taking aboard ship; Apple tree as symbol of seduction
    See also
    Shareable link
    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries
    Default > standalone items: Cross Reference
    Property definition
    • Information about other sources in which a description of or information about the resource may be found.
    Recording values
    • Provide any references to other Sephardic ballad collections given for this ballad as it is described in "Romances judeo-españoles de Oriente : nueva recolección".
    • Locate the song in "Romances judeo-españoles de Oriente: nueva recolección" by Rina Benmayor and Judith H. Mauleón.

    • Copy the list of cross references--including the resource (or an abbreviation denoting a resource) and numeric page number--which appears after the word "bibliographia."
    • Include full titles for each abbreviation.
    • Separate multiple values with a semicolon and space ("; ").

    • Resource abbreviations are as follows:
    • AMP - Armistead, Samuel G., with the collaboration of Selma Margaretten, Paloma Montero, and Ana Valenciano and with musical transcriptions edited by Israel J. Katz. El romancero judeo-español en el Archivo Menéndez Pidal (Catálogo-índice de romances y canciones) (Catálogo-índice de romances y canciones ) 3 vols. Madrid: Catedra-Seminario Menéndez Pidal, 1977, 387; 393; 358 pp. bit.ly/1NMq6Pt
    • Attias - Attias, Moshe, 1972. Romancero sefardí: romanzas y cantes populares en judeo-espanol. 2nd ed. Jerusalem: Ben-Zewi Institute, 1961, 350 pp.
    • FLSJ - Armistead, Samuel G. and Joseph H. Silverman. Folk Literature of the Sephardic Jews. Series in eight volumes. Catalog online at: http://www.sephardifolklit.org/
    • Larrea - Larrea, Palacín, Arcadio de. Romances de Tetuán, 2 vols. Madrid: C.S.I.C., 1952, 351; 377 pp.
    • MP - Menéndez Pidal, Ramón. “Catálogo del romancero judío-español,"" Cultura Española, 4 (1906), 1045–1077; 5 (1907), 161–199. bit.ly/1NT9xPL
    • RJEO - Benmayor, R. Romances judeo-españoles de Oriente: Nueva recolección. Musical transcriptions by Judith H. Mauleón. Madrid: Gredos, 1979.
    • Optional: Provide information about one or more sources which provide additional information about the resource.
    Examples / well-formed values
    • RJEO 5a; AMP F7; MP 45; FLSJ IX, 45
    • RJEO - Benmayor, R. Romances judeo-españoles de Oriente: Nueva recolección. Musical transcriptions by Judith H. Mauleón. Madrid: Gredos, 1979.
    • AMP - Armistead, Samuel G., with the collaboration of Selma Margaretten, Paloma Montero, and Ana Valenciano and with musical transcriptions edited by Israel J. Katz. El romancero judeo-español en el Archivo Menéndez Pidal (Catálogo-índice de romances y canciones) (Catálogo-índice de romances y canciones ) 3 vols. Madrid: Catedra-Seminario Menéndez Pidal, 1977, 387; 393; 358 pp. http://bit.ly/1NMq6Pt
    • MP - Menéndez Pidal, Ramón. “Catálogo del romancero judío-español,"" Cultura Española, 4 (1906), 1045–1077; 5 (1907), 161–199. http://bit.ly/1NT9xPL
    • FLSJ - Armistead, Samuel G. and Joseph H. Silverman. Folk Literature of the Sephardic Jews. Series in eight volumes. Catalog online at: http://www.sephardifolklit.org/
    See also
    Shareable link
    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries
    Default > standalone items: Individuals Discussed
    Property definition
    • Individuals given significant attention in the resource.
    Recording values
    • Provide names of individuals given significant attention in the interview.
    • When appropriate, search the Library of Congress Name Authority File via id.loc.gov for the names of individuals discussed in the oral history.
    • If a potential match is found, confirm that it is the person associated with the resource. It may be helpful to review information included in the web display such as source(s) of information and occupation (for persons), and/or to follow the links provided for exact and/or closely matching concepts from other schemes.
    • Copy the name string for use just as it appears at the top of the page, above the URI(s), including dates.
    • If no record exists, record personal names as "Lastname, Firstname".
    • When recording names without a match in the NAF, reuse the recorded form consistently when the same person appears in the metadata for a different resource.
    • For a personal name like Alexander Ben Guiat, "Ben" is considered part of the first name and is transcribed as: "Guiat, Alexander Ben".
    • Separate multiple entries with a semicolon and space (“; “).
    • Order of values does not matter.
    Examples / well-formed values
    • Adatto, Albert; Maimon, Bension
    See also
    Shareable link
    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries
    Default > standalone items: Organizations Discussed
    Property definition
    • Organizations given significant attention in the resource.
    Recording values
    • Provide the name or names of an organization or organizations given significant attention in the interview.
    • When appropriate, search the Library of Congress Name Authority File via id.loc.gov for the names of organizations discussed in the oral history.
    • If a potential match is found, confirm that it is the organization associated with the resource: it may be helpful to review information included in the web display such as source(s) of information, and/or to follow the links provided for exact and/or closely matching concepts from other schemes.
    • Copy the name string for use just as it appears at the top of the page, above the URI(s), including dates.
    • If no match is found, record an organization name.
    • When recording names without a match in the NAF, reuse the recorded form consistently when the same person appears in the metadata for a different resource.
    • Separate multiple entries with a semicolon and space (“; “).
    • Order of values does not matter.
    Examples / well-formed values
    • Congregation Ezra Bessaroth
    • Congregation Ezra Bessaroth; Longacres Race Track
    See also
    Shareable link
    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries
    Default > standalone items: Geographic Coverage
    Property definition
    • The spatial characteristics given significant attention in the resource.
    Recording values
    • For metadata creation taking place outside the UWL Cataloging and Metadata Services unit:
    • Enter broad and local geographic locations given significant attention in the resource in natural language, providing sufficient information to disambiguate place names as needed.
    • As a rule, include more information rather than less.
    • For example, when providing the name of a city, also provide the state, region, and/or country name(s) as available.
    • Cataloging staff will use this information to create a structured value.
    • Separate multiple entries with a semicolon and space (“; “).

    • For UWL cataloging staff creating structured values:
    • Forms of the names should be derived from the Library of Congress Authority File.
    • Enter as follows:
    • Country--State or Province--City
    • For neighborhoods or other types of locales below the city level, enter an LCSH heading in the Subjects (LCSH) field.
    • Separate multiple entries with a semicolon and space (“; “).
    Examples / well-formed values
    • [Natural-language values for review by cataloging staff:]
    • Tacoma, Washington, USA
    • Rhodes, Greece

    • [Structured values provided by cataloging staff:]
    • United States--Washington (State)--Tacoma
    • Greece--Rhodes
    See also
    Shareable link
    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries
    Default > standalone items: Time Period Discussed
    Property definition
    • Representation of time periods given significant attention in the resource.
    Recording values
    • Enter a period in time as needed.
    • If practical, enter the date using one of the following formats:
    • YYYY
    • YYYY?
    • [month spelled out] [day], YYYY
    • [month spelled out], YYYY
    • between YYYY and YYYY
    • between YYYY and YYYY?
    • When a date or date range is not practical, prefer an LCSH heading reprenting the time period.
    • When none of the options above are practical, enter the most practical representation of the time period.
    Examples / well-formed values
    • 1964
    • between 1986 and 1990
    • Twentieth century
    • Nineteen forties
    See also
    Shareable link
    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries
    Default > standalone items: Index
    Property definition
    • An abridged transcript, or list of contents, for the resource.
    Recording values
    • Enter an abridged transcript or a list of contents.
    • Start each list entry on a new line preceded by a hyphen.
    • When entering index values in a spreadsheet, note that depending on the spreadsheet-editing application, CTRL + ENTER, ALT + ENTER, or another key combination can be used to enter a new line within a cell.
    • Non-English interviews do not need an index.
    Examples / well-formed values
    • Topics presented in order of discussion on recording:
    • - More on civil rights and local activism.
    • - Phone rings in the background
    • - Made presentation to Jim Ellis.
    • - Federal case involving racism and employment opportunities.
    • - Nixon Administration.
    • - 1989 Supreme Court case about employment and racism.
    • - Had a series of mini strokes that forced me to retire.
    • - Narrator's comments about people he has talked to. Lists names. I'm not a journalist. This is an oral history. Intention is to create oral history of the whole city.
    • - Intention to publish. - Discusses the scope of the publication.
    • - Events in the 1960s precede the scope. - Discuss other potential subjects for the project.
    See also
    Shareable link
    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries
    Default > standalone items: Recording Location
    Property definition
    • A location, usually a city, where a resource was recorded.
    Recording values
    • For metadata creation taking place outside the University of Washington Libraries (UWL) Cataloging and Metadata Services unit:
    • Enter a recording location in natural language, providing sufficient information to disambiguate place names as needed.
    • As a rule, include more information rather than less.
    • For example, when providing the name of a city, also provide the state, region, and/or country name(s) as available.
    • UWL Cataloging staff will use this information to create a structured value.
    • Be sure to provide the value 'xyz' for the Cataloging property to indicate to cataloging staff that revision of the unstructured value is needed.
    • Separate multiple entries with a semicolon and space (“; “).
    • Order of values does not matter.
    • When reusing existing metadata, include only the place name in the value for Recording Location.
    • Add any other relevant information as a value for the Notes property.
    • For example, adapt existing value “Seattle, in her home” as:
    • Recording Location: Seattle, Washington, USA
    • Notes: Recorded in the home of [name].

    • For UWL cataloging staff creating structured values:
    • Forms of the names should be derived from the Library of Congress Authority File.
    • Enter as follows:
    • Country--State or Province--City
    • Separate multiple entries with a semicolon and space (“; “).
    • Order of values does not matter.
    Examples / well-formed values
    • [Natural-language values for review by cataloging staff:]
    • Seattle, WA, USA

    • [Structured values provided by cataloging staff:]
    • United States--Washington (State)--Seattle
    See also
    Shareable link
    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries
    Default > standalone items: Language
    Property definition
    • A language of the resource.
    Recording values
    • Enter language names, fully spelled out, as they appear in the ISO 639 Code Tables "Language Name(s)" column. Note that Ladino is listed as such, and not as Judeo-Spanish or Judezmo.
    • Separate multiple values using a semicolon and space (“; “).
    • Order of values does not matter.
    • Required for all standalone objects.
    Examples / well-formed values
    • Ladino
    • Hebrew
    • Ladino; Hebrew
    See also
    Shareable link
    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries
    Default > standalone items: Digital Collection
    Property definition
    • Name of the digital collection.
    Recording values
    • Enter the following value:
    • Sephardic Studies Digital Collection at the University of Washington
    • Required for all standalone objects.
    Examples / well-formed values
    • Sephardic Studies Digital Collection at the University of Washington
    See also
    Shareable link
    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries
    Default > standalone items: Sephardic Studies Accession Number (SSAN)
    Property definition
    • A number assigned to each resource in the Sephardic Studies Digital Collection Master Catalog; each resource's number is unique in the Catalog.
    Recording values
    • Find the item in Sephardic Studies Collection Master Catalog in column AX (File Name) and enter its corresponding number here.
    • Required for all standalone objects.
    Examples / well-formed values
    • ST00495
    • LAA0003
    See also
    Shareable link
    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries
    Default > standalone items: Restrictions
    Property definition
    • Any restrictions on the use of a resource.
    Recording values
    • Required for all standalone objects.
    • Enter the following value:
    • To inquire about permissions, contact sephstud@uw.edu. Please cite the Sephardic Studies Accession Number.
    Examples / well-formed values
    • To inquire about permissions, contact sephstud@uw.edu. Please cite the Sephardic Studies Accession Number.
    See also
    Shareable link
    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries
    Default > standalone items: Rights URI
    Property definition
    • URI that dereferences to a rights statement.
    Recording values
    Examples / well-formed values
    • http://rightsstatements.org/vocab/CNE/1.0/
    See also
    Shareable link
    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries
    Default > standalone items: Ordering Information
    Property definition
    • Instructions for ordering.
    Recording values
    • Enter the following value:
    • Reproductions are not available for order.
    Examples / well-formed values
    • Reproductions are not available for order.
    See also
    Shareable link
    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries
    Default > standalone items: Repository
    Property definition
    • The institution holding the resource.
    Recording values
    • This value will be entered by University of Washington Libraries Special Collections Staff following transfer of collection resources.
    • Value will be as follows:
    • University of Washington Libraries. Special Collections
    • This value will be entered by University of Washington Libraries Special Collections Staff following transfer of collection resources.
    • Value will be as follows:
    • University of Washington Libraries. Special Collections
    Examples / well-formed values
    • University of Washington Libraries. Special Collections
    • University of Washington Libraries. Special Collections
    See also
    Shareable link
    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries
    Default > standalone items: Repository Collection
    Property definition
    • Collection to which the original resource is a part.
    Recording values
    • Where applicable, this value will be entered by University of Washington Libraries Special Collections Staff following transfer of collection resources.
    • Where a finding aid for an archival collection including the resource exists, the value will be constructed using the collection name and accession number given there.
    Examples / well-formed values
    • 🚧 🚧 🚧
    See also
    Shareable link
    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries
    Default > standalone items: Repository Collection Guide
    Property definition
    • URI to an EAD finding aid.
    Recording values
    • Where applicable, this value will be entered by University of Washington Libraries Special Collections Staff following transfer of collection resources.
    • Where a finding aid for an archival collection including the resource exists, the value will be the Ark URL for this finding aid in ArchivesWest.
    Examples / well-formed values
    • 🚧 🚧 🚧
    See also
    Shareable link
    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries
    Default > standalone items: Type
    Property definition
    • Describes the nature or genre of the content of the resource.
    Recording values
    • Values entered for this property are not visible in the public interface.

    • Values for this property must come from the DCMI Type Vocabulary.
    • For ballad, and oral history compound objects, provide the following value:
    • Sound
    • Values for this property must come from the DCMI Type Vocabulary.
    • For textual-resource compound objects, provide the following value:
    • Text
    • Values for this property must come from the DCMI Type Vocabulary.
    • For image-file compound-object items (digitized pages), provide one or both of the following values depending on content:
    • Text
    • StillImage

    • Separate multiple entries with a semicolon and space (“; “).
    • Order of values does not matter.
    • For audio-file compound-object items (ballad recordings), provide the following value:
    • Sound
    • For image-file compound-object items which are performer photographs, provide the following value:
    • StillImage
    • For image-file compound-object items which are digitized sheet music, provide the following value:
    • Image
    • For audio-file compound-object items (interview recordings), provide the following value:
    • Sound
    • For image-file compound-object items which are interviewee photographs, provide the following value:
    • StillImage
    • For image-file compound-object items which are interview transcripts, provide the following value:
    • Text
    Examples / well-formed values
    • Sound
    • Text
    • Text
    • StillImage
    • StillImage; Text
    • Sound
    • StillImage
    • Image
    • Sound
    • StillImage
    • Text
    See also
    Shareable link
    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries
    Default > standalone items: Extent
    Property definition
    • Size or duration of the resource.
    Recording values
    • For audio files, enter the runtime of the digital access file.
    • Format runtime as HH:MM:SS.
    Examples / well-formed values
    • 00:12:58
    See also
    Shareable link
    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries
    Default > standalone items: Digital Format
    Property definition
    • File format of a digital resource.
    Recording values
    • Enter the file format of the file representing the compound-object item--that is, the access item.
    • This should be the format of the file given as a value for the digitalFileName property.
    • Use media types listed at http://www.iana.org/assignments/media-types/index.html.
    • For audio WAVE files, enter "audio/wav".
    Examples / well-formed values
    • audio/mpeg
    • image/jpeg
    • application/pdf
    • text/plain
    • video/mp4
    See also
    Shareable link
    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries
    Default > standalone items: Original Format
    Property definition
    • File format, physical medium, and/or dimensions of the original resource.
    Recording values
    • 🚧 🚧 🚧
    Examples / well-formed values
    • audiocassette
    • sheet
    • online resource
    • sheet
    See also
    Shareable link
    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries
    Default > standalone items: Physical Description
    Property definition
    • Description of the physical attributes of the original medium in which data, sound, images, etc., are stored; the carrier; may include an extent statement.
    Recording values
    • For textual resources, Physical Description is recorded at the compound-object level.
    • If information is available, provide a description of the physical resource from which the digital surrogate (compound object) was created.
    • If information is available, include both the number of pages and a measurement for the volume.

    • Recording number of pages:
    • For pages numbered with Roman or Arabic numerals, record the number of the final page in either Roman or Arabic numerals followed by “pages”.
    • When a volume includes both Roman- and Arabic-numbered pages, provide the roman numeral followed by a comma and space (“, “), the Arabic numeral followed by a space, and “pages”.
    • If pages are not numbered, record a number of pages in Arabic numerals followed by a space (“ “) and “pages”.
    • Optionally, record an unnumbered page count before or after an Arabic- and/or Roman-numbered page count, separating with a comma and space (“, “).

    • Recording physical dimensions:
    • Add this information following page information, separating with a comma and space (“, “).
    • Record the height of the volume in centimeters.
    • Record the height using Arabic numerals.
    • Use a space and “cm” (no following punctuation) after the numeral(s) (“ cm”).
    • For ballad recordings, Physical Description is recorded at the compound-object-item level.
    • If information is available, provide a description of the physical resource from which the digital surrogate (compound-object item) was created.

    • For audio-file items (song recordings), if information is available, provide a runtime for the analog media from which the audio file was created.
    • Format runtime as HH:MM:SS.

    • For image-file items (photographs of performers, digitized sheet music), if information is available, provide a measurement or measurements of the physical media from which image files were created.

    • For photographs of performers, if information is available, record the height and width of the photo in centimeters, excluding any frame or mount, using Arabic numerals.
    • Use a space and “cm” (no following punctuation) after the measurements (“ cm”), to record as:
    • [height] x [width] cm

    • For sheet music, if information is available, record the height of the sheet or volume in centimeters.
    • Record the height using Arabic numerals.
    • Use a space and “cm” (no following punctuation) after the numeral(s) (“ cm”), to record as:
    • [height] cm
    • For oral histories, Physical Description is recorded at the compound-object-item level.
    • For SSDC oral history audio files and transcript files which are born-digital, do not record a Physical Description value.

    • For image-file items (photographs of interviewees), if information is available, provide a measurement or measurements of the physical media from which image files were created.
    • For photographs of interviewees, if information is available, record the height and width of the photo in centimeters, excluding any frame or mount, using Arabic numerals.
    • Use a space and “cm” (no following punctuation) after the measurements (“ cm”), to record as:
    • [height] x [width] cm
    Examples / well-formed values
    • xi pages, 25 cm
    • 25 pages, 25 cm
    • xi, 25 pages, 25 cm
    • 15 unnumbered pages, 30 cm
    • xi, 25 pages, 15 unnumbered pages, 30 cm
    • 2 unnumbered pages, 300 pages, 35 cm
    • 00:32:23
    • 10 x 15 cm
    • 28 cm
    • 10 x 15 cm
    See also
    Shareable link
    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries
    Default > standalone items: Timecode Start
    Property definition
    • When an audio file has been created from a portion of a longer original recording, the time at which the audio file's content begins in the original recording.
    Recording values
    • If information is available, provide the timecode at which the clip included in the audio file begins.
    • Only applicable for compound-object audio files, when an audio file has been created from a portion of a longer original recording.
    • Record using the format HH:MM:SS.
    Examples / well-formed values
    • 00:34:32
    See also
    Shareable link
    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries
    Default > standalone items: Digital Reproduction Information
    Property definition
    • Description of the digital conversion process, date scanned, etc.
    Recording values
    • If available, provide details regarding the digitization of the text.
    • For texts, digital reproduction details are assumed to be the same or similar for all compound-object items (pages), so information should be recorded at the compound-object level.
    • If available and applicable, provide details regarding the digitization of ballad compound-object items (singer photo, audio file, etc.).
    • If available and applicable, provide details regarding the digitization of oral history compound-object items (interviewee photos, audio file, etc.).
    Examples / well-formed values
    • Scanned from original text or image at 400 dpi, saved in TIFF format, resized and enhanced using Adobe Photoshop, and imported as JPEG2000 using Contentdm software's JPEG2000 Extension. 2006.
    • Sample rate: 96KHz. Bit depth: 24. Issues encountered: Repaired several faulty splices. Date of transfer: 2019-01-04. Applicable conservation treatments: Baked and repaired several splices. De-noise and de-hum (iZotrope RX5).
    • Digital, stereo. Copied from analog recording to compact disc. Converted to 24 bit/48kHz Broadcast WAV format files by University of Washington Libraries in 2010.
    See also
    Shareable link
    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries
    Default > standalone items: Cataloging
    Property definition
    • Messages for local catalogers.
    Recording values
    • Values entered for this property are not visible in the public interface.

    • Enter "xyz" to request the creation and/or review of values for one or more of the following fields by UWL cataloging staff:
    • Subjects (LCSH)
    • Genre/Form (LCGFT)
    • Related OCLC Record
    • Geographic fields: Geographic Coverage, Interviewee Birthplace, Performer Birthplace, Recording Location, Printer Location, Publisher Location
    Examples / well-formed values
    • xyz
    See also
    Shareable link
    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries
    Default > standalone items: Staff Notes
    Property definition
    • Notes for staff only, notes of an administrative nature.
    Recording values
    • Values entered for this property are not visible in the public interface.

    • Staff Notes values are hidden in the public CONTENTdm interface.
    • These values will be used by University of Washington Libraries (UWL) cataloging staff to assign controlled values for the following fields for textual resources.

    • For books, catalogers may supply values for:
    • Subjects (LCSH)
    • Genre/Form (LCGFT)
    • Related OCLC Record
    • Printer Location
    • Publisher Location

    • For ephemera, catalogers may supply values for:
    • Subjects (LCSH)
    • Genre/Form (LCGFT)

    • To facilitate cataloging of books:
    • Briefly summarize the genre, subject, and intended use.
    • Descriptions of novels should briefly summarize the arc of the story.
    • For religious texts, such as prayer books and bibles, note for which Jewish holiday and/or ritual they are used.
    • Note if the work is a translation, and the author and language of the original text.

    • To facilitate cataloging of ephemera:
    • Record any relevant information characterizing the resource which isn’t included in values for any other metadata field.
    • Translate non-English text or terminology to aid cataloging staff in metadata creation.

    • Required for all textual-resource compound objects which will require subject or genre/form analysis from UWL cataloging staff.
    • Staff Notes values are hidden in the public CONTENTdm interface.
    • These values will be used by University of Washington Libraries (UWL) cataloging staff to assign controlled values for the following fields for ballad recordings:
    • Genre/Form (LCGFT)
    • Performer Birthplace
    • Recording Location

    • Staff notes should not be necessary for UWL catalogers entering structured values for ballad recordings.
    • Other staff notes may be entered as needed.
    • Staff Notes values are hidden in the public CONTENTdm interface.
    • These values will be used by University of Washington Libraries (UWL) cataloging staff to assign controlled values for the following fields for oral histories:
    • Subjects (LCSH)
    • Genre/Form (LCGFT)
    • Geographic Coverage
    • Interviewee Birthplace
    • Recording Location

    • Add any available relevant information which is not given in Index, Notes, or other property values, which will assist UWL catalogers assigning values for Subjects (LCSH) and Geographic Coverage.
    • Catalogers will the use unstructured values provided for Interviewee Birthplace and Recording Location to create structured values for these fields, so Staff Notes will not be required for them.
    Examples / well-formed values
    • Rosh ha-Shanah postcard featuring a pink plush heart with the words “טובה לשנה” “La-Shanah Tovah” [A Happy New Year] embroidered in the center with gold glitter. Postcard features a glitter design of a Star of David below two doves. In the center of the star is the image of a woman’s hand shaking a man’s hand. Printed in English, “With My Good Wishes And Hearty Greetings, A Happy New Year” and “Le-Shanah Tova Tikhtevu” [May you be inscribed for a Happy New Year] printed in Hebrew characters.
    See also
    Shareable link
    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries
    Default > standalone items: Institution
    Property definition
    • Information for the purpose of facilitating browsing in the University of Washington Libraries Digital Collections online interface.
    Recording values
    • Values entered for this property are not visible in the public interface.

    • Use the following value:
    • special collections
    Examples / well-formed values
    • special collections
    See also
    Shareable link
    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries
    Default > standalone items: collectionPageCategory
    Property definition
    • A category for the resource, for use in presenting resources by category on a collection landing page.
    Recording values
    • Values entered for this property are not visible in the public interface.

    • Provide the category within which the resource should be presented on the collection landing page.
    Examples / well-formed values
    • Novelesque Ballad - Various subjects
    • Institutional Publications
    • Ephemera
    See also
    Shareable link
    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries
    Default > standalone items: Original File Name
    Property definition
    • The complete name including file extension of a digital file representing a resource to be described by one or more property/value pairs in CONTENTdm.
    Recording values
    • Values entered for this property are not visible in the public interface.

    • When entering values in a metadata spreadsheet, each row will include values describing a resource--either a compound object, compound-object item, or standalone object.
    • Each row describing either a compound-object item or a standalone object must include a filename provided as a value for this property.
    • Enter the filename of the image file for the page described in the spreadsheet row.
    • When entering values in a metadata spreadsheet, each row will include values describing a resource--either a compound object, compound-object item, or standalone object.
    • Each row describing either a compound-object item or a standalone object must include a filename provided as a value for this property.
    • For ballads, compound-object items will either be audio files, image files (photographs) of a singer, or musical transcriptions (image or PDF files).
    • For oral histories, compound-object items will either be audio files, image files (photographs) of an interviewee, or transcripts (PDF files).
    Examples / well-formed values
    • ST-001.jpg
    • 86_El_Robo_de_Elena.mp3
    • Estrea_Chiprut.jpg
    • La_Muerte_del_Duque_de_Gandía.pdf
    • interview_001_audio.mp3
    • interviewee_001_photo.jpg
    • interview_001_transcript.pdf
    See also
    Shareable link
    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries

    Field configuration details and further information

    Information for CONTENTdm administrators and additional details.

    Metadata field configuration: Title

    Source data: 'title' | p88

    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries

    Metadata field configuration: Title (Translated)

    Source data: 'titleTranslated' | p130

    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries

    Metadata field configuration: Title (Non-Latin Script)

    Source data: 'titleNonLatin' | p116

    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries

    Metadata field configuration: Title (ALA-LC Romanization)

    Source data: 'titleALALCR' | p117

    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries

    Metadata field configuration: Title (Harvard Romanization)

    Source data: 'titleHarvard' | p118

    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries

    Metadata field configuration: Interviewee

    Source data: 'interviewee' | p45

    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries

    Metadata field configuration: Interviewee Birthplace

    Source data: 'intervieweeBirthplace' | p131

    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries

    Metadata field configuration: Primary Performer

    Source data: 'primaryPerformer' | p132

    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries

    Metadata field configuration: Performer

    Source data: 'performer' | p138

    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries

    Metadata field configuration: Performer Birthplace

    Source data: 'performerBirthplace' | p139

    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries

    Metadata field configuration: Interviewer

    Source data: 'interviewer' | p47

    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries

    Metadata field configuration: Videographer

    Source data: 'videographer' | p140

    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries

    Metadata field configuration: Author

    Source data: 'author' | p6

    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries

    Metadata field configuration: Editor

    Source data: 'editor' | p114

    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries

    Metadata field configuration: Publisher

    Source data: 'publisher' | p119

    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries

    Metadata field configuration: Publisher Location

    Source data: 'publisherLocation' | p120

    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries

    Metadata field configuration: Printer

    Source data: 'printer' | p121

    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries

    Metadata field configuration: Printer Location

    Source data: 'printerLocation' | p122

    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries

    Metadata field configuration: Translator

    Source data: 'translator' | p115

    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries

    Metadata field configuration: Donor

    Source data: 'donor' | p125

    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries

    Metadata field configuration: Lender

    Source data: 'lender' | p126

    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries

    Metadata field configuration: Former Owner

    Source data: 'formerOwner' | p127

    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries

    Metadata field configuration: Date (EDTF)

    Source data: 'dateEdtf' | p23

    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries

    Metadata field configuration: Date

    Source data: 'date' | p21

    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries

    Metadata field configuration: Dates

    Source data: 'datesAll' | p26

    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries

    Metadata field configuration: Interviewee Biography

    Source data: 'intervieweeBiography' | p46

    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries

    Metadata field configuration: Notes

    Source data: 'notes' | p55

    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries

    Metadata field configuration: Subjects (LCSH)

    Source data: 'subjectsLcsh' | p85

    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries

    Metadata field configuration: Genre/Form (LCGFT)

    Source data: 'genreFormLcgft' | p128

    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries

    Metadata field configuration: Related OCLC Record

    Source data: 'relatedOclcNo' | p124

    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries

    Metadata field configuration: Object Type

    Source data: 'objectType' | p57

    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries

    Metadata field configuration: Romancero Theme

    Source data: 'romancero' | p141

    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries

    Metadata field configuration: Cross Reference

    Source data: 'crossReference' | p133

    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries

    Metadata field configuration: Individuals Discussed

    Source data: 'individualsDiscussed' | p136

    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries

    Metadata field configuration: Organizations Discussed

    Source data: 'organizationsDiscussed' | p137

    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries

    Metadata field configuration: Geographic Coverage

    Source data: 'geographicCoverage' | p53

    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries

    Metadata field configuration: Time Period Discussed

    Source data: 'timePeriodDiscussed' | p98

    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries

    Metadata field configuration: Index

    Source data: 'index' | p135

    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries

    Metadata field configuration: Recording Location

    Source data: 'recordingLocation' | p142

    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries

    Metadata field configuration: Language

    Source data: 'language' | p50

    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries

    Metadata field configuration: Digital Collection

    Source data: 'digitalCollection' | p28

    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries

    Metadata field configuration: Sephardic Studies Accession Number (SSAN)

    Source data: 'ssan' | p123

    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries

    Metadata field configuration: Restrictions

    Source data: 'restrictions' | p75

    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries

    Metadata field configuration: Rights URI

    Source data: 'rightsUri' | p77

    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries

    Metadata field configuration: Ordering Information

    Source data: 'orderingInformation' | p59

    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries

    Metadata field configuration: Repository

    Source data: 'repository' | p71

    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries

    Metadata field configuration: Repository Collection

    Source data: 'repositoryCollection' | p72

    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries

    Metadata field configuration: Repository Collection Guide

    Source data: 'repositoryCollectionGuide' | p73

    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries

    Metadata field configuration: Type

    Source data: 'type' | p90

    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries

    Metadata field configuration: Extent

    Source data: 'extent' | p37

    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries

    Metadata field configuration: Digital Format

    Source data: 'digitalFormat' | p29

    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries

    Metadata field configuration: Original Format

    Source data: 'originalFormat' | p62

    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries

    Metadata field configuration: Physical Description

    Source data: 'physicalDescription' | p67

    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries

    Metadata field configuration: Timecode Start

    Source data: 'timecodeStart' | p143

    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries

    Metadata field configuration: Digital Reproduction Information

    Source data: 'digitalReproductionInformation' | p31

    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries

    Metadata field configuration: Cataloging

    Source data: 'cataloging' | p11

    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries

    Metadata field configuration: Staff Notes

    Source data: 'staffNotes' | p79

    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries

    Metadata field configuration: Institution

    Source data: 'institution' | p44

    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries

    Metadata field configuration: collectionPageCategory

    Source data: 'collectionPageCategory' | p146

    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries

    Metadata field configuration: Original File Name

    Source data: 'digitalFileName' | p134

    MAP info | TOC | PROPERTY LIST
    MIG Data Dictionaries