International Conference on Dublin Core and Metadata Applications DC-Scholar, 24 th September /10/2014 Scholarly Works Application Profile : reviewed Wednesday 24 th September 2008 Julie Allinson

BERLIN DC Scholarly Works Application Profile SWAP : a Dublin Core Application Profile (DCAP) for describing scholarly works (eprints) held in institutional repositories By ‘eprints’ or ‘scholarly works’, we mean –''scientific or scholarly research text'‘ (as defined by the Budapest Open Access Initiative iterature) iterature –including peer-reviewed journal articles, preprints, working papers, theses (just), book chapters, reports, etc.

BERLIN DC Application profiles according to Dublin Core

BERLIN DC Usage Board Review Criteria Objectives and scope Functional requirements Domain model Description set profile : description templates Description set profile : metadata terms used Syntax encoding guidelines / format [OPTIONAL] –Not reviewed as SWAP epdcx format will be deprecated for the new Dublin core XML encoding guidelines shortly 04/10/2014DC-Scholar, 24 th September

BERLIN DC Functional requirements Objective/Scope: Scholarly Works, for discovery … a richer metadata set – more properties, fit-for-purpose consistent, good quality metadata – less ambiguity and divergence unambiguous method of identifying full-text(s) distinguish open access materials from restricted support OpenURL link servers and support citation analysis identify the research funder and project code identify the repository or other service making available the copy say when a copy of a scholarly work will be made available better search and browse options some suggestions towards version identification Identifying duplicates and finding the most appropriate copy of a version support for added-value services 04/10/2014DC-Scholar, 24 th September

BERLIN DC Domain model A Domain model (also known as a data, application or entity-relationship model) to define the entities we need to describe, the relationships between them and the properties needed –domain models are not tied to any specific metadata vocabulary SWAP’s is based on FRBR It defines entities and relationships (and attributes) these appear as metadata properties in the description set profile Because it is based on the Dublin Core Abstract Model we can group together descriptions of the different entities in our model into a description set for sharing as a metadata record

BERLIN DC The model in pictures ScholarlyWork Expression 0..∞ isExpressedAs Manifestation isManifestedAs 0..∞ Copy isAvailableAs 0..∞ isPublishedBy 0..∞ isEditedBy 0..∞isCreatedBy 0..∞ isFundedBy isSupervisedBy AffiliatedInstitution Agent

BERLIN DC Example, in pictures My Paper ScholarlyWork 1 Publisher’s PDF Manifestation 2 Word Document Manifestation PDF Manifestation 2 Conference paper Expression Journal article Expression 1 PDF from Conference repository Copy 1 DOC in WRRO Copy 2 PDF from Publisher’s site Copy PDF in WRRO Copy

BERLIN DC Description set profile This defines our metadata properties, identifies which metadata vocabularies they are from and constrains how they are used – … description set profiles are relatively new in Dublin Core and can be machine-readable (there is an XML format) Additionally usage guidelines annotate the description set profile with human-readable guidance and examples The DSP says things like –This property can only appear once –This property can use the following Vocabulary Encoding Scheme –This property is a literal (a string) –This property can offer a link to a further description 04/10/2014DC-Scholar, 24 th September

BERLIN DC And so to SWAP SWAP passed the review with some minor corrections That’s great … but what does this really mean for implementation? or for other application profile developers? or for the DC-Scholar Community? Discuss …