DRSPT Catskills Institute

From Digital Scholarship Group
Jump to: navigation, search


General Information

Toolkit Site Development

Work being done in a Google Doc: https://docs.google.com/document/d/1COty0kx2VOnPxG15eN9luwV1XMfN3QkUYJbrCI_67ac/edit?usp=sharing


Record Analysis

Summary of Files

Number of files
  • 4366 files
  • 1375 parent objects and 2991 child objects
Types of objects
  • Complex objects
    • Consist of multiple image files
    • Most common types- post cards (2 pages/2 images), books and booklets (multiple pages/multiple images), brochures (complex page structure/multiple images, digital representation attempts to mimic experience of folding and unfolding brochure to see different parts)
    • Parent/child hierarchy
      • Parent displays entire digital object, multiple images, 1 METS record and 1 MODS record (represents entire object)
      • Parent points down to child items ("Page Image") and lists child items in order based on structure of object
        e.g. Child items for book listed in page number order
        Not sure how parent/child relationship structured on back end
      • Child item consists of single image and 1 METS and 1 MODS record
      • Child points up to parent (not sure how this is done on back end)
      • Parents and children have distinct PIDs


  • 4 records have additional titleInfo element with @displayLabel @type=“alternative"

Do the records use the nonSort field, or are initial articles included in the title field?

  • nonSort used along with partNumber and subTitle elements

How are names handled?

  • <mods:name type="[type]">
  • <mods:namePart>[name]</mods:namePart>
    • Personal names in indirect order
    • Personal names include <mods:namePart type="date">[inclusive dates]</mods:namePart>
    • Where necessary personal names, also include <mods:namePart type="termsOfAddress">[term of address]</mods:namePart>
  • Use role element with @roleTerm type=“text"
    • Agent and recipient used as values but are not on relators term list
    • 131 records have @authority=“marcrelator"

Are they stored in indirect order in the namePart field, or are name parts separated using the type attribute?

  • namePart [name in indirect order] for personal names

Does this field follow the MODS convention, or are there other values?

  • Follows convention
  • Values: still image, text, three-dimensional object
  • Not used with every record? investigate further

What controlled vocabulary, if any, is used for this field?

  • AAT
  • 3 records have no value for @authority
  • Place
    • 2 placeTerm elements
      • First element has @authority="marccountry," @type="code" the second element has @type="text"
      • Values are usually cities
  • What date fields are used? (dateIssued? dateCreated?)
    • CopyrightDate, dateCreated, dateIssued
  • Are approximate and questionable values represented with the appropriate attributes, or are there any extra characters in the date field, like "ca." or "?"? (Dates need to be stored in YYYY-MM-DD format in order for Solr to be able to index the records.)
    • Qualifiers are correct except for some inclusive dates, where instead of being expressed as two elements each with @point, it's expressed as one element with inclusive range as value

If the language field is used, what standard is used to control the language values?

  • ISO639-2b

Are they stored as values or codes?

  • Codes

Is this field used? If so, what subfields are used?

  • 1 extent element
    • Format: [extent]; [dimensions in cm]
  • 1 digitalOrigin element
  • Some records have note elements that contain cryptic alphanumeric codes
  • Some records have <mods:subject> opening tags in them

How is the abstract field used?

  • Generally 1 sentence description of what object is or is about, sometimes includes information about accompanying materials

Is this field used?

  • Only used for 1 digital object (20 files)

Is this field used?

  • No

If this field is used, what note types are there?

  • Some cryptic numeric and alphanumeric notes
    • Some of these are numbers that appear on original item
  • Additional description for post cards
    • e.g. "Message and address on the back" and also date postmarked and information about stamp, sometimes telephone numbers
  • Identifies items that are photocopies

Could this information be represented elsewhere?

  • Some could be moved to <abstract>

What controlled vocabulary, if any, is used for this field? What subelements, if any, are used?

  • No controlled vocabulary declared

Most subject headings are hierarchicalGeographic with some corporate names and personal names
<mods:hierarchicalGeographic />

<mods:country />
<mods:state />
<mods:city /> OR <mods:county />

Some geographic names represented with <mods:geographic />
For personal and corporate names

<name type="" />
<namePart />

Is this field used?

  • No

Is this field used?

  • Primarily used to identify item as part of Catskills Institute collection
  • Also used to identify item as part of series
  • Structure:
<mods:relatedItem displayLabel="Collection:" type="host" />
<mods:titleInfo />
<mods:title>Catskills Institute</mods:title>
<mods:identifier type="COLID">41</mods:identifier>
<mods:identifier type="URI">http://dl.lib.brown.edu/catskills</mods:identifier>
  • Some relatedItem elements have subject nested under them??

Is this field used?

  • Used in parent records to identify METS ID

Is this field used?

  • No

Is this field used?

  • No

Is this field used?

  • Used to identify order of child items
  • <mods:part />
<mods:extent />

Is this field used?

  • No

Is this field used?

  • No

Changes Made


edited titles to reflect Northeastern cataloging practice


MARC relators

  • Changed local value "recipient" to MARC relator term "addressee" (3 records)
  • Added @authority to all records, 5 records have @authority="local," all others value is "marcrelator"


added @authority="aat" to 3 records



  • removed unnecessary dashes from 5 dates
  • date syntax fixes
    • split inclusive dates into two elements, one with @point="start," other with @point="end" (69 records)


changed @type="code" to @type="text," changed element value from coded language value to full-text value (4070 records)


changed semicolon to [space]:[space] in extent element


added 1-2 LCSH topical subject headings to all parent records (1375) records


added "BDR_" to @type value for all parent records (1375 records)

Forthcoming Changes (with XSLT)


strip out Brown University-specific information


  1. Evaluate objects.
    • Examine objects in Brown digital repository to determine types of objects present and structure.
  2. Retrieve MODS records from Brown digital repository.
  3. Evaluate MODS records.
    1. Use XPath to examine each MODS element across the entire set of MODS records.
    2. Note practices employed by Brown and determine where they diverge from Northeastern practices and guidelines.
    3. Discuss findings with other project members. Determine changes that need to be made.
  4. Edit records to conform to Northeastern guidelines. Document any changes made to the MODS records.
    1. Copy the records you are editing to your desktop/laptop hard drive.
      • When you are editing, you should always be working with copies of the records, rather than the originals, that way if something goes awry, you always have the original records to go back to.
    2. Make changes that can be made en masse, using the Find/Replace in Files feature in Oxygen.
      • Before making any global changes, make sure that the "Make backup files" box is checked, in case a change does not work like you expected. In addition, after you click Replace All, a dialog box will pop up asking if you want to go ahead and make the changes or to see a preview. Always view the preview to take a look at a few records to ensure that the change you are making will work like you expect.
      • Examples: changing the value of an attribute for every instance of a particular element; changing the value of an element if it's the same across all of the records in your search results set.
    3. Makes changes that require hand-editing individual records.
      • Examples: Adding subject headings; altering titles.
  5. Replace original records with edited records.
    • Only replace the original records with the edited records once you have clearance from your supervisor.


Website structure

Structure map

Content from old site to be included in Phase 2

  • Conference
    • Papers
    • Reports
    • Purchase Recordings
  • Hotel and bungalow table
    • Ideally each hotel would have link that would search DRS for content related to that hotel
  • "History" section from old site
    • Interviews, articles, poems, etc.--there may be copyright issues with this
  • Links and resources
    • Some of the links are broken, someone will have to go through this to make sure it all works before it gets moved to the new site

Website Design

Home page wireframe

Other pages (no wireframes for these they're all either static and use basic WordPress functionality or layout will be determined by plugins or by browse/search tool Eli is designing to pull content from the DRS):


  • Static content with link to Join page


  • Content moved over from Become a Member page on the old site


  • Eli is designing this component

Discussion Board

  • Will require using a discussion board plugin--bbPress is widely used, well-documented, and has an active user community.


  • WordPress blog page


    • Static page with contact info