Repository FringeJournal Research Data Policy Registry (JRDPR)

4 August 20155

2

To develop best practice on journal policies between publishers and other stakeholders. To make it easy for researchers to know how to follow policies and for journals to create RD policies

Journal Research Data Policies Registry

•Start: April 2015•End: September 2016•Website: http://bit.ly/1Ks8jhb

•End Goals: a shared service with easy access to journal research data policies and common related standards

MNo. Objective Deadline1 To build a community of engaged stakeholders

who will accomplish a number of key tasks for the project as well as raise the profile of the project with both the UK sector and the international research community.

First round April-June 2015

Second round September 2016

2 To build consensus on the elements and understanding of journal research data policies through a range of activities such as an RDA group, the Project Expert Advisory Group and practitioner engagement through testing.

Project Expert Advisory group June 2015

RDA Group September 2015 – March 2017

3 To develop and build a prototype Journal Research Data Policy Registry service which meets the needs of the use cases developed and prioritised in consultation with the stakeholder group.

September 2015 (Rapid prototype)

Iterative development to April 2016 then wider user-testing.

4 To evaluate the prototype against the use cases as a proof of concept exercise.

September 2016

5 To evaluate the potential for a Journal RD Policy Registry service and the further implementation and uptake of the best practice developed

September 2016

https://flic.kr/p/rob872 (cc-by) jakerust/gotcredit@flickr

3

Research Data Question Set

» Standard definitions: ‘the dataset’, ‘the data’, ‘supplemental data’» Introducing a hierarchy of publisher and journal policies, where a journal

policy may adopt a publisher policy.» The level of granularity required to capture policy at the data set level.

Certain policies will omit mentioning the specifics of the data set, yet others will specify what they require. Exceptions for data – sensitive data, commercial data, 3rd party data

» Data Access Statements are required by funders and institutions but may not be mentioned by the journal. What is the best way to address this area?

» Licencing arrangements? Same as OA or will this be an RD specific field in time?

Issues Log – some examples

5

Rapid Prototype

»Look and feel?»Usability?»Functionality?

Use case development

»Potential users of the service are considered to be:› Researchers› Research Managers› Librarians/RDM support staff› Funders/policy makers› Publishers/journal editors/learned societies› Research data repository managers› Others?01/05/202

3JRDPR Expert Advisory Group - Use Case Development 6

»Users could potentially access data in a variety of ways

Use case development

01/05/2023

JRDPR Expert Advisory Group - Use Case Development 7

JRDPR

Search on single title/ISSN

Search by field/subject

Search by data type (and field/subject)

Side-by-side comparison of titles

Filter against funder reqts

Filter by publisher

Total number of policies (by owner, region, type etc)

Report on changes over time?

Entry/update of details

API?

Data repositories

Institutional CRIS?Other services?

8

Next Steps

»Refining the data model/question set»Use case development»Rapid prototype testing»RDA 6th Plenary, September 23rd – 25th

September – Birds of a Feather session.»Next meeting