DCMI Administrative Metadata Working Group
NOTE: This proposal has been superceded by a newer version as of 2002-10-07.
AC - Administrative Components
Dublin Core™ DCMI Administrative Metadata
A proposal to be discussed in the DCMI Administrative Metadata Working Group
24 SEPTEMBER 2002
Creators:
Jytte Hansen, Danish Bibliographic Centre
Leif Andresen, Danish National Library Authority.
The process of this document
This proposal is for discussion in the DCMI Administrative Working Group in September 2002. Based on the discussion the authors will revise the document including adding some examples and present a new version on the DC-2002 in Florence in October 2002. Next step will be a formal approval in the working group. Parallel with this process the proposal will be sent to DCMI Directorate.
Please feel free to send comments and questions to the DCMI Administrative WG mailing list:
[email protected]
You are also welcome to send questions and proposals for editorial changes to the chair, Leif Andresen, [email protected]
Introduction
On the meeting on the working group in October 2001 a proposal for a A-Core (Administrative Core) was discussed. Based on the discussion we have revised the scope for this set of metadata for administrative use. First of all: the goal is not to promote a core set of metadata. The goal is to give a practical tool for users of metadata to manage metadata with special focus on interoperability between different systems. That is the reason for the in June 2002 announced changed name for this metadata set: Administrative Components.
This implies the limitations of this proposal: it is for administration of metadata - not for administration of resources. This aspect is handle by other communities (e.g. ISO TC46 / SC11) and another DCMI working group.
In consequence of the focus on interoperability between systems, we have renounced the idea of make a solution useable also in very simple implementation. We have also remarked the growing importance of XML, so this proposal is based on use of XML. This solves the problem of tying information together: e.g. creation of metadata record, date of creation, who create, comments to the creation etc.
This document does not provide guidelines for encoding Dublin Core™ in RDF/XML. Nor does it take a position on the relative merits of encoding metadata in 'plain' XML rather than RDF/XML.
This document sets out a three part proposal:
· Metadata for the entire record
· Metadata for update and change
· Metadata for batch interchange of records
General rules
The name of this metadata element set is Administrative Components.
The DCMI namespace URI is not yet determined, but shall follow the rules for DCMI namespaces. So the namespace for AC will be http://purl.org/dc/AC-terms/
All metadata elements are optional and repeatable. A specific implementation can define additional rules including that some elements are mandatory.
None of the elements are specified as mandatory for all kinds of use of AC. It is up to the individual project, organisation, website etc. to decide which elements are to be mandatory. A tool for that can be an Application Profile to specify instructions for use of Dublin Core, domain specific metadata element set(s) and metadata about management of the content metadata - including e.g. mandatory AC-core elements for specific use.
The idea is that the different projects, organisations, institutions etc. shall pick up the elements they can use.
This version only includes the definitions of the elements. In the next version we will complement this with some examples of XML records and practical use.
Formal definitions
Metadata for the entire record
Name: Identifier
Identifier: identifier
Definition: A string or a number, which identified the metadata record
Comment: Can be the internal number in a database.
Name: Scope
Identifier: scope
Definition: Declaration of the scope of application
Comment: Will often be declared by means of a separate form. This element can be used either as unstructured text just with an informal declaration like "national bibliography" or by using a SCHEME for a formal declaration like "catalogue code.
Name: Comment
Identifier: comment
Definition: Comment on the Acore metadata
Comment: E.g. comments pointing at special circumstances in connection with the transmitted metadata
Name: Metadata Location
Identifier: location
Definition: An unambiguous reference to the content metadata within a given context
Comment: This element is used if the content metadata and A-Core metadata
are not in the same location. Recommended best practice is to identify the content metadata by means of a string or number conforming to a formal identification system. Examples of formal identification systems include the Uniform Resource Identifier (URI) (including the Uniform Resource Locator (URL)) and the Digital Object Identifier (DOI).
Other identifiers, such as local repository/database keys, may be used.
Name Language
Identifier: language
Definition: Language of metadata
Comment: Encoded ISO 8601 ISO 639-2.
Name: Rights Ownership
Identifier: rights
Definition: Information about rights held in and over the content metadata
Comment: Typically, the Rights element will contain a rights management statement for the content metadata, or refer to a service providing such information. For at more detailed control specific projects can use a SCHEMEs for administration of rights for the specific project.
Name: Valid Date Range
Identifier: dateRange
Definition: The start and/or end date of the validity of the content metadata
Comment: Content metadata accessed outside the date ranges should be considered to be invalid.
Encoded to the W3C Profile of ISO 8601 including the use of the "/" to indicate the range scope. For example, "/1999-12-31" indicates validity up to 31 December 1999, "1999-01-01/" indicates validity from 1 January 1999 onwards, and "1999-01-01/1999-12-31 indicates validity between the two specified dates.
Name: Handling specification
Identifier: handling
Definition: Instructions for handling the administrative metadata and the metadata record in full. To this element is attached a SCHEME with the values:
· Harvest: the record shall be included in a harvesting
· Public: the content metadata must be shown to the public
· Manual: can the metadata record be checked automatically
· Keep: when adding administrative metadata, shall old versions of same element be kept
· Mail: Mail to be sent
Comment: This element defines instructions of future actions. (See also the element: Activity)
Metadata for update and change
Name: Activity
Identifier: activity
Definition: The action performed on the content metadata by the responsible entity
Comment: The actions are taken from a non-exhaustive list including:
created, submitted, modified, checked, link collected, resource harvested, expired, mail sent and three codes for deleted: delete_error_record, delete_disappearance and delete_out_of_scope
This list may be seen as showing the history of actions. (See also the element: Handling).
Other sources may be used for the activity values such as codes from the USMARC Relator List.
Refinements
Name: Name
Identifier: name
Definition: The name of the entity responsible for undertaking a defined action on the content metadata
Comment: Examples of Name include a person, an organisation, or a service.
Where the person has an affiliation with an organisation, this information may be included.
The name of a person should be provided in reverse order, that is, last name before first name, with a comma separator.
Name: Email Address
Identifier: email
Definition: Electronic Mail address for the responsible entity
Comment: The email address must be encoded to be consistent with Internet Address standard RFC822.
Name: Contact Information
Identifier: contact
Definition: Information on how to contact the responsible entity
Comment: The information should be one or more of: a street or postal address, a telephone number, a facsimile number, an Internet address, or other forms of physical or electronic contact information.
Links to full descriptions of the responsible entity may also be included, such as name registries.
Name: Date
Identifier: date
Definition: The date on which the activity took place by the responsible entity
Comment: Encoded to the W3C Profile of ISO 8601.
This unspecified date must be used in connection with a declared activity, e.g. "submitted"
Name: Affiliation
Identifier: affiliation
Definition: The organization with which the named person was associated when involved with the resource
Comment: Often the "affiliation institution" will be the formally responsible entity
Metadata for batch interchange of records
A number of elements relevant in connection with data exchange via batch files
Name: Database
Identifier: database
Definition: Code identifying a database
Comment: The code is used to identify the database to which a batch file is sent.
Is related to Metadata Location.
Name: Transmitter
Identifier: transmitter
Definition: Name or code for transmitter
Comment: The name/code (e.g. a library number) will be used to identify an organization with which formal routines of data exchange are established.
A code may include the type of transmitter (e.g. public library, research library, publisher)
Name: Filename
Identifier: filename
Definition: Name of a batch file
Comment: Name of the individual batch file. It may be combined with transmitter name.
Name: Technichal format
Identifier: technichalFormat
Definition: Technical data exchange format
Comment: The format is taken from a non-exhaustive list including:
ISO2709, XML, HTML
Name: Character set
Identifier: characterSet
Definition: Name of character set used
Comment: The character sets must refer to relevant standards
Name: Bibliographic format
Identifier: BibliographicFormat
Definition: Bibliographic format for data exchange
Comment: The actions are taken from a non-exhaustive list including:
MARC21, danMARC2, DC
Name: Address of result file
Identifier: resultFile
Definition: Localization of result file
Comment: E.g. an email address of a transmitter