As discussed during the JISCMRD Programme Launch in Nottingham, projects thought it would be good to share what each one is doing regarding the Data Asset Framework (DAF) and/or gathering user needs, in order to see if it can be used/re-used by the other projects. We have been describing Kaptur’s approach, and the rationale for this approach, in a series of blog posts. Previous blog posts on this topic are available by searching the tag ‘environmental assessment‘, the two most relevant of these are: ‘Methodology for the Environmental Assessment‘; and ‘Environmental Assessment interview questions‘. Feedback is welcomed.
Kaptur is not using DAF, although we have considered what can be learned from the DAF approach. DAF provides institutions with a means to:
“identify, locate, describe and assess how they are managing their research data assets”
DAF recommend that you begin by deciding what you mean by ‘data assets’, for example they mention:
“numerical data, statistics, output from experimental equipment, survey results, interview transcripts, databases, images or audiovisual files, amongst other things”
Our initial probing interviews and research in the area of visual arts data tell us that we are not ready yet to pin this down to specific assets, although potentially all of the above could be included. One of the issues arising out of the probing interviews was the concept of what ‘research data’ was in the first place. We decided to undertake formal interviews to gather detailed qualitative information that could better inform Kaptur and help to build relationships with visual arts researchers at the four institutions. This approach, whilst not following DAF exactly, did also include questions that enabled information to be gathered about the types of data asset that researchers were producing and how they were being managed.
The scope of the Kaptur Environmental Assessment report has been defined in our methodology, which we make available for use and re-use:
Following the imminent publication of our report, the next stage is to establish working groups in each institution as a way to both continue the dialogue with the visual arts researchers and also to encompass a wider range of stakeholders. We have been looking at the CARDIO assessment tool, particularly as this is designed to “improve communication and understanding” between stakeholders. However this is normally used following a more formal data audit procedure, and therefore we may adapt the approach of CARDIO to suit our timescales and circumstances. For example there is a clear benefit to holding face-to-face meetings with all the stakeholders and this will take priority, however it may be that questions or elements of the CARDIO tool can be used to inform the agenda for these meetings. This is yet to be discussed, and will be raised at the Steering Group meeting on Monday as part of the Implementation Plan.
Simon Hodson, JISCMRD Programme Manager, has asked all projects to do a short blog post about commonalities.
Kaptur has previously highlighted the commonalities with the first round of JISCMRD programme funding (2009-11) and how we plan to use training materials produced by Project CAiRO and also have spent time looking at JISC Incremental. The commonalities identified so far from the JISCMRD Programme launch are:
The session on the last day put a few of the projects together in an ‘Arts and Humanities’ group. Some of the projects that are particularly relevant to us are:
- data.bris – Simon Price, Project Manager and Stephen Gray, Digital Projects Support Officer (formerly Project CAiRO Project Manager)
- Sustainable Management of Digital Music Research Data – similar approach to us with their interviews
- iridium – covering a range of subject areas including the arts
- REWARD – a six month project at UCL (Archaeology)
- Research Data @Essex
2. Pilot infrastructure
Kaptur is one of 17 projects in Strand A of the JISCMRD programme (Simon Hodson’s blog post on this) – we are therefore seeking to both learn lessons from more experienced projects in this strand (who had previous JISCMRD funding or links) and also find out how similar pilot projects are approaching things.
- Managing Research Data: a pilot study in Health and Life Sciences – a pilot project at University of the West of England (UWE are also a member of the Kultur II Group and have a ‘kulturised’ EPrints research repository!)
- DataFlow – keeping an eye on Data Management Rollout at Oxford (DaMaRO) – although DataFlow is in the ‘Cloud’ there does also appear to be an option to have a local Web server.
- SWORD-ARM – SWORD & Archaeological Research data Management
- During the Programme Launch there was a lot of talk about DCC tools including DMP Online, DAF, and CARDIO – look out for a future blog post about our environmental assessment methodology.
- Also keen to learn lessons from the MaDAM project, which is now MiSS (MaDAM into Sustainable Service) – http://www.miss.manchester.ac.uk/ (great URL!)
- Research360@Bath looks good too!
Please let me know if I have overlooked any projects that are relevant to Kaptur – we are interested in engaging with other projects and welcome feedback!
- JISCMRD02-Commonalities Google spreadsheet
- Google Reader “Research data management” bundle created by Jez Cope
Simon Hodson, JISCMRD Programme Manager, has asked all 18 month JISCMRD projects to write a blog post about the key expected benefits that each project will achieve, and what metrics we will use to evidence these at the end of the project.
- Report on the Benefits from the Infrastructure Projects in the JISC Managing Research Data Programme
- The KRDS Benefits Analysis Toolkit and specifically: Introduction to the KRDS Benefits Analysis Toolkit; Guide to the KRDS Benefits Framework Tool; Guide to the Value Chain and Benefits Impact Tool
Following a presentation by Neil Beagrie, Director of consultancy at Charles Beagrie, the JISCMRD projects were provided with a ‘Summary of Benefits Identified by the RDMI Projects’ and a ‘Summary of Metrics Identified by the RDMI Projects’. We were invited to select three benefits and then match these up with the appropriate metrics, making sure to include both quantitative and qualitative metrics for each benefit. I would like to emphasise that the following has not been discussed within the project team yet and is subject to confirmation.
- Sustainability of research data infrastructure.
- Change to user practices.
- Mitigating organisational risks.
- By each institution creating and approving its own Business Costs and Sustainability plans; the ultimate proof is in the longevity of the research data infrastructure. Qualitative data will be gathered through the Steering Group meetings which will include high-level senior staff across the four institutions. Quantitative data may include percentage or estimated cost savings/efficiencies for central services and/or departments.
- By taking a snapshot of existing practice at the four institutions through the Environmental Assessment report and then through maintaining user engagement throughout the project and taking snapshots at key stages to monitor progress. Qualitative data will be gathered through the interviews undertaken as part of the Environmental Assessment report, and through ongoing engagement e.g. through working groups and/or focus groups. Quantitative data will be gathered in the following ways: online questionnaires and/or feedback forms to record the impact on working practice of the project, these would be undertaken at key points e.g. we are planning an online survey in January, and would also gather feedback after training events; if online training materials are created then usage statistics will be gathered.
- By taking a snapshot of existing practice at the four institutions through the Environmental Assessment report and then through maintaining user engagement throughout the project and taking snapshots at key stages to monitor progress. Qualitative data will include a range of stakeholder examples of improved risk management e.g. organisational practice before Kaptur and how this has changed during/afterwards. Quantitative data may include a percentage improvement in routine back-up of data, and/or a percentage improvement in research data management awareness and policies/systems.
Neil emphasised that when using the KRDS tools it is a good idea to do initial work by one individual and then work this up in a project team context. Therefore the points raised in this blog post will be discussed at our next meeting in early January and possibly again at the Steering Group meeting. Neil also mentioned that it was important to adapt the tools to your project needs. From reading the documentation I am also aware of the need to start with the benefits framework tool prior to moving on to the value chain and benefits impact tool. The work done by other projects giving example worksheets is really useful, in particular the UK Data Archive and the Archaeology Data Service. Reference: Report and Presentations from the JISC Digital Curation/Preservation Benefits Tools Project Dissemination Workshop
Links (via @briankelly)
- Blog post: Trip Report: Blogging Practices Session at the JISC MRD Launch Event (#jiscmrd)
- SlideShare: Blogging Practices to Support projects
- Storify: Blogging Practices to Support projects
- Blog post: Smartr For Following JISC MRD Project Twitter Links
- Blog post: Blog Analytic Services for JISC MRD Project Blogs
Tips from Brian Kelly
- Instead of having a separate website and blog, integrate the web pages into the blog or vice versa.
- Think about what will happen to the blog if you leave or what happens after the end of the project.
- Use the ‘about’ page to really say how you are going to use the blog e.g. your blogging practices and approach and why – see Blog Policies.
- Write a ‘Communications Strategy’.
- Engage with high impact channels in the following ways: think of a human interest angle to your story; be proactive in seeking opportunities e.g. if there is a relevant news story that your project relates to in some way.
- Write a ‘Press Release from the Future’ as a way of setting where you want to be and then working out how you will achieve it.
How we are planning to use these for Kaptur
- Plan to integrate website/blog; our Technical Manager is back in mid-January so may ask him to set up a wordpress.org via our website instead of the current wordpress.com (will require re-directs obviously and not ideal so will think about it first).
- We are working towards a Data Management Plan for our project’s research data including the blog, a blog post about this will be forthcoming.
- We have now updated our About page to include a blog policy.
- Although the JISC Project Plan has various plans within the document such as a Dissemination Plan (ours is available here: Kaptur Project Plan (PDF)), Brian was talking specifically about how to target those channels that are high impact e.g. Times Higher Education, radio, and TV. See point 5 for tips.
- The visual arts researchers that we are engaging with at each of the institutions have the potential to address these points, subject to the research criteria we are applying of ‘informed consent’. We will look out for these opportunities.
- This is on my ‘to-do’ list e.g. ours may include ‘having an article in Times Higher’
On a side note, I chose to use SlideShare for Kaptur based on reading Brian Kelly’s blog post about SlideShare, which I then blogged about for a different project back in May: Identifying impact with SlideShare
This session was presented by Jonathan Tedds, Senior Research Liaison Manager (IT Services) at University of Leicester and Meik Poschen, Manchester eResearch Centre (MeRC), Requirements and Evaluation Lead from the University of Manchester. Both presentations were interactive, so the key points in this blog are a mixture of points from their slides and from general discussion. The group raised the issue of commonality in terms of approaches and methodologies to identify researcher requirements; an outcome for the programme could be projects sharing what they are doing in this area. The Sustainable Management of Digital Music Research Data project have written a few blog posts about their methodology.
- Meik Poschen – JISCMRD Launch presentation: MaDAM to MISS (PDF)
- Whyte, A., Tedds, J. (2011). ‘Making the Case for Research Data Management’. DCC Briefing Papers. Edinburgh: Digital Curation Centre. Available online: http://www.dcc.ac.uk/resources/briefing-papers
- MiSS (MaDAM into Sustainable Service) JISCMRD-02 project
- MaDAM JISCMRD-01 project
- JISCMRD02-Commonalities Google spreadsheet
- Google Reader “Research data management” bundle created by Jez Cope
- BRISSkit – Biomedical Research Infrastructure Software Service kit
- HALOGEN: History Archaeology Linguistics Onomastics and Genetics (Pilot Project)
MaDAM Key points
- researchers themselves were a useful source of information but it was also important to talk to experimental officers, other PIs, other research groups in order to view the institution’s wider picture
- for user group scoping try and select groups where there could be mutual benefit – researchers should also get benefit from taking part and giving their time
- they used an iterative approach; developers and users had a lot of meetings; the project team observed researchers’ work practice; then involved them with the evaluation of the technical system and soft infrastructure
- funder requirements are now clearer – over the course of an 18 month project things change with researchers and funders
- one of the huge benefits of MaDAM was awareness raising – at the beginning it may have initially been perceived as increasing researchers’ workload but this perception changes over time as funder requirements have changed – now data management is viewed favourably
- cultural change is needed, high level institutional support is crucial too
- importance of personal contact and observation of researchers’ day-to-day research practice
- some questions:
how much storage will researcher need over time? how long has data to be kept in an active or easy accessible state for re-use or sharing? how will the relationship between new policies and research practices develop? how will dissemination practices and hence scholarly communications be effected?
The group felt that although researchers were getting more engaged in this area, the research councils need to do more to enable cultural change with researchers i.e. there is a sense that the research councils have panicked the institutions rather than the researchers. One institution mentioned that a major grant was rejected on the grounds of the technical appendix; the group agreed that researchers need to know about this.
Research Data Management at Leicester – key points
- professorial level champions are good, but also good to get those who are more technically engaged within researcher groups – engaging at different levels
- in the past a project like HALOGEN would have used in-house IT expertise, but would be a one-off solution; they wanted to be able to re-use the infrastructure for future inter-disciplinary and inter-institutional projects
- Tedds raised the importance of ensuring that requirements analysis is iterative – continuous engagement
- challenges included: retro-fitting data to make it interoperable (versioning and provenance issues)
- key thing is to provide something that is less effort for researchers as it is more standardised
- there was a great slide on ‘direct benefits’, this included 1.3 million pounds worth of funding from the Leverhulme Trust
- another great slide on ‘indirect benefits’, which included costs avoided
- Tedds recommended recognising the different cultures and mindsets – the research liaison role helped with this
- top tip: grab researchers’ attention when they are applying for funding – system now includes some checkboxes they have to select when applying for funding e.g. ‘do you need support?’ – this also provides a record of demand
- Leicester’s research computing management group will be chaired by the Pro Vice Chancellor for research so this will feed back to senior management
There was some discussion about the use of SharePoint in the group – the educational pricing for SharePoint in the Cloud is not going to be released now until next Summer.
The group talked about the issue of researchers’ understanding of what research data is; terminology and disciplinary challenges. An example was given of a ‘fabrics database’ which was accepted by an institution – however there was a misunderstanding about what constituted a ‘database’ – an articulated lorry of wool fabric samples turned up = ‘the database’.
We need to provide different options for training – not just face-to-face – as time is a big issue even if researchers recognise they need it. It may be that we could also offer a component to plug into existing courses rather than offering something totally new.
The group discussed the importance of extending training beyond researchers themselves in order to provide consistency across the board irrespective of which department the researchers go to – a common language – a shared agreement of what we are all up to in supporting researchers.
The full-size poster has a visible link to full image credits: http://vads.ac.uk/kaptur/publicity/
Simon Hodson, JISC MRD Programme Manager has asked all projects to produce a poster for the Start Up Programme meeting taking place in Nottingham, 1st-2nd December. We have also been invited to present these at the 7th International Digital Curation Conference next week in Bristol, our 1-minute-madness PowerPoint slide (SlideShare) is available here:
It was decided to produce the poster in the form of a roller banner as we hope this is something that can be re-used at more than one event. The design is aimed to generate discussion with the questions; this is also the reason why the image credits do not appear directly on the poster itself (image credits are available here: http://vads.ac.uk/kaptur/publicity/).
What is Kaptur?
- Kaptur is a highly collaborative research project with four institutional partners: Glasgow School of Art; Goldsmiths, University of London; University for the Creative Arts (UCA); and University of the Arts London. Kaptur is led by the Visual Arts Data Service, a Research Centre of UCA, and funded by the JISC Managing Research Data Programme from Monday 3rd October 2011 to Friday 29th March 2013.
Specifically, we are one of 17 projects funded by JISC, described on the Managing Research Data Programme 2011-13 Web page as:
17 large institutional projects will help universities pilot or further develop and extend infrastructures for research data management as part of an institutional mission to provide high quality support for research. They will also be developing institutional or departmental research data management policies and guidance materials.
The answer to ‘why Kaptur?’ is something addressed in detail through the project proposal, written by Leigh Garrett, VADS Director. In very basic terms (but we are happy to elaborate!):
- to investigate the nature of visual arts research data building on the work of previous JISC MRD projects and the work of the DCC
- to support visual arts researchers through institutional infrastructure, focusing on the four institutional partners but also producing outputs that can be re-used and re-purposed by other UK institutions
How are we going to achieve this?
- user engagement – this will be ongoing throughout the project, but also specifically relates to the first phase of environmental assessment which will inform the implementation plan
- modelling – drafting institutional data management policies
- technical structure – producing pilot research data management systems
- training and support for visual arts researchers
- sustainability – business and sustainability plans to continue the work of Kaptur at the four institutions, after the end of the project and beyond
The images on the poster/banner show:
- some concrete examples of visual arts research data
- examples of research data generated through our own Kaptur project
- the sheer volume of some research data e.g. contact prints for photographs – selection and storage issues
- the blurring of boundaries between visual arts research data and visual arts research outputs
- the space in which research data is generated