Difference between revisions of "CURATEcamp OR11 Ideas"

Revision as of 16:31, 6 June 2011

Feel free to use this space to share ideas for discussion at CURATEcamp #OR11.

Preserving faculty web output; Do you collect scholarly output native to the web? Web pages, blog posts, comments, tweets, winks, likes, zips, whistles? What are current policies, practices, plans, and pie-in-the-sky-semantic-web-dream-scenarios? + 2

Poolside is coolside; Let's test the theory that holding #curatecamp by a pool with margaritas leads to us solving all the digital curation problems.

Managing controlled vocabulary terms: How can we best incorporate terms from controlled vocabularies as subject keywords for improved searching/browsing? + 1

ORCID and other person IDs: Widely adopted person identifiers would solve many of our name authority control problems. How should we store them and how do we want repositories to interact with services like ORCID that provide them?

GUI batch editing system: DSpace has introduced a highly useful system for editing batches of records, but it still requires a bit of back-end-knowhow. Let's make some strides toward designing and developing a user interface for this feature. What are the requirements to make this useful in a variety of repositories?

Using a HAMR: HAMR is a (not-yet-functional) tool for comparing a locally held record to an authority record and easily applying changes. Will the current design work for your repository system? What features would you like to see in this tool?

Tools for knowing when an article is published: Wouldn't it be nice to have an automated notification that additional, more authoritative metadata is available for an item? Also has particular importance for repositories with embargo periods.

Statistics issues/discussion: How to improve what we display? What to report to users? How to measure impact? Standards for excluding robots, local users, etc. Will the DSpace stats setup work for other repositories?

Requirements for reporting systems: What types of reports are most helpful for curators? Can we develop a standard set of reports that all repository platforms should support? One example is frequency reporting -- What values are typical for a field? What are the range of values in this field?

Codified taxonomies vs. folksonomies, how to manage that

Identity & access management + 2

What repository software does for data curation, and how to adapt it (dspace, fedora, etc.) + 1

Building a brilliant new repository system (how to do that, how to start)

Distributed network (nationally, state-wide, campus-wide) for curation + 3

Libraries working with IT / "Rogue IT"

Ways to automate/batch ingest (SWORD?) & dissemination + 1

Authority control in the IR + 1

Tiered preservation policies (different metadata, etc.)

Discovery of science data in repositories

Social feedback loops (comments, trackbacks) in repositories + 1

Incentivizing work among developers / Working with developers

How to scale up to "Big Data"

Usability of repository interfaces (how to serve diverse user audiences)

Standards (metadata, formats, etc.) for long-term data preservation

Workflow systems (e.g. ingest) + 1

Multimedia and web formats

Integrating collections w/ GIS mapping, creative uses of GIS

--

curation microservices-based repositories

models for institutional data curation services

scalable architectures