p16786coll3 MAP

From 6fefc920b2426acd54dfbf1a941f33b2a7f280a5 Mon Sep 17 00:00:00 2001 From: Benjamin Riesenberg Date: Fri, 19 Apr 2024 22:06:50 -0700 Subject: [PATCH] update to use CSS --- html/p16786coll3.html | 2173 +++++++++++++++++++++++++++++++++++++---- 1 file changed, 2006 insertions(+), 167 deletions(-) diff --git a/html/p16786coll3.html b/html/p16786coll3.html index fe97d99..0a61b1d 100644 --- a/html/p16786coll3.html +++ b/html/p16786coll3.html @@ -3,7 +3,7 @@ - + p16786coll3 MAP @@ -650,6 +650,21 @@

text > Compound objects

this field exactly as it appears, even if it doesn’t conform to the Aki Yerushalayim standard.

All compound objects must have a title.

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.

@@ -716,6 +731,18 @@

text > Compound objects

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.

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.

@@ -794,6 +821,29 @@

text > Compound objects

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.

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.

@@ -855,6 +905,13 @@

text > Compound objects

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.

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.

@@ -926,6 +983,23 @@

text > Compound objects

Author names usually appear on the title page after the following designations: el autor; kompuesto; por.

Required for all compound objects.

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.

@@ -997,6 +1071,22 @@

text > Compound objects

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.

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.

@@ -1068,6 +1158,23 @@

text > Compound objects

publikado por mano; publikado por.

Separate multiple entries with a semicolon and space (“; “).

Order of values does not matter.

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.

@@ -1144,6 +1251,28 @@

text > Compound objects

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.

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.

@@ -1219,6 +1348,22 @@

text > Compound objects

(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.

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.

@@ -1295,6 +1440,28 @@

text > Compound objects

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.

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.

@@ -1372,6 +1539,23 @@

text > Compound objects

aranzhado; imitado; rezumido; reskrito; trezlador; trezladado; tradusio.

Separate multiple entries with a semicolon and space (“; “).

Order of values does not matter.

When appropriate, search the Library of Congress Name Authority File via id.loc.gov for the translator name.

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.

@@ -1445,6 +1629,24 @@

text > Compound objects

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.

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.

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.

@@ -1518,6 +1720,24 @@

text > Compound objects

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.

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.

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.

@@ -1590,6 +1810,24 @@

text > Compound objects

name and is transcribed as: "Guiat, Alexander Ben".

Separate multiple entries with a semicolon and space (“; “).

Order of values does not matter.

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.

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.

@@ -1662,6 +1900,23 @@

text > Compound objects

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.

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.

@@ -1728,7 +1983,14 @@

text > Compound objects

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.

- +

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.

+ @@ -1806,6 +2068,24 @@

text > Compound objects

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.

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.

@@ -1874,6 +2154,17 @@

text > Compound objects

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.

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.

@@ -1941,6 +2232,17 @@

text > Compound objects

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 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).

@@ -2011,6 +2313,18 @@

text > Compound objects

genre and form terms.

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 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).

@@ -2080,6 +2394,19 @@

text > Compound objects

manager(s) or metadata liaison(s).

For UWL cataloging staff:

Separate multiple values with a semicolon.

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.

@@ -2140,6 +2467,9 @@

text > Compound objects

Enter one of the following values:

book

newspaper

Enter one of the following values:

book

newspaper

@@ -2198,6 +2528,8 @@

text > Compound objects

Optional: Provide information about one or more sources which provide additional information about the resource.
Optional: Provide information about one or more sources which provide additional information + about the resource.

@@ -2261,6 +2593,13 @@

text > Compound objects

Separate multiple values using a semicolon and space (“; “).

Order of values does not matter.

Required for all compound objects where applicable.

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.

@@ -2320,6 +2659,9 @@

text > Compound objects

Enter the following value:

Sephardic Studies Digital Collection at the University of Washington

Required for all compound objects.

Enter the following value:

Sephardic Studies Digital Collection at the University of Washington

Required for all compound objects.

@@ -2378,6 +2720,9 @@

text > Compound objects

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.

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.

@@ -2436,6 +2781,10 @@

text > Compound objects

Enter the following value:

To inquire about permissions, contact sephstud@uw.edu. Please cite the Sephardic Studies Accession Number.

Required for all compound objects.

Enter the following value:

To inquire about permissions, contact sephstud@uw.edu. Please cite the Sephardic Studies + Accession Number.

@@ -2493,6 +2842,8 @@

text > Compound objects

Unless otherwise instructed, enter the following URI: http://rightsstatements.org/vocab/CNE/1.0/.
Required for all compound objects.
Unless otherwise instructed, enter the following URI: http://rightsstatements.org/vocab/CNE/1.0/.
Required for all compound objects.

@@ -2549,6 +2900,8 @@

text > Compound objects

Enter the following value:
Reproductions are not available for order.
Enter the following value:
Reproductions are not available for order.

@@ -2607,6 +2960,10 @@

text > Compound objects

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

@@ -2665,6 +3022,10 @@

text > Compound objects

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.

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.

@@ -2723,6 +3084,10 @@

text > Compound objects

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.

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.

@@ -2781,6 +3146,9 @@

text > Compound objects

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 textual-resource compound objects, provide the following value:

Text

@@ -2857,6 +3225,27 @@

text > Compound objects

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 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”).

@@ -2920,6 +3309,10 @@

text > Compound objects

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, 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.

@@ -2990,6 +3383,19 @@

text > Compound objects

Recording Location

Printer Location

Publisher Location

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

@@ -3068,6 +3474,29 @@

text > Compound objects

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 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.

@@ -3139,6 +3568,8 @@

text > Compound objects

Values entered for this property are not visible in the public interface.

Use the following value:

special collections

Use the following value:

special collections

@@ -3268,6 +3699,20 @@

text > Compound-object items

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).

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).

@@ -3335,6 +3780,9 @@

text > Compound-object items

Enter the following value:

Sephardic Studies Digital Collection at the University of Washington

Required for all compound-object items.

Enter the following value:

Sephardic Studies Digital Collection at the University of Washington

Required for all compound-object items.

@@ -3393,6 +3841,10 @@

text > Compound-object items

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

@@ -3455,6 +3907,13 @@

text > Compound-object items

StillImage

Separate multiple entries with a semicolon and space (“; “).

Order of values does not matter.

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.

@@ -3516,6 +3975,11 @@

text > Compound-object items

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".

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".

@@ -3581,6 +4045,11 @@

text > Compound-object items

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.

Enter the filename of the image file for the page described in the spreadsheet row.

@@ -3644,6 +4113,11 @@

song > Compound objects

(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:

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.

@@ -3701,6 +4175,9 @@

song > Compound objects

Translate the song title.

Use title-case capitalization.

Do not use a period at the end of the translated title.

Translate the song title.

Use title-case capitalization.

Do not use a period at the end of the translated title.

@@ -3770,6 +4247,21 @@

song > Compound objects

name and is transcribed as: "Guiat, Alexander Ben".

Separate multiple entries with a semicolon and space (“; “).

Order of values does not matter.

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.

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.

@@ -3840,6 +4332,22 @@

song > Compound objects

name and is transcribed as: "Guiat, Alexander Ben".

Separate multiple entries with a semicolon and space (“; “).

Order of values does not matter.

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.

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.

@@ -3917,8 +4425,30 @@

song > Compound objects

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 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 @@ -3995,6 +4525,26 @@

song > Compound objects

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.

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.

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.

@@ -4070,6 +4620,26 @@

song > Compound objects

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.

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.

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.

@@ -4142,6 +4712,24 @@

song > Compound objects

name and is transcribed as: "Guiat, Alexander Ben".

Separate multiple entries with a semicolon and space (“; “).

Order of values does not matter.

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.

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.

@@ -4214,6 +4802,23 @@

song > Compound objects

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.

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.

@@ -4276,6 +4881,9 @@

song > Compound objects

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.

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.

@@ -4352,6 +4960,24 @@

song > Compound objects

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.

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.

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.

@@ -4421,6 +5047,18 @@

song > Compound objects

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.

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.

@@ -4489,6 +5127,13 @@

song > Compound objects

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.

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.

@@ -4545,6 +5190,8 @@

song > Compound objects

Enter the following value:
ballads
Enter the following value:
ballads

@@ -4601,6 +5248,11 @@

song > Compound objects

Search for the song title on pages 219-221 of "Romances judeo-españoles de Oriente : nueva recolección." +
Separate multiple thematic elements with a semicolon and space ("; ").
Begin each new thematic element with a capital letter.
If no match is found, do not provide a value.
Search for the song title on pages 219-221 of "Romances judeo-españoles de Oriente : nueva recolección."
Separate multiple thematic elements with a semicolon and space ("; ").
Begin each new thematic element with a capital letter.

song > Compound objects

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.
Provide any references to other Sephardic ballad collections given for this ballad as it is described in "Romances judeo-españoles de Oriente : nueva recolección".
Locate the song in "Romances judeo-españoles de Oriente: nueva recolección" by Rina + Benmayor and Judith H. Mauleó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.

@@ -4767,6 +5435,30 @@

song > Compound objects

Country--State or Province--City

Separate multiple entries with a semicolon and space (“; “).

Order of values does not matter.

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.

@@ -4829,6 +5521,11 @@

song > Compound objects

Separate multiple values using a semicolon and space (“; “).

Order of values does not matter.

Required for all compound objects.

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.

@@ -4888,6 +5585,9 @@

song > Compound objects

Enter the following value:

Sephardic Studies Digital Collection at the University of Washington

Required for all compound objects.

Enter the following value:

Sephardic Studies Digital Collection at the University of Washington

Required for all compound objects.

@@ -4949,6 +5649,12 @@

song > Compound objects

Ladino Audio Archive tab in column P (Digitized File Name) and enter its corresponding number here.

Required for all compound objects.

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.

@@ -5007,6 +5713,10 @@

song > Compound objects

Enter the following value:

To inquire about permissions, contact sephstud@uw.edu. Please cite the Sephardic Studies Accession Number.

Required for all compound objects.

Enter the following value:

To inquire about permissions, contact sephstud@uw.edu. Please cite the Sephardic Studies + Accession Number.

@@ -5064,6 +5774,8 @@

song > Compound objects

Unless otherwise instructed, enter the following URI: http://rightsstatements.org/vocab/CNE/1.0/.
Required for all compound objects.
Unless otherwise instructed, enter the following URI: http://rightsstatements.org/vocab/CNE/1.0/.
Required for all compound objects.

@@ -5120,6 +5832,8 @@

song > Compound objects

Enter the following value:
Reproductions are not available for order.
Enter the following value:
Reproductions are not available for order.

@@ -5178,6 +5892,10 @@

song > Compound objects

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

@@ -5236,6 +5954,10 @@

song > Compound objects

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.

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.

@@ -5294,6 +6016,10 @@

song > Compound objects

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.

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.

@@ -5352,6 +6078,9 @@

song > Compound objects

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 ballad, and oral history compound objects, provide the following value:

Sound

@@ -5420,6 +6149,19 @@

song > Compound objects

Recording Location

Printer Location

Publisher Location

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

@@ -5483,6 +6225,14 @@

song > Compound objects

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 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.

@@ -5541,6 +6291,8 @@

song > Compound objects

Values entered for this property are not visible in the public interface.

Use the following value:

special collections

Use the following value:

special collections

@@ -5666,6 +6418,16 @@

song > Compound-object items

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:

[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.

@@ -5725,6 +6487,9 @@

song > Compound-object items

Enter the following value:

Sephardic Studies Digital Collection at the University of Washington

Required for all compound-object items.

Enter the following value:

Sephardic Studies Digital Collection at the University of Washington

Required for all compound-object items.

@@ -5783,6 +6548,10 @@

song > Compound-object items

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

@@ -5846,6 +6615,14 @@

song > Compound-object items

For image-file compound-object items which are digitized sheet music, provide the following value:

Image

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

@@ -5904,6 +6681,8 @@

song > Compound-object items

For audio files, enter the runtime of the digital access file.
Format runtime as HH:MM:SS.
For audio files, enter the runtime of the digital access file.
Format runtime as HH:MM:SS.

@@ -5963,6 +6742,11 @@

song > Compound-object items

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".

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".

@@ -6028,6 +6812,13 @@

song > Compound-object items

audiocassette

For image files (singer photos) and digitized sheet music:

sheet

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

@@ -6100,6 +6891,22 @@

song > Compound-object items

Use a space and “cm” (no following punctuation) after the numeral(s) (“ cm”), to record as:

[height] 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

@@ -6162,6 +6969,11 @@

song > Compound-object items

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.

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.

@@ -6218,6 +7030,8 @@

song > Compound-object items

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 ballad + compound-object items (singer photo, audio file, etc.).

@@ -6286,6 +7100,14 @@

song > Compound-object items

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).

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).

@@ -6351,6 +7173,11 @@

oh > Compound objects

Provide the interviewee name in natural order.

(Do not enter square brackets around the interviewee name.)

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.

@@ -6420,6 +7247,21 @@

oh > Compound objects

name and is transcribed as: "Guiat, Alexander Ben".

Separate multiple entries with a semicolon and space (“; “).

Order of values does not matter.

Provide the name of the interviewee.

When appropriate, search the Library of Congress Name Authority File via id.loc.gov for the interviewee name.

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.

@@ -6496,6 +7338,28 @@

oh > Compound objects

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.

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.

@@ -6570,6 +7434,21 @@

oh > Compound objects

name and is transcribed as: "Guiat, Alexander Ben".

Separate multiple entries with a semicolon and space (“; “).

Order of values does not matter.

Provide the name of the interviewer.

When appropriate, search the Library of Congress Name Authority File via id.loc.gov for the interviewer name.

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.

@@ -6639,6 +7518,21 @@

oh > Compound objects

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.

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.

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.

@@ -6714,6 +7608,26 @@

oh > Compound objects

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.

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.

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.

@@ -6789,6 +7703,26 @@

oh > Compound objects

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.

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.

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.

@@ -6861,6 +7795,24 @@

oh > Compound objects

name and is transcribed as: "Guiat, Alexander Ben".

Separate multiple entries with a semicolon and space (“; “).

Order of values does not matter.

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.

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.

@@ -6933,6 +7885,23 @@

oh > Compound objects

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.

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.

@@ -6995,6 +7964,9 @@

oh > Compound objects

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.

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.

@@ -7071,6 +8043,24 @@

oh > Compound objects

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.

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.

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.

@@ -7131,6 +8121,9 @@

oh > Compound objects

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.

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.

@@ -7198,6 +8191,18 @@

oh > Compound objects

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.

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.

@@ -7267,6 +8272,18 @@

oh > Compound objects

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).

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).

@@ -7333,7 +8350,14 @@

oh > Compound objects

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.

- +

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.

+ @@ -7389,6 +8413,8 @@

oh > Compound objects

Enter the following value:
oral histories
Enter the following value:
oral histories

@@ -7458,6 +8484,21 @@

oh > Compound objects

name and is transcribed as: "Guiat, Alexander Ben".

Separate multiple entries with a semicolon and space (“; “).

Order of values does not matter.

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.

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.

@@ -7526,6 +8567,20 @@

oh > Compound objects

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.

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.

@@ -7598,6 +8653,23 @@

oh > Compound objects

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 (“; “).

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 (“; “).

@@ -7732,6 +8804,12 @@

oh > Compound objects

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.

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.

@@ -7822,6 +8900,30 @@

oh > Compound objects

Country--State or Province--City

Separate multiple entries with a semicolon and space (“; “).

Order of values does not matter.

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.

@@ -7884,6 +8986,11 @@

oh > Compound objects

Separate multiple values using a semicolon and space (“; “).

Order of values does not matter.

Required for all compound objects.

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.

@@ -7943,6 +9050,9 @@

oh > Compound objects

Enter the following value:

Sephardic Studies Digital Collection at the University of Washington

Required for all compound objects.

Enter the following value:

Sephardic Studies Digital Collection at the University of Washington

Required for all compound objects.

@@ -8004,6 +9114,12 @@

oh > Compound objects

Ladino Audio Archive tab in column P (Digitized File Name) and enter its corresponding number here.

Required for all compound objects.

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.

@@ -8062,6 +9178,10 @@

oh > Compound objects

Enter the following value:

To inquire about permissions, contact sephstud@uw.edu. Please cite the Sephardic Studies Accession Number.

Required for all compound objects.

Enter the following value:

To inquire about permissions, contact sephstud@uw.edu. Please cite the Sephardic Studies + Accession Number.

@@ -8119,6 +9239,8 @@

oh > Compound objects

Unless otherwise instructed, enter the following URI: http://rightsstatements.org/vocab/CNE/1.0/.
Required for all compound objects.
Unless otherwise instructed, enter the following URI: http://rightsstatements.org/vocab/CNE/1.0/.
Required for all compound objects.

@@ -8175,6 +9297,8 @@

oh > Compound objects

Enter the following value:
Reproductions are not available for order.
Enter the following value:
Reproductions are not available for order.

@@ -8233,6 +9357,10 @@

oh > Compound objects

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

@@ -8291,6 +9419,10 @@

oh > Compound objects

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.

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.

@@ -8349,6 +9481,10 @@

oh > Compound objects

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.

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.

@@ -8407,6 +9543,9 @@

oh > Compound objects

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 ballad, and oral history compound objects, provide the following value:

Sound

@@ -8475,6 +9614,19 @@

oh > Compound objects

Recording Location

Printer Location

Publisher Location

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

@@ -8542,6 +9694,18 @@

oh > Compound objects

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.

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.

@@ -8601,6 +9765,8 @@

oh > Compound objects

Values entered for this property are not visible in the public interface.

Use the following value:

special collections

Use the following value:

special collections

@@ -8724,6 +9890,14 @@

oh > Compound-object items

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.

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.

@@ -8783,6 +9957,9 @@

oh > Compound-object items

Enter the following value:

Sephardic Studies Digital Collection at the University of Washington

Required for all compound-object items.

Enter the following value:

Sephardic Studies Digital Collection at the University of Washington

Required for all compound-object items.

@@ -8841,6 +10018,10 @@

oh > Compound-object items

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

@@ -8905,6 +10086,15 @@

oh > Compound-object items

For image-file compound-object items which are interview transcripts, provide the following value:

Text

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

@@ -8963,6 +10153,8 @@

oh > Compound-object items

For audio files, enter the runtime of the digital access file.
Format runtime as HH:MM:SS.
For audio files, enter the runtime of the digital access file.
Format runtime as HH:MM:SS.

@@ -9022,6 +10214,11 @@

oh > Compound-object items

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".

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".

@@ -9087,6 +10284,13 @@

oh > Compound-object items

online resource

For image files (interviewee photos):

sheet

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

@@ -9152,6 +10356,15 @@

oh > Compound-object items

Use a space and “cm” (no following punctuation) after the measurements (“ cm”), to record as:

[height] x [width] 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

@@ -9212,6 +10425,11 @@

oh > Compound-object items

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.

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.

@@ -9268,6 +10486,8 @@

oh > Compound-object items

If available and applicable, provide details regarding the digitization of oral history compound-object items (interviewee photos, audio file, etc.).
If available and applicable, provide details regarding the digitization of oral history + compound-object items (interviewee photos, audio file, etc.).

@@ -9336,6 +10556,14 @@

oh > Compound-object items

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).

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).

@@ -9395,25 +10623,63 @@

Metadata creation guidance: default > Recording values
-
A brief descriptive phrase that includes these elements, generally in this order: - who, what, where, when.
-
The Title is a concise sentence which will be used to label the thumbnails in - CONTENTdm; it will also be the first line of the descriptive information. The Title - may - be the caption assigned by the photographer or the collector, or it may be created - by - Special Collections staff from the given caption and from additional sources. In the - absence of any caption, the Title will be provided by Special Collections staff.
-
If the caption provided by the photographer is adequate, place it in the Title field. - Then, the Notes field should include this phrase: Title taken from photograph.
-
If the caption provided by the photographer is inadequate, a created title should - be - placed in the Title field; the Notes field should then read: Caption on image: "Image - title."
-
If there is a series caption, it should be added, in the Notes field, in sequence - after the title on the image: Caption on image: "Image title"; "Series title." There - should also be a separate notation in the Notes field in the form: Part of Hegg series - entitled: "Series title."
+
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.

@@ -9469,7 +10735,9 @@

Metadata creation guidance: default > Recording values
-
Provide a name for the resource by translating an existing title.
+
Translate the song title.
+
Use title-case capitalization.
+
Do not use a period at the end of the translated title.

@@ -9524,8 +10792,18 @@

Metadata creation guidance: default > Recording values
-
Record a name for the resource in non-Latin script, if applicable.
-
Record a name for the resource in non-Latin script, if applicable.
+
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.

@@ -9584,8 +10862,29 @@

Metadata creation guidance: default > Recording values
-
Provide a non-Latin script title which has been Romanized according to the ALA-LC - Romanization Tables.
+
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.

@@ -9640,8 +10939,12 @@

Metadata creation guidance: default > Recording values
-
Provide a Ladino title in Hebrew script Romanized according to the Harvard Library - standard.
+
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.

@@ -9696,11 +10999,21 @@

Metadata creation guidance: default > Recording values
-
Enter the name of of person interviewed.
-
Format of personal name: Lastname, Firstname.
-
Use LC Name Authority File for form of name when available: http://authorities.loc.gov - or http://id.loc.gov/
-
Separate multiple values with a semicolon.
+
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.

@@ -9755,8 +11068,28 @@

Metadata creation guidance: default > Recording values
-
Provide the place of birth of a person interviewed.
-
Provide a controlled form of the place name if possible.
+
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.

@@ -9813,8 +11146,21 @@

Metadata creation guidance: default > Recording values
-
Provide the name of a primary performer who is seen, heard, or otherwise featured - in the resource.
+
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.

@@ -9869,7 +11215,22 @@

Metadata creation guidance: default > Recording values
-
Provide the name of a performer who is seen, heard, or otherwise featured in the resource.
+
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.

@@ -9924,7 +11285,30 @@

Metadata creation guidance: default > 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.
+
@@ -9976,11 +11360,21 @@

Metadata creation guidance: default > Recording values
-
Enter the name of the person who interviewed the subject.
-
Format of personal name: Lastname, Firstname.
-
Use LC Name Authority File for form of name when available: http://authorities.loc.gov - or http://id.loc.gov/
-
Separate multiple values with a semicolon.
+
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.

@@ -10037,8 +11431,21 @@

Metadata creation guidance: default > Recording values
-
Provide the name of a person who created a resource which is a video recording.
-
If possible, use a controlled form of name.
+
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.

@@ -10093,11 +11500,22 @@

Metadata creation guidance: default > Recording values
-
Input lastname, firstname or the corporate body name.
-
Use LC Authority File for form of name, if available.
-
Multiple names are okay; separate multiple names with a semicolon.
-
If the Creator is determined from a resource other than the item, create a Note.
-
If there is no author, leave the field blank.
+
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.

@@ -10149,12 +11567,27 @@

Metadata creation guidance: default > - - Recording values - -
- - + + 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 @@ -10206,8 +11639,23 @@

Metadata creation guidance: default > Recording values
-
Provide the name of a person or corporate body responsible for publishing the resource.
-
If possible, use a controlled form of name.
+
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.

@@ -10262,8 +11710,28 @@

Metadata creation guidance: default > Recording values
-
Provide a location, usually a city, associated with the publisher of a resource.
-
If possible, use a controlled form of the place name.
+
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.

@@ -10319,8 +11787,22 @@

Metadata creation guidance: default > Recording values
-
Provide the name of a person or corporate body responsible for publishing the resource.
-
If possible, use a controlled form of name.
+
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.

@@ -10375,8 +11857,28 @@

Metadata creation guidance: default > Recording values
-
Provide a location, usually a city, associated with the printer of a resource.
-
If possible, use a controlled form of the place name.
+
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.

@@ -10433,9 +11935,21 @@

Metadata creation guidance: default > Recording values
-
Provide the name of a person or corporate body responsible for translating the textual - content of the resource from one language into another.
-
If possible, use a controlled form of name.
+
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.

@@ -10490,7 +12004,26 @@

Metadata creation guidance: default > 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.
+
@@ -10544,7 +12077,24 @@

Metadata creation guidance: default > 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.
+
@@ -10598,10 +12148,21 @@

Metadata creation guidance: default > Recording values
-
Provide the name of a person or corporate body who previously owned a physical or - digital resource.
-
Provide the name of a person or corporate body who previously owned a physical or - digital resource.
+
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.

@@ -10660,6 +12221,8 @@

Metadata creation guidance: default >
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:
@@ -10669,7 +12232,7 @@

Metadata creation guidance: default >
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 specification to determine +
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.
@@ -10731,23 +12294,13 @@

Metadata creation guidance: default > Recording values
-
If the resource is a still image or moving images, the date the image(s) was captured.
-
In cases where a painting, engraving, or architectural drawing was photographed, the - date the artwork was created.
-
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?
-
In CONTENTdm, this field is used for display purposes only and should be user-friendly.
-
Date value should agree with date values entered in Date-Edtf and Dates fields.
-
If the date when the image/resource in hand was produced is known, and is different - from that of the original image, so note in the Notes field.
-
If the date is unknown, enter an approximate date using one of the two above formats - that express uncertainty, namely YYYY? or between YYYY and YYYY?.
-
If none of the date formats above are adequate, use a custom date format.
+
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.

@@ -10809,7 +12362,9 @@

Metadata creation guidance: default >

Values entered for this property are not visible in the public interface.

-
Reflects the date in the "Date" field.
+
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 @@ -10881,7 +12436,11 @@
Metadata creation guidance: default > 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.
+
@@ -10934,8 +12493,10 @@
Metadata creation guidance: default >

Enter any information of importance that is not represented elsewhere.
-
Each separate "note" should be a paragraph. Additional notes can be added, separated - from the previous note using a blank line.
+
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.

@@ -10993,8 +12554,29 @@
Metadata creation guidance: default > Recording values
-
Values for this property are taken from the LC Subject Headings list (LCSH) at http://authorities.loc.gov or http://id.loc.gov.
-
Separate multiple headings with a semicolon.
+
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).

@@ -11053,8 +12635,27 @@
Metadata creation guidance: default > Recording values
-
Values for this property are taken from the Library of Congress Genre/Form Terms.
-
The Library of Congress Genre/Form Terms are available as PDF files at https://www.loc.gov/aba/publications/FreeLCGFT/freelcgft.html, and can also be searched via id.loc.gov.
+
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)

@@ -11108,8 +12709,19 @@
Metadata creation guidance: default > Recording values
-
Provide a 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.
+
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.

@@ -11165,10 +12777,8 @@
Metadata creation guidance: default > Recording values
-
Input a term or terms taken from a controlled source. Recommended: LC Thesaurus for - Graphic Materials.
-
Enter the heading exactly as it appears in the thesaurus.
-
Separate multiple values with a semicolon and space.
+
Contact the collection manager(s) or metadata liaison(s) regarding appropriate Object + Type values for standalone objects in the collection.

@@ -11226,7 +12836,7 @@
Metadata creation guidance: default > Recording values
-
Search for the song title on pages 219-221 of ""Romances judeo-españoles de Oriente : nueva recolección"." +
Search for the song title on pages 219-221 of "Romances judeo-españoles de Oriente : nueva recolección."

Separate multiple thematic elements with a semicolon and space ("; ").

Begin each new thematic element with a capital letter.
@@ -11288,7 +12898,23 @@
Metadata creation guidance: default > Recording values
-
Provide information about one or more sources which provide additional information +
Provide any references to other Sephardic ballad collections given for this ballad as it is described in "Romances judeo-españoles de Oriente : nueva recolección".
+
Locate the song in "Romances judeo-españoles de Oriente: nueva recolección" by Rina + Benmayor and Judith H. Mauleó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.

@@ -11346,7 +12972,21 @@
Metadata creation guidance: default > Recording values
-
Provide the names of individuals given significant attention in the resource.
+
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.

@@ -11400,8 +13040,19 @@
Metadata creation guidance: default >

Provide the name or names of an organization or organizations given significant attention - in the resource.
-
If possible, use a controlled form for each organization's name.
+ 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.

@@ -11458,12 +13109,23 @@
Metadata creation guidance: default > Recording values
-
Enter broad and local geographic locations given significant attention in the resource.
-
Forms of the names should be derived from the LC Authority File.
-
Enter Country--State or Province--City.
+
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 above.
-
Separate multiple entries with a semicolon.
+ in the Subjects (LCSH) field. +
Separate multiple entries with a semicolon and space (“; “).

@@ -11593,7 +13255,12 @@
Metadata creation guidance: default > Recording values
-
Enter an abridged transcript, or list of contents, for the resource.
+
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.

@@ -11646,8 +13313,30 @@
Metadata creation guidance: default > Recording values
-
Provide a location, usually a city, where the resource was recorded.
-
If possible, use a controlled form of the place name.
+
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.

@@ -11702,7 +13391,10 @@
Metadata creation guidance: default > Recording values
-
Enter the name of the language of the resource fully spelled out.
+
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.

@@ -11759,7 +13451,9 @@
Metadata creation guidance: default > Recording values
-
Enter the name given to the digital collection.
+
Enter the following value:
+
Sephardic Studies Digital Collection at the University of Washington
+
Required for all standalone objects.

@@ -11815,7 +13509,11 @@
Metadata creation guidance: default > 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.
+
@@ -11869,9 +13567,10 @@
Metadata creation guidance: default > Recording values
-
Input the following text:
-
For information on permissions for use and reproductions please visit UW Libraries - Special Collections Use Permissions page: http://www.lib.washington.edu/specialcollections/services/permission-for-use
+
Required for all standalone objects.
+
Enter the following value:
+
To inquire about permissions, contact sephstud@uw.edu. Please cite the Sephardic Studies + Accession Number.

@@ -11927,10 +13626,8 @@
Metadata creation guidance: default > Recording values
-
Enter a rights statement from rightsstatements.org.
-
UW Libraries Special Collections policy: for items with a date later than 95 years - ago, enter http://rightsstatements.org/vocab/InC/1.0/ ("In Copyright"); for all else - enter http://rightsstatements.org/vocab/CNE/1.0/ ("Copyright Not Evaluated.")
+
Unless otherwise instructed, enter the following URI: http://rightsstatements.org/vocab/CNE/1.0/.
+
Required for all standalone objects.

@@ -11986,8 +13683,8 @@
Metadata creation guidance: default > Recording values
-
Enter the instructions for ordering. If the item cannot be ordered, state that it - cannot be ordered.
+
Enter the following value:
+
Reproductions are not available for order.

@@ -12044,7 +13741,14 @@
Metadata creation guidance: default > Recording values
-
Enter the name of the institution in which the original item is held.
+
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

@@ -12101,8 +13805,10 @@
Metadata creation guidance: default > Recording values
-
Enter collection name and number, represented as a phrase.
-
Collection name is the name assigned by the holding repository to the original collection.
+
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.

@@ -12157,7 +13863,10 @@
Metadata creation guidance: default > Recording values
-
Enter only the URI to the EAD finding aid.
+
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.

@@ -12213,7 +13922,36 @@
Metadata creation guidance: default >

Values entered for this property are not visible in the public interface.

-
Input a value from the Dublin Core Type Vocabulary at http://dublincore.org/documents/dcmi-terms/.
+
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

@@ -12268,11 +14006,8 @@
Metadata creation guidance: default > Recording values
-
Enter the extent of digital access file.
-
Enter duration of the access audio or video file and/or the length of a text-based - file.
-
Duration should be entered hh:mm:ss.
-
Extent of text will use a numeral and the word "pages" as follows: "128 pages."
+
For audio files, enter the runtime of the digital access file.
+
Format runtime as HH:MM:SS.

@@ -12329,7 +14064,9 @@
Metadata creation guidance: default > Recording values
-
Enter the file format of the access item.
+
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".

@@ -12390,11 +14127,7 @@
Metadata creation guidance: default > Recording values
-
Enter the original format.
-
When the original is non-digital, use a label from one of the entries of the RDA Registry's - RDA Carrier Type Vocabulary currently available at https://www.rdaregistry.info/termList/RDACarrierType/
-
When the original is digital, use media types listed at http://www.iana.org/assignments/media-types/index.html
-
For audio WAVE files, enter "audio/wav".
+
🚧 🚧 🚧

@@ -12456,14 +14189,52 @@
Metadata creation guidance: default > Recording values
-
Input a term or terms describing the format of the original resource in which data, - sound, images, etc., are stored.
-
The term should be taken from an authoritative source.
-
Recommended source: RDA chapter 3, especially 3.3.
-
Former recommended source: Graphic Materials: Rules for Describing Original Items - and Historical Collections. Use of this source is no longer recommended.
-
Entry may include an extent statement, dimensions, base material, or any other carrier - description, as described in detail in RDA chapter 3.
+
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

@@ -12530,9 +14301,10 @@
Metadata creation guidance: default > Recording values
-
Provide the timecode at which the clip included in the audio file begins.
-
Only needed when the audio clip is only a section of the recording on a side of the - original audio.
+
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.

@@ -12588,7 +14360,14 @@
Metadata creation guidance: default > Recording values
-
Input a paragraph with pertinent information on the digital conversion process.
+
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.).

@@ -12645,7 +14424,13 @@
Metadata creation guidance: default >

Values entered for this property are not visible in the public interface.

-
Enter "xyz" to denote that the item requires subject headings from local catalogers.
+
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

@@ -12701,7 +14486,49 @@
Metadata creation guidance: default >

Values entered for this property are not visible in the public interface.

-
Input your staff notes however you wish.
+
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.

@@ -12759,7 +14586,8 @@
Metadata creation guidance: default >

Values entered for this property are not visible in the public interface.

-
[Uncertain]
+
Use the following value:
+
special collections

@@ -12877,8 +14705,19 @@
Metadata creation guidance: default >

Values entered for this property are not visible in the public interface.

-
Enter the name of the digital file representing the standalone object, that is, an - access item.
+
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).