Dublin Core Collection Description Working Group

1
Dublin CoreCollection DescriptionWorking
Group DC CD WG Meeting, DC-2005,Madrid, Spain,
Wednesday 14 September 2005 Pete
Johnston Research Officer, UKOLN, University of
BathChair, DC Collection Description Working
Group
UKOLN is supported by
www.bath.ac.uk
2
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/2006
• ------- Break --------
• Member Presentations
• Any Other Business

3
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

4
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

5
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

6
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 2005-08-25 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

7
Item
8
Activity 2004/2005
9
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

10
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)
• collectionC dcformat formatF .
• formatF a dctermsIMT .
• formatF rdfslabel "audio/mp3" .
• Or (2)
• collectionC someitemFormat formatF .
• formatF a dctermsIMT .
• formatF rdfslabel "audio/mp3" .
• Or (3)
• impossible to express

11
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

12
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

13
Issue 4 Collection Location, Collection
Service Relationships
Collection Location (RSLP CD model/schema)
Collection
Collection
Collection
14
Issue 4 Collection Location, Collection
Service Relationships
15
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

16
Issue 5.Subproperty relations and DCAPs

• "Associated Collection" dcrelation
• value is a collection
• "Associated Publication" dctermsisReferencedBy
• value type unrestricted, but not necessarily a
  collection
• But
• CollectionC dctermsisReferencedBy BookB .
• implies
• CollectionC dcrelation BookB .
• To avoid any ambiguity, preferable to use new
  subproperty of dcrelation for "Associated
  Collection"
• Same for dctermsabstract/dcdescription

17
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

18
Proposed Work Plan for 2005/2006
19
Dublin CoreCollection DescriptionWorking
Group DC CD WG Meeting, DC-2005,Madrid, Spain,
Wednesday 14 September 2005 Pete
Johnston Research Officer, UKOLN, University of
BathChair, DC Collection Description Working
Group
UKOLN is supported by
www.bath.ac.uk