A centre of expertise in digital information management UKOLN is supported by: Dublin Core Collection Description Working Group DC CD WG Meeting, DC-2005, Madrid, Spain, Wednesday 14 September 2005 Pete Johnston Research Officer, UKOLN, University of Bath Chair, DC Collection Description Working Group

A centre of expertise in digital information management Dublin Core Collection Description Working Group Introduction Review of 2004/2005 activity Review of DC CD AP –Outstanding Issues Proposed charter/work plan for 2005/ Break Member Presentations Any Other Business

A centre of expertise in digital information management DC Collection Description Working Group Active 2001 (really 2003) - Growing interest in collection-level description for resource discovery Collection as "an aggregation of items" Collection-level description –information about collection as whole, rather than items Charter –Provide forum for sharing information about CLD activity –Develop a DC AP for collection-level description –Develop supporting materials for use of AP

A centre of expertise in digital information management DC Collection Description Working Group Informed by experience of RSLP CD (2000- ) RSLP CD Model –Entity-Relation model (Michael Heaney, University of Oxford) RSLP CD Schema –DC-based metadata schema (Andy Powell, UKOLN) –Subset/simplification of model –Significant influence on other initiatives But concerns over status, ownership, visibility, persistence, maintenance, etc

A centre of expertise in digital information management Functional Requirements for DC CD AP A "core" set of collection description properties –For simple collection-level descriptions –Suitable for a broad range of collections Allow a user to –Discover collections of potential interest –Identify a collection –Select one or more collections from amongst a number of discovered collections –Identify the location of the collection –Identify the services that provide access to the collection

A centre of expertise in digital information management DC Collection Description Application Profile (DC CD AP) Collection attributes (only) of RSLP CD Schema as starting point –excludes Location, Agent description –introduces Service as entity-type, but does not cover Service description Draft covers –Identification of collection –Content of items in collection –Process by which items gathered into collection –Ownership of collection –Rights of access to/use of collection –Location of collection –Services that provide access to collection –Relationships between collections

Item Collection is-gathered-into m n Location is-located-at m n Service is-accessed-via m 1 administers n m Agent collects m n owns m n Collection Description is-described-by 1 m

Activity 2004/2005 Oct 04Proposals for accrualMethod, accrualPeriodicity, accrualPolicy properties accepted by DCMI Usage Board. Nov 04/ Jan 05 Review of Collection Type Vocabulary: added Collection Description Types Jan 05Presentation to IESR workshop, London Mar 05NISO Metasearch Initiative; presentation to NISO MI meeting (Follow-up work on mappings) May/Jun 05Capture examples via Wiki template Jun/Jul 05Discussion of media-type of items/dc:format Jul 05Presentation to Distributed Service Registries workshop, Warwick, UK July/Aug 05Revised DC CD AP to specify value URI/value representation constraints Aug 05Draft DC CD AP to DCMI Usage Board for interim review DeferredSyntax guidelines, crosswalks

A centre of expertise in digital information management Issue 1. Value reference/representation "Do I use a (value) URI or a (value) string?" Added additional constraints to DC CD AP –value URI (M/O/N) –value string (M/O/N) –syntax encoding scheme –rich representation (M/O/N) Related descriptions may be available –but DC CD AP neutral on terms used

A centre of expertise in digital information management Issue 2. Media-type of items Functional requirement: search for/select collections according to media-type of items within collection –e.g. collections containing items of media-type audio/mp3 Either (1) –collection:C dc:format format:F. –format:F a dcterms:IMT. –format:F rdfs:label "audio/mp3". Or (2) –collection:C some:itemFormat format:F. –format:F a dcterms:IMT. –format:F rdfs:label "audio/mp3". Or (3) –impossible to express

A centre of expertise in digital information management Issue 3. Open-ended date ranges DC CD AP requires representation of open-ended date ranges W3CDTF date format does not support date ranges ISO8601 supports date ranges, but not open- ended ranges Requirement presented to DC Date WG –still work in progress Temporary solution –refer to Recordkeeping Metadata Schema extension to ISO 8601 –replace when DC Date WG formulates solution

A centre of expertise in digital information management Issue 4: Collection – Location, Collection – Service Relationships Collection –An aggregation of one or more items Location –A place where a collection is held –Michael Heaney, Analytical Model Service –A system that provides one or more functions of value to the end-user. Examples include: a photocopying service, a banking service, an authentication service, interlibrary loans, a Z39.50 or Web server –DCMI Type Vocabulary –Provided physically or digitally –User may be human, organisation or software application. (DC CD AP) Service –A system that provides access to the Items within the Collection

Issue 4: Collection – Location, Collection – Service Relationships Collection – Location (RSLP CD model/schema) Electronic Repository is-located-in Collection Location is-located-in Collection Physical Repository is-located-in Collection

Issue 4: Collection – Location, Collection – Service Relationships Collection Location is-located-in Collection Physical Repository is-located-in Collection Electronic Repository is-located-in Service is-accessed-via Physical Service is-accessed-via Network Service is-accessed-via

A centre of expertise in digital information management Issue 4: Collection – Location, Collection – Service Relationships Physical collection –easy to distinguish between Location (e.g. library (building), archival repository) Service (e.g. lending service, reference service etc) –distinction useful to user of description? Digital collection –distinction less clear? –less useful to user? –may describe only provision of access? Retain current distinction in DC CD AP –develop guidelines for physical/digital cases

A centre of expertise in digital information management Issue 5. Subproperty relations and DCAPs "Associated Collection" = dc:relation –value is a collection "Associated Publication" = dcterms:isReferencedBy –value type unrestricted, but not necessarily a collection But –Collection:C dcterms:isReferencedBy Book:B. implies –Collection:C dc:relation Book:B. To avoid any ambiguity, preferable to use new subproperty of dc:relation for "Associated Collection" Same for dcterms:abstract/dc:description

A centre of expertise in digital information management Activity for 2005/2006 Continue activity Charter still valid Main work items –Revise DC CD AP in response to Usage Board review –Complete DC CD AP Item Format proposal Location v Service Open date range formats (DC Date WG) –Provide supporting materials Bindings, guidelines, crosswalks

A centre of expertise in digital information management Proposed Work Plan for 2005/2006 ItemStartEnd 1Revise in light of Usage Board review Resolve item media-type issue Finalise isLocatedIn/isAccessedVia properties Work with DC Date WG on date range format ? 5Update DCAP Syntax (based on work by DC Arch WG) ? Crosswalks Usage Guidelines Usage Board Review

A centre of expertise in digital information management UKOLN is supported by: Dublin Core Collection Description Working Group DC CD WG Meeting, DC-2005, Madrid, Spain, Wednesday 14 September 2005 Pete Johnston Research Officer, UKOLN, University of Bath Chair, DC Collection Description Working Group