• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Swap For Dummies Rsp 2007 11 29
 

Swap For Dummies Rsp 2007 11 29

on

  • 6,684 views

 

Statistics

Views

Total Views
6,684
Views on SlideShare
6,676
Embed Views
8

Actions

Likes
0
Downloads
37
Comments
0

1 Embed 8

http://www.slideshare.net 8

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

CC Attribution-NonCommercial-ShareAlike LicenseCC Attribution-NonCommercial-ShareAlike LicenseCC Attribution-NonCommercial-ShareAlike License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Swap For Dummies Rsp 2007 11 29 Swap For Dummies Rsp 2007 11 29 Presentation Transcript

  • SWAP FOR DUMMIES
  • Scholarly Works Application Profile
    • a Dublin Core Application Profile for describing scholarly works (eprints) held in institutional repositories
    • also known as eprints application profile – name changed due to confusion with EPrints
    • By ‘eprints’ or ‘scholarly works’, we mean
      • ''scientific or scholarly research text'‘
        • (as defined by the Budapest Open Access Initiative http:// www.earlham.edu/~peters/fos/boaifaq.htm#literature )
      • including peer-reviewed journal articles, preprints, working papers, theses (just), book chapters, reports, etc.
  • Application Profiles?
  • Application profiles according to Dublin Core
  • Application Profile components
    • A set of Requirements help us to understand what we need our metadata to do
    • 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
      • existing community domain models include FRBR, CIDOC CRM, CERIF
      • domain models are not tied to any specific metadata vocabulary
    • A Description Set Profile 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
      • metadata vocabularies examples: MODS, LOM, Dublin Core, FOAF
    • Usage guidelines provide guidance and examples for users on how to construct descriptions – they annotate the description set profile with human-readable information
    • For exchange, we also need machine-readable syntax guidelines and formats
      • e.g. the SWAP epdcx format, Dublin Core XML encoding guidelines
  • It’s all about interoperability
    • This is important, because it means metadata vocabularies and application profiles don’t provide a blueprint for internal database design
    • Rather, they offer a way of encoding and sharing metadata between systems
    • And a good place to start!
  • SWAP?
  • And so to SWAP
    • SWAP has all of the application profile building blocks
      • requirements specification
      • domain model
      • usage guidelines / description set profile
      • XML format
    • It is based on the Dublin Core Abstract Model – this allows us to group together descriptions of the different entities in our model into a description set for sharing as a metadata record
  • DCAM summary record (encoded as HTML, XML or RDF/XML) Slide courtesy of Andy Powell, Eduserv Foundation http://www.slideshare.net/eduservfoundation/the-dublin-core-abstract-model-a-packaging-standard description set description (about a resource (URI)) statement property (URI) value (URI) value string
  • SWAP Model
    • Based on FRBR
    • Defines entities and relationships
    • and ‘attributes’
    • these appear as metadata properties in the application profile
  • the model in pictures ScholarlyWork Expression 0..∞ isExpressedAs Manifestation isManifestedAs 0..∞ Copy isAvailableAs 0..∞ isPublishedBy 0..∞ 0..∞ isEditedBy 0..∞ isCreatedBy 0..∞ isFundedBy isSupervisedBy AffiliatedInstitution Agent
  • Enough theory : a worked example
    • An example of a Scholarly Work, containing two expressions.
      • Expression one has two manifestations, each with one copy.
      • Expression two has one manifestation with two copies.
    • The Scholarly Work
      • SWAP for Dummies by Beccy Shipman, University of Leeds; Julie Allinson, University of York; and Rachel Proudfoot, University of Botswana. A paper given at Open repositories 2008, 3rd April 2008
      • Expression one - published in the conference proceedings
          • Published online in the conference repository as a PDF [a manifestation with one copy ]
          • A word document of the same content is available in White Rose Research Online [a manifestation with one copy ]
      • Expression two - revised version published in a peer-reviewed journal
          • publishers PDF [a manifestation ]
            • available by restricted access from the publishers web site [a copy ]
            • a copy of the same, deposited in WRRO [a copy ]
  • Example, in pictures SWAP for Dummies 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
  • The Practical Bit
  • Exercise
    • Each of these entities is described with a defined set of metadata properties
    • Look at the SWAP application profile documentation
    • and the worked example provided
    • then, use the templates provided to ‘assemble’ a SWAP record
  • Why?
  • functional requirements
    • 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
  • Why Simple DC isn’t enough
    • <dc:title> multiple titles, what language?
    • <dc:creator> normalised form? person or org?
    • <dc:publisher> normalised form? person or org?
    • <dc:identifier> full-text or metadata? is it a uri?
    • <dc:date> of what? modification? publication?
    • <dc:format> is this a MIME type?
    • <dc:subject> local keyword or controlled scheme?
    • <dc:contributor> what did they contribute?
    • <dc:language> is this an RFC 3066 value?
    • <dc:relation> what relationship? is this a uri?
    • <dc:rights> what does this tell me?
    • <dc:source> is this a citation? or something else?
    <metadata> <dc:title> <dc:creator> <dc:publisher> <dc:identifier> <dc:date> <dc:format> <dc:subject> <dc:contributor> <dc:language> <dc:relation> <dc:rights> <dc:source> </metadata>
  • What does this tell us? SWAP for Dummies 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 These two are intellectually different ‘versions’ These two are the same, just in different formats These two are exact copies of each other, just in different places The identifier for this is a URI and will give me information about the work as a whole This one is restricted access This one is closed for two years The URI for this will get me directly to the copy
  • What this means ‘back home’
    • this relatively complex underlying model may be manifest in relatively simple metadata and/or end-user interfaces
    • existing systems probably capture much of this detail already but lack a data model and a mechanism for sharing their richer metadata
  • Back home in the repository
    • How can a repository manager make amendments to their metadata to become compliant with SWAP?
      • Know your own data model – what entities do you want to describe, what information do you need to describe them? Does that map to SWAP?
        • remember that SWAP can be used in a relatively ‘flat’ way
      • Check that your internal metadata maps to SWAP metadata properties; create additional elements if necessary
      • Configure your repository to expose epdcx (SWAP) records over OAI-PMH, or get your technical gurus to
      • Put pressure on EPrints and DSpace developers do the above, so that you don’t have to
  • More information
    • Documentation:
    • www.ukoln.ac.uk/repositories/digirep/index/SWAP
    • Dublin Core Scholarly Communications Community - for discussion, advice and suggestions for the future
      • [email_address]
    • Repository Support Project
    • www.rsp.ac.uk
    • Repositories Research Team
    • www.ukoln.ac.uk/repositories/digirep/