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 |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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 |
|
| 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:
Also include a shelf locator, with the local LCC call number, and a url to the object. |
| Examples |
|
| Field |
mods:accessCondition |
| Value |
“Use of this public-domain resource is unrestricted.” |
| Examples |
|
| Field |
mods:recordInfo |
| Value |
The Voyager BIB number is always required with the source “NIUDb.” |
| Examples |
|