Versions Compared

Old Version 12

changes.mady.by.user Tim Donohue

Saved on

compared with

New Version Current

changes.mady.by.user Tim Donohue

Saved on

Key

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

...

  • Early mockups of "Edit Relationships" tab of Edit Item (Presented by Lieven)
    • This tab already exists in codebase, but currently you can just view relationships and delete them.
    • Mockups show a new "add" button.  Pops up the same search module that is used by Submission UI to locate Entities & select ones that are related.
    • All agree this looks like a good early design.  Might be some usability improvements to make later.
  • Discussion of "Live Import" vs "External Sources"
    • Live Import
      • Existing feature in DSpace 6.x, docs at 2016 Framework for live import from external sources
      • This feature is a separate step in the Submission process (usually at the beginning).  The step lets you (1) select source to search, (2) enter in search fields, (3) select an entry to import metadata from.  If the WorkspaceItem is new, then that metadata is imported into the WorkspaceItem as a way to kick off the submission by prefilling a lot of the metadata.   If this is a WorkflowItem (under workflow), then a visual "diff" of current metadata fields versus those returned from the external API is displayed.  User can then decide whether to update the metadata to match that of the external API
      • Current example is with PubMed
      • This feature is more about importing metadata from an external API into the current submission (as a way of pre-populating metadata fields)
    • External Sources
      • New feature, specific to Entities. Contract: https://github.com/DSpace/Rest7Contract/blob/master/external-authority-sources.md  (Original PR https://github.com/DSpace/Rest7Contract/pull/74)
      • This feature is enabled on individual input fields within the Submission process.  It allows you to select a related external object/entity, and import that related entity into DSpace.  It does NOT directly modify the current submission, except to add in a new "relationship" to the imported object/entity. 
      • It may include some (but not all) of the same external APIs as the "Live Import" feature, e.g. ORCID.  Therefore it should share underlying code (to access those external APIs) as the Live Import feature.    That said, some "Live Import" external APIs (like PubMed) cannot be used as an External Source, as they do not represent Entities or Authorities (instead they are just external repositories of metadata).
      • This feature is more about creating related entities from an external API, and it does not modify the current submission's metadata.  It just adds a new relationship and imports a new object (entity).
    • Tim notes terminology here is definitely confusing
      • Live Import seems like it should be a "section" of the new Submission UI.  It's more about importing metadata into current submission from an external API.  May need to be named something like "Import Metadata" or "Metadata Importer"
      • External Sources is enabled on individual fields (if they are entity enabled). It's more about creating relationships between current submission and an imported Entity (again from an external API).  So, it's a different type of Import, more related to Importing an entire Object/Entity and relating it to the current submission.
      • May need to be careful about how each appear in the UI layer, as it could be confusing what each is doing.
    • These features are definitely different, but also related (in that they sometimes share the same External API, e.g. ORCID)