2022-01-25 Meeting notes

General Updates

Eric, Beth, Steve

• Final DAWG Charge

  • Charge

• DAMS Self-Evaluation Toolkits Summary of Findings

  • https://docs.google.com/presentation/d/1WE6xd2CVjg4MnmwF0ij5MTt-I2M5tbPyroU8ExiLAJw/edit?usp=sharing

  • https://docs.google.com/document/d/1owzXwIDHQJsr8DdRzlh-OsY8cbgJVLpKvUuvUtCCVMw/edit?usp=sharing

  • https://docs.google.com/spreadsheets/d/1hrUPghl9lZLtCiF1XPnELSSBQEHuR4N2wYhBkcYwwl0/edit?usp=sharing

• Hyrax Testing

  • Samvera/Hyrax testing notes

DAMS Update

Dave

• Brief overview of the upcoming DAMS work/timeline

  • Dave is working on a report for COLD and will provide them with an update at their February meeting

  • Work is expected to move forward on the DAMS, either additional fact finding if requested by COLD or on design/implementation of Hyrax

Potential Upcoming Projects

All

• Priority #1: Demo/Proof of Concept of Hyrax for COLD

  • Show an example of systemwide shared DAMS using sample collections from a few campuses (LA, Northridge, SB, Channel Islands, others)

  • If other campuses participate have a space for them to drop their digital objects and metadata; DAWG members will then work to get this content into the Hyrax instance

  • Use Hyrax functionality of “nested collections” to show an example of how content at multiple campuses can be integrated and displayed together (by topic, format, etc); similar to a digital exhibit of sorts

  • Use a Hyrax test instance set-up at the CO (ready sometime in March possibly)

  • For COLD, point to the benefits of Hyrax:

    • Design is under CSU control, not the vendor

    • Annual costs not at the discretion of a vendor

    • System can evolve over time as needed to limit platform changes/additional migrations

    • Can support harvesting for campuses using their own DAMS

    • How a systemwide DAMS can support instruction and lead to student success

• Collaborative work with MWG on DAMS metadata schema/approach

  • Work not slated to begin yet

• DSpace collection analysis (e.g., extent, format types, metadata) for DAMS seed collections

  • Will address when/if needed

• DAMS documentation/testing

  • Will address closer to system design/implementation