��ࡱ�>�� BD����A��������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������q��?bjbjt+t+-NAA�;������]������������ �$�� ���������� � � � � � � $� ���� ������� Y������YYY������� �������� YBY� ��� ����-��0������ AC - Administrative Components Dublin Core DCMI Administrative Metadata Creators: Jytte Hansen, Danish Bibliographic Centre Leif Andresen, Danish National Library Authority The process of this document This version of AC - Administrative Components is sent to Dublin Core Directorate for publication as a DCMI Note after approval in DCMI Administrative Metadata Working Group in spring 2003. Introduction The goal of AC - Administrative Components is to provide a practical tool for users of metadata to manage metadata with special focus on interoperability between different systems. This indicates the limitations of this proposal: it is for administration of metadata - not for administration of resources. Relation to other initiatives: The focus for AC - Administrative Components metadata set is interoperability between systems with content metadata. Other initiatives have others focuses. The word "administrative" is in METS (Metadata Encoding & Transmission Standard) used for management of digital library objects. Other related functions are record keeping, resource management and preservation metadata. OAI-PMH (The Open Archives Initiative Protocol for Metadata Harvesting) includes some metadata elements for administration. For users of OAI-PMH information such as identifier and date will be handled by OAI-PMH and not AC. None of these initiatives meet all the requirements in relation to control interchange of metadata records between systems. This is the reason for the present specification. This document sets out a three-part proposal for a standard for administrative metadata: � Metadata for the entire record � Metadata for update and change � Metadata for batch interchange of records One informative annex complements it. AC - Administrative Components Dublin Core DCMI Administrative Metadata Final version JUNE 2003 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/ 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, web-site 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 elements for specific use. The idea is that the different projects, organisations, institutions etc. shall pick up the elements they can use. Definitions Metadata for the entire record Name: identifier Label: Identifier Definition: A string or a number, which identifies the metadata record Comment: Can be the internal number in a database. Name: scope Label: 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 Label: Comment Definition: Comment on the Administrative Component metadata Comment: E.g. comments pointing at special circumstances in connection with the transmitted metadata Name: location Label: Metadata Location Definition: An unambiguous reference to the content metadata within a given context Comment: This element is only used if the content metadata and administrative 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 Label: Language Definition: Language of metadata Comment: Encoded ISO 8601, ISO 639-2. Name: rights Label: Rights Ownership 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 SCHEMEs for administration of rights for the specific project. Name: dateRange Label: Valid Date Range 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 Label: Handling specification 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: the metadata record must 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: Action) Metadata for update and change Name: activity Label: Activity Definition: This element reflects an action performed on the content metadata Comment: The element functions as a container, which connects an action (see below) with the one responsible for its accomplishment, the date on wich the activity took place, etc. Refinements Name: action Label: Action 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 shows the history of actions. (See also the element: Handling). Other sources may be used for the action values such as codes from the USMARC Relator List. To this element is attached a SCHEME TypeOfActivity with the values: � created � submitted � modified � checked � link collected � resource harvested � expired � mail sent � delete_error_record � delete_disappearance � delete_out_of_scope Name: name Label: 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 Label: Email Address 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 Label: Contact Information 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 Label: Date Definition: The date on which the activity took place Comment: Encoded to the W3C Profile of ISO 8601. This unspecified date must be used in connection with an action, e.g. "submitted" Name: affiliation Label: 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 Label: 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 Label: 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 Label: Filename Definition: Name of a batch file Comment: Name of the individual batch file. It may be combined with transmitter name. Name: technicalFormat Label: Technical format Definition: Technical data exchange format Comment: The format is taken from a non-exhaustive list including: ISO2709, XML, HTML Name: characterSet Label: Character set Definition: Name of character set used Comment: The character sets must refer to relevant standards Name: BibliographicFormat Label: Bibliographic format Definition: Bibliographic format for data exchange Comment: The format are taken from a non-exhaustive list including: MARC21, danMARC2, DC Name: resultFile Label: Address of result file Definition: Localization of result file Comment: E.g. an email address of a transmitter Annex 1 Informative annex Examples of Encoding in XML of three records Namespaces: Beyond the actual namespaces of DCMI "dc" and "dcterms" these examples include the proposed namespace "ac" and namespace "dkbib" for elements, schemes, etc. defined specifically for interchange of DC records among Danish libraries.- --- metadatapool 870970 测试文件1 XML ISO8859-1 直流/交流 st@dbc.dk--- - 2 418 799 3 870970 NET200234-- 创建 2002-10-03 - 丹麦设计 向阿恩·雅各布森致敬 丹斯克m�贝尔昆斯特;丹斯克设计;工业设计;1900-1999 76.6 99.4雅各布森,阿恩f。1902 Nogle af designeren Arne Jacobsens (1902-1971) m�bler og indretningsartikler pr�senteres p� de lokaliteter hvor de i dag er placeret.Derudover vises m�bler og andre genstande fra en bred vifte af danske designere World Pictures 2002 文本/html http://www.worldpictures.dk/did/dfdindex/indexdid.html -- - 2 412 191 7 870970 IDO20228-- 创建 2002-06-12 - modified Andresen, Leif lea@bs.dk 2002-10-03 - 丹麦图书馆政策 最近文章和论文的选择 Thorhauge, Jens 藏书人;图书馆�森;丹麦; 02.26 来自丹斯克图书馆政治的艺术家 丹麦国家图书馆管理局 2002 应用程序/ pdf 410675字节 http://www.bs.dk/downloads/2302/Danish_Library_Policy.pdf -- - 2 381 393 9 870970 无法访问-- 创建 2001-11-30 - delete_disappearance 汉森,Jytte 2002-10-03 IDO200201- 来丹麦? a guide to education and training uddannelsessystemet;uddannelse;studieophold;Danmark;vejledninger;for udl�ndinge 37.36 定向直到udl�在丹麦学习期间,我将在丹麦进行监督,直到有人参加学习 西里乌斯 2001 应用程序/ pdf 870164 bytes http://www.ciriusonline.dk/download/Coming%20to%20Dk_654.pdf ��������C Q ���d�������o$�$***"*Q*E+�?������������������������������6� 5�6�mH 6�mH 5�mH mH H���������dE � � M � � �  + C D R S � , - ����������������������������H���������dE � � M � � �  + C D R S � , - � �����������)*��bc�����#��������������������������������������������� �����������������������v���w���6���7���z���{���������8���9���E���F���G���i������������������������������� ���� ����:- � �����������)*��bc�����#�����������������������������#�&1;Lakw�����\ !!�" #�#o$p$q$�$�$�$�%�%�&������������������������������&1;Lakw�����\ !!�" #�#o$p$q$�$�$�$�%�%�&�&~''.(/(W(�(�(�(~))*****#*$*Q*R*F+G+H+#;�?�?�����������������������������������������6�&�&~''.(/(W(�(�(�(~))*****#*$*Q*R*F+G+H+#;�?�?��������������������������+0P��. ��A!��"��#��$�n%����� [4@��4 NormalCJ_HmHsHtHFF Overskrift 1$���<@& 5�CJ KHBB Overskrift 2$�h@&^�h5�CJ>> Overskrift 3$���<@&5�FA@���F Standardskrifttype i afsnit8�O8 H2$�d�d@&5�CJ$htHu8�O8 H3$�d�d@&5�CJhtHuJ�OJ Blockquote�h�h�d�d]�h^�h htHu(U@�!( Hyperlink>*B*@Y2@ Dokumentoversigt-D OJQJ�; N�����? - #�&�?!#$&��?"%�8�@�����������0�( � ��B �S ���� ?�HH��<�������G,R,Y,e,�1�1�1�1 22 2,2777#7z7�7�7�7�;��%(03:=ANVcjmqy����H'M'$/0/$7&7�;�� Leif AndresenW\\BOB\LEA$\WPWIN61\PROJEKTE\METADATA\ADMIN Core\AdminComp final proposal March 2003.doc Leif AndresenW\\BOB\LEA$\WPWIN61\PROJEKTE\METADATA\ADMIN Core\AdminComp final proposal March 2003.doc Leif AndresenW\\BOB\LEA$\WPWIN61\PROJEKTE\METADATA\ADMIN Core\AdminComp final proposal March 2003.doc Leif AndresenLC:\WINDOWS\TEMP\Automatisk gendannet AdminComp final proposal March 2003.asd Leif AndresenLC:\WINDOWS\TEMP\Automatisk gendannet AdminComp final proposal March 2003.asd Leif AndresenM\\BOB\LEA$\WPWIN61\PROJEKTE\METADATA\ADMIN Core\AdminComp final June 2003.doc Leif AndresenBC:\WINDOWS\TEMP\Automatisk gendannet AdminComp final June 2003.asd Leif AndresenM\\BOB\LEA$\WPWIN61\PROJEKTE\METADATA\ADMIN Core\AdminComp final June 2003.doc Leif AndresenBC:\WINDOWS\TEMP\Automatisk gendannet AdminComp final June 2003.asd Leif AndresenM\\BOB\LEA$\WPWIN61\PROJEKTE\METADATA\ADMIN Core\AdminComp final June 2003.doc�@��&�&�]��&�&�;�@G��:�Times New Roman5��Symbol3&� �:�Arial5&� �:�Tahoma"0���Zvfcv�ks��&1h$������20d[<y� ?@��������C����������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������Root Entry�d�'s�s�d�'s�s�e��e�������� �F\�/�@1O��0�E�esl1Table���ally�k�'s�sj��������������ol`'s`s`�'s�s� �'s(P�'sWordDocument����0�����0�� �'s�s���������'s�s��'s�s��'s�ala-N�eSummaryInformation�ly�ous�ly�ic�(����������������������������������������1����DocumentSummaryInformation��������8������������������������������������������������9����CompObj����������������������������������������������������������������������j����ObjectPool������������������������������������������������������@1O��0�@1O��0�����������������������������������������������������������������������������������������s�s�ment�'s�ing�ly�ous�ly�ic������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������� ���� �FMicrosoft Word-dokument MSWordDocWord.Document.8�9�q