Curarium - Revision history

BerkmanSysop: old project

2019-03-18T14:51:46Z

old project

← Older revision		Revision as of 14:51, 18 March 2019
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.

BerkmanSysop: /* Ideal candidate criteria */

2016-02-18T23:07:08Z

Ideal candidate criteria

← Older revision		Revision as of 23:07, 18 February 2016
Line 20:		Line 20:
	**embed works visualization (whole collection or search results) into LTS		**embed works visualization (whole collection or search results) into LTS

	*Convert remaining "how we got it" code to much cleaner HTML5 and "the ruby way" styles

	*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

BerkmanSysop: /* Ideal candidate criteria */

2016-02-18T23:06:44Z

Ideal candidate criteria

← Older revision		Revision as of 23:06, 18 February 2016
Line 9:		Line 9:
	===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:

WikiSysop at 19:28, 20 February 2015

2015-02-20T19:28:15Z

← Older revision		Revision as of 19:28, 20 February 2015
Line 5:		Line 5:
	More information: [http://www.curarium.com http://www.curarium.com]		More information: [http://www.curarium.com http://www.curarium.com]

	GitHub repo:		GitHub repo: https://github.com/berkmancenter/curarium

	===Ideal candidate criteria===		===Ideal candidate criteria===

WikiSysop at 18:25, 20 February 2015

2015-02-20T18:25:50Z

← Older revision		Revision as of 18:25, 20 February 2015
Line 13:		Line 13:
	Example sub-projects include:		Example sub-projects include:

	*Visualizations of works of art (thumbnails, titles, topics, other properties) within and across library collections (including brainstorming, sketching, implementing, & testing)		*Visualizations of works of art (thumbnails, titles, topics, other properties) within and across library collections (including brainstorming, sketching, implementing, and testing)

	*Curarium as an Learning Tools Interoperability (LTI) component for an LTS (e.g~~, canvas~~)		*Curarium as a Learning Tools Interoperability (LTI) component for an LTS (e.g. [http://www.canvaslms.com/ Canvas])
	**embed individual works into LTS		**embed individual works into LTS
	**embed tray of images/annotations into LTS		**embed tray of images/annotations into LTS
	**embed works visualization [whole collection or search results] into LTS		**embed works visualization (whole collection or search results) into LTS

	*Convert remaining "how we got it" code to much cleaner HTML5 + "the ruby way" styles		*Convert remaining "how we got it" code to much cleaner HTML5 and "the ruby way" styles

	*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

WikiSysop: /* Ideal candidate criteria */

2015-02-20T18:23:35Z

Ideal candidate criteria

← Older revision		Revision as of 18:23, 20 February 2015
Line 9:		Line 9:
	===Ideal candidate criteria===		===Ideal candidate criteria===

	Curarium is interested in candidates with experience with Ruby on Rails, JavaScript, HTML5, AJAX, JSON, and PostgreSQL. Example sub-projects include:		Curarium is interested in candidates with experience with Ruby on Rails, JavaScript, HTML5, 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, & testing)		*Visualizations of works of art (thumbnails, titles, topics, other properties) within and across library collections (including brainstorming, sketching, implementing, & testing)

WikiSysop at 18:23, 20 February 2015

2015-02-20T18:23:07Z

← Older revision		Revision as of 18:23, 20 February 2015
Line 3:		Line 3:
	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.		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.

	~~===Tasks===~~		More information: [http://www.curarium.com http://www.curarium.com]

	~~1. visualizations of works of art (thumbnails, titles, topics, other properties) within and across library collections (including brainstorming, sketching, implementing, & testing)~~		GitHub repo:

	~~2. Curarium as an Learning Tools Interoperability (LTI) component for an LTS (e.g, canvas)~~		===Ideal candidate criteria===
	*embed individual works into LTS
	*embed tray of images/annotations into LTS
	*embed works visualization [whole collection or search results] into LTS

	3. ~~convert remaining "how we got it" code to much cleaner HTML5 + "the ruby way" styles~~		Curarium is interested in candidates with experience with Ruby on Rails, JavaScript, HTML5, AJAX, JSON, and PostgreSQL. Example sub-projects include:

	~~4. tighter integration between WAKU~~ (~~spotlight/story creation web app~~) ~~via JSON APIs~~		*Visualizations of works of art (thumbnails, titles, topics, other properties) within and across library collections (including brainstorming, sketching, implementing, & testing)

	5. collection ~~extraction from libraries and subsequent importing to Curarium; not just the act but also improving the online process~~		*Curarium as an 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

	~~===Technology===~~		*Convert remaining "how we got it" code to much cleaner HTML5 + "the ruby way" styles

	*~~Ruby on Rails~~		*Tighter integration between WAKU (spotlight/story creation web app) via JSON APIs
	*JavaScript
	*HTML5		*Collection extraction from libraries and subsequent importing to Curarium; not just the act but also improving the online process
	*AJAX
	*JSON
	*~~PostgreSQL~~

WikiSysop at 16:41, 20 February 2015

2015-02-20T16:41:17Z

← Older revision		Revision as of 16:41, 20 February 2015
Line 3:		Line 3:
	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.		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.

	Tasks:		===Tasks===

	1. visualizations of works of art (thumbnails, titles, topics, other properties) within and across library collections (including brainstorming, sketching, implementing, & testing)		1. visualizations of works of art (thumbnails, titles, topics, other properties) within and across library collections (including brainstorming, sketching, implementing, & testing)
Line 18:		Line 18:
	5. collection extraction from libraries and subsequent importing to Curarium; not just the act but also improving the online process		5. collection extraction from libraries and subsequent importing to Curarium; not just the act but also improving the online process

	Technology:		===Technology===

	*Ruby on Rails		*Ruby on Rails

WikiSysop at 16:40, 20 February 2015

2015-02-20T16:40:54Z

← Older revision		Revision as of 16:40, 20 February 2015
Line 8:		Line 8:

	2. Curarium as an Learning Tools Interoperability (LTI) component for an LTS (e.g, canvas)		2. Curarium as an Learning Tools Interoperability (LTI) component for an LTS (e.g, canvas)
	*embed individual works into LTS		*embed individual works into LTS
	*embed tray of images/annotations into LTS		*embed tray of images/annotations into LTS
	*embed works visualization [whole collection or search results] into LTS		*embed works visualization [whole collection or search results] into LTS

	3. convert remaining "how we got it" code to much cleaner HTML5 + "the ruby way" styles		3. convert remaining "how we got it" code to much cleaner HTML5 + "the ruby way" styles

WikiSysop at 16:40, 20 February 2015

2015-02-20T16:40:15Z

← Older revision		Revision as of 16:40, 20 February 2015
Line 8:		Line 8:

	2. Curarium as an Learning Tools Interoperability (LTI) component for an LTS (e.g, canvas)		2. Curarium as an Learning Tools Interoperability (LTI) component for an LTS (e.g, canvas)
	~~(a)~~ embed individual works into LTS		*embed individual works into LTS
	~~(b)~~ embed tray of images/annotations into LTS		*embed tray of images/annotations into LTS
	~~(c)~~ embed works visualization [whole collection or search results] into LTS		*embed works visualization [whole collection or search results] into LTS

	3. convert remaining "how we got it" code to much cleaner HTML5 + "the ruby way" styles		3. convert remaining "how we got it" code to much cleaner HTML5 + "the ruby way" styles