CURATEcamp OR11, 06/06/11

Notes taken by moderators during the camp are online at http://wiki.curatecamp.org/index.php/CURATEcamp_OR11_Ideas

There's a Digital Curation Google group with 450+ members, for ongoing idea-sharing among the wider community.

Highlights from my own notes include:

  • a list of tools to explore (Archivematica, Curator's Workbench, BagIt, Islandora)
  • model institutions with successful strategies & policies (UNC, UMN)
  • ideas for improving ingest strategies (effective analogies between traditional technical services and digital curation workflows; customizable ingest interfaces for different users or collections)
  • the 100 year view in considering what to keep
  • useful resources we could provide to facilitate/expedite preservation decisions (boilerplate NSF data management plan for researchers like UCSD does; list of disciplinary repositories and metadata schema)
  • Partnership model at UC San Diego - libraries partnering with supercomputer center for storage + partnership with office of research - library as broker for these services with the users/scholars.  Their supercomputer is mostly on soft $$, but hopes to move toward hard $$.
  • thoughts on strategies for collecting faculty web output (Archive-It, Internet Archive, wget, anthologize wordpress plugin)
  •  ideas for capitalizing on IT more effectively in library context (including developers in policy building process; using common language in planning, like the systems model approach; http://www.joelonsoftware.com/ cited as excellent resource)

- Melanie 06/09/11


06/21/11....and then a couple of additional notes from my (Zach) time at CurateCamp:

  • Declan Fleming, one of the CurateCamp organizers and system admin(?) at UCSD Libraries, made a comment about UCSD's digital collections being "too big to fit into Fedora."  It had something to do with a limit to how much storage or files a UNIX-based filesystem can handle.  Declan's comment seems to be related to metadata, rather than file storage (and so would be related to our discussions of management systems).  UCSD went with an RDF/Triplestore based system to accommodate its large amounts of metadata.  Wikidpedia article on Triplestore: http://en.wikipedia.org/wiki/Triplestore
  • Another program UCSD is involved in is Chronopolis, which provides long-term mass digital storage: https://chronopolis.sdsc.edu/ 
  • "Encoded Archival Context"