Note about Administrative Metadata
To be discussed on Break Out Session "Administrative Metadata" at the first day of 8th International Dublin Core Metadata Initiative Workshop (DC-8)
By:
Leif Andresen, Danish National Library Authority
Jytte Hansen, Danish Bibliographic Centre (DBC)
From different projects we have learned that projects based on Dublin Core also have a requirement for metadata about not the content of the described resource, but also about the metadata itself. Last year Debbie Campbell and Renato Iannella published a draft for an A-Core. As far we se the requirement is a longer list of elements and/or qualifiers. E.g. the Danish project Denmark’s Electronic Research Library (DEF) have a sub-project with a portal to resources on these libraries. It is based on harvesting metadata from the libraries. This project needed more complex metadata and makes their own DEF-namespace.
As appendix to this note there a list of element in the draft A-core and some examples of administrative Metadata.
We have asked for a Break Out Session on DC-8 and have a proposal:
Sent to DC General the 26th September 2000.
Appendix:
From:
The A-Core: Metadata about Content Metadata by R. Iannella and D.
Campbell
(Internet-Draft of 30 June 1999)
URL : http://metadata.net/admin/draft-iannella-admin-01.txt
| Name: | Name |
| Identifier: | Name |
| Definition: | The name of the entity responsible for undertaking a defined action on the content metadata |
| Obligation: | Mandatory |
| Name: | Email Address |
| Identifier: | |
| Definition: | Electronic Mail address for the responsible entity |
| Obligation: | Mandatory |
| Name: | Contact Information |
| Identifier: | contact |
| Definition: | Information on how to contact the responsible entity |
| Obligation: | Optional |
| Name: | Activity |
| Identifier: | activity |
| Definition: | The action performed on the content metadata by the responsible entity |
| Obligation: | Mandatory for the act of creation. Other actions are Optional |
| Name: | Date of Activity |
| Identifier: | date |
| Definition: | The date on which the activity took place by the responsible entity |
| Obligation: | Mandatory for the act of creation. Other dates are optional |
| Name: | Valid Date Range |
| Identifier: | dateRange |
| Definition: | The start and/or end date of the validity of the content metadata |
| Obligation: | Optional |
| Name: | Metadata Location |
| Identifier: | Location |
| Definition: | An unambiguous reference to the content metadata within a given context |
| Obligation: | Optional |
From:
Danish project Denmark’s Electronic Research Library (DEF) metadata description
|
Administrative metadata of DEF | ||
| Date for creating of record | DC.Date.X-MetadataCreated | ISO 8601 |
| Date for next check of record | DEF.Record-Next-Verified-Date | ISO 8601 |
| Date for last change of record | DC.Date.X-MetadataLastModified | ISO 8601 |
| Subject portal-PID | Fagportal.PID | -- |
| Link collector email | DEF.collectorEmail | |
| Record creators email | DEF.RecordCreatorEmail |
|
| Record created by | DEF.RecordCreatorUID |
User ID |
| Record modified by | DEF.RecordModifierUID |
User ID |
| Standard mail to resource webmaster after incl. in Food-i | DEF.ResourceNotification | - |
| Record Creator Comments |
DEF.RecordCreatorComments |
Free text |
| To be harvested | DEF.HarvestOption | DEFharvestoption |
| Status. Record to be showed outside editormodul | DEF.RecordStatus | DEFrecordstatus |
From:
The EUN Data Handbook and Publication Guidelines
URL: http://www.educat.hu-berlin.de/~kluck/datahandbook_V_300.htm
DC.Date.X-LastModified
| EUN.Metadata.Release |
| EUN.Metadata.DateLastModified |
| EUN.Metadata.Approver.PersonalName |
| EUN.Metadata.Approver.Address |
A note from The Danish Bibliographic Centre
Description of various needs for administrative metadata experineced by The Danish Bibliographic Centre
================================================================================
In addition to the DC element set, describing an Internet ressource, DBC has found a growing need to use metadata in connection with the administration of sets of "content" metadata. As described in the expired Internet Draft: The A-Core: Metadata about Content Metadata:
http://metadata.net/admin/draft-iannella-admin-01.txt
At this time we use the following types of administration information:
In connection with various types of cooperation projects, we are notified of the existence of an Internet ressourse. The notification is sent to us via the DC metadata form.The ressource will be catalogued by DBC and is only identified by title og URL - i.e. "content" metadata. In addition we need fields for a range of administrative information, e.g.:
Field stating area: e.g.: National bibliography. Various types of cooperation projects.
(This "field of area" should maybe lie "outside" the admin core as a declaration).
Contact person (email, telephone)
Institution (Address, email, telephone, etc.): Normally only necessary in connection with the first contact. (See below: the box "Background", a part of A-Core, used for administrative information that seldom changes).
Comments: Describing special circumstances in connection with the administration.
Dates: of notification, of administration (e.g. checking)
The "background" metadata is of course parallel with information handled in usual database systems, but it is in our context very often the same metadata which are used in the administration of "content" metadata.
DBC has another example of administrative usage in connection with the administration of the ISBN-system. In addition to ordinary address and contact information, there will be a need of fields with drop down menus choosing number of ISBN-numbers required. Of course the is not the core, but an example of a possible usage/extension.