Difference between revisions of "ORCID connector"
(→Requirements) |
|||
| Line 61: | Line 61: | ||
|| Record ORCID ID against creator || EPrints field available to record ORCID ID in EPrint record || Must || Should || Should || Suggested | || Record ORCID ID against creator || EPrints field available to record ORCID ID in EPrint record || Must || Should || Should || Suggested | ||
|- | |- | ||
| − | || Display ORCID ID | + | || Display ORCID ID in User Profile || ORCID is rendered in User Profile || Could || Could || Should || Suggested |
|- | |- | ||
| − | || | + | || Display ORCID ID in EPrint abstract page || ORCID is rendered EPrint abstract pages || Should || Should || Should || Suggested |
| − | + | |- | |
| + | || Enable administrators to import items from ORCID || Records can be imported from ORCID || Won't || Must || Should || Suggested | ||
| + | |- | ||
| + | || Enable administrators to export items to ORCID || Records can be exported to ORCID || Won't || Won't || Should || Suggested | ||
|} | |} | ||
| − | |||
==Concerns== | ==Concerns== | ||
Revision as of 14:19, 9 June 2016
Contents
Use Cases
No API connection
As a repository connecting to ORCID through another system
I need a field to record ORCID IDs
So that I can display and link the ORCID ID to other systems
As a repository which records ORCID IDs
I need to render the ORCID as a link
So that I can display the ID in the recommended format
Tier 1 (public) API connection
As a repository
I need to harvest information from ORCID public profiles
So that I can populate item records with information
Tier 2 (private) API connection
As a repository connecting to ORCID through this system
I need to communicate with ORCID
So that I can authenticate ORCID IDs
As a researcher
I need to choose which permissions to give my institution
So that I can integrate my ORCID to meet my personal requirements
End User
As a third party harvesting from EPrints
I need ORCID IDs to be exported in all metadata formats, not just oai_dc
So that I can reuse the metadata in my system
Requirements
This table is designed to record requirements for ORCID plugin development. It shows the function, how you would test it is doing the intended job, how desirable it is for each level of integration and whether the information is suggested, proposed or agreed by the community.
| Function | Test | No API | Tier 1 API | Tier 2 API | Status |
|---|---|---|---|---|---|
| Record ORCID ID against user | EPrints field available to record ORCID ID in User Profile | Could | Could | Must | Suggested |
| Record ORCID ID against creator | EPrints field available to record ORCID ID in EPrint record | Must | Should | Should | Suggested |
| Display ORCID ID in User Profile | ORCID is rendered in User Profile | Could | Could | Should | Suggested |
| Display ORCID ID in EPrint abstract page | ORCID is rendered EPrint abstract pages | Should | Should | Should | Suggested |
| Enable administrators to import items from ORCID | Records can be imported from ORCID | Won't | Must | Should | Suggested |
| Enable administrators to export items to ORCID | Records can be exported to ORCID | Won't | Won't | Should | Suggested |
Concerns
Compatibility
- The plugin needs to be compatible with other standard plugins, e.g. Rioxx
