Difference between revisions of "CURATEcamp DLF 2012 Discussion Ideas"
From CURATEcamp
Robin Dean (talk | contribs) |
|||
| Line 1: | Line 1: | ||
== Topics == | == Topics == | ||
| − | * linked data | + | * linked data (7) |
| − | * digital curation | + | * digital curation |
| − | * | + | * records management |
| − | * metadata & authority control | + | * metadata & authority control (10) |
| − | * long-term preservation of | + | * long-term preservation of complex objects (16) |
| − | * ( | + | * data model from UCSD (17) |
| − | * bootstrapping repository services | + | * bootstrapping repository services (getting started with minimal resources) - 15 |
* development trends | * development trends | ||
* standards | * standards | ||
* data management tools & processes | * 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 | + | * community development (e.g. Hydra project on top of not Fedora) - 15 |
| − | + | * METS development - 1 | |
| − | * METS development | + | * UI/UX development and reuse (how to do this, formal roles, community development) - 16 |
| − | * UI/UX development and reuse (how to do this, formal roles) | + | * Has the digital realm affected our idea of what digital preservation means? selection (e.g. of content types) for digital preservation - |
| − | * selection (e.g. of content types) for digital preservation | ||
* How the digital environment has changed the concept of selection for preservation - are we saving too much? | * How the digital environment has changed the concept of selection for preservation - are we saving too much? | ||
* preservation of bits & preservation of behavior/experience | * preservation of bits & preservation of behavior/experience | ||
| Line 32: | Line 31: | ||
* funding models for repository/curation services (grants, etc.) | * funding models for repository/curation services (grants, etc.) | ||
* e-book preservation | * e-book preservation | ||
| − | |||
== Timeline == | == Timeline == | ||
* 09:00-09:40: Introductions | * 09:00-09:40: Introductions | ||
Revision as of 17:33, 3 November 2012
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) - 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) - 16
- Has the digital realm affected our idea of what digital preservation means? selection (e.g. of content types) for digital preservation -
- How the digital environment has changed the concept of selection for preservation - are we saving too much?
- preservation of bits & preservation of behavior/experience
- usage of curation tools by users (vs. curators)
- multi-institutional repositories (UC, CIC, etc.)
- community-building: future of CURATEcamp, sustainability
- PREMIS for preservation metadata
- persistent identifiers, e.g., ARKs
- demos: scholarsphere, UCSD DAMS data model, ... ?
- curation & preservation in the wild (sans repo)
- service models for big data ingest: in-house repos and facilitated ingest within disciplinary repos
- project is done. now what?
- funding models for repository/curation services (grants, etc.)
- e-book preservation
Timeline
- 09:00-09:40: Introductions
