Open Access Repository Junction
Post on 19-Dec-2014
1003 Views
Preview:
DESCRIPTION
Transcript
Open Access Repository Junction
1
OARJ Project@#jiscDEPO programme meeting 1st March 2011
Theo AndrewProject Manager
EDINA
Open Access Repository Junction
2
Talk outline• Aims
• Background– Discovery– Delivery
• Proof-of-concept
• Demonstrator service
• Issues & Next steps
Open Access Repository Junction
3
Aims: assist deposit into multiple existing repository services by developing middleware that will aid both discovery of repository targets and delivery of the content
Open Access Repository Junction
4
Background
• Depot (2007/09) - unmediated eprints repo
• EDINA added a referral service, called Repository Junction, to redirect users to existing IR services.
• Survived by the OpenDepot.org service run by EDINA.
• OA-RJ (2009/11) – to expand on the concept of the Repository Junction
• Initial focus on the discovery aspect; however,
• Concept of data mining for target repo identification lead to broker service.
Open Access Repository Junction
5
Discovery: The Junction
openDOAR
ROAR
UKAMF
Junction db:Org IDs matched to IRs
Named entity recognition
WhoIS
ORCID
Funding codes
Other AMFs
SOURCES
AP
I
Known org ID
Article XML
Known IP location
INPUTS
Matched repositories
Open Access Repository Junction
6
The Junction API
Suite of three APIs for interacting with the data:/api [primary point of interaction]/cgi/list/ [lists known values - type/content/country/lang/org/net] /cgi/get [used for internal AJAX functions orgs, repos, net]
http://oarepojunction.wordpress.com/junction-api/
•/api can be given a specific locus to deduce repositories (IP address or an ID code) to specify the organisation, or it will deduce a locus based on the calling client.
•The script can be asked to restrict the returned list by repository type (institutional/learning/..) or accepted content (pre-prints/data/thesis/...)
•Data is returned in either JSON, Text, or XML formats
Open Access Repository Junction
7
Consider a complete bipartite graph between 2 sets,
where Set A (=3 nodes) passes information to Set B (= 5 nodes) :
Set a
Set b
Total number of edges = 15
Each data provider needs to broker an agreement
with every target repository, and each target repository
needs to authenticate each data provider - this does not scale
Open Access Repository Junction
8
Consider adding a central node to connect the sets:
Set a
Set b
Set A (=3 nodes) passes information to central node,
Central node passes information to Set B (= 5 nodes),
number of edges = 8
In this structure, each party maintains just one
relationship with a trusted operator
Open Access Repository Junction
9
Nodes:• 185 repos listed in openDOAR for UK• 200+ publishers listed in SHERPA
Edges:
37,000 or 385
... what are the Global Figures? Researchers are not confined to the UK borders
Open Access Repository Junction
10
Proof-of-concept
• http://oarepojunction.wordpress.com/2011/02/25/proof-of-concept-demonstrator/
Open Access Repository Junction
11
How a broker model could simplify things:- one consistent deposit process- single sign up for content providers and receivers- building a network of trust
Demonstrator service
Broker
Institutional Repository 1
Institutional Repository 2
Institutional Repository 3
Open Access Repository Junction
12
Case study 1: multiple authored paper
Paper A
Copy A2Researcher 2 Copy A1 Researcher 3
Metadata A2Metadata A3Metadata A1
Researcher 1
Journal Y
Repository 1Repository 2 Repository 3
Copy A3
Open Access Repository Junction
13
Case study 2: Mandated open access
Journal Y
Paper A
Researcher 1
£000s
Copy A1
Copy A1
Researchers 2 & 3
Open Access Repository Junction
14
Institutional partner
All NPG journals
Participating NPG journals
50% author participation rate*
Edinburgh 194 65 32
Cambridge 1429 476 237
Oxford 962 321 160
MIT 499 166 83
Cornell 275 92 46
Yale** 248 83 41
Auckland 53 17 8
TOTAL 3660 1220 607
Estimate of the number of broker transferred items during a six month demonstrator service. Data is based upon the number of papers published in journals from the participating NPG portfolio during Jan - June 2010. Data retrieved from PubMed Central and ISI Web of Knowledge. (*Figure rounded down, **Still to be confirmed as a participating institutions).
Open Access Repository Junction
15
Issues and dependencies
• Common deposit package for SWORD
• Missing data – provenance/embargo details/ author affiliations
• Licensing – content providers and repos
• Institutional sign-up – federation model?
Open Access Repository Junction
16
Project Blog:http://oarepojunction.wordpress.com/
Thankyou for listening.Questions?
top related