Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

#TimeItemInformationWho
15mins

Agenda

Any additional topics to today's agenda?

All
225minsUpdates on OpenAIREv4

Any updates to discuss this week?

Question from last week (Nov 26):  How do we handle "relatedIdentifiers" vs "alternateIdentifiers" in our DSpace metadata?

  1. The new Schema.org identifier fields in PR#2576 seem to correspond to "alternateIdentifiers" (e.g. person.identifier.gsid is an alternative Google Scholar identifier for the Person Entity). 
    1. These fields represent (externally created) Identifiers that correspond to the Entity in DSpace. For example, if a publisher has its own DOI, then the publisher's DOI would be stored in these fields....while the DSpace-generated DOI would be stored in "dc.identifier.uri" as normal.
  2. "relatedIdentifiers" concept could be represented as new "oaire.relatedIdentifier.*" fields perhaps?  (Jose Carvalhoand Paulo Graçawill discuss and get back to useus)

Discussion about entities on XOAI layer (https://github.com/DSpace/DSpace/pull/2592) The way XOAI uses Solr, we foresee that Solr will get some weight and also the "/dspace/bin/dspace oai import" method will be a little bit slower using this approach (this was negligible with our experience with DS5, but we just processed Publications, now we may also process Persons). At the moment the only possible solution that occurs is to have a configuration (perhaps on oai.cfg) to enable/disable entities. Other suggestions includes filtering by the relationship label, like: isAuthorOfPublication.

Work based on:

All
315minsWrap-up and Assigning tasks
  • Assign tasks / PRs to review (as needed)
  • Next meeting is Tues, Dec 10

...