== Dublin Core == The Dublic Core !DataStreams contain the bibliographic metadata about the object. Or more precisely, the metadata about the item, that the digital object represents. So, do not encode in dublin core, who made the digital object, or when. Fedora will handle this internally. Rather, encode who made the original article, and when. If the object does not represent something realworld like that, just don't encode any metadata in dublin core. === The DC Datastream === The Fedora Dublin Core (DC) datastream ''has'' to be present in a Fedora object. It only accepts restricted dublin core, and will therefore not be used. Fedora '''demands''' that the title field is set, but otherwise no DC fields may be set in a DOMS object. The title element must always have the same value as the DomsDC title element. === The DomsDC Datastream === The '''DOMS''' Dublin Core (DomsDC) datastream ''has'' to be present in a DOMS object. The DomsDC is the primary Dublin Core of the digital object and it uses qualified Dublin Core. The official list of Dublin Core terms can be found at http://dublincore.org/documents/dcmi-terms/ All DOMS objects MUST have the title element set. The value depends on the type of object, and can be found under the description of the object type. All other DC elements are allowed, but not required. The only exception is objects of [[DataModel/Type file| Type_file]]. These objects must not contain any other DC terms than title. ## * '''title''' ## * A name given to the object. The title will be a name by which the object is formally known. ## * '''creator''' ## * An entity primarily responsible for making the resource. Can be a person, an organization, or a service. ## * '''subject''' ## * The topic of the resource, or keywords, phrases, or classification descriptors that describe the subject or content of the resource. Use the collection-name, if nothing else is applicable. ## * ''description'' ## * An account of the resource, but only short text, no images. Description may include but is not limited to: an abstract, a table of contents, or a ##free-text account of the resource. ## * '''publisher''' ## * An entity responsible for making the resource available. Can be a person, an organization, or a service. ## * ''identifier'' ## * ''Collection-objects:'' Collection-specific access-point, specified by URL. Example: http://vortsognshistorie.dk ## * ''Other objects;'' The object in collection-specific context, specified by URL. Example: ##http://vortsognshistorie.dk/record.jsp?ref=040293&browse=yes ## * ''type'' [[BR]] Not used, as types are modelled by relations to type objects? ## * ''contributors'' [[BR]] Not used. ## * ''language'' - http://www.ietf.org/rfc/rfc3066.txt http://www.w3.org/WAI/ER/IG/ert/iso639.htm ## * A language of the resource, using a controlled vocabulary such as RFC 3066 [RFC3066]. This will often be danish ("da"). ## * ''relation'' [[BR]] Not used. ## * ''date'' - http://www.w3.org/TR/NOTE-datetime ## * Start date for the object in DOMS-context. ## * ''Note:'' Metadata for dates, regarding the content, are to be stored in dc:coverage. ## * ''format'' [[BR]] Not used, as format are modelled by relations to format objects? ## * ''source'' ## * DCMI: The resource from which the described resource is derived. The described resource may be derived from the related resource in whole or in ##part. Recommended best practice is to identify the related resource by means of a string conforming to a formal identification system. ## * ''Collection-objects:'' As defined by DCMI, if the collection is based on a limited and uniquely identifiable source, else a textual description. ## * ''Other objects;'' As defined by DCMI, if the object represents a ''work'' or similar. If the object describes part of a work or is fully ##disconnected from outside sources, a PID to one or more Fedora objects should be used. ## * ''coverage'' - http://www.getty.edu/research/tools/vocabulary/tgn/index.html ## * The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant. ##Spatial topic may be a named place or a location specified by its geographic coordinates. Temporal period may be a named period, date, or date range. A ##jurisdiction may be a named administrative entity or a geographic place to which the resource applies. Recommended best practice is to use a controlled ##vocabulary such as the Thesaurus of Geographic Names [TGN]. Where appropriate, named places or time periods can be used in preference to numeric ##identifiers such as sets of coordinates or date ranges. ## * ''Rights'' Not used, as rights are modelled by relations to rights objects? ## Giving hard rules about the contents of the DomsDC will be restrictive for most objects, and as we allow multiple inheritance, possibly conflicting. But File and Fileformat objects tend ## not to be subclasses or collection specific, and giving the DomsDC meaningful content can be difficult. So for these, the rules are described below. ## == File objects == ## * '''title''': ## * '''creator''': The collection, or subcollection that added this file to DOMS ## * '''subject''': ## * '''publisher''': "Statsbiblioteket" ## == Fileformat objects == ## * '''title''': "DOMS Fileformat " ## * '''creator''': "Statsbiblioteket"/"State and University Library of Denmark" ## * '''subject''': '''title''' ## * '''publisher''': '''creator'''