About this Guide

This guide is intended for people who want to find information on repositories and organisations, and who wish to determine if the UK RepositoryNet+ ORI "micro service" can help them to do so.

The Frequently Asked Questions (FAQs) are provided to clarify the service and the terms under which it may be used.

If you have further questions about the service that are not answered by the guide please contact the EDINA help desk team, or send email direct to: edina@ed.ac.uk

Frequently Asked Questions

What is ORI?
Organisation and Repository Idenitification (ORI) is an managed "micro service" providing access to an edited union of several authoritative sources of data on organisations and repositories: UKAMF, ROAR, OpenDOAR, Webometrics, UCAS, data from the former JISC Monitoring Unit, and the WHOIS records for DNS entries.
How many organisation records does ORI contain?
At present (Q3, 2013) ORI holds records on 25,000 organisations, 14,000 networks that map to those organisations, and over 3,000 repositories associated within those organisations.
Who provides the ORI service?
The service was developed as a "micro service" for UKRepositoryNet+, a JISC initiative being developed by EDINA as a socio-technical infrastructure supporting deposit, curation and exposure of Open Access research literature.
The service is operated by EDINA
What can ORI be used for?
See the Example Use Cases section for some possible uses.
How do I use ORI
Although simple manual queries can be made using parameterised URLs from a web browser, access will usually be machine to machine via an application that is developed in-house or as added functionality for an existing application. Typically, the calling application will use an Ajax framework such as jQuery to request data from ORI and present the results to the user.
Are there live examples of using the ORI service that I can study?
The ORI technical manual provides some simple URL based calls to the main API and documents the syntax for these. Experienced application programmers will be able to develop applications on the basis of this information. In-house demonstration clients with code samples to call ORI and format the returned data are available for inspiration.
What restrictions are there on the use of the ORI?
There are no restrictions on access to the main API calls, so anyone may access the service over HTTP.
What licences apply to the ORI data?
All data in the ORI has been harvested from public sources, therefore use of the ORI data is unrestricted.
Who do I contact if I need help or support?
If you have further questions about the service that are not answered by the guide please contact the EDINA help desk team, or send email direct to: edina@ed.ac.uk
How does ORI gather information on organisations?
Information is harvested from external sources using a set of scripts running on an automated schedule.
What information does ORI hold on an organisation?
Please see the section Data Returns of the technical manual for complete details of the data that ORI returns on organisations, repositories, networks and identities.
Can I trust the organisation data held by ORI?
The database is built from multiple online sources, so there may be inconsistencies. These errors would be present in any call to services such as ROAR or OpenDOAR. Extensive curation procedures both scripted and manual are undertaken on the data to ensure that errors in the data held are kept to an absolute minimum.
How do I report any errors I find in the data?
Please report any errors that you find to the EDINA helpdesk (contacts as above). It would assist in correcting the data if you could include a copy of the returned data in the format that it was requested in e.g. JSON or XML.
Who should I report bugs to?
Bugs or other issues that you encounter when querying the ORI should be reported to the EDINA help desk (contact details above) who will forward the issue(s) on to the ORI development team for their attention.

Acknowledgement

ORI was developed by EDINA, with funding from JISC