Skip to content

Re-evaluate metadata blocks, metadata display, help, and metadata sources #6030

@djbrooke

Description

@djbrooke

As Dataverse expands to new disciplines and as we seek new ways to ensure high quality metadata, we should take an opportunity to discuss where we can make some improvements. We’ve had good feedback from the community across several issues (#5938, #6003, #3622, #6000, #4772, #350, #2603, #4282), which I’ve tried to capture as use cases below.

  • I want depositors to select subjects more appropriate to the discipline(s) the dataverse installation supports
  • I want depositors to select contributor types more appropriate to the disciplines the dataverse installation supports
  • I want depositors to select from a list of people provided by LDAP (or another system) for fields such as author, contributor, producer
  • I want depositors to be presented with the most appropriate experience (dropdown, checkbox, autocomplete) for selecting/populating metadata values
  • I want depositors to be able to select from metadata options provided by an API instead of from hard coded values
  • I want depositors to be able to select multiple fields for certain metadata elements

This issue will focus on proposing a solution to cover as many of these use cases as possible (and others that I'm sure I'm missing) instead of trying to push forward individual issues.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Status

    Proposals

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions