Difference between revisions of "CURATEcamp DLF 2012 Discussion Ideas"
From CURATEcamp
Line 14: | Line 14: | ||
* making contribution/ingest "easier" esp. with complex & novel formats | * making contribution/ingest "easier" esp. with complex & novel formats | ||
* interoperability (abstraction layers) from early and/or bespoke systems | * interoperability (abstraction layers) from early and/or bespoke systems | ||
− | * | + | * community development (e.g. Hydra project) |
+ | * Hydra on top of NotFedora | ||
* METS development | * METS development | ||
* UI/UX development and reuse (how to do this, formal roles) | * UI/UX development and reuse (how to do this, formal roles) | ||
Line 27: | Line 28: | ||
* demos: scholarsphere, UCSD DAMS data model, ... ? | * demos: scholarsphere, UCSD DAMS data model, ... ? | ||
* curation & preservation in the wild (sans repo) | * 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 | ||
+ | * 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) | ||
== Timeline == | == Timeline == | ||
* 09:00-09:40: Introductions | * 09:00-09:40: Introductions |
Revision as of 17:52, 3 November 2012
Topics
- linked data
- digital curation
- e-records
- metadata & authority control
- long-term preservation of heterogeneous content
- (meta)data modeling
- bootstrapping repository services
- development trends
- standards
- data management tools & processes
- seamless interoperability across v. different systems & workflows
- libraries' role in providing infrastructure for non-traditional purposes
- making contribution/ingest "easier" esp. with complex & novel formats
- interoperability (abstraction layers) from early and/or bespoke systems
- community development (e.g. Hydra project)
- Hydra on top of NotFedora
- METS development
- UI/UX development and reuse (how to do this, formal roles)
- 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
- 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)
Timeline
- 09:00-09:40: Introductions