IS&T Archiving Conference CURATEcamp 2013/collaboration

From CURATEcamp
Revision as of 14:30, 4 April 2013 by Meg Phillips (talk | contribs)
Jump to: navigation, search

Session 1 : Crowdsourcing and Collaboration


•BitTorrent for replication

•Many different things that could be shared (work, SW, discovery, access, infrastructure, expertise, development)...

•Hydra project

•Tool registry (Illinois, Paul Wheatley/Spruce)

•MediaInfo - A/V md extraction (Caltura uses it?)

•Avalon (Ind.) is a Hydra head

•Denmark - lots of crowd participation (advertised on TV, radio)

•How to leverage collaboration in a really effective way

•What you can’t outsource ◦What community am I trying to serve? ◦What does that community need?

•Lack of collaboration spaces ◦Share procedures, templates, policies ◦Ask questions◦Easy to find what you need when you need it

•Language is a barrier

•Within your institution - how your work fits into the larger collaborations

- Would it be possible to come up with an intellectual framework for collaboration so we can talk more clearly about the options and figure out the areas where different institutions can get the biggest multiplier effects from working with others? For example:

- shared work: outsource some work to others, including crowdsourcing, using other volunteers, etc: help creating metadata, help creating new tools for you specifically using APIs, etc. Sharing particular kinds of digital preservatione expertise could fit here, too - mentoring and consulting with peers at other institutions, for example - Shared tools - many institutions using the same tools, develop once, use many times across the community - Shared infrastructure, for example participation in a LOCKSS network for bitstream preservation - many institutions actually using the same repository/ digital preservation system. It's a fine line between this and participation in a network, but I think there's a distinction. This last option, where the local institution may be using a system that they aren't running, could be helpful for very small institutions with no local DP expertise or a strong IT infrastructure.