Page Comparison

Record!

Submission types

• What are DAWGs needs for submission types?

  • Could be some overlap, but also so much more

  • Text, audio/visual (will get remainder later)

  • Archival needs differ

• Is there overlap between student or faculty submission types and DAWGs needs?

• Tension over granularity

• DC type terms maybe too broad for someone looking for something specific

• Maybe need for genre/form

• High document level only a handful of terms (UC)

  • Getty for granular

  • Genre/form are keyword searchable

• How many facets in discovery layer? Can become convoluted

• Master data modeling spreadsheet

  • https://docs.google.com/spreadsheets/d/1ygz9MsxGGivP36iCfKGE3bbP_TgL0QIaqEG6sBtakMQ/edit#gid=0

• Need for different fields in textual vs. audio/visual

• https://docs.google.com/spreadsheets/d/19fep6Ij_PdEuRaNnK19XCCbakzugEHSOWVUIUYH-i7Q/edit#gid=0

• Remediation plan?

Landing page

• Sister system (OER + digital collections)

• Outside users not likely to submit

• Workforms probably not applicable as much

File and descriptive metadata

• What file or descriptive metadata will we need?

  • CSUN and Sonoma file types limited by Content DM

  • Type driven (.jpg, PDF, etc.)

  • Technical metadata (even hidden fields) may be needed by some campuses

  • Versioning may also be important

  • IDs - will we need something that shows everything in the repository?

  • Persistent URL

  • File naming convention can contain location information

  • File name can also connect to location of finding aid

  • Migrating out of ContentDM can be problematic down the line because of number conversion (some scripts exist for this issue)

  • What is expected at DPLA and Calisphere?
    

Digital archives

• How does DAWG envision digital archives in the future?

  • That every campus participates (sharing metadata) - exhibits and grant proposals a major possibility

  • Connecting regional collections throughout California

  • How can we encourage participation or make it possible? Self evaluations and surveying interest, recording readiness for this project. Working on implementing test sites. Lay out different ways to commit without migration if willing to harvest.