KAPTUR

Working in stages with Figshare and DataStage

Parallel Session 2B: Data Repositories and

Storage

Carlos Silva

Visual Arts Data Services

24 October 2012

Technical Analysis Report

• Two different systems

– DataStage to EPrints

– Figshare to EPrints

• Pros

– Upload tool

– WebDAV

– Open API

– SWORD2

• Cons

– Sustainability

– Pricing models • Cost / user / record when not

publicly available

– Commercial approach

Currently in negotiations about pricing model and the type of the development work needed from Figshare

• Pros

– Institutionally based – Open Source under MIT license – SWORD2

• Cons

– Sustainability – Currently in Beta Version – SWORD2 not fully working with other

repositories others than DataBank

• What has worked/is working

– Both systems have been tested separately, and both systems have performed well

– SWORD2 between two same systems has worked just fine – Costing model

• Lessons learned so far… – Sustainability is key when looking in the medium – long term for every

software – When working with beta versions further testing time needs to be allowed in

order to fix unexpected errors – Collaboration from other institutions is key – As well as collaboration from similar projects working on the same goal

• Challenges remaining and what we intend to do – Integration between DataFlow and EPrints using SWORD2

• Issues with the SWORD submission on the DataStage side need to be solved

– Feedback from Project Officers on whole integration – SWORD2 was envisioned to fully work with DataStage and EPrints when it

becomes available and that previous versions of DataStage managed to work okay with EPrints

– Assess upgrades issues from partner institutions using a kulturized version of EPrints

• Activities needed – Gathering developers and experts in SWORD2 to look at the main issue of

transferring data across multiple repositories or systems (Hackatlon) – Getting external help with SWORD 2 if needed (ask advisors)