Difference between revisions of "CURATEcamp OR11 Ideas"
From CURATEcamp
(Preserving faculty web output;) |
(formatting) |
||
| Line 1: | Line 1: | ||
| + | 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? | |
Revision as of 00:26, 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?
