KAPTUR conference, London, March 2013

  1. @jiscdatapool colleagues Clare and Adam should be arriving at Kaptur #jiscmrd workshop. Looking forward to hearing their report.
  2. At the #jiscmrd #kaptur_mrd workshop today – picked up lots of fabulous resources already – as to be expected of an arts project! 😉
  3. #kaptur_mrd have put together a research data word search for the closing conference #jiscmrd
  4. For those at #kaptur_mrd – here is the KAPTUR blog bit.ly/15sYNmu with lots of information about the project #jiscmrd
  5. Research data matters in the visual arts – introductory presentation from Leigh Garrett, VADS Director and KAPTUR Principal Investigator
  6. #kaptur_mrd hightlights 1) What is research data in the visual arts: extremely complex question which the project has explored #jiscmrd
  7. #kaptur_mrd hightlights 2) Policy adoption: almost there across the four institutions, with policies on managing research data #jiscmrd
  8. #kaptur_mrd highlights 3) Infrastructure: complex user requirements led to lack of comprehensive solution, but knowledge developed #jiscmrd
  9. #jiscmrd thought provoking questions to hand over after the end of the event **how what you learnt today will impact on yr practice?**
  10. Keynote: Research data – challenges for the visual arts – Kerstin Mey, Director of Research and Enterprise, University for the Creative Arts
  11. Now up at #kaptur_mrd Kerstin Mey, Director of research and enterprise at UCA: research data challenges for the visual arts #jiscmrd
  12. Definition of research data, from Edinburgh: ‘data which arises out of, and evidences, research’ #kaptur_mrd #jiscmrd
  13. @fmuir See also our research data and other definitions in our repository support pages: ed.ac.uk/schools-department…
    #kaptur_mrd #jiscmrd
  14. Fascinating overview of research data in the visual arts at #kaptur_mrd. Question: do artists also want to cite data? #jiscmrd
  15. #kaptur_mrd @brian_hole I can very well imagine artists, critics, historians wanting to reference ‘data’ (workings, materials, etc) #jiscmrd
  16. At the final KAPTUR workshop in London today. Excellent so far, providing inspiration for DCC’s future Arts support work. #jiscmrd #ukdcc
  17. Supporting Research Data Management: the JISC MRD programme – Simon Hodson, JISC MRD Programme Manager
  18. #kaptur_mrd @simonhodson99 giving an overview of #jiscmrd & thinking about what research data actually is “…it’s the workings”
  19. Really good intro to Data Managment and Ideas on implementation for researchers
    opus.bath.ac.uk/30772 #jiscmrd
  20. royalsociety.org/policy/pro…

    Science as an Open Enterprise #jiscmrd

    cc @lescarr Sure you know all about this stuff anyway

  21. Piloting KAPTUR in the Arts – Carlos Silva, KAPTUR Technical Manager
  22. Wonderfully visual presentation now from Carlos Silva, #kaptur_mrd technical officer #jiscmrd
  23. #jiscmrd Q: which technical system is the most suitable for managing data?
  24. #kaptur_mrd identified short list of six systems for managing visual arts data: DataFlow, ePrints, DSpace, Fedora, CKAN, Figshare #jiscmrd
  25. interesting evernote not be included in the technical analysis ? #jiscmrd (I’m not a big fan but…just wondering) #eprints – final 4 yay 😀
  26. #jiscmrd not all the research output in Arts is in digital format
  27. nice ckan upload form. EdShare UI could work like this stepped approach for inputing materials…#eprints @edsharesoton #edshareredux #jiscmrd
  28. #jiscmrd CKAN Impressive functionality of imputing & showing art research data – demo by Carlos Silva
  29. Great closing gag from Carlos ‘FIN (ish…)’ – there will be ongoing work on CKAN with other #jiscmrd projects and the community #kaptur_mrd
  30. ckan is where you collect your stuff (desktop client ala evernote?) then connects to ePrints as the place for the finished output #jiscmrd
  31. Raising the profile of Research Data Management: the UCA story – Anne Spalding, KAPTUR Project Officer
  32. #jiscmrd Great digital storytelling presentation by Anne Spalding
  33. #jiscmrd key messages to take away: Communicate- Disseminate- Collaborate by Anne Spalding #kaptur_mrd
  34. Research data matters in the visual arts. Follow #kaptur_mrd for interesting thoughts from today’s workshop kapturmrd.eventbrite.co.uk/ #jiscmrd
  35. Towards a research data management policy at Goldsmiths – Andrew Gray, KAPTUR Project Officer
  36. Goldsmiths will have training aims at gathering data for the repository #jiscmrd #kaptur_rdm
  37. PI takes responsibly to work with the Research Data Management policy at GS – Goldsmiths using ePrints – Tetrabyte(?) of Storage #jiscmrd
  38. #jiscmrd think how a RDM policy will impact on researchers workload – key recommendation by Andrew Gray
  39. I believe ePrints has pretty good stats. at least the data i grabbed from EdShare also built on ePrints is nice #jiscmrd
  40. Arts Research Data. It’s as easy as 123 or is that ABC? – Robin Burgess, KAPTUR Project Officer
  41. #jiscmrd Very creative approach to relate an A-Z terminology for #RDM in Glasgow School of Art
  42. #jiscmrd need to check YouTube later for this song singing what is #RMD
  43. wow KAPTUR project seems to have really moved forward Art & Design Research Data Management & implementation at project partners #jiscmrd
  44. Important question: what licence are you using for artistic materials/outputs/data in the GSA repository? #kaptur_mrd #jiscmrd
  45. GSA are still working on licensing and advice – VADS have issues with CC0 #kaptur_mrd #jiscmrd
  46. Engaging policies at UAL: towards a policy for Research Data Management – Sarah Mahurter, KAPTUR Project Officer
  47. Archiving the process is a term that resonated at UAL, rather than ‘research data’ #jiscmrd #kaptur_mrd
  48. @UALKaptur mentioning Charlotte Hodes – see detail of papercut on #jiscmrd #kaptur_mrd USB stick – if you look closely u can see figures!
  49. University of the Arts London research data management policy and some guidance bit.ly/PmmE3O #jiscmrd #kaptur_rdm
  50. Mahurter argues that there are unique issues and opportunities in looking after research data / assets at UAL #jiscmrd #kaptur_mrd
  51. Research data matters in the visual arts – #jiscmrd #flickstackr – my Flickr pics from today #fb flickr.com/photos/procter/s…
Advertisements

Working in Stages with DataStage and Figshare

With thanks to Carlos Silva, Technical Manager, for the following blog post:

The KAPTUR Technical Analysis report (PDF) recommended the piloting and further investigation of two different systems: DataStage to EPrints; and Figshare to EPrints.

Figshare to Eprints

Some of the advantages of integrating Figshare with EPrints are:

  • The upload tool to Figshare allows multiple uploads using WebDAV and javascript.
  • The Figshare team is currently working on a desktop uploading tool to allow users a streamlined process of submission.
  • Feedback from the Steering Group was that the user interface of Figshare was attractive and clear; it is already being used by researchers to store and manage research data and therefore the integration with EPrints would enable many institutions (as EPrints is the major repository platform in the UK) to encourage researchers to better manage their research data and then upload selectively to an institutional repository for publication.

Following telephone and Skype chats with the Figshare team a requirements document was created and shared with project partners and Simon Hodson. The idea was to create an API which would be free for use by any institution who wanted to link Figshare with an EPrints repository using the SWORD 2 protocol.  Additional features included the development of the desktop uploader; a custom user interface design; back-end application development; and custom user accounts for the KAPTUR project partners to test the system.

Currently, negotiations are still in progress and further thought has been given to the infrastructure and pricing models that will eventually have an impact when adopting a commercial approach with technologies such as Figshare and that if not considered could lead to an unsustainable solution for the sector.

DataStage to EPrints

The second pilot recommended by the report was to link DataStage (from the JISC funded DataFlow project* with EPrints.  The technical implementation of this pilot started in June 2012 when the Technical Manager set-up DataStage and DataBank on a local machine; demonstrated this to the Project Officers (in June) and the Steering Group (in July) and started collecting feedback on this.  After testing the DataFlow software internally, the team started to explore the best way of linking DataStage with EPrints directly.

The advantages of integrating DataStage with EPrints are:

  • DataStage offers the potential of being institutionally based, and therefore tighter control.
  • It provides a structured metadata collection interface.
  • It also provides flexibility when uploading, for example with the integration of a shared drive which uses a popular storage approach similar to Dropbox but with the advantages that the data is held on the institution’s servers.

Proposed integration of DataStage with EPrints, July 2012 (SlideShare)

The Technical Manager through VADS’  host institution – the University for the Creative Arts – set-up a test environment for the KAPTUR project (http://kaptur.ucreative.ac.uk).  Test accounts have been given to project partners and an online feedback form set-up to capture this information.

To test the DataStage connection with EPrints, a test repository with the latest EPrints version (3.3.10) was needed in order to use the SWORD 2 protocol; this was created (http://kaptur_repo.ucreative.ac.uk).

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

The DataStage software should allow users to submit entire folders as ‘packages’ to a repository using the SWORD2 protocol, however currently there is an issue** with the default version of DataStage and no transfers can be done on any other repository other than into Databank (the DataFlow project’s repository).

As well as contacting DataFlow and EPrints, the Technical Manager has been in contact with various colleagues across the sector, from the Centre for Digital Music at Queen Mary, University of London (see blog post about connecting DataStage with DSpace) to other colleagues who have also looked into connecting DataStage with EPrints such as the UK Data Archive, University of Essex and the RoaDMaP project, University of Leeds.

At this point there are the following conclusions:

  1. EPrints 3.3 is required in order to have SWORD 2 fully enabled [completed].
  2. EPrints have tested the SWORD 2 protocol successfully with other EPrints repositories, however connectivity with other types of repositories hasn’t been tested by EPrints yet.
  3. The DataFlow project manager replied saying that there were issues with the SWORD submission on the DataStage side, however they were expecting to come up with a workaround for their V 1.0 release [It is noted that Richard Jones will be presenting about DataFlow at the JISCMRD Nottingham programme event so this is hopeful!!].
  4. The lead DataStage developer mentioned that 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, however due to new developments and enhancements at either end some changes in the DataStage side need to happen before it fully complies and can connect with EPrints.

*DataFlow was funded by JISC, under the University Modernisation Fund, from June 2011 – May 2012 to further develop a prototype out of the JISC-funded ADMIRAL project (2009-11).

**A blog post at the end of August noted the action “Review Sword access problems, isolate and fix (getting external help if needed).”


KAPTUR ten months into the project – (10/18)

This is our update for the end of the tenth month:

WP1: Project Management

WP3: Technical Infrastructure

  • The Technical Manager provided a demonstration of DataStage and Figshare at our steering group meeting in July; feedback from partners was very useful in informing the development of the KAPTUR pilot infrastructure.

WP4: Modelling

  • The UAL Project Officer has been continuing with the DCC University Engagement programme and interviewing arts researchers face-to-face using an online survey developed with Marieke Guy and Dr Paul Ryan. This will inform their RDM policy development.
  • There are now draft RDM policies for Goldsmiths, University of London; The Glasgow School of Art; and the University for the Creative Arts.
  • Development of The Glasgow School of Art and the University for the Creative Arts draft RDM policies will continue in September when the University term resumes.
  • The Goldsmiths Project Officer reported that on 25th July an informal working group convened including representatives from a variety of departments (academic, support, management) and Martin Donnelly from the DCC. After presentations by Martin, Jacqueline Cooke, and the Project Officer, a draft policy prepared by the Project Officer was discussed as well as requirements for putting it into action. Martin provided extremely useful and relevant information for everyone involved. The proposal for an RDM policy was well received. The group (though perhaps not in the exact original composition) will reconvene in the autumn with a view to finalising a commitment relating to RDM to be tabled at meetings at the end of the year.

WP5: Training and Support

  • This workpackage is due to begin in September, however it was necessarily an item on the agenda of the steering group meeting in July.
  • During August the Project Manager has been researching existing training materials, for example from previous JISCMRD funded projects, in preparation for discussion at the next project team meeting in September, including using Pinterest here: http://pinterest.com/mtgwork/rdm-training/
  • In particular, in response to feedback from the steering group, a selection of 45 RDM videos have been bookmarked here: http://pinterest.com/mtgwork/rdm-videos/
  • The event on 14th September will also be an opportunity to get feedback on training materials and inform the development of the KAPTUR toolkits.

WP6: Evaluation and Sustainability

  • This workpackage is due to begin in September, however it was necessarily an item on the agenda of the steering group meeting in July.
  • In response to discussion at the steering group, the Technical Manager has been working with the Project Director and Project Manager on a costings template and method for the project partners. This will enable costs to be estimated for visual arts technical infrastructure at each institution over the next 5-10 years, and lead into the Business and Sustainability plans.

WP7: Dissemination

  • The Project Manager has continued to work with Angus Whyte of the DCC and Laura Molloy, JISC Evidence Gatherer, on the ‘Selecting and Appraising Research Data’ event to take place in London on 14th September. This has now been renamed ‘Managing the Material: Tackling Visual Arts as Research Data’ and is almost fully booked. The last few places, and more details, are available here: http://kapturmrd01.eventbrite.co.uk/
  • The UAL Project Officer will be presenting about KAPTUR at the UAL Information Services Staff conference on Friday 21st September.
  • The Project Director has, with the Technical Manager and Project Manager, written and submitted a paper to the 8th International Digital Curation Conference which builds upon the research undertaken as part of the Technical Analysis report

Technical development update

Since the beginning of the KAPTUR project, the Technical Manager has maintained contact with the UCA IT department to ensure they are aware of the project and its requirements. Work requests to IT have established precise deadlines, however for the purposes of this blog post the following tasks are represented in a month-by-month format for easy viewing:

Who What When (2012)
June July August September October
KAPTUR Technical Manager Download and install DataFlow on a local environment (not server).  X
KAPTUR Technical Manager Once DataFlow is stable, setup EPrints in the same local environment.  X
KAPTUR Technical Manager Development work to link DataFlow with EPrints.  X
KAPTUR project team and partner institutions First round of feedback and tests.  X
UCA IT Department Create Virtual Machine (VM) on servers hosted by UCA.  X
UCA IT Department Assign the URL kaptur.ucreative.ac.uk to the VM.  X
UCA IT Department Create back-up mechanisms in line with usual procedures for the VM.  X
KAPTUR Technical Manager Transfer local development environment to the new VM.  X
KAPTUR Technical Manager Test and debug.  X
KAPTUR project team and partner institutions Further feedback and tests of the system via the VM.  X
KAPTUR Technical Manager Further tests and debugging leading to initial pilot system.  X

The above table is based upon the original KAPTUR workpackages, additional investigations undertaken as part of the Technical Analysis report, and ongoing consultation with the project team.


Building a pilot demonstrator service for the visual arts

The following blog post is adapted from the Conclusion and Recommendations section of the Technical Analysis report (PDF):

The KAPTUR Technical Manager investigated 17 different types of software which were compared to the requirements of the four partner institutions (details and appendices in the report). The next stage of the research reduced the choice of software to five options: DataFlow, DSpace, EPrints, Fedora, Figshare. These were all found to be suitable for managing research data in the visual arts; through a further selection process EPrints, Figshare, and DataFlow were identified as the strongest contenders.

[…] it is recommended that two pilots occur side by side: an integration of EPrints with Figshare and a separate piece of work linking DataFlow’s DataStage with EPrints. By integrating EPrints with Figshare, the project can take advantage of a system which has been built with, and for, researchers to handle research data specifically, and has a user-friendly visual interface (which is constantly evolving and enhanced by Figshare directly). […]By integrating DataStage with EPrints the research data storage and software will be hosted within each institution, providing them with better control over the type of data that can be stored, published and managed. The integration will also enable content uploaded in DataStage to be securely backed up by the institution and accessible from anywhere in the world. A ‘Dropbox’-like tool is featured in the latest beta version, providing a user-friendly interface which will benefit visual arts researchers. EPrints will effectively provide the role of DataFlow’s DataBank.


Kaptur – seven months into the project (7/18)

This is our update for the end of the seventh month:

WP1: Project Management

WP3: Technical Infrastructure

WP4: Modelling

  • University of the Arts London (UAL) held its first Research Data Management (RDM) working group meeting on Tuesday 10th April; the Kaptur RDM discussion paper was amended for UAL’s use and went forward to their Research Standards and Development Committee on 1st May.

WP7: Dissemination

  • The Project Officers were asked to suggest three ways to increase the profile of the project, including: an internal event, an internal website/newsletter/email, and something innovative.
  • The GSA Project Officer has had some Web training with a view to adding information about the project to the Research Web pages; Kaptur has already been promoted on the GSA Facebook page.
  • The Goldsmiths Project Officer has given two presentations about the project on 26 April and on 2 May for Library and Research Office staff; an item will also be in the May edition of the Goldsmiths Research newsletter.
  • The UCA Project Officer gave a presentation at the Staff Research Conference about the challenges and opportunities of running an institutional repository which included information on the Kultur, Kultivate, eNova and Kaptur projects; a targeted email will be sent to faculty librarians to provide more information about Kaptur.
  • The UAL Project Officer will submit a paper for the UAL Information Services Staff Conference (September), and an article for the Library Services Newsletter.
  • Watch this space for more creative dissemination ideas, several are in discussion including events, videos, music and artwork!

4. Issues/challenges

Following the original vision of the Principal Investigator (Project Director) the collaborative aspect of KAPTUR is working really well, as in particular at this month’s meeting we were able to learn and reflect on different approaches at each institution regarding the modelling workpackage.

The challenge this month has been to select the system for the KAPTUR pilot technical infrastructure. The research method led to a short-list of five systems, all of which were similar in ‘score’ based on the user requirements, this required the application of an additional selection process. A blog post will be forthcoming about this.


Mackintosh and visual arts research data at The Glasgow School of Art

Entrance to The Glasgow School of Art. Photo MTG

Last week the Kaptur team gathered for a project meeting in The Glasgow School of Arts’ incredible Mackintosh building. Representatives from all the project partners met in the Mackintosh room (also known within the School as the Design Room):

“In 1906 Mackintosh was asked to include a new, more formal Board Room into the building and used part of an existing studio on the ground floor, to the left of the entrance. In return what had been the School’s original Board Room, a chiefly white interior on the first floor was turned into a design room. This space (Studio 37) has now reverted back to a meeting room.”

[Text on wall next to the Mackintosh Room]

Fireplace in the Mackintosh Room. Photo MTG

A photograph of the Mackintosh Room by Bedford Lemere (described as The Board Room) shows the fireplace as it was in 1910 [Buchanan (2004) Mackintosh’s Masterwork: The Glasgow School of Art, pp.114-5].

The purpose of the meeting was:

  1. for the project team to be updated about work at each institution in order to enhance collaboration and lessons learned across the partner institutions;
  2. to agree and assign tasks for promoting Kaptur internally/externally to the institutions;
  3. to discuss applicability of the Digital Curation Centre (DCC) tools for the modelling and technical work packages.

This was addressed as follows:

  1. each Project Officer reported progress on the development of the institutional RDM policies; the Technical Manager reported progress on the Technical Analysis;
  2. each Project Officer will suggest three different ways of awareness raising within their institution and this will be reported in the next Kaptur monthly blog post;
  3. we were delighted to welcome Martin Donnelly, Senior Institutional Support Officer, DCC to the meeting; it was very useful to ask specific questions within the context of the project team.

Key points to share:

  • A need for awareness raising about managing research data within the institutions through promotion of Kaptur. One of the points to engage researchers is when they ask the institution for Letters of Support for their funding applications.
  • The awareness raising needs to be clear about the differences between data storage and data curation; although the storage aspect may still be an incentive for researchers to manage their research data effectively.
  • On RDM policy development there was some discussion about the pros and cons of a small more research-focused working group compared to a larger working group which may help with embedding and take-up of the policy as well as awareness raising, but may take longer to discuss and approve a policy. Two institutions have smaller working groups and the other two plan working groups with a wider range of stakeholders. It is useful to share these experiences collaboratively.

Mackintosh and visual arts research data:

Detail of bookcase, dark stained oak with leaded glass (1901.038). Photo MTG

This bookcase was originally designed in 1901 by Mackintosh for the drawing room at Windyhill. It was presented to the School by William Davidson on the sale of Windyhill. Also in The Glasgow School of Art’s collection is a scale drawing in pencil with annotations, an example of Mackintosh’s own visual arts research data. Another example is Mackintosh’s Northern Italian sketchbook, available from the Visual Arts Data Service (VADS) and also via the project website. The research was part-funded by The Glasgow School of Art and the creation of the database was funded by the Arts and Humanities Research Council (AHRC).

Left: Lake Como, Campo, Villa del Balbiano, studies of gates, Charles Rennie Mackintosh, 1891 © The Glasgow School of Art. Available from VADS: http://vads.ac.uk/large.php?uid=92819

Right: Modern photo of gates at Lake Como, Campo, Villa del Balbiano © The Glasgow School of Art. Available from VADS: http://vads.ac.uk/large.php?uid=92819&sos=0&pic3=its39p