August Dublin Core Collection Application Profile Task group Dublin Core Conference 2007, Singapour

August Members Leads: Sarah L. Shreeves/Muriel Foulonneau Ann Apps Douglas Campbell Ann Chapman Gordon Dunsire Tom Habing Pete Johnston John Phipps Theo van Veen Juha Hakala

August DCCAP Approval in March 2007 Comments cld:isLocatedAt is a sub-property of dc:Relation: when dumbing down the AP to DC, it may not make sense Cld:isLocatedAt vs cld:isAccessedVia vs dc:Identifier: traditional use of dc:Identifier to indicate the location. This could raise confusion, especially for physical vs digital collections Usage of « metadata records » in the library –world meaning, instead of in the larger DCAM meaning

August NISO MetaSearch Initiative NISO Standards Committee BB (Task Group 2): Collection & Service Descriptions developed a draft specification for collection description (see NISO Z x, Collection Description Specification DSFTU.pdf DSFTU.pdf is meant to be used by vendors, libraries, archives, and other organizations who are providing access to collections through metasearch applications such as Z39.50, SRU, and the NISO Metasearch XML Gateway Protocol Objective is to align with the current version of the DCCAP

August What we have to do the NISO set is very similar to the August 2005 DC Collection Description Mandatory elements not necessarily the same Specificities: Completeness XML bindings Terminologies

August Future Correct (small) inconsistencies found in DC Collections Application Profile (Oct 2007) - Sarah and Muriel Consider Usage Board's comments in their review (Oct 2007) - Task Group Complete alignment of the NISO Collection Description Standard with the DC Collections Application Profile (Oct 2007) - Sarah, Muriel, and Juha Assess and align current DC Collections Application Profile with current version of Abstract Model and ongoing work on Description Set Profiles. (DC 2008) Task Group Alignment with the current Abstract Model by the spring Usage Board meeting Alignment with the work on Description set profiles by DC2008

August Virtual Collections for researchers The HAL archive and The Digital Repositories Infrastructure Vision for European Research Dublin Core Conference 2007, Singapour

August The HAL platform

August Multiple portals, multiple deposit interfaces Deposit portals HAL INRIA HAL-SHS OTHER UNIV INRA haLhaL EXPORTS IMPORTS XML, WS TEL generic domain-dependent typological institutional OAI-PMH REDIF RSS Etc. Common metadataDomain-specific metadataInstitutional metadata

August The HAL platform hosts various portals

August Virtual collections in HAL The difference with portals: The same metadata set the same deposit interface Criteria for creating collections? Laboratories/Institutions Congresses Project BUT for display only Browsing Customizing interface

August A collection in HAL Stamps document Name Identifier Super-collection Display template (logo, css …) Automatic (query) or Manual collection process Creation date Administrator Person who requested the collection 08/16/2007

August The DRIVER project Objectives: The design of an infrastructure for digital repositories Proof of concept : National networks of institutional repositories Partners University of Athens (Gr) University of Bielefeld (Ger) CNR (It) SURF (NL) University of Nottingham (UK) Centre National de la Recherche Scientifique (Fr) University of Bath (UK) University de Warsaw (Pol) University of Ghent (Be) University of Göttingen (Ger)

August National networks From 5 countries with different IR networks history UK : SHERPA Belgium : under construction Netherlands : DAREnet Germany : DINI France : Archives-Ouvertes

August An infrastructure to connect « digital repositories » Distributed OAI-PMH, including DC-based guidelines Service oriented architecture (SOA) To facilitate the creation of services For access, customization etc (eg. The DRIVER demonstrator) To support research communities

August European repositories

August The distributed architecture (SOA)

August The demonstrator: a portal with collections

August A DRIVER collection

August Internal description of a virtual collection DRIVER internal system DCCAP NameIdentifier Title CreatorCollector AdministratorCollector Description Number of documents Size

August Also relations between collections + for a service Relation to other collections DRIVER internal system DCCAP FatherSuper- collection ChildrenSub-collection Property Inheritance DRIVER internal system Definition BeFrozenPropagation of properties to children Deletion Survival if father dies Functional for Display Icon Visibility

August Problem: how do you share collection structure? In HAL, OAI sets But does not share set description : OAI sets are metadata collections (see DLF Forum Spring 2006 presentation M. Foulonneau, C. Arms, S. L. Shreeves) Membership through the OAI infrastructure DRIVER guidelines include OAI sets by service provider Textual content in open access Need to build a Web service access But in DRIVER, membership is not an item property Registries such as OpenDOAR are based on repository description

August References HAL DRIVER project An article on HAL and DRIVER : The repository jigsaw 28