CURATEcamp DLF 2012 Discussion Ideas
From CURATEcamp
Revision as of 17:56, 3 November 2012 by Robin Dean (talk | contribs) (→Contribution and Ingest: Lowering Barriers)
Contents
Agenda
Contribution and Ingest: Lowering Barriers
- just-in-case vs. just-in-time metadata
- what's "good enough": department, creator, hit send?
- how can we get digital stuff with the minimum amount of effort?
- recap of C4L 2011 discussion: why does ingest suck?
- set up a pre-ingest staging area for review to make sure content is "repository worthy"
- promise of permanence sets up a barrier (forever is intimidating)
- perception that ingest makes objects less discoverable
Fighting the "One Tool to Rule Them All" Mindset
Cylinders of Excellence: living with multiple systems (interoperability, one system to rule them all?) combatting "one tool" philosophy (three tools: DAMS for simple items, repo for authorial/ETD workflow, GIS data somethingsomethin'), how not to shoehorn everything (platform/layers vs. monolithic) - especially issues with multiple workflows - 18
- project is done, now what? - proving value of investment - ROI ALSO funding models for repository/curation services (grants, etc.)- 18
- long-term preservation of complex objects (16)
- UI/UX development and reuse (how to do this, formal roles, community development)- usage of curation tools by users (vs. curators) - 16
- bootstrapping repository services (getting started with minimal resources) curation & preservation in the wild (sans repo) - 15
- Has the digital realm affected our idea of what digital preservation means? selection (e.g. of content types) for digital preservation -
are we saving too much? who decides? - 15
- Gather round for demos at 3:30 - 25ish
- data model from UCSD (17)
- Wrap-up session: community-building: future of CURATEcamp, sustainability - 19
Topics
- linked data (7)
- digital curation
- records management
- metadata & authority control (10)
- long-term preservation of complex objects (16)
- data model from UCSD (17)
- bootstrapping repository services (getting started with minimal resources) curation & preservation in the wild (sans repo) - 15
- development trends
- standards
- data management tools & processes
- Cylinders of Excellence: living with multiple systems (interoperability, one system to rule them all?) combatting "one tool" philosophy (three tools: DAMS for simple items, repo for authorial/ETD workflow, GIS data somethingsomethin'), how not to shoehorn everything (platform/layers vs. monolithic) - especially issues with multiple workflows - 18
- expanding the value of library infrastructure/tools (business use, scholarship) - 12
- Contribution/ingest - 20
- Abstraction layer for repositories especially from early and/or bespoke systems - 2
- community development (e.g. Hydra project on top of not Fedora) - 15
- METS development - 1
- UI/UX development and reuse (how to do this, formal roles, community development)- usage of curation tools by users (vs. curators) - 16
- Has the digital realm affected our idea of what digital preservation means? selection (e.g. of content types) for digital preservation -
are we saving too much? who decides? - 15
- Now that the bits are preserved, how do we preserve behavior/experience - 7
- multi-institutional repositories (UC, CIC, etc.)
- Wrap-up session: community-building: future of CURATEcamp, sustainability - 19
- PREMIS for preservation metadata (user feedback, requests) and changes coming in PREMIS 3 - 4
- persistent identifiers, e.g., ARKs - 8
- Gather round for demos at 3:30 - 25ish
- service models for ingest: internal repos vs external or subject repos - 8
- project is done, now what? - proving value of investment - ROI ALSO funding models for repository/curation services (grants, etc.)- 18
- e-book preservation - 4
Timeline
- 09:00-09:40: Introductions