Skip to content

Latest commit

 

History

History
119 lines (114 loc) · 4.3 KB

classSchema.md

File metadata and controls

119 lines (114 loc) · 4.3 KB

Schema for Aggregation Party

For your crosswalk (draft due 4/29), map your own schema to the class schema below. Include details on how you will normalize your data values (if necessary) to meet the requirements of the target schema. For instance, you may need to trim your creation dates back to only yyyy or replace personal name URIs with string values.

For the aggregation party (5/6), you will bring 20 of your records transformed from your own schema to the class schema. Serialize your records in a single csv file (element names in the top row as a header, one record per row below). Separate repeated values within a single cell with semicolons.

We will be trying out some of Viewshare's visualization tools, including the Map View, so I strongly encourage you to include geographic coordinates for any spatial data you may have.

REQUIRED
Element Definition Repeatable? Comments
dc:title The title of the resource. Y
dc:identifier A unique reference to the resource within the context of our aggregated class data. N The only reason your identifier may duplicate another classmate's is if you are both describing the same resource (ex., ISBN). Please make an effort to create unique identifier
dc:type The nature of the resource. Y Select value(s) from the DCMI Type Vocabulary.
dc:publisher The entity responsible for making the resource available. N Normally, this is the name of the organization making the digital resource available. For our purposes, use your own name (or handle, if you don't want your real name out there in public).
dc:rights Information about rights held in and over the resource. N This should be a brief, free-text statement about rights and permissions regarding the resource (not the metadata!)
RECOMMENDED
dc:creator An entity primarily responsible for making the resource. Y Use a text string for this value rather than a URI.
dc:date The date associated with the creation of the resource. N Encode in ISO 8601 for single year only: yyyy. No date ranges--choose a single date.
dc:description An account of the resource. N
dc:subject The topic of the resource Y Unless part of a subject string, enter geographic or temporal subjects in dc:spatial and dc:temporal.
dc:language A language of the resource Y Use the full text of the language, not the code.
OPTIONAL
dc:contributor An entity responsible for making contributions to the resource. Y Use a text string for this value rather than a URI.
dc:spatial The geographic coverage of the resource. Y Include coordinates in local:coordinates
dc:temporal The temporal coverage of the resource. Y Free-text, may include LC subdivisions, date ranges, etc.
local:coordinates Any spatial coverage of the resource expressed in latitude, longitude Y Include both latitude and longitude in this format: latitude,longitude
local:url The online location of a digital resource N If you are describing a resource online, include the URL here. It may be a duplicate of dc:identifier.
local:genre The specific genre of the resource Y Use this field for types more specific than DCMI type, (ex., "postcards" or "books").