DC_tool_interoperability_andresen_DC2006

Dublin Core as a tool for interoperabilityCommon presentation of data from archives, libraries and museumsDC-2006 - 4 October 2006 : 

Dublin Core as a tool for interoperabilityCommon presentation of data from archives, libraries and museumsDC-2006 - 4 October 2006 Leif Andresen Danish National Library Authority

The speaker : 

Leif Andresen - DC-2006 Slide 2 The speaker Leif Andresen Library Advisory Officer Danish National Library Authority Chair Danish Standards S24 - Information and Documentation (Mirror committee ISO TC46) ISO TC46/SC4 Technical Interoperability Chair DCMI Standards Member Danish ALM standard WG

Presentation : 

Leif Andresen - DC-2006 Slide 3 Presentation Introduction ABM standard working group 2003 report 2006 report Common content format National addition: dkdcplus XML schema How to transport DC records Conclusion

Introduction : 

Leif Andresen - DC-2006 Slide 4 Introduction In 2003 the Danish Ministry of Culture entrusted the three national authorities: Danish State Archives Danish National Library Authority National Cultural Heritage Agency to develop recommendations for data content, data formats and data transport to facilitate presentation of joint information from archive, library and museum sectors

ABM standard working group : 

Leif Andresen - DC-2006 Slide 5 ABM standard working group Steering group: the heads of A, L and M national authorities Working group members: Danish State Archives City archives of Aalborg Danish National Library Authority State and University Library Aarhus National Cultural Heritage Agency (2)

First report (2003) : 

Leif Andresen - DC-2006 Slide 6 First report (2003) Point out Dublin Core as basis for interoperability - the WG don’t find alternatives Drafts for mapping between sector specific formats and Dublin Core Mapping cause loss of data Recommend XML and work out mapping

Refine requirements : 

Leif Andresen - DC-2006 Slide 7 Refine requirements Only data relevant to the public for search and presentation to be converted No need for all details in a common database Important to get a pointer (a link) to the original database No duplication of functionality, e.g. requests of library holdings - but links

Final report 2006 : 

Leif Andresen - DC-2006 Slide 8 Final report 2006 Based on first report Involvement of consultants from The Royal School of Library and Information Science and the company Index Data Complete mappings Develop XML schema

Staring point : 

Leif Andresen - DC-2006 Slide 9 Staring point Mapping from the ALM-formats should point to one of the fifteen basic Dublin Core elements if possible Refinements of Dublin Core should only be used if absolutely necessary Other metadata formats should only be used if absolutely necessary New additional Danish metadata elements should be the last option

Conditions : 

Leif Andresen - DC-2006 Slide 10 Conditions Different traditions in sectors Different registrations levels Collections with no details about the units Relation versus record databases Only libraries and local archives on document/unit level

Mappings : 

Leif Andresen - DC-2006 Slide 11 Mappings Developed mappings from four sector specific formats: Daisy for governmental archives Arkibas 4 for local archives danMARC2 for libraries Regin for museums

Dissimilarity for DC Creator : 

Leif Andresen - DC-2006 Slide 12 Dissimilarity for DC Creator Museum: person responsible for composition of museums file Library: Author, composer etc. Archive: institution or part of institution who established the archive So: some additional information needed to ensure informative presentation

Dissimilarity for DC Title : 

Leif Andresen - DC-2006 Slide 13 Dissimilarity for DC Title Museum: constructed - normally not titles in source system Library: mandatory Archive: constructed - normally not titles in source system

Common content format : 

Leif Andresen - DC-2006 Slide 14 Common content format The dkabm format consists of: dc: Dublin Core 15 basic elements dcterms: Dublin Core refinements ac: Administrative Components dkdcplus: Danish additions

Both general and specific : 

Leif Andresen - DC-2006 Slide 15 Both general and specific dkabm include guidelines for how to map to metadata elements not all elements in dc, dcterms and ac are used but no elements are excluded: the format is for broader use in the A, L and M sectors in library sector a extend profile is planed

dc: Dublin Core 15 basic elements : 

Leif Andresen - DC-2006 Slide 16 dc: Dublin Core 15 basic elements Title Creator Subject Description Publisher Contributor Date Type Format Identifier Source Language Relation Coverage Rights

dcterms: Dublin Core refinements : 

Leif Andresen - DC-2006 Slide 17 dcterms: Dublin Core refinements Used are: Alternative (Title) Extent and Medium (Format) isPartOf and HasPart (Relation) Spatial and Temporal (Coverage)

ac: Administrative Components : 

Leif Andresen - DC-2006 Slide 18 ac: Administrative Components Metadata about metadata needed to describe the source Metadata about metadata outside the scope of Dublin Core AC Identifier: Identification in original system for linking AC Source: Identify the delivering organisation/institution

dkdcplus: Danish additions : 

Leif Andresen - DC-2006 Slide 19 dkdcplus: Danish additions Elements: preferredName (Creator) alternativeName (Creator) actPeriod (Creator) with scheme Period version (Description) Schemes: SubjectType (Subject) Danish translation DCMI Type (Type)

dkdcplus: Version : 

Leif Andresen - DC-2006 Slide 20 dkdcplus: Version Version is the only general refinement hasVersion (Relation) is not useable: Definition is “A reference to a related resource” Many application profiles have version, edition or synonymous elements the IFLA metadata report is consulted http://www.ifla.org/VII/s13/guide/metaguide03.pdf

Comparison IFLA metadata and DC : 

Leif Andresen - DC-2006 Slide 21 Comparison IFLA metadata and DC

The combined schema (1) : 

Leif Andresen - DC-2006 Slide 22 The combined schema (1)

The combined schema (2) : 

Leif Andresen - DC-2006 Slide 23 The combined schema (2)

Survey of XML schemas (1) : 

Leif Andresen - DC-2006 Slide 24 Survey of XML schemas (1) dkabm.xsd: collecting schemas below dc.xsd: 15 basic Dublin Core elements ac.xsd: Administrative Components dkdcplus.xsd: defines Danish elements and subject lists dcterms_ext.xsd: import Danish elements from dkdcplus.xsd together with dcterms and dc

Survey of XML schemas (2) : 

Leif Andresen - DC-2006 Slide 25 Survey of XML schemas (2) dcterms.xsd: defines Dublin Core refinements dcmitype.xsd: defines Dublin Core resource types dktype.xsd: defines Danish language of DCMI types ISO639-2.xsd: defines valid language codes

dkabm XML schema : 

Leif Andresen - DC-2006 Slide 26 dkabm XML schema

Extract of dkdcplus XML schema : 

Leif Andresen - DC-2006 Slide 27 Extract of dkdcplus XML schema

Transport of metadata records : 

Leif Andresen - DC-2006 Slide 28 Transport of metadata records Harvesting OAI-PMH Search and retrieve SRU File transport National guidelines

Harvesting with OAI-PMH : 

Leif Andresen - DC-2006 Slide 29 Harvesting with OAI-PMH <ListRecords> <record> [DKABM-record] </record> <record> [DKABM-record] </record> </ListRecords>

Search and retrieve with SRU : 

Leif Andresen - DC-2006 Slide 30 Search and retrieve with SRU <searchRetrieveResponse> <records> <record> [DKABM-record] </record> <record> [DKABM-record] </record> </records> </searchRetrieveResponse>

File transport (national/local model) : 

Leif Andresen - DC-2006 Slide 31 File transport (national/local model) <collection> <record> [DKABM-record] </record> <record> [DKABM-record] </record> </collection>

Conclusion (1) : 

Leif Andresen - DC-2006 Slide 32 Conclusion (1) Dublin Core has three different roles in practical work: the original: a simple schema to register Internet documents the extended: as basis for project and domain specific registration schemas interoperability: as basis for interchange of information between domains

Conclusion (2) : 

Leif Andresen - DC-2006 Slide 33 Conclusion (2) This paper shows a way to use Dublin Core for interoperability between three related sectors. Arguably the sectors are related but with major differences. This indicates that Dublin Core has a more general role as carrier for interoperability.

Contact : 

Leif Andresen - DC-2006 Slide 34 Contact Leif Andresen Danish National Library Authority lea@bs.dk Report: http://www.kulturarv.dk/tjenester/publikationer/emneopdelt/kulturarv-it/abm2006/index.jsp