SWORD at the unconference

From DigiRepWiki

Jim - making improvements to the API; is implementation from scratch quicker than the api

Les - SWORD as creating a level playing field; what does SWORD buy people? direct deposit to a single repository is quicker to implement

reducing the cost of plastering over the crack - not solving all of the problems

Uses and potential uses

SPECTRa - one client implementation - making his client process more popular; reduces ghettoisation of this kind of work, for e.g. this will be part of EBank 3

Potential use in ethosnet

The Depot - should be encouraged

ROAD project - Stuart (half pointless because of re-packaging)

EPrints accepts same packages as DSpace

pass-by-value is a valuable alternative to pass-by-reference (ORE approach)

SWORD needs to consider it relates to ORE, i.e. how much of SWORD is entirely geared to pass-by-value

bottom-up approach - SWORD is done for a small part of the problem

repository as client

Creation tools to support SWORD directly, e.g. reload; plugin for word - ICE project; interest in EPrints but no capacity at present

  • Core dist of DSpace - Richard, Jim and Stuart agreed to push this forward
  • Core dist of EPrints
  • Intralibrary - February

Next steps:

  • implementing the rest of APP as extra levels
  • issues of integrity of what goes into a repository - controlling how it is unpacked
  • formal support for identifiers - Richard outlined an Imperial use case using LNI, this could be replaced with SWORD, if it were extended to act as an internal content interchange mechanism, effectively extending to CRU(D); PUTs which add new content to existing items

possible use cases - sharepoint; moodle; Richard's internal identifiers

one benefit of SWORD is pushing DSpace to do identifiers 'properly'

is there money in CRIG to take this forward? for meetings?http://www.ukoln.ac.uk/repositories/digirep/index.php?title=SWORD_testing_at_the_unconference&action=edit Editing SWORD testing at the unconference - Edit - DigiRepWiki

ACTION - talk to Neil about best way forward for this

Jim - could bring in Unilever Centre or Microsoft project


Autodiscovery - needs to be firmed up; SWORD Conventions - rel="sword" - should be to the service document (check headers of blogs) - make sure that the test installations support this too.

also integration into IESR

Scott Wilson - FeedForward has implemented SWORD