Select one of the following thumbnails to view a close-up and slideshow:
This is our update for KAPTUR for February with one month of the project left to run!
WP1: Project Management
- The project team had meetings on 31st January and 28th February in order to both report and monitor progress of outstanding tasks.
- The Project Manager has begun final reporting procedures for JISC.
WP3: Technical Infrastructure
- The Technical Manager has completed a case study on the technical aspects of the project which will be presented at the KAPTUR conference on 6th March.
- The Project Officers have uploaded visual arts research data to the EPrints pilot repository.
- The Technical Manager has resolved issues with the CKAN pilot repository and will be completing development work on this soon.
- The fourth and final RDM policy was approved by The Glasgow School of Art’s Research and Knowledge Exchange Committee on 13th February.
- The four policies will be made available through DCC in due course and will also be linked to from the KAPTUR Outputs page.
- This work package is now closed.
WP5: Training and Support
- The Glasgow School of Art training workshop took place on 31st January with the assistance of Laura Molloy, JISCMRD Evidence Gatherer. The presentations are available here: http://www.slideshare.net/kaptur_mrd/tag/gsardmtraining
- The fourth and final training workshop took place on 22nd February at Goldsmiths, University of London with assistance from Kerry Miller of the Digital Curation Centre. The presentations are available here: http://www.slideshare.net/kaptur_mrd/tag/goldrdmtraining
- The first draft of the KAPTUR toolkits has been completed using Xerte Online Toolkits. They will be completed by the close of the project and made available both online and through JORUM for use and re-use.
WP6: Evaluation and Sustainability
- The four case studies from the Project Officers as well as the additional fifth case study from the Technical Manager have been completed and are being edited for online publication.
- A template for the KAPTUR Business, Financial and Sustainability Plans was circulated to the Project Officers for use in their institutions.
- The Glasgow School of Art have already completed a good draft of their Business Plan using the template.
- The Project Manager is awaiting feedback from the final workshop, the conference, and another short survey before completing the Benefits’ reporting.
- The Project Director attended the Reskilling for RDM workshop at University of the West of England on 29th January
- The Technical Manager attended the CKAN workshop in London on 18th February – a blog post is available: http://kaptur.wordpress.com/2013/03/02/ckan4rdm-workshop/
- The Technical Manager also attended the Research Data Management Storage Requirements Workshop in London on 25th February: http://rdm-storage.eventbrite.co.uk/ This was hosted by JISC, DCC and JANET.
- On Monday 4th March, Lynda Agili, Head of Research Office, and Andrew Gray, the KAPTUR Project Officer, both from Goldsmiths, University of London will present at an ARMA event.
- The KAPTUR end-of-project conference will take place on Wednesday 6th March. It is fully booked: http://kapturmrd.eventbrite.co.uk/
With thanks to Carlos Silva, KAPTUR Technical Manager, for the following blog post.
On 18th February I attended a workshop led by the JISC funded Orbital project, to gather information about the open source software CKAN and how it could be used to support research data management in the academic sector.
The workshop started with a presentation from Mark Wainwright (community co-ordinator for the Open Knowledge Foundation) on the latest release of CKAN, its origins and potential in the academic community.
One of the big advantages with using CKAN is that the ‘core’ system is surrounded by APIs allowing it to be flexible enough to accommodate different user and institutional needs. This means that the core software can be updated without affecting the APIs or having to adapt external code to fit with the core software.
Another important feature that looks promising is the ability of CKAN to not only harvest other CKAN databases, but also to search other types of repositories such as EPrints and DSpace. The mechanism developed covers different repository sources not only EPrints and DSpace, but also Geospatial Servers, Web catalogues and other HTML index pages.
In terms of sustainability, CKAN has been developed over the last 6 years, so it is relatively mature now with an extensive and very streamlined workflow process to add features, fix bugs and enhance the core services. The latest version 2.0 (recently released as Beta) promises to be an exciting release with more visually enhanced tools, improved groups feature, customisable metadata and a rich search experience based on their Apache Solr search.
The workshop continued with a presentation from the data.bris project at the University of Bristol. It is amazing to note that each Principle Investigator can apply for up to 5TB of storage for free and backed up securely for 20 years!
Academics receive a mapped network drive which they can access and use to deposit content, however this requires additional features to manage research data. Therefore, the data.bris project was interested in CKAN due to its flexibility, data access (ability to have private datasets), organisation schema, ability to share with external researchers and the CKAN search engine.
In the future, the University of Bristol is considering two instances of CKAN, one for a public read-only catalogue of research data publications and another for controlled access (which would include teaching and other types of data).
The third presentation was from Orbital; Project Manager Joss Winn provided a virtual tour of the latest tools developed by the project. They have connected CKAN between different instances: to their EPrints repository and also to different departmental databases, such as an awards management system.
The Orbital set up allows their researchers to have different types of data located in a central place, this includes the policies, profiles, publications and analytics information from specific outputs, making the most of the CKAN software.
The demonstration included mention of the software created to enable deposit of data from CKAN to their EPrints repository – something which we have been anticipating for the last few months and is an exciting development for the sector. Orbital have released the code through Github which in theory should work with CKAN version 1.7. The functionality enables CKAN to submit the metadata to EPrints using the SWORD2 protocol but not the actual files themselves – instead a link is added to EPrints which links back to the files deposited in CKAN.
The Orbital team are proposing a two year roadmap to their senior management team to take responsibility and carry this project forward and embed it further into the University of Lincoln’s infrastructure.
During the group discussion session, workshop participants suggested a comprehensive list of about 80 tools, features, amendments and requests that we would like to see as part of a new version of CKAN (a Google Docs spreadsheet is available: http://lncn.eu/mxz2). Again in groups we did a GAP analysis for the specific items requested and a CKAN expert was available to answer any questions.
As an academic community we found that there were lots of similar challenges which should be easier to address collaboratively.
From the visual arts community perspective although CKAN can’t currently address all the requirements from our user requirements list (PDF) there is scope for further development and this is continuing in the right direction.
With thanks to Robin Burgess, KAPTUR Project Officer for The Glasgow School of Art for this blog post.
At the KAPTUR Research Data Management workshop held at The Glasgow School of Art (GSA), in response to the question
“What information should be kept?”
the analogy of baking a cake was given i.e. the end product (research output/s) being the cake and the “research data” being the ingredients – but you wouldn’t necessarily want to keep the dirty mixing bowl as you have now got the finished cake?
The group discussion dwelt upon the value of research and the information being collected. It was felt that research data needs to be determined and managed by the individual researcher; that they should ultimately have the control over their information.
The group went on to discuss specific research types and issues were raised in relation to whether the information was being seen as primary or secondary data; how it would be selected for data curation; and finally the distinction between the data and the actual research output.
Defining visual arts research data
Another theme from the day was defining visual arts research data. Laura Molloy offered Leigh Garrett’s working definition for discussion in her presentation (see the bottom of this blog post: What is visual arts research data? revisited).
During the workshop research data was discussed using examples. This raised a lot of questions, debate and conflict in relation to the interpretation of research data including:
- there was little consensus on a definition for research data as it would depend which discipline and department you were working for;
- research data should be a ‘thing’ rather than a ‘thought’;
- the process of research is essential and therefore should be recorded and documented as part of the research lifecycle as research data;
- the effects of research and the evidence of research were seen as being important within the definition of research data;
- the importance of expression and reflection were also discussed.