Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Date

Participants

Notes

  • MAP Review based on Alicia’s feedback

    • Further questions will be addressed via Slack or email

    • Stefanie consolidate CV doc and MAP doc

  • ETD Migration

    • Holly’s follow-up with Carla re: migrating directly from ProQuest

    • Timeline

  • Advisory Schedule

  • Choice Management

  • Authority Control Module

    • Summary

      • Authority control (authentication keys) vs ‘choice management’ (CVs)- two separate things

      • A tool for administrators… only displays on back end

      • Can be required, or not. ‘Not’ is recommended… the status will still be clear to the repo manager, and the lookup option will help them correct these

      • Complex interaction with submission form options (see table below)

    • ORCID lookups

    • Authority control master doc… not updated since 1.?

    • See also the 5.x documentation, especially the section on how authority control behaves in the administrative UI, pictured here:

    • Overall, Authority control is confusing and poorly documented. See this thread where Tim Donohue, DSpace 7’s lead developer, says 'Unfortunately, authority control is an area of DSpace that is still poorly documented… I admit I don't even have a clear understanding of each of the configuration options.” Gabe Galson will implement regular authority control in one field and report back to the group.

Alicia Pucci Assuming LCNAF is implementable in every appropriate MAP field, authority control is his table should be consulted when creating the submission forms. I’ll try to find out if this is up to date:

Action items

  •  

Decisions

  • No labels