The technical report summarizes work from the KAPTUR project including: 1) An environmental assessment report analyzed researcher data practices and found they want to share research but with privacy. 2) A technical analysis reviewed 17 systems and recommended piloting Figshare and DataStage. 3) A costing model analyzed institutional vs cloud hosting and identified risks and integration challenges to cloud computing. 4) The meeting presented on piloting Figshare, DataStage, EPrints and CKAN as research data management systems.

1. Technical Report
KAPTUR
Carlos Silva
8th January 2013 - London
KAPTUR STEERING GROUP:8TH JANUARY:LONDON
VADS : GSA: GOLDSMITHS : UAL : UCA : JISC

2. Objectives
• Environmental Assessment Report
- Data gathered from interviews with researchers
• Technical Analysis Report
- Technical requirements
- Technical systems
- Selection of software
• Costing Model
- Institutionally hosted vs. cloud hosted
• Pilot Demonstration Service
- Figshare
- Datastage
- Eprints
- CKAN
KAPTUR STEERING GROUP:8TH JANUARY:LONDON
VADS : GSA: GOLDSMITHS : UAL : UCA : JISC

3. Environmental Assessment Report
• Formed the basis of the technical side of the project
• The report outlined:
- Issues with how researchers handle research data
- Creation of visual arts research data
- Use/reuse of research data not only from them but from other
researchers
- Preservation issues
• The conclusions were:
- Researchers agree research data is important for them, students,
other researchers and the general public
- Researchers want to share data, but with caveats for sensitive
information
- VA researchers document their research process, however this is
following a situated rather than normative archival practice
KAPTUR STEERING GROUP:8TH JANUARY:LONDON
VADS : GSA: GOLDSMITHS : UAL : UCA : JISC

4. Technical Analysis Report
• Research Question:
- Which technical system is most suitable for managing visual arts
research data?
• User Requirements Document
• Analysis and assessment of 17 different systems
• The conclusions were:
- Three systems were very close in terms of grading by partner
institutions
- It was recommended piloting of two systems side by side
- Risks to be considered
- Plans to mitigate existing risks if the likelihood increases
KAPTUR STEERING GROUP:8TH JANUARY:LONDON
VADS : GSA: GOLDSMITHS : UAL : UCA : JISC

5. Costing Model
• Previous Steering Group Meeting
• Institutional Vs Cloud Hosting
• IT Cost Template
KAPTUR STEERING GROUP:8TH JANUARY:LONDON
VADS : GSA: GOLDSMITHS : UAL : UCA : JISC

6. Costing Model (cont)
• Considerations
- Identify a clear integration strategy for moving applications to the cloud
- Identify resources needed to monitor the points of integration
- Security plan in place to protect sensitive information
- Understand risks associated with cloud computing
- Understand integration (issues of how to integrate data and
applications does not simply “go away” with cloud computing)
- Costs including maintenance of all of the above
KAPTUR STEERING GROUP:8TH JANUARY:LONDON
VADS : GSA: GOLDSMITHS : UAL : UCA : JISC

7. Pilot System – Figshare
KAPTUR STEERING GROUP:8TH JANUARY:LONDON
VADS : GSA: GOLDSMITHS : UAL : UCA : JISC

8. Pilot System – Figshare (cont)
How is your uploaded data licensed?
KAPTUR STEERING GROUP:8TH JANUARY:LONDON
VADS : GSA: GOLDSMITHS : UAL : UCA : JISC

9. Pilot System – DataStage
KAPTUR STEERING GROUP:8TH JANUARY:LONDON
VADS : GSA: GOLDSMITHS : UAL : UCA : JISC

10. Pilot System – EPrints
KAPTUR STEERING GROUP:8TH JANUARY:LONDON
VADS : GSA: GOLDSMITHS : UAL : UCA : JISC

11. Pilot System – CKAN – Orbital
KAPTUR STEERING GROUP:8TH JANUARY:LONDON
VADS : GSA: GOLDSMITHS : UAL : UCA : JISC

12. Pilot System – CKAN – Orbital (cont)
http://orbital.blogs.lincoln.ac.uk/
KAPTUR STEERING GROUP:8TH JANUARY:LONDON
VADS : GSA: GOLDSMITHS : UAL : UCA : JISC

13. Technical Report
KAPTUR
Carlos Silva
8th January 2013 - London
KAPTUR STEERING GROUP:8TH JANUARY:LONDON
VADS : GSA: GOLDSMITHS : UAL : UCA : JISC