Dime Novels Project Profile: Specifications for Metadata Creation

 

Contextual Information

Collection finding aid, if any http://libguides.niu.edu/rarebooks/dimenovels
Catalog record(s), if any Approx. 40,000 MARC records available, many series still uncataloged
Collection site, if any http://dimenovels.lib.niu.edu/
Other pertinent reference information https://dimenovels.org/

Project Files

Digital image files

N:/Staging/dime_novels

N:/Staging/johannsen

Metadata form definition, if any N/A
MARC transformation, if any MARC records for a series are broken into MARC/XML and batch transformed into MODS.
Controlled vocabulary for project Library of Congress Name Authority File and Library of Congress Subject Headings
Standards used for project Resource Description and Access
Level of quality control High

MODS Metadata Guidelines

Field

mods:titleInfo

Value In order of preference, the title proper may be taken from the title page, caption, or cover. If the title on the caption differs from the title on the cover, include the cover title as an alternative title and make a note. It is not necessary to include alternative titles for parts of titles (e.g. everything after “or” in the title “Arkansas Kit, or, The river sprite’s choice”). Only add lengthy subtitles if they include keywords that are not present elsewhere in the description.
Examples
<mods:titleInfo>
  <mods:title>Arkansas Kit, or, The river sprite's choice</mods:title>
  <mods:subTitle>a tale of the Crowfoot country</mods:subTitle>
</mods:titleInfo>


<mods:titleInfo>
  <mods:title>Nick Carter on the limited, or, The man in the smoker who
didn't smoke</mods:title>
</mods:titleInfo>

 

 

Field

mods:name

Value

Names should be taken from the Library of Congress Name Authority File and given the authority attribute “naf.” URI’s from id.loc.gov must always be included as attributes for names that have a corresponding record in the LCNAF. If a name is not found in the LCNAF and there are no conflicts, add the fullest form of the name available or the name by which the person is most commonly known to the dimenovels.org database, then use the authority value “dime” with corresponding URI attributes.

In general, use the name as it appears on the resource. If the name on the resource takes the form “author of,” “Anonymous,” etc. or there is no name, use the identity known to be related to the resource, if discernable from reference sources (e.g. “Noname” is “Senarens, Luis, 1863-1939”). In cases where there is a preferred form of a name in the LCNAF with a pseudonym used as a variant name, use the preferred form (e.g. “New York detective, -1917” is “Doughty, Franicis Worcester, -1917”).

Always include a textual role to identity how the name has contributed to the resource, using MARC relator terms for values. The publisher must always be added as a name access point.

Examples
<mods:name type="personal" authority="naf" authorityURI="http://id.loc.gov/authorities/names" valueURI="http://id.loc.gov/authorities/names/no89009378">
  <mods:namePart>Doughty, Francis Worcester</mods:namePart>
  <mods:namePart type="date">-1917</mods:namePart>
  <mods:role>
    <mods:roleTerm authority=”marcrelator” type="text">author</mods:roleTerm>
  </mods:role>
</mods:name>

<mods:name authority="naf" authorityURI="http://id.loc.gov/authorities/names" type="personal" valueURI="http://id.loc.gov/authorities/names/n85352294">
  <mods:namePart>Orr, Nathaniel</mods:namePart>
  <mods:role>
    <mods:roleTerm authority=”marcrelator” type="text">illustrator</mods:roleTerm>
  </mods:role>
</mods:name>

<mods:name authority="naf" authorityURI="http://id.loc.gov/authorities/names" type="corporate" valueURI="http://id.loc.gov/authorities/names/n86111811">
  <mods:namePart>Beadle and Company</mods:namePart>
  <mods:role>
    <mods:roleTerm type="text">publisher</mods:roleTerm>
  </mods:role>
</mods:name>

 

 

Field

mods:genre

Value

At least one genre term is always required. If a particular story participates in multiple genres, it is strongly recommended that all relevant genres be included in the description. Below is a list of genre terms currently in use, but please note that any LCSH genre terms may be used, if appropriate. When using an LCSH genre term, the authority value should also be “lcsh.” Add URI’s corresponding to the genre found in id.loc.gov.

Adventure stories

Animal stories

Bildungsromans

Biographical fiction

College stories

Detective and mystery stories

Domestic fiction

Fan fiction

Fantasy fiction

Ghost stories

Historical fiction

Horror stories

Humorous stories

Legal stories

Romance fiction

Railroad stories

School stories

Science fiction

Sea stories

Sports stories

Spy stories

War stories

Western stories

Local genre terms may be added for specificity, but they must be supplied by J. Randolph Cox’s Dime Novel Companion. If possible, a more specific term should be combined with one of the broader genre terms above. When a genre from Cox’s Companion is used, the value of authority will be “dime.” Here is a complete list of genres that may be taken from the Companion:

American Revolutionary War stories

Bandit, outlaw, and highwayman stories

Circus and carnival stories

Civil War stories

Fire fighters and firefighting stories

Klondike gold rush stories

Northwest mounted police stories

Pirates and privateering stories

Polar exploration stories

Slums and social action stories

Spanish-American War stories

Stage and theatre stories

Success stories

Temperance stories

Travel and exploration stories

Examples
<mods:genre authority="lcsh" authorityURI="http://id.loc.gov/authorities/subjects" valueURI="http://id.loc.gov/authorities/subjects/sh85146287">Western stories</mods:genre>

<mods:genre authority="dime">Success stories</mods:genre>

 

 

Field

mods:originInfo

Value Always add the full imprint for the publisher, including the street address. Record the imprint exactly as it appears on the resource. The publication date can be inferred from the cover or caption date. Always include the most complete date possible in the form YYYY-MM-DD. If there is no cover or caption date, infer the publication date from the copyright date, with the qualifier “inferred.” Do not infer the copyright date from the publication date. If there is no explicit copyright statement, omit the copyright date.
Examples
<mods:originInfo eventType="publication">
  <mods:place>
    <mods:placeTerm authority="marccountry" type="code">nyu</mods:placeTerm>
    <mods:placeTerm authority="marccountry" type="text">New York</mods:placeTerm>
  </mods:place>
  <mods:publisher>Beadle and Company, 141 William St.</mods:publisher>
  <mods:dateIssued keyDate="yes" encoding="w3cdtf">1861</mods:dateIssued>
  <mods:copyrightDate encoding="w3cdtf">1861</mods:copyrightDate>
</mods:originInfo>

<mods:originInfo eventType="publication">
  <mods:place>
    <mods:placeTerm authority="marccountry" type="code">nyu</mods:placeTerm>
    <mods:placeTerm authority="marccountry" type="text">New York</mods:placeTerm>
  </mods:place>
  <mods:publisher>Harry E. Wolff, Publisher, West 23rd St.</mods:publisher>
  <mods:dateIssued encoding="w3cdtf" keyDate="yes">1925-03-27</mods:dateIssued>
</mods:originInfo>

 

 

Field

mods:physicalDescription

Value

Include a local form with authority “local” using the values and definitions below. Dime novel formats were very fluid, so the following definitions are intended only as a guide. Variations will occur.

Dime novels: 4 x 6 in., approximately 100 pages long, contains a complete work of fiction, sold for ten cents, and most closely associated with Beadle’s dime novels.

Nickel weeklies: 8 ½ x 11 in. with at least 16 pages of double or triple-column fine print issued regularly in sequence, sold for 5-10 cents. Variations include 6 X 8 ½ in. with 32 pages and 9 x 12 in. with 60+ pages. For our purposes, weeklies are the same as libraries.

Story papers: periodicals that include more than one serialized story, in addition to verse and news. Nickel weeklies may also include backup matter, but will almost always begin with a complete story.

Thick books: 5 x 7 in., with 150-300 pages, often containing several stories originally appearing as nickel weeklies. Record only the numbered pages.

Examples
<mods:physicalDescription>
  <mods:form authority="local">Nickel weeklies</mods:form>
  <mods:form authority="rdacontent" type="content">text</mods:form>
  <mods:form authority="rdamedia" type="media">computer</mods:form>
  <mods:form authority="rdacarrier" type="carrier">online resource</mods:form>
  <mods:internetMediaType>image/tiff</mods:internetMediaType>
  <mods:internetMediaType>image/jp2</mods:internetMediaType>
  <mods:internetMediaType>image/jpeg</mods:internetMediaType>
  <mods:internetMediaType>application/pdf</mods:internetMediaType>
  <mods:internetMediaType>text/plain</mods:internetMediaType>
  <mods:extent unit="pages">31</mods:extent>
  <mods:digitalOrigin>reformatted digital</mods:digitalOrigin>
</mods:physicalDescription>

 

 

Field

mods:note

Value

Always include the statement of responsibility in a note with the type value “statement of responsibility.” Include a note indicating the source used for the title proper. If using the cover or caption date, transcribe the date as it appears on the resource and identify the source.

All other notes are optional.

Examples
<mods:note type="statement of responsibility">by a Self-made man.</mods:note>
<mods:note>Caption title.</mods:note>
<mods:note>Illustrated paper cover in colors.</mods:note>
<mods:note>"May 29, 1925"—Cover.</mods:note>
<mods:note>Printed in double columns.</mods:note>
<mods:note>Includes chapters XXI-XXIII of: Gus and the guide, or, Three
weeks lost in the Rockies / by Gaston Garne.</mods:note>

 

 

Field

mods:subject

Value

Subject access will vary significantly from series to series. In general, try to include 1) the location used as the setting for the story, 2) any recurring characters, 3) any groups that are featured prominently in the story (e.g. “Apache Indians,” “African American men,” “Women heroes”, “Inventors”), and 4) significant historical events or persons (e.g. American Revolutionary War, Simon Girty). For the purpose of collocation, use broader and narrower subjects separately rather than precoordinated headings. Local names may be used for fictional characters on a series-by-series basis.

If a complex heading can be found in the authority file, use “lcsh” for the subject authority. If no complex heading exists, include “lcsh” for the subject, with “lcsh,” “naf”, or local for each component of the complex heading. Likewise, include a URI for each subject at the appropriate level.

Examples
<mods:subject authority="lcsh" authorityURI="http://id.loc.gov/authorities/subjects/" valueURI="http://id.loc.gov/authorities/subjects/sh2008100054">
  <mods:geographic>Colorado</mods:geographic>
  <mods:genre>Fiction</mods:genre>
</mods:subject>

<mods:subject authority="lcsh">
  <mods:name authority=”naf”
authorityURI="http://id.loc.gov/authorities/names" type="corporate" valueURI="http://id.loc.gov/authorities/subjects/n50071988">
    <mods:namePart>Sons of Liberty</mods:namePart>
  </mods:name>
  <mods:genre>Fiction</mods:genre>
</mods:subject>

<mods:subject authority="lcsh">
  <mods:geographic authorityURI="http://id.loc.gov/authorities/subjects" valueURI="http://id.loc.gov/authorities/subjects/sh95010548">Mohawk River Valley (N.Y.)</mods:geographic>
  <mods:genre>Fiction</mods:genre>
</mods:subject>

<mods:subject authority="lcsh">
  <mods:name type="personal" authority="local">
    <mods:namePart>Carter, Trim</mods:namePart>
    <mods:namePart type="termsOfAddress">(Fictitious character)</mods:namePart>
  </mods:name>
  <mods:genre>Fiction</mods:genre>
</mods:subject>

 

 

Field

mods:relatedItem

Value

Every issue must include a complete series statement proper and series statement preferred. Use LCNAF for the uniform title, with the type “uniform,” the authority “naf” or “local,” and a URI if the series is taken from the LCNAF. partNumber must be used to indicate the issue number, including both the volume and the number. ALWAYS include a space after “no.” or “v.”

This element can also be used to describe constituent parts, such as backup stories. When describing constituents, include the title, the name of the author, and the part. Parts should include the chapter range as well as the start and end pages.

Examples
<mods:relatedItem type="series">
  <mods:titleInfo>
    <mods:title>Beadle's dime novels</mods:title>
    <mods:partNumber>no. 283</mods:partNumber>
  </mods:titleInfo>
  <mods:titleInfo authority="naf" authorityURI="http://id.loc.gov/authorities/names" type="uniform" valueURI="http://id.loc.gov/au
thorities/names/no2002097759">
    <mods:title>Beadle's dime novels</mods:title>
    <mods:partNumber>no. 283</mods:partNumber>
  </mods:titleInfo>
</mods:relatedItem>

<mods:relatedItem type="series">
  <mods:titleInfo>
    <mods:title>Deadwood Dick library</mods:title>
    <mods:partNumber>v. 4, no. 40</mods:partNumber>
  </mods:titleInfo>
  <mods:titleInfo authority="naf" authorityURI="http://id.loc.gov/authorities/names" type="uniform" valueURI="http://id.loc.gov/authorities/names/nr2005006857">
    <mods:title>Deadwood Dick library</mods:title>
    <mods:partNumber>v. 4, no. 40</mods:partNumber>
  </mods:titleInfo>
</mods:relatedItem>

<mods:relatedItem type="series">
  <mods:titleInfo>
    <mods:title>Fame and fortune weekly</mods:title>
    <mods:partNumber>no. 1026</mods:partNumber>
  </mods:titleInfo>
  <mods:titleInfo authority=”local” type="uniform">
    <mods:title>Fame and fortune weekly</mods:title>
    <mods:partNumber>no. 1026</mods:partNumber>
  </mods:titleInfo>
</mods:relatedItem>

<mods:relatedItem type="constituent">
  <mods:titleInfo>
    <mods:title>Young fresh from &apos;Frisco, or, The boy who bossed the mine</mods:title>
 </mods:titleInfo>
  <mods:name authority="local" type="personal">
    <mods:namePart>Garne, Gaston</mods:namePart>
    <mods:role>
      <mods:roleTerm type="text">author</mods:roleTerm>
    </mods:role>
  </mods:name>
  <mods:part>
    <mods:detail type="chapter">
    <mods:number>1-2</mods:number>
  </mods:detail>
  <mods:extent unit="pages">
    <mods:start>20</mods:start>
    <mods:end>21</mods:end>
  </mods:extent>
  </mods:part>
</mods:relatedItem>

 

 

Field

mods:location

Value

Add “JNA” as a physical location with the authority “oclcorg” and a separate physical location for the collection. We will only be digitizing dime novels from two collections:

  • Edward T. LeBlanc Collection. Rare Books and Special Collections, Northern Illinois University.
  • Johannsen Collection. Rare Books and Special Collections, Northern Illinois University.

Also include a shelf locator, with the local LCC call number, and a url to the object.

Examples
<mods:location>
  <mods:physicalLocation authority="oclcorg">JNA</mods:physicalLocation>
  <mods:physicalLocation>Edward T. LeBlanc Collection. Rare Books and Special Collections, Northern Illinois University.</mods:physicalLocation>
  <mods:shelfLocator>PS3166.W43 D32 1899a v. 4 no. 40</mods:shelfLocator>
  <mods:url access="object in context" usage="primary display">http://dimenovels.lib.niu.edu/islandora/object/dimenovels:22039</mods:url>
</mods:location>

 

 

Field

mods:accessCondition

Value

“Use of this public-domain resource is unrestricted.”

Examples
<mods:accessCondition type="useAndReproduction">Use of this public-domain resource is unrestricted.</mods:accessCondition>

 

 

Field

mods:recordInfo

Value

The Voyager BIB number is always required with the source “NIUDb.”

Examples
<mods:recordInfo>
  <mods:descriptionStandard>rda</mods:descriptionStandard>
  <mods:recordContentSource authority="oclcorg">JNA</mods:recordContentSource>
  <mods:recordCreationDate encoding="marc">070320</mods:recordCreationDate>
  <mods:recordChangeDate encoding="iso8601">20070321180744.0</mods:recordChangeDate>
  <mods:recordIdentifier source="NIUDb">1663774</mods:recordIdentifier>
  <mods:recordOrigin>Converted from MARCXML to MODS version 3.5 using MARC21slim2MODS3-4.xsl (Revision 1.79 2012/07/11), modified for MODS version 3.5 and NIU's Dime Novel Collection</mods:recordOrigin>
</mods:recordInfo>

 

Lee Schreiner Sheet Music Collection Project Profile: Specifications for Metadata Creation

 

Contextual Information

Collection finding aid, if any

Tracking spreadsheet:

https://docs.google.com/spreadsheets/d/1tQrGSumXcBzpC6DlcYTmJz-tTDZkGMKrKtKaDGUFP4g/edit?usp=sharing

Finding aid:

https://docs.google.com/spreadsheets/d/1nQ25RjUeYgOCqmAOIuXehcwiycdrCgAtvvIMR_MTRxM/edit?usp=sharing

Catalog record(s), if any 20% of pieces have copy in LC or the Sheet Music Consortium, as much as 50% may have copy elsewhere
Collection site, if any http://rbsc.lib.niu.edu/islandora/object/rbsc:schreiner
Other pertinent reference information http://digital2.library.ucla.edu/sheetmusic/

Project Files

Digital image files N:/Staging/sheetmusic
Metadata form definition, if any N/A
MARC transformation, if any

https://github.com/mshort/niu_metadata/blob/master/sheet_music_transform.py

https://github.com/mshort/niu_metadata/blob/master/xsl/music_marcxml2mods.xsl

Controlled vocabulary for project Library of Congress Name Authority File (NAF), Library of Congress Subject Headings (LCSH), the Library of Congress Genre/Form Terms for Library and Archival Materials (LCGFT), Library of Congress Medium of Performance Thesaurus for Music (LCMPT), Art & Architecture Thesaurus (AAT)
Standards used for project Resource Description and Access
Level of quality control High

MODS Metadata Guidelines

Field mods:titleInfo
Value

In order of preference, the title proper may be taken from the cover, caption, or a reference source. If the title on the caption differs from the title on the cover, include the cover title as an alternative title and make a note. When taking the title from a reference source, use “yes” for the attribute supplied and describe the source in a note. If no title is available on the piece or from a reference source, one must be constructed. When constructing a title, consider using the first line of lyrics or the first line of chorus. Use your judgment when determining the end of a line. (Notes for first lines are still required.)

If a song has been published under multiple titles or is part of a larger work, construct a uniform title. Uniform title is not required, unless we are digitizing two manifestations of the same work.

Include any title that differs from the title proper with “alternative” for the attribute type, except for other part of title.

Examples
<mods:titleInfo>
  <mods:title>How I long for the USA</mods:title>
  <mods:subTitle>march song</mods:subTitle>
</mods:titleInfo>

 

 

Field mods:name
Value

Names should be taken from the Library of Congress Name Authority File and given the authority attribute “naf.” URI’s from id.loc.gov must always be included as attributes for names that have a corresponding record in the NAF. If a name is not found in the NAF and there are no conflicts, add the fullest form of the name available or the name by which the person is most commonly known with the authority value “local” and no URI attributes.

In general, use the name as it appears on the resource. If the name on the resource takes the form of “Anonymous” or there is no name, use the identity known to be related to the resource, if discernable from reference sources, then transcribe the name in a note for the statement of responsibility.

The following contributors must be traced when available: composer, arranger of music, lyricist, and publisher. Also include the performer and dedicatee, if their names are on the piece. Do not trace the performer or dedicatee if those names have been added to the resource after publication (e.g. handwritten dedications). Performers may include conductor, instrumentalist, and singer.

The cover art is often as important as the score itself. Engraver, lithographer, or artist should also be traced when their names can be identified on the piece.

Always include a textual role to identity how the name has contributed to the resource, using MARC relator terms for values.

Examples
<mods:name type="personal" authority=”naf” authorityURI=”http://id.loc.gov/authorities/names” valueURI=”http://id.loc.gov/authorities/names/no96047710”>
  <mods:namePart>Klickmann, F. Henri (Frank Henri)</mods:namePart>
  <mods:namePart type=”date”>1885-1966</mods:namePart>
  <mods:role>
    <mods:roleTerm type="text" authority=”marcrelator”>composer</mods:roleTerm>
  </mods:role>
</mods:name>

<mods:name type="personal" authority=”local”>
  <mods:namePart>Sliger, Chas. (Charles)</mods:namePart>
  <mods:role>
    <mods:roleTerm type="text" authority=”marcrelator”>composer</mods:roleTerm>
  </mods:role>
</mods:name>

 

 

Field mods:genre
Value

Every piece should be assigned one of the following terms from the Art & Architecture Thesaurus.

scores: Original and entire drafts or transcripts of musical compositions or arrangements, with the parts of all the different instruments or voices written on staffs one above another, so that they can be read at a glance.

sheet music: Music printed on unbound sheets of paper.

songs (documents): Documents containing musical compositions, generally short, containing words.

songbooks: Books containing brief musical compositions written or adapted for singing.

At least one genre term from the Library of Congress Genre/Form Terms for Library and Archival Materials (LCGFT) is always required. These should be used to indicate a genre of music that implies certain rhythmic, tempo, or instrumentation patterns, such as Minstrel music or Ragtime music. If a piece participates in multiple genres, it is strongly recommended that all relevant genres be included in the description. When using an LCGFT genre term, the authority value should be “lcgft.”

Add URI’s corresponding to the genre found in id.loc.gov, which may be found here.

A list of all available music terms is available here.

For guidance in assigning these terms, refer to Best Practices for Using LCGFT for Music Resources.

Below is a list of LCGFT terms commonly used in this collection, but any appropriate terms from the vocabulary may be used.

Ballads

Bawdy songs

Camp songs

Campaign songs

Christmas music

Dance music

Dirges (Music)

Epic songs

Fanfares

Fight songs

Folk songs

Funeral music

Gospel music

Humorous songs

Hymns

Marches (Music)

Medleys (Music)

Military music

Minstrel music

Mission music

Narrative songs

Nonsense songs

Novelty songs

Pastoral music

Popular music

Quicksteps (Marches)

Ragtime music

Satirical songs

Sea shanties

Work songs

Library of Congress Subject Headings should not be assigned as genres, unless to indicate the genre of some textual component of the piece (e.g. Love stories). LCSH terms should be used sparingly in mods:genre.

Examples
<mods:genre authority="aat" authorityURI=" http://vocab.getty.edu/aat" valueURI=”http://vocab.getty.edu/aat/300026430”>sheet music</mods:genre>

<mods:genre authority="lcgft" authorityURI=" http://id.loc.gov/authorities/genreForms" valueURI=” http://id.loc.gov/authorities/genreForms/gf2014026939”>Minstrel music</mods:genre>

 

 

Field mods:originInfo
Value

Always add the full imprint for the publisher, including the street address. If the street address varies from resource to resource, record the address using abbreviations like st., ave., blvd., etc. (“LaVern Music Pub. Co., 5631 Drexel Ave.”). It may not be possible to create uniform addresses across series.

mods:dateIssued is always required. The publication date can be inferred from the cover or caption date. Always include the most complete date possible in the form YYYY-MM-DD. If there is no cover or caption date, infer the publication date from the copyright date, with the qualifier “inferred.” Do not infer the copyright date from the publication date. If the date cannot be derived from the resource itself, dates from a reference source are acceptable. When using a reference source, include a quoted note indicating the source of the date. Where exact dates are unknown, supply a range of possible dates, such as the decade or century in which the piece was created or published. Indicate supplied dates with the type attribute “supplied.”

Examples
<mods:originInfo eventType="publication">
    <mods:place>
        <mods:placeTerm type="code" authority="marccountry">nyu</mods:placeTerm>
         <mods:placeTerm type="text">Buffalo, N.Y</mods:placeTerm>
    </mods:place>
    <mods:publisher>Sliger Heusinger Music Pub. Co., 22 Reed St. </mods:publisher>
    <mods:dateIssued keyDate="yes" encoding="w3cdtf" qualifier=”inferred”>1910</mods:dateIssued>
    <mods:copyrightDate encoding="w3cdtf">1910</mods:copyrightDate>
</mods:originInfo>

 

 

Field mods:physicalDescription
Value

mods:extent includes the format of noted music, with the number of pages or leaves. Omit the size of the resource. RDA 3.4.3 applies when constructing the extent statement, including the following values for formats containing notated music:

score

condensed score

study score

piano conductor part

violin conductor part

vocal score

piano score

chorus score

part

choir book

table book

mods:internetMediaType, mods:digitalOrigin, and RDA forms should never vary.

Examples
<mods:physicalDescription>
  <mods:form authority="rdacontent" type="content">notated music</mods:form>
  <mods:form authority="rdamedia" type="media">computer</mods:form>
  <mods:form authority="rdacarrier" type="carrier">online resource</mods:form>
 <mods:internetMediaType>image/tiff</mods:internetMediaType>
 <mods:internetMediaType>image/jp2</mods:internetMediaType>
 <mods:internetMediaType>image/jpeg</mods:internetMediaType> 
 <mods:internetMediaType>text/plain</mods:internetMediaType>
 <mods:digitalOrigin>reformatted digital</mods:digitalOrigin>
 <mods:extent>1 score (5 pages)</mods:extent>
</mods:physicalDescription>

 

 

Field mods:note
Value

Many users are more familiar with the first line of lyrics or the first line of the chorus than the title proper. Include these in a note with the type attribute “first line of lyrics” or “first line of chorus.”

Include a description of the cover illustration, with the type attribute “cover illustration,” including a statement of responsibility for the artist.

Always include the statement of responsibility for the piece in a note with the type value “statement of responsibility.”

Include a note indicating the source used for the title proper, e.g. “Cover title” or “Caption title”

If using the cover or caption date, transcribe the date as it appears on the resource and identify the source in a quoted note.

At least one term from the Library of Congress Medium of Performance Thesaurus for Music (LCMPT) is always required. These should be used to indicate the voice, instruments, and other entities needed to perform a piece of music. Each instrument should be recorded in a separate mods:note with type=”medium of performance.” If several accompanying instruments are listed as alternatives for accompaniment under a vocal line, include each instrument. Available terms may be found here.

For guidance on assigning these terms, refer to Best Practices for Using LCMPT.

All other notes are optional.

Examples
<mods:note type=”first line of lyrics”> I heard a voice in the still of night.</mods:note>
<mods:note type=”first line of chorus”> Here I am! Uncle Sammy, take me.</mods:note>
<mods:note type=”cover illustration”> Drawing of Uncle Sam holding American flag and American eagle / E.S. Fisher.</mods:note>
<mods:note type=”statement of responsibility”> words by Dean T. Wilton ; music by James McHugh</mods:note>
<mods:note type=”medium of performance”>piano</mods:note>
<mods:note type=”medium of performance”>voice</mods:note>
<mods:note>Title from cover.</mods:note>
<mods:note>”1917”--Caption.</mods:note>

 

 

Field mods:subject
Value

Use Library of Congress Subject Headings (LCSH) to describe topics, places, events, and people that occur in the song’s lyrics or title.

FAST subject headings should be assigned to describe what the cover art is about (concept) and what it is of (descriptive). There is no limit on the number of headings that may be assigned. FAST may be searched here: http://fast.oclc.org/searchfast/.

If a complex heading can be found in the authority file, use “lcsh” for the subject authority. If no complex heading exists, include “lcsh” for the subject, with “lcsh,” “naf”, or local for each component of the complex heading. Include a URI for each subject at the appropriate level.

Examples
<mods:subject authority=”lcsh” authorityURI=”http://id.loc.gov/authorities/subjects” valueURI=”http://id.loc.gov/authorities/subjects/sh2008113367”>
    <mods:topic authorityURI=”http://id.loc.gov/authorities/subjects” valueURI=”http://id.loc.gov/authorities/subjects/sh85148236”>>World War, 1914-1918</mods:topic>
    <mods:genre>Songs and music</mods:topic>
</mods:subject>

 

 

Field mods:relatedItem
Value

If the piece is part of a larger series, then the record must include mods:relatedItem with the type “series”, with a complete series statement proper and series statement preferred. Use LCNAF for the uniform title, with the type “uniform,” the authority “naf” or “local,” and a URI if the series is taken from the LCNAF. partNumber must be used to indicate the issue number, including both the volume and the number. ALWAYS include a space after “no.” or “v.”

Also use this element to describe constituent parts or hosts that exist in a vertical relationship to the resource being described. Also include the title and an identifier for constituent parts or hosts.

Always include the host collection, with title and location.

Examples
<mods:relatedItem type=”host”>
    <mods:titleInfo>
        <mods:title>Lee Schreiner Sheet Music Collection</mods:title>
    </mods:titleInfo>
    <mods:location>    <mods:url>http://rbsc.lib.niu.edu/islandora/object/rbsc:schreiner</mods:url>
    </mods:location>
</mods:relatedItem>

<mods:relatedItem type="series">
  <mods:titleInfo>
    <mods:title>Beautiful modern and classic pianoforte pieces</mods:title>
  </mods:titleInfo>
</mods:relatedItem>

 

 

Field mods:identifier
Value

Record the plate number, using the type “plate number.” A plate number is a designation assigned to an item by a music publisher, usually printed at the bottom of each page, and sometimes also appearing on the title page. It may include initials, abbreviations, or words identifying a publisher and is sometimes followed by a number corresponding to the number of pages or plates. Transcribe the number exactly as it appears on the item.

Include the publisher number, with the type “publisher number.” Publisher numbers are assigned to an item by a music publisher, appearing normally only on the title page, the cover, and/or the first page of music. They may include initials, abbreviations, or words identifying the publisher. Transcribe the number exactly as it appears on the item.

Use the OCLC number, with prefix and the authority “oclc.”

Examples
<mods:identifier type="oclc">ocm13128616</mods:identifier>

 

 

Field mods:location
Value

Add “JNA” as a physical location with the authority “oclcorg” and a separate physical location for the collection. We will only be digitizing dime novels from:

  • Music Special Collection. Rare Books and Special Collections, Northern Illinois University.

Also include a shelf locator, with the local LCC call number, and a url to the object.

Examples
<mods:location>
  <mods:physicalLocation authority="oclcorg">JNA</mods:physicalLocation>
  <mods:physicalLocation>Music Special Collection. Rare Books and Special Collections, Northern Illinois University.</mods:physicalLocation>
  <mods:shelfLocator>PS3166.W43 D32 1899a v. 4 no. 40</mods:shelfLocator>
  <mods:url access="object in context" usage="primary display">http://digital.lib.niu.edu/islandora/object/schreiner:22039</mods:url>
</mods:location>

 

 

Field mods:accessCondition
Value “Use of this public-domain resource is unrestricted.”
Examples
<mods:accessCondition type="useAndReproduction">Use of this public-domain resource is unrestricted.</mods:accessCondition>

 

 

Field mods:recordInfo
Value The Voyager BIB number is always required with the source “NIUDb.”
Examples
<mods:recordInfo>
  <mods:descriptionStandard>rda</mods:descriptionStandard>
  <mods:recordContentSource authority="oclcorg">JNA</mods:recordContentSource>
  <mods:recordCreationDate encoding="marc">070320</mods:recordCreationDate>
  <mods:recordChangeDate encoding="iso8601">20070321180744.0</mods:recordChangeDate>
  <mods:recordIdentifier source="NIUDb">1663774</mods:recordIdentifier>
  <mods:recordOrigin>Converted from MARCXML to MODS version 3.5 using MARC21slim2MODS3-4.xsl (Revision 1.79 2012/07/11), modified for MODS version 3.5 and the Lee Schreiner Sheet Music Collection.</mods:recordOrigin>
</mods:recordInfo>