2019-04-23 Meeting notes

Owned by Rachel Appel (Unlicensed)
Last updated: Apr 23, 2019
2 min read

Date

Apr 23, 2019

Participants

  • @Rachel Appel (Unlicensed)

  • @Alicia Pucci

  • @Holly Tomren

  • @Matthew Ducmanas

  • @Leanne Finnigan (Unlicensed)

  • @Stefanie Ramsay (Unlicensed)

  • @Gabe Galson

  • @Jasmine Clark

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

      • Margery also said that it includes corrections students requested over the years

      • Conclusion: migrate from CONTENTdm with already cleaned data and work with Alicia while Carla and Celio review authority control

      • Bulk clean up tool in DSpace (after we move to hosted)

    • Timeline

      • LTD had a high-level discussion, don’t believe that the local install is sustainable long-term

        • Start with what we have long-term and move to hosted Spring 2020

          • Open Repository based on DSpace that’s offered by Atmire

          • Includes extra features and a full back-end

      • Filenames need to be checked and matched for migration; need to decide when to migrate and into which version

  • Choice Management

    • Controlled Vocabulary form

  • 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.?

    • LC available. Uses this endpoint.

    • 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:

  • Advisory Schedule

    • Reconvene: October 22nd at 10am

      • Discuss state of soft launch

      • What do we need to do moving toward a hosted DSpace

Action items

Decisions