Posted by: Theo | August 27, 2009

OA-RJ Use Cases

Use case One: Research Funders

Our first use case scenario will focus on the role of the research funding body in the scholarly communication chain as a driver for open access content and how to assist ‘right actions’ by Principal Investigators, being co-authors of funded work and leaders of funded research giving rise to articles written by others, including author/researchers at other institutions.

Currently 16 funding organisations within the UK have some form of deposit policy, directing deposit either to UK PubMed Central (UKPMC), to a specific named repository (e.g. ESRC awards and outputs repository, or the NERC Open Research Archive) or into an appropriate institutional repository. This can manifest itself as confusing for the Principal Investigators (PIs) to know the appropriate place(s) in which to deposit their research outputs. PIs would benefit from assistance in locating such a repository, or in the case of multi-authored work a number of such repositories, and funders would benefit from information about such deposits (also thereby assisting PIs and their institutions with issues of compliance).

We propose to investigate the differing requirements of funder and author-researcher and methods for ensuring computer-assisted deduction about output from activity subject to mandates and, using the Repository Junction broker, to enable re-direction and deposit into the appropriate repository/ies.

Use case Two: Publishers

The next use case scenario we will focus on is the role of the publisher in the scholarly communication chain as a primary source of open access content.

A number of scholarly journal publishing groups wish to assist their authors to deposit articles under terms of open access. Some publishers already deposit articles into PubMed Central (PMC) and UK PubMed Central (the British version) on behalf of authors for the last 6 months or so. In this case the Authors’ post-print versions of manuscripts are flagged for submission at the point of publication and sent by batch to PMC.

Publishers have expressed a keen interest to extend this deposit offer to institutional repositories but have encountered problems due to the distributed nature of IRs. The publisher cannot easily identify appropriate repository locations to transfer the articles, which is especially true for multi-authored work.

We propose to address this problem by exploring use of the Repository Junction broker as the redirect mechanism. One possible solution would be to send automated batches of data direct from the publisher to the Repository Junction broker, whereupon the broker could process and identify appropriate IRs to which to redirect/notify. If none were available, then deposit in the Depot might be an option.

A common approach for both scenarios

use cases
For both use cases we are building a generic broker system that is able to intervene and act intelligently to deposit in multiple repository locations. Determining an appropriate location for deposit relies on making correct deductions from the information available to us – for example depositors IP addresses or research grant codes. In the next blog post in the series Ian will talk more about the work we are doing to identify users via IP (and why it’s not as simple as it could be!).



  1. […] institutional repositories can work more closely together (we’ve previously blogged about this here). This new post describes how we envision the Authors’ post-print versions of journal articles […]

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s


%d bloggers like this: