You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 22 Next »

short link to this page: http://bit.ly/dcat-dec

Date & Time

  • December 08 16:00 UTC/GMT - 11:00 EST

Dial-in

We will use the international conference call dial-in. Please follow directions below.

  • U.S.A/Canada toll free: 866-740-1260, participant code: 2257295
  • International toll free: http://www.readytalk.com/intl
    • Use the above link and input 2257295 and the country you are calling from to get your country's toll-free dial in #
    • Once on the call, enter participant code 2257295

Agenda

ORCID: Experiences - Ambitions - Challenges

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:

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

This one is already added in DSpace 5.2, but there is no general awareness about this, so we'll discuss it as well:

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Other topics

Preparing for the call

ORCID

  • If your institution is not interested in using the ORCID integration, tell us why
  • If your institution wants to adopt the ORCID integration but faces specific challenges/blockers, please list those challenges
  • If you are already using the ORCID integration, but are confronted with additional needs or requests for features, please list them as issues in JIRA so we can discuss them.

XMLUI Test plan for DSpace 6 Testathon

Even though we have a LOT of tests already, we are still no where near "full coverage" of the DSpace featureset. If you think of a feature that is not covered by the test plan, please add your tests in the plan OR add them in the comments below so someone else can add them.

 

Meeting notes

ORCID

Introduction

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.

Q & A

Is there an ORCID integration for JSPUI?

Up to now the ORCID integration was only developed for XMLUI. There is no JSPUI integration available out of the box.

In case Symplectic Elements is integrated in your DSpace, how does ORCID identifiers get matched to names entered in Elements?

For being able to do this, Symplectic Elements should not only push the author string name but also the ORCID Identifier to DSpace.

Is there support for other metadata fields than author names as well?

Currently there is only support for the author metadata fields. There is, however, ongoing development to support project and funder identifiers.

Integrating ORCID means adding ORCID links to existing files. How could we do this in a time effective way?

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.

Suggestions

  • It would be convenient if only identifiers of your own institutions are shown by default. Alternatively it might be an option to display an authors affiliation with their ORCID identifier.
  • There is a need for a web interface to manipulate the authority cache so it can be extended or corrected. Currently their is only a script to here is a script to add new information (update) to the authority cache. This script can also remove id's which are not used in the repository, so the cache does not become polluted.

Results from the meeting

Unable to locate Jira server for this macro. It may be due to Application Link configuration.  

Included in the scope of the use case at Integrations - Support external authorities (ORCID) in Authority Cache

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Integrations - Support for external identifiers (ORCID) in the CSV Batch edit

XMLUI Test plan for DSpace 6 Testathon

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.

UI prototype challenge

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.

Call Attendees

  • No labels

All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.