Date

Invitees

Team

Guests

Goals

Discussion items

ItemWhoNotes
News since previous meeting

Ellen


  1. Update on Statement of Work (pre-contract document) from Avyre (migration vendor)
  2. Update on recommended priority collections for migration
    DAMS-I Prioritized Content for Migration
  3. Project Risk Register
Milestones/
Today's Work
All
  1. SOW finalization
  2. Censhare contract start date discussion
    1. System configuration timing
    2. Migration timing
Updates/QuestionsAll

System overlap considerations: ArchivesSpace, DAMS, tracksys

Apollo - Our Mountain Work might need to move to Virginia Chronicle, per Jennifer Roper. It is a Virginia newspaper, per Heather. If it is in VA Chronicle, would no longer be hosted by UVA.

Putting in data in different formats is a good practice for determining metadata needs (Perry can check that they work as expected in DAMS).

Questions about purpose of DAMS came up again.

  • Stan: impasse on which collections to select for the project is slowing us down. ultimately everything should go into the DAMS. 
  • Gathering things together is a purpose of the DAMS. Jennifer removes her concern about Our Mountain Work.
  • Perry: is a collection-based approach the best way to test the system? What about one piece of each type of content so we can show we can describe and access each type adequately (video, XML-marked up text, images, etc). Handle collections later? Start with unaggregated objects, then build up to collections/aggregations. 
Up NextAll

DAMS-ArchivesSpace metadata discussion on (KR, MD, CD, ER, BG)

Collections for migration are Edgehill and Apollo, pending a contract with migration vendor.

AOBAll

Action items