SWORD: The Story So Far
Upcoming SlideShare
Loading in...5
×
 

SWORD: The Story So Far

on

  • 3,714 views

Seminar on SWORD at UKOLN by Adrian Stevenson on 24th September 2007, University of Bath, UK

Seminar on SWORD at UKOLN by Adrian Stevenson on 24th September 2007, University of Bath, UK

Statistics

Views

Total Views
3,714
Views on SlideShare
3,712
Embed Views
2

Actions

Likes
0
Downloads
3
Comments
0

1 Embed 2

http://www.slideshare.net 2

Accessibility

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
  • SWORD ‘itself’ is the profile of APP. Essentially 2 strands: The profile The test implementations Advocacy/dissemination
  • Didn’t want to reinvent the wheel Looked at a range of existing standards
  • ATOMPUB came out as best fit Used for publishing blog posts
  • Thorny issue of package support MIME Multipurpose Internet Mail Extensions (MIME) is an Internet standard that extends the format of e-mail to support: * Text in character sets other than ASCII * Non-text attachments * Message bodies with multiple parts * Header information in non-ASCII character sets Not enough information to dscribe compund types and their content So, SWORD extends atomPub to understand and accept packages – significant part of the profile
  • Some issues with X-On-Behalf-Of and looking at this now I may be a cataloguer or repository metadata expert submitting on behalf of an author
  • Auto- discovery – link rel=“sword” href=[service doc url] Nested Service Desc: No of collections in server system can become v large such that APP service doc becomes too large. So SWORD adds sword:service as a child of app:collection APP doc to allow nesting
  • This is how 1.2 differs from 1.3
  • Web architecture based with standard GET and POST Make a request to GET a service doc The service doc explains the service in terms of its collections and what file types and packages it can accept, developer extensions etc. HTTP response details whether the deposit has been successful
  • Number of clients – some SWORD funded, some other JISC and wider projects.
  • Drop down for SWORD demo repos or can test your own Can be implemented via any website Can have own repositories list and own look and feel – radio buttons Highlight the on behalf of
  • Service details highlight – version, developer functions, max upload size Info about the collections - Open and Geography collection What they accept
  • FeedForward is a desktop application that keeps you on top of your personal information environment, enabling you to scan, organise, remix, and republish entries from your feeds to everything from Twitter to bibliographic databases
  • JISC had strong ideas on this. Devise a model for supporting SWORD including developing a website knowledge base and enhanced documentation including a technical primer for SWORD implementers. Develop additional SWORD usage and implementation case studies e.g. based on Microsoft uptake Hold SWORD promotional event with show-and-tells, demonstrations, and technical workshops
  • Develop a ‘SWORD enabled’ repositories registry prototype and populate for use in promoting SWORD uptake.
  • Any suggestions for other

SWORD: The Story So Far SWORD: The Story So Far Presentation Transcript

  • UKOLN is supported by: SWORD: The Story So Far 24 th September 2009 UKOLN Seminar University of Bath Adrian Stevenson SWORD Project Manager
  • SWORD Quick Introduction
    • Vision: “lowering barriers to deposit”
    • S imple W eb service O ffering R epository D eposit
    • Aims to provide a standard mechanism for ‘doing deposit’ into repositories
    • JISC funded project started 2007, SWORD 2 from June 2008
    • SWORD3 starting now!
  • What is it?
    • A lightweight protocol for deposit
    • A profile of the Atom Publishing Protocol
    • Implementations of SWORD in IntraLibrary, Fedora, DSpace and Eprints repositories
    • SWORD clients – web-based, desktop,, Facebook client, MS Office add-on, widgets
  • Motivations – why?
    • no standard interface for tagging, packaging or authoring tools to upload objects into a repository
    • no standard interface for transferring digital objects between repositories
    • no way to deposit into more than one repository with one ‘click’
    • no way of initiating a deposit workflow from outside a repository system
  • Use Cases
    • Deposit from a Desktop/Online tool
    • Multiple deposit - e.g. deposit to institutional and (mandated) funders’ repository with one action
    • Machine deposit - e.g. automated deposit from a laboratory machine
    • Migration/transfer - e.g. to a preservation service
    • Mediated deposit - e.g. deposit by a nominated representative, to additional repositories
  • The Project Partners
    • SWORD partners:
      • UKOLN - Adrian Stevenson (Project Management, some content)
      • University of Cambridge – Jim Downing (Profile)
      • University of Aberystwyth (DSpace, Fedora, & clients) –
      • Stuart Lewis, Neil Taylor, Glen Robson, Richard Jones
      • University of Southampton (EPrints) – Les Carr, Seb Francois
      • Intrallect (IntraLibrary) – Andrew Robson
      • University of York - Julie Allinson
      • SWORD3 – Scott Wilson, Anyone else?
  • SWORD AtomPub Profile
  • Standards
    • WebDAV (http://www.webdav.org/)
    • JSR 170 (http://www.jcp.org/en/jsr/detail?id=170)
    • JSR 283 (http://www.jcp.org/en/jsr/detail?id=283)
    • SRW Update (http://www.loc.gov/standards/sru/)
    • Flickr Deposit API (http://www.flickr.com/services/api/)
    • Fedora Deposit API (http://www.fedora.info/definitions/1/0/api/)
    • OKI OSID (http://www.okiproject.org/)
    • ECL (http://ecl.iat.sfu.ca/)
    • ATOM Publishing Protocol (http://www.ietf.org/htmlcharters/atompub-charter.html)
  • “ The Atom Publishing Protocol is an application-level protocol for publishing and editing Web resources”
    • benefits
      • supports many parameters and requirements - file deposit
      • already exists and has growing support - blogs
      • has an extension mechanism
      • good fit with Web architecture
    • drawbacks / risks
      • retrofit?
      • designed for a single package/file or an atom document – means that we need to package metadata and files
  • SWORD AtomPub Profile
    • SWORD profile builds on AtomPub
    • Provides set of extensions, constraint relaxations and enforcements for:
      • Clients posting compound resources (zip,tar)
      • When mediated deposit required
      • Where workflows involved
    • Part A adds to AtomPub, Part B highlights how SWORD diverges
    • SWORD compliance does not preclude AtomPub compliance
  • SWORD APP Package Support
    • AtomPub uses MIME to describe resources
    • Inadequate for compound types e.g.
      • Zip, tar
      • METS, IMS-CP, MPEG21, DIDL packages
    • SWORD extends AtomPub:
      • sword:acceptPackaging element
      • Value taken from SWORD package types
  • SWORD APP Mediated Deposit
    • SWORD deposit client user may not be owner of resource
    • SWORD allows clients to set a HTTP header:
      • X-On-Behalf-Of
    • Assumes trust between owner and mediating user
  • SWORD APP Developer Features
    • No-Op (Dry Run)
    • Verbose Output
    • Client and Server Identity
    • Auto-Discovery
    • Error Documents
    • Nested Service Description
  • SWORD APP Error Documents
    • SWORD adds new class of doc to AtomPub to allow better error description
      • ErrorContent
      • ErrorChecksumMismatch
      • ErrorBadRequest
      • TargetOwnerUnknown
      • MediationNotAllowed
  • SWORD Profile of AtomPub
    • Part B follows AtomPub spec highlighting where SWORD profile diverges
    • Covers:
      • Protocol Operations
        • Retrieving Service Document
        • Listing Collections
        • Creating a Resource
        • Editing a Resource - Not currently implemented
      • Category Documents – MUST NOT be required
      • Service Documents
        • SWORD requires support for service documents
        • new elements: version, verbose, noOp, maxUploadSize
  • SWORD v1.3 Profile Updates
    • SWORD Profile Version 1.3 includes:
    • Revised deviations from AtomPub and Atom
      • increasing requirement for persistent Atom Entry Documents
    • Includes description of SWORD specific extensions
    • Removed notion of levels of compliance
    • Added sword:userAgent, sword:error, sword:service, sword:version and sword:maxUploadSize elements
  • How it Works
    • APP and SWORD work by issuing HTTP requests (GET, POST)
      • GET Service Document (explain/discover)
      • POST a file or package to collection URI
    • HTTP response and ATOM document is returned
    • HTTP basic authentication is required
  • SWORD In Use
  • Implementations
    • Repository implementations
      • DSpace
      • EPrints
      • IntraLibrary
      • Fedora
    • Client implementations
      • command-line, desktop and web clients
      • Facebook Client
      • Java, PHP and .NET libraries
      • Deposit from within MS Word
      • Feedforward / FOREsite and others: http://www.swordapp.org/sword/implementation
  • Web Interface
  • Fedora deposit
  • Fedora Deposit response
  • Validation
  • Deposit via Facebook
  •  
  •  
  •  
  •  
  •  
  • Netvibes Widget
  •  
  •  
  • Deposit in Intralibrary
  • FeedForward Deposit
  • Intralibrary preview of deposited item
  • OfficeSWORD Add-on
    • http://www.codeplex.com/OfficeSWORD
  • SWORD in use
    • In addition to the case study implementations:
      • Feedforward has implemented
      • ICE project is using SWORD
      • EU PEER project implementing SWORD
      • Microsoft Zentity Research-Outputs Repository
      • OAI-ORE - FOREsite work
      • EM-Loader
      • YODL-ING – University of York
      • Others coming along all the time
    • Collaboration with Nature Publishing Group
    • Any more? Let us know.
  • SWORD Phase 3
    • 11 months, starting now
    • S upport interest and activities around SWORD
    • SWORD package types registry
    • SWORD enabled repositories registry?
    • Formal standardisation?
    • R enewed and increased advocacy efforts
  • WP2: Community Support & Advocacy
    • Reflective piece on why SWORD has been a success
    • Devise a support model for SWORD
    • Increase uptake by marketing and promotion
    • Additional use and implementation case studies
    • Feed into the developer community work
  • WP3: Development work
    • Maintenance and development of SWORD application profile
    • Update SWORD demonstrator repositories and clients
    • Synergies with project activity in the area
    • Tie in with repository handshake strand of international repositories workshop
  • WP4: Prototyping Registries
    • Prototype SWORD package types registry.
    • P rototype ‘SWORD enabled’ repositories registry?
    • Explore adding ‘SWORD enabled’ info to existing registries e.g. OpenDOAR
  • WP5: Standardising SWORD
    • Investigate standardising SWORD profile with e.g. NISO, CEN, and others. Suggestions?
    • Evaluate cost/benefit and make recommendations.
    • Consider alternatives to formal standardisation
  • More Info and Contact
    • SWORD Website:
    • http://www.swordapp.org
    • http://twitter.com/swordapp
    • General queries:
      • Adrian Stevenson [email_address]
    • Technical queries:
      • Sword sourceforge list [email_address]
  • Questions?
    • http://www.swordapp.org
    • http://www.twitter.com/swordapp
    • [email_address]