Versions Compared

Old Version 1

changes.mady.by.user Mark Diggory

Saved on

compared with

New Version 2

changes.mady.by.user Bram Luyten (Atmire)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: rescoped the use case
Title (Goal)Integrations - Support external authorities (ORCID) in Authority Cache
Primary ActorSystem
Scope 
Level 
Story (A paragraph or two describing what happens)

The basic dspace metadata shouldn’t be polluted with subfields. In order to keep the relation with external authority data such as ORCID metadata, we’re keeping a separate SOLR index with additional metadata. The DSpace should have a separate infrastructure to keep a local copy of externally sourced authority information. Technically, the standard Authority key field on dspace metadata fields are used to tie together the metadata fields and the entries in the "authority cache".

There is a need to manipulate these authority records as well. Therefore the authority cache needs robust features for CRUD (create, read, update, delete) on these authority records.