Curarium: Difference between revisions
No edit summary |
BerkmanSysop (talk | contribs) (old project) |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
{{Template:Oldproject}} | |||
Curarium is a platform for exploring, analyzing, and making arguments about collections and the objects they comprise. It leverages the power of collections to tell stories by giving users tools ranging from item-level annotations to comprehensive, repository-wide visualizations, allowing them to bring both objects and the communities to which they belong into dialogue with one another. | Curarium is a platform for exploring, analyzing, and making arguments about collections and the objects they comprise. It leverages the power of collections to tell stories by giving users tools ranging from item-level annotations to comprehensive, repository-wide visualizations, allowing them to bring both objects and the communities to which they belong into dialogue with one another. | ||
| Line 9: | Line 11: | ||
===Ideal candidate criteria=== | ===Ideal candidate criteria=== | ||
Curarium is interested in candidates with experience with Ruby on Rails, JavaScript, HTML5, AJAX, JSON, and PostgreSQL. | Curarium is interested in candidates with experience with Ruby on Rails, JavaScript, HTML5, Booststrap, AJAX, JSON, and PostgreSQL. | ||
Example sub-projects include: | Example sub-projects include: | ||
| Line 20: | Line 22: | ||
**embed works visualization (whole collection or search results) into LTS | **embed works visualization (whole collection or search results) into LTS | ||
*Tighter integration between WAKU (spotlight/story creation web app) via JSON APIs | *Tighter integration between WAKU (spotlight/story creation web app) via JSON APIs | ||
*Collection extraction from libraries and subsequent importing to Curarium; not just the act but also improving the online process | *Collection extraction from libraries and subsequent importing to Curarium; not just the act but also improving the online process | ||
Latest revision as of 09:51, 18 March 2019
Curarium is a platform for exploring, analyzing, and making arguments about collections and the objects they comprise. It leverages the power of collections to tell stories by giving users tools ranging from item-level annotations to comprehensive, repository-wide visualizations, allowing them to bring both objects and the communities to which they belong into dialogue with one another.
Curarium isn’t an online exhibition platform, but an environment for pursuing and sharing collections-based research nimbly, intuitively, and iteratively. Browse vast numbers of objects, using an expanding library of visualization tools to generate dynamic data portraits of collections. Annotate records and images, curating them to highlight relationships and juxtapositions. Assemble those records into trays of objects, images, and visualizations to share and work collaboratively with your social circles, and transform trays into published spotlights that unlock the stories and arguments bound up in collections.
More information: http://www.curarium.com
GitHub repo: https://github.com/berkmancenter/curarium
Ideal candidate criteria
Curarium is interested in candidates with experience with Ruby on Rails, JavaScript, HTML5, Booststrap, AJAX, JSON, and PostgreSQL.
Example sub-projects include:
- Visualizations of works of art (thumbnails, titles, topics, other properties) within and across library collections (including brainstorming, sketching, implementing, and testing)
- Curarium as a Learning Tools Interoperability (LTI) component for an LTS (e.g. Canvas)
- embed individual works into LTS
- embed tray of images/annotations into LTS
- embed works visualization (whole collection or search results) into LTS
- Tighter integration between WAKU (spotlight/story creation web app) via JSON APIs
- Collection extraction from libraries and subsequent importing to Curarium; not just the act but also improving the online process