Versions Compared

Old Version 15

changes.mady.by.user Paulo Graça

Saved on

compared with

New Version 16

changes.mady.by.user Paulo Graça

Saved on

Key

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

...

#TimeItemInformationWho
110minsQuick overviewhttps://docs.google.com/presentation/d/1YDrAoD3QUwhxUCfuznXa7-LmK0nGbGXHqVa7Y0A4wIgPaulo
25mins

Revisiting Priorities Listing

We've started #1 and #2. Priorities #3 and #4 are worth digging into a bit more (background reading at https://docs.google.com/document/d/1X0XsppZYOtPtbmq7yXwmu7FbMAfLxxOCONbw0_rl7jY/edit#heading=h.wjaqg235p53r) :and there is a new #14 priority in our list.

All
310mins

Author name variants - UI Proposal and discussion

Status update on UI for relationship lookups in the submission forms (Atmire).

Based on the work done for Mockups for the Submission process with support for the Author (Person Entity) first version: https://drive.google.com/open?id=1wRIsDJr3A7AHrrLqNHlSGGBphPryhd-l we propose to visually enhance the process to allow the user to pick the author name from the name variants.

Please check at: https://drive.google.com/file/d/1L8dYoqLXY0DIWfFf5dr3f305D8EM58um/view

RCAAP and All
410minsSupport for defining relationship lookups in the submission formsBased on the feedback on https://github.com/DSpace/Rest7Contract/pull/64, it should be determined whether any of the suggestions should be changed, and how all the details can be included in that caseAll
510minsLabels on relationshipsClarification on labels of relationships: https://www.dropbox.com/s/m28kgyarazolif9/entities%20labels%20direction.pdf?dl=1Atmire
610mins

Metadata fields for each Entity type

The discussion started at "DS-4223 Metadata Schemas for configurable entities" - https://github.com/DSpace/DSpace/pull/2443, regarding the missing Orcid ID. We need to decide what which strategy to follow, not only for Orcid IDs, but also to other Entity IDs fields, like Organization ISNI or Ringgold which none of them is supported by Schema.org or Dublin Core. The proposed strategies are:

  • Rely on the DC specification for identifiers - dc.identifier, the values will be stored in the type of a URI - dc.identifier.uri = http://orcid.org/0000-0001-2492-3701
  • It will be created a set of non standard dc.identifier qualifiers (we already have some), like dc.identifier.orcid, dc.identifier.isni, ... and each installer will decide the best way to manage their qualifiers
  • Rely on the Schema.org to add new specific fields, for example it supports the DUNS number in the Organization schema
All
75minsWrap-up and Assigning tasks
  • Assign tasks / PRs to review (as needed)
  • Next Meeting is Tues, July 16.
Paulo

...