Archive

Archive for the ‘SWORD’ Category

ACErep update for the PORSCHE Executive Board meeting on Wednesday 10th August 2011

August 12, 2011 Leave a comment

This was the final meeting of the PORSCHE Executive Board – I attended by telephone and submitted this written update from ACErep:

After initial testing of the EasyDeposit SWORD client with the Jorum development server (see April 6th update) we have now configured the client with a SWORD endpoint for each of the several repository platforms we hope to deposit into. These include a demo install of DSpace – http://demo.dspace.org/ – the NDLR (in lieu of Jorum), the WRRO EPrints repository and our own intraLibrary repository.

We have been able to successfully deposit into http://demo.dspace.org/ and into the NDLR (also DSpace) but the client fails with EPrints with a generic error message. I have not yet established what the problem might be and queries have been raised with ‘sword-app-tech@lists.sourceforge.net’ and ‘eprints-tech@ecs.soton.ac.uk’.

SWORD has now also been implemented at York St John (Archivalware) and is currently being tested – I have not yet been able to test with EasyDeposit.

DSpace, EPrints and Archivalware should all accept METS packages but in order to deposit into intraLibrary it is necessary to extend EasyDeposit to package as IMS – negotiation is currently underway to carry out this work in partnership with Intrallect hopefully in time for the ALPS Showcase on 16th September* (there will still also the requirement to standardise Application Profiles across the repositories).

In terms of repository cross-search it was suggested that we may be able explore doing this via the DSpace (v1.6) API (the version run by the NDLR) though I have not yet seen any documentation though our content has now been successfully harvested into the NDLR (test install) via OAI-PMH.

* This work has now been scheduled for w/c 29th August

EPrints & SWORD – can you help?

August 4, 2011 Leave a comment

I’ve installed Stuart Lewis’ EasyDeposit sword client – http://easydeposit.swordapp.org/ – and configured it with several sword endpoints covering the several repository platforms we hope to deposit into:

http://demo.dspace.org/

http://training1.eprints.org/ (Thanks to Dave Tarrant)

http://repository-intralibrary.leedsmet.ac.uk/

http://www.ndlr.ie/ (Thanks to Phil Franks)

I’ve been able to successfully deposit into http://demo.dspace.org/ and into the NDLR (also DSpace) but the client fails with the EPrints training install with a generic error message – I don’t know EPrints very well so don’t know if it’s a problem with EasyDeposit or the configuration of the EPrints repository I’m trying to deposit into. I can see two collections in the client (see below) and had a quick rummage around in training1.eprints.org but can’t see an obvious way to configure collections [am Training Admin]….any EPrints folk out there able to help?

(It also won’t yet work into IntraLibrary but that’s due to the fact that EasyDeposit packages as METS and IL only accepts IMS-CP.)

Categories: SWORD Tags: , ,

Project update

March 4, 2011 1 comment

One of the most challenging aspects of ACErep continues to be working across multiple institutions and organisations and recently progress has stalled somewhat as we liaise with our partners and wait for development work essential to the overall infrastructure.

In November last year we were able to build a prototype using Xpert which harvests OAI-PMH from our repository at Leeds Met and which we are then able to selectively search by keyword. We had initially hoped to work with Jorum but at that time there was no Open API, nor were there any plans to harvest by OAI-PMH, so we liaised instead with Pat Lockley of Xpert who was able to help with both requirements.

A lot has happened since November however, both at Xpert and Jorum. Pat is moving on to another (OER related) post which raises questions for us around the sustainability of that service now it has lost its key developer and I have been working with the PORSCHE project at Newcastle University which aims to provide seamless access to academic and clinical learning resources for healthcare students primarily from the respective collections in Jorum and the NHS National eLearning Repository (NeLR). As such, PORSCHE has also requested that Jorum harvest by OAI-PMH and provide an open API; the project team includes the Jorum service manager Hiten Vaghmaria as well as Kate Lomax of the NeLR (which, like Leeds Met’s repository, is also based on intraLibrary.) Jorum have now released a first iteration of an open API and hopefully both projects, and the UKOER community at large, can now work with the national OER service to develop that API to meet our requirements – PORSCHE’s Suzanne Hardy has set up a the Jorum API discussion space (wiki) at http://jorumapi.pbworks.com/w/page/35601929/Jorum-API-discussion-space. I am, in fact, yet to contribute to the discussion myself partly due to a lack of knowledge around API development – I’m far from clear, for example, how we may most effectively use an API to return just a subset of the resources in Jorum (i.e. ALPS/medical resources). In the Xpert prototype we just filtered on keyword but this feels a little unsatisfactory and Pat suggested a custom URL search would be better…

The other pieces of the jigsaw are repository-shaped and variously lacking the dove-tailing standards required to make the model workable. At Leeds University the learning and teaching repository is ExLibris’ DigiTool while York St John have a system called ArchivalWare, both systems are OAI-PMH compliant but do not support SWORD – development work is underway to rectify this at York St John while Jodie has set up an out of the box test install of e-prints to investigate OER object management.

Mike has also made some progress with EasyDeposit which is now working on a Leeds Met server and, after a few teething problems, will now successfully deposit a METS package to Jorum (DSpace), we will still need to test with EPrints (METS should be OK I think) and ArchivalWare when SWORD is integrated with that platform…probably METS again. There is an issue with intraLibrary, however, in that it only accepts IMSCP by SWORD, not METS, so we will also need to write an IMS content packager for EasyDeposit.

We are very grateful to Tamsin Treasure-Jones of ALPs for her continued support with this challenging project and I’m hopeful that all of these pieces can be put together over the Spring and Summer as we move towards a local, regional and national infrastructure for sharing medical teaching, learning and assessment material with an approach that will have the benefit of digital assets being preserved in one location (an institutional repository) while providing several points of access as well as allowing the ALPS branded web-site and the institutional repositories to “piggyback” on Jorum’s Google pagerank and improving discoverability.

Plug for ACErep on John’s CETIS blog

January 26, 2011 Leave a comment

John Robertson of CETIS discusses ACErep in his recent post “workflow and deposit tools for learning materials” – http://blogs.cetis.ac.uk/johnr/2011/01/25/workflow-and-deposit-tools-for-learning-materials/

I’ll comment on John’s post soon!

Categories: ACErep, SWORD Tags: , ,

Working search prototype and a SWORD fight

November 23, 2010 3 comments

Since the last meeting, Mike has done a great job in putting together a working (search) prototype that uses the Xpert API to search http://www.nottingham.ac.uk/xpert/ for just those resources tagged “alpsportal” i.e. ALPS resources that I have added to our repository and that have been harvested by Xpert.  Currently Xpert is only harvesting Leeds Met but it should now be fairly straightforward to also harvest YSJ and Leeds such that any resources appropriately tagged will be returned from the portal.  It’s on a restricted test server at the moment so this what it looks like (with a few explanatory slides):

And the SWORD fight? There are 3 repositories (possibly 4 if we count JORUM) that we need to be able to deposit into – this is a problem as currently only one of them – intraLibrary at Leeds Met – has fully functioning SWORD.  This did lead us to consider a hybrid deposit process allowing for manual package forwarding but given limited technical resources (this approach would have its own, not inconsiderable, overheads) and the clear advantages of utilising SWORD, it probably makes sense to focus on a prototype that can utilise the protocol and that can, hopefully, plug into the other repositories in the future.

One of the issues we face is that intraLibrary is based on IEEE LOM and only accepts IMS Content Packages by SWORD whereas the majority of (open source) repositories are based on Dublin Core metadata and only accept METS by SWORD; I have been working with Jorum to test their SWORD deposit – as a customised DSpace repository it accepts METS (not IMS) so we have had to map IMSCP for one of our resources -> METS in order for it to be accepted.  Currently I have only been able to achieve this with a very simple package comprising just title, description and author (I’ve also tried to add keyword and rights but these don’t seem to be picked up by Jorum – I’m not sure if this is a problem with Jorum or with my XML – probably the latter!)

It is still a moot point whether we will need METS or IMSCP for YSJ/Leeds until various questions around their specific repository implementations have been answered but we probably need to progress on the basis that we should support both. We will need to get Mike involved on the technical side and I’m hoping that he can start developing a web-based SWORD deposit client that, eventually, will be able to post to any SWORD service URL whether at Leeds Met, Leeds, YSJ or Jorum; as the only viable target repository at this stage is Leeds Met we will want to package as IMSCP in the first instance, ultimately with a view to also packaging as METS depending on the requirements of the destination repository.

MT – I may be asking for the moon on a stick here but I know you’ll put me straight and tell me what we can actually achieve and in what time-scale…just to summarise, below, what (I think) I understand about SWORD so far and what I anticipate might be required of this type of implementation:

SWORD works by means of a service URL that a package is posted to via the ATOM publishing protocol – this service URL allows a “service document” to be retrieved from the target repository which itemises available collections for SWORD deposit. The desktop client I have been using with our repository and with Jorum is available from Sourceforge – http://sourceforge.net/projects/sword-app/.  It enables me to post a .zip containing a resource + its metadata in an imsmanifest.xml to intraLibrary (or resource + mets.xml to Jorum)

Screenshots below:

Authenticate to repository / retrieve service doc (note SWORD service URL)

Authenticate to repository / retrieve service document (note SWORD service URL)

Service doc successfully retrieved – choose collection to deposit into:

Service doc successfully retrieved - choose collection to deposit into:

Confirm collection details for post operation:

Confirm colection details for post operation

Browse to zip on hard drive (already containing imsmanifest.xml) and click button to post to repository:

Browse to zip on hard drive (already containing imsmanifest.xml) and click button to post to repository

Resource and full metadata record successfully posted to repository:

Resource and full metadata record successfully posted to repository:

I imagine we would need a web-form that allows similar metadata to be captured and transformed into an imsmanifest.xml, then allows file upload and zips resource and manifest into an IMSCP that is then posted to a specified collection in the service doc at http://repository-intralibrary.leedsmet.ac.uk/IntraLibrary-Deposit/service.

Erm, sounds a bit tricky to me, Mike?

It might also be worth looking again at Stuart Lewis’ EasyDeposit (blogged about at http://repositorynews.wordpress.com/2010/06/04/easydeposit-the-sword-client-creation-toolkit/) which packages as METS for DSpace/EPrints etc.