Supported by a lot of caffeine, you can dig into the details of DataCite and ORCID APIs during a 1,5 day and night codesprint. Results from the sprint will be presented at the ODIN 1st year “Big Bang” public conference where you can engage with cutting edge leaders in the field of data sharing and re-use services.
Bootcamp sessions and a platform to join an discuss the projects will be on-line very soon! Meanwhile, you can have a look at the first projects here. Feel free to suggest new projects in the registraion form or sending us an e-mail! (odin.project@cern.ch)
PROJECT 1: From ORCID to INSPIRE
Proposed by: Laura Rueda
Introduction: Add a new box to the author profile page where we can show the list of publications retrieved from ORCID that do not exist on INSPIRE (matching DOIs?). Add a [+] button for each, so users can request the addition of that particular publication to INSPIRE. In preliminary phases this can generate a ticket and a manual checking can be done...
Estimated effort: 2 developers, 1 user
Prerequisites: experience with ORCID’s API and Invenio internals
PROJECT 2: ORCID authorship monitoring for data centres
Proposed by: Tom Demeranville
Introduction: In order to complete the “virtuous circle” of updates to DOI metadata data-centres need easy access to the information stored against their DOIs in ORCID. A service will be developed that allows a set of DOIs to be registered and monitored for changes of authorship within ORCID. The authorship information will be intelligently “diffed” against the DOI metadata and differences provided to the registrant. This could either be as a batch job, a query API or a human readable website.
Estimated effort: 2 developers, 1 user
Prerequisites: Any of the following: Scripting or programming skills, experience with ORCID’s API, familiarity with DOI metadata, data-centre domain knowledge.
PROJECT 3: Integrating with institutional workflows
Proposed by: Tom Demeranville
Introduction: It would be great if we could get more input from those responsible for managing identities, registration and IT within academic institutions. This would enable us to identify where ORCID fits into workflows used in those environments. Possible codefest outputs include widgets within VLEs or preliminary identity management integration workflows/designs.
Prerequisites: Involvement with institutional IT, Library or registration workflows
PROJECT 4: Federated identity - proving ORCID affiliation and linking ORCIDS to trusted identities.
Proposed by: Tom Demeranville
Introduction: Develop a prototype service that links federated identity with ORCIDs. Users logging into a single service with both would enable a bidirectional link between an ORCID and a trusted federated identity.
Estimated effort: 2 developers, 1 user
Prerequisites: Knowledge of federated technologies such as SAML or involvement with institutional IT, Library or registration workflows
[TJV: consider a Shibboleth developer: http://shibboleth.net/consortium/]
PROJECT 5: Harmonization of ORCIDs in DataCite and Crossref
Proposed by: Todd Vision
Introduction: A service that, given a DOI for a relevant CrossRef or DataCite record, compares ORCIDs for names that match between the two records. The output would be, for each name, whether the ORCIDs agree, disagree, are missing, or are available in one metadata store but not the other. This could be a building block for services that allow missing and incorrect ORCIDs to be filled in or corrected, respectively.
Estimated effort: ?
Prerequisites: Fluency with Crossref, DataCite, and ORCID APIs
