Difference between revisions of "CURATEcamp OR11 Ideas"

From CURATEcamp
Jump to: navigation, search
Line 12: Line 12:
  
 
'''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.
 
'''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?
 +
 +
'''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?
 +
 +
'''XMLUI batch editing system for DSpace''': Batch editing by exporting and importing the contents of the repository is not ideal. 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?
 +
 +
'''[http://wiki.code4lib.org/index.php/HAMR:_Human/Authority_Metadata_Reconciliation HAMR]''': Continued work on this tool for comparing your record to an authority record and easily applying changes.
 +
 +
'''Tools for knowing when an article is published (other than PubMed) Bibapp?''': 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?
 +
 +
'''Reporting system for DSpace''': Particularly thinking about frequency reporting -- What values are typical for a field? What are the range of values in this field?

Revision as of 22:30, 3 June 2011

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

Here's an example:

MICROSERVICES THROWDOWN (Mike Giarlo): The fixity microservice has a beef with the storage microservice -- which will win? Lorem ipsum, checksum ipsum, yada yada.




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?

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?

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?

XMLUI batch editing system for DSpace: Batch editing by exporting and importing the contents of the repository is not ideal. 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?

HAMR: Continued work on this tool for comparing your record to an authority record and easily applying changes.

Tools for knowing when an article is published (other than PubMed) Bibapp?: 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?

Reporting system for DSpace: Particularly thinking about frequency reporting -- What values are typical for a field? What are the range of values in this field?