SWORD v2 at JISC Depo meeting


Published on

Slides presented at the 1st March 2011 JISC Depo programme meeting.

Published in: Technology, Education
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

SWORD v2 at JISC Depo meeting

  1. 1. SWORD 2.0 Supporting Full Deposit Lifecycles Richard Jones richard@cottagelabs.com
  2. 2. The purpose of SWORD is to: Provide an interoperable interface that allows deposits to be easily made into repositories . What is the purpose of SWORD?
  3. 3. Deposit from a desktop client SWORD use cases e.g. DepositMO
  4. 4. Deposit to multiple repositories SWORD use cases e.g. OA-RJ Institutional repository Funder repository Subject-based repository
  5. 5. Deposit by lab equipment SWORD use cases
  6. 6. Repository to repository deposit SWORD use cases Institutional repository National repository
  7. 7. Publishing system / publisher to repository deposit SWORD use cases e.g. OJS client Publishing system (e.g. OJS) Long term storage repository
  8. 8. Research Information System to repository deposit SWORD use cases e.g. Bibapp client RePosit project Research Information System Long term storage repository
  9. 9. SWORD 2.0 Project Organisation Developers Tim Brody (EPrints Server) Richard Jones (Java Client) Stuart Lewis (PHP Client) Mark MacGillivray (BibApp Client, DSpace Server) Ben O'Steen (Python Client) Eddie Shin (Fedora Server) David Tarrant (EPrints Server) Project Team Paul Walk – Project Director Stuart Lewis – Community Manager Richard Jones – Technical Lead Technical Advisory Group ~30 International Members
  10. 10. Packaging* Metadata** Authentication Authorization * use Atom Multipart to avoid while still having a “default” format ** use Atom Entries to avoid while still having some metadata options SWORD 2.0 out of scope
  11. 11. SWORD 2.0 Timeline November – February Consultation and development of a draft profile and internet drafts March – May Client and Server Development
  12. 12. SWORD 2.0 Clients/Servers Clients PHP (+ Facebook) Java Python Ruby (+ Bibapp) Servers DSpace EPrints Fedora Simple SWORD Server
  13. 13. SWORD 2.0 Documents Internet Drafts Packaged Content Delivery over HTTP AtomPub Extensions for Packaged Content AtomPub Extensions for Scholarly Systems Atom Multipart Extensions for Packaged Content Profile SWORD Profile SWORD Ontologies
  14. 14. <entry xmlns=&quot;http://www.w3.org/2005/Atom&quot; xmlns:sword=http://purl.org/net/sword/> <content type=&quot;application/zip&quot; src=&quot;http://myrepository.ac.uk/geography-collection/deposit1.zip&quot;/> <sword:packaging>http://purl.org/net/sword/package/default</sword:packaging> <link rel=&quot;edit&quot; href=&quot;http://www.myrepository.ac.uk/geography-collection/my_deposit.atom&quot; /> <link rel=&quot;edit-media&quot; href=&quot;http://www.myrepository.ac.uk/geography-collection/my_deposit&quot; /> <link rel=&quot;http://purl.net/sword/terms/statement&quot; href=&quot;http://www.myrepository.ac.uk/geography-collection/my_deposit.rdf&quot; /> </entry> The Deposit Receipt
  15. 15. You Deposit your money You get a Receipt Your Statement tells you what happened to your money since A Banking Analogy
  16. 16. Introducing: The SWORD Statement It tells you what files were produced when the repository unpackaged your deposit It tells you what new files have been added to your deposit (e.g. via format migration, mediated deposit, etc) It tells you where to get the package(s) you originally uploaded It tells you where in the workflow your item is (or any other state that it might be in). For example, “under review” or “deleted”
  17. 17. <rdf:RDF xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot; xmlns:ore=&quot;http://www.openarchives.org/ore/terms/&quot;> <rdf:Description rdf:about=&quot;http://localhost/edit-uri/43/d0&quot;> <ore:describes rdf:resource=&quot;http://localhost/agg-uri/43/d0&quot;/> </rdf:Description> <rdf:Description rdf:about=&quot;http://localhost/agg-uri/43/d0&quot;> <ore:isDescribedBy rdf:resource=&quot;http://localhost/edit-uri/43/d0&quot;/> <ore:aggregates rdf:resource=&quot;http://localhost/part-uri/43/d0/example.zip&quot;/> <sword:originalDeposit rdf:resource=&quot;http://localhost/part-uri/43/d0/example.zip&quot;/> <sword:state rdf:resource=&quot;http://purl.org/net/sword/state/archived&quot;/> </rdf:Description> <rdf:Description rdf:about=&quot;http://localhost/part-uri/43/d0/example.zip&quot;> <sword:packaging rdf:resource=&quot;http://purl.org/net/sword/package/default&quot;/> <sword:depositedOn>2011-02-24T19:50:04Z</sword:depositedOn> <sword:depositedBy>sword</sword:depositedBy> </rdf:Description> <rdf:Description rdf:about=&quot;http://purl.org/net/sword/state/archived&quot;> <sword:stateDescription> The work has passed through review and is now in the archive </sword:stateDescription> </rdf:Description> </rdf:RDF> Can be an OAI-ORE Resource Map
  18. 18. Richard Jones - richard@cottagelabs.com Stuart Lewis - stuart@swordapp.org The SWORD project http://swordapp.org/ Funded by JISC http://www.jisc.ac.uk/ Licence Creative commons