The initial integration between DSpace and ORCID is a feature that was added in DSpace 5:
Documentation: ORCID Integration
Bram Luyten (Atmire) will give a 5 minute introduction on how the feature works with following slides:
http://www.slideshare.net/bramluyten/orcid-identifiers-for-dspace
During the call, participants are invited to share experiences with this feature. We will discuss the challenges of adopting ORCID in DSpace and hope to collect use cases or feature requests for further development.
The issues that are already logged in JIRA will be discussed as well:
This one is already added in DSpace 5.2, but there is no general awareness about this, so we'll discuss it as well:
An often occurring problem was is the lack of authority control on metadata in DSpace. An author's name, for example, often occurs as multiple variants in the same repository.
The solution was to create an authority cache in DSpace. This is an XML file in the solr core which logs values used for a certain metadata field after submission. These values can be retrieved later on using the submission form's lookup functionality.
Although using the Authority cache already decreases metadata value ambiguity, it is still limited to one repository. It is also not capable of dealing with homonyms. For example, when two different authors have the same name, it can not distinguish between them. These are issues which can be dealt with by ORCID.
ORCiD is a cross-platform persistent author identifier. As an ORCiD ID is unique, it enhances trust in the author's metadata field more than the authority cache. ORCID also handles homonyms well and deals with author name ambiguity.
Since DSpace 5.x XMLUI there is an integration with ORCID in DSpace. Similar to the authority cache, ORCiD lookups can be done in the submission form's author field.
Up to now the ORCID integration was only developed for XMLUI. There is no JSPUI integration available out of the box.
For being able to do this, Symplectic Elements should not only push the author string name but also the ORCID Identifier to DSpace.
Currently there is only support for the author metadata fields. There is, however, ongoing development to support project and funder identifiers.
By exporting the metadata in a CSV file you are able to batch-edit items and re-import the metadata to DSpace. This way you can add an author's ORCID identifier to all their items at once.
Included in the scope of the use case at Integrations - Support external authorities (ORCID) in Authority Cache
Included in the scope of the use case at Integrations - Support for external identifiers (ORCID) in the CSV Batch edit
Included in the scope of the use case at Integrations - Support external authorities (ORCID) in Authority Cache
Although we already have many test, the test plan is far from complete. Anyone interested in creating new tests or defining expected results is welcome. The goal is to have a solid test plan in place prior to the start of the testathon on January 4th 2016.
Currently there is a UI prototyping challenge going on to replace both XMLUI and JSPUI. An overview of the competing prototypes can be found on https://wiki.duraspace.org/display/DSPACE/DSpace+UI+Prototype+Challenge. The goal is to develop a uniform UI and bring the community back together for DSpace 7. This challenge will be used to decide which technologies should be used.