| 
  • If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • Finally, you can manage your Google Docs, uploads, and email attachments (plus Dropbox and Slack files) in one convenient place. Claim a free account, and in less than 2 minutes, Dokkio (from the makers of PBworks) can automatically organize your content for you.

View
 

CCMetadataEntryRules

Page history last edited by PBworks 14 years, 9 months ago

CyberCemetery Metadata Entry Rules

Starr Hoffman

7.9.2006; edited on 9.14.06


These rules are designed to make metadata entry straightforward and standard. This is currently a changing document.

 

 

DC Title

  • use the title coded in the html metadata as "officialtitle"
  • if this is not available, use what appears to be the title on the homepage by using visual cues:
    • appears near the top of the document
    • appears on multiple pages of the website
    • uses a larger, colored, and/or different font than the main text
  • if the html metadata title differs from the homepage title, enter the html title under "DC Title" and the qualifier "officialtitle," then select "add" for a second title, and select the qualifier, "alternatetitle"
  • if other title(s) appear elsewhere in the site, add them as alternate titles as well (or select the qualifier that best describes each title)

 

DC Creator

  • distinguishing between Creator / Contributor / Publisher may be difficult
  • "An entity primarily responsible for making the content of the resource. Examples of Creator include a person, an organization, or a service. Typically, the name of a Creator should be used to indicate the entity."
  • currently, do not enter titles (such as Ms., Dr. , Rev.)
  • enter names in this format: Last, First
  • use qualifiers to note specific role, when possible
    • example: for the Access America e-zine website, Patricia Wood is marked as "Creator" and qualified as "editor" (she was the editor-in-chief)

 

DC Subject

  • enter as many and as specific subject terms as possible to encourage discovery
  • controlled vocabulary: LIV
  • obtain subjects by:
  • reading/evaluating site
  • site description
  • "about" or "intro" page

 

DC Description

  • use the description coded in the html metadata as "description"
  • if this is not available, look on the homepage and rest of website for a summary, abstract, description, or "about us" page
  • if this is not available, write a brief description of the site

 

DC Contributor

  • distinguishing between Creator / Contributor / Publisher may be difficult
  • “An entity responsible for making contributions to the content of the resource. Examples of Contributor include a person, an organization, or a service. Typically, the name of a Contributor should be used to indicate the entity.”
  • in the example mentioned under "Creator," the non-editorial staff were classed as "Contributor"
    • these examples could be either left without qualifiers (since the site calls them "contributors"), or qualified as "correspondent"
  • when possible, use qualifiers to illuminate the role of each contributor

 

DC Publisher

  • distinguishing between Creator / Contributor / Publisher may be difficult
  • may often be the Government Agency responsible for the site
  • “An entity responsible for making the resource available. Examples of Publisher include a person, an organization, or a service. Typically, the name of a Publisher should be used to indicate the entity.”
  • like Creator, currently, do not enter titles (such as Ms., Dr. , Rev.)
  • like Creator, enter personal names in this format: Last, First
  • enter full agency names; do not use acronyms/abbreviations

 

DC Identifier

  • currently, use the URL (permalink)

 

DC Source

 

DC Relation

 

DC Language

  • default English (eng), unless other languages are included

 

DC Coverage

  • input the time period, place name, single date, and/or date range
  • in most cases, place name = United States
  • for a "snapshot" of a website, enter a date range
    • example: start date range: 1999-03-09 (date site first published online)
    • end date range: 2001-01-03 (date of capture)

 

DC Date

  • format
    • year-month-day (four-digit year, two-digit month and day)
    • i.e.: 2001-01-03 for January 3, 2001
  • follow CRS practice of dating days as “01,” if the specific date was not recorded
    • i.e., if you have "August 2001," enter 2001-08-01
  • currently, there are no qualifiers for date, thus:
    • enter the site creation date (if present)
    • if there isn't one, use the last modified date (if present)
    • if there isn't one, use the harvest date

 

Future DC Date Thoughts

  • enter each of these various kinds of dates (repeatable), and select the appropriate qualifiers:
    • site creation date
      • will not always be present; optional
      • qualifier: "sitecreationdate?"
    • site last modified date
      • will not always be present; optional
      • qualifier: "modifieddate?"
    • harvest date
      • for this information, see: G:/digital projects/CyberCemetery/CCdocumentation.xls
      • qualifier: "harvestdate?"
    • date made public (on CC)
      • for this information, see: G:/digital projects/CyberCemetery/CCdocumentation.xls
      • qualifier: "publicdate?"
    • metadata creation
      • automatically generated
    • metadata modification
      • automatically generated

 

DC Resource Type

  • currently, use "interactive_resource" for website
  • adding qualifier "website"

 

DC Format

  • currently, use "other"
  • adding qualifier "website"

 

DC Rights

 

Institution

  • select "UNT"

 

Collection

  • select "UNTGD"
  • added option "GDCC" (use both)

 

System

  • UNT Digital Collections

 

Digital Objects

  • enter the number of digital objects (files) associated with the website

 

Permalink

  • enter the permalink/URL here


Back to CyberCemetery Metadata Working Plan

Back to CyberCemetery Metadata

Back to GovDocs Notes & Training

Back to Front Page

Comments (0)

You don't have permission to comment on this page.