Curricle - Revision history

BerkmanSysop at 22:11, 9 March 2017

2017-03-09T22:11:53Z

← Older revision		Revision as of 22:11, 9 March 2017
Line 2:		Line 2:

	The core of the project will take the form of a comprehensive experiment employing course-listing data from the Harvard Registrar’s office and Harvard Archive. These data will produce aggregate visualizations that reveal clusters, connections, cross-disciplinary themes and threads. The aim will be to establish what sorts of approaches yield the most interesting new ways to see, experience, and explore the curriculum with an eye to developing a platform that would leverage the power of curricular data to tell stories that help to orient, guide, and shape student choices in richer, more interactive and imaginative ways.		The core of the project will take the form of a comprehensive experiment employing course-listing data from the Harvard Registrar’s office and Harvard Archive. These data will produce aggregate visualizations that reveal clusters, connections, cross-disciplinary themes and threads. The aim will be to establish what sorts of approaches yield the most interesting new ways to see, experience, and explore the curriculum with an eye to developing a platform that would leverage the power of curricular data to tell stories that help to orient, guide, and shape student choices in richer, more interactive and imaginative ways.

			Curricle demo site: http://curricle.dev.berkmancenter.org/

			'''Login instructions:''' You can make up a username and password and it will create an account for you that will save any courses you favorite.


	==Potential projects for Summer 2017==		==Potential projects for Summer 2017==

BerkmanSysop: /* User accounts and workflow */

2017-03-07T18:31:33Z

User accounts and workflow

← Older revision		Revision as of 18:31, 7 March 2017
Line 7:		Line 7:

	===User accounts and workflow===		===User accounts and workflow===
	# Problem statement. Curricle’s primary user base will be students seeking to assemble their class schedules for an upcoming semester. They need to be able to easily organize (and sort) classes they’re interested in. We’re looking for both the obvious solutions and the non-obvious, the functional solutions as well as the unconventional. As much as this is an exercise in practicality, it should also be considered as creative and exploratory.		==== Problem statement.====
	# Development tasks.		Curricle’s primary user base will be students seeking to assemble their class schedules for an upcoming semester. They need to be able to easily organize (and sort) classes they’re interested in. We’re looking for both the obvious solutions and the non-obvious, the functional solutions as well as the unconventional. As much as this is an exercise in practicality, it should also be considered as creative and exploratory.
	## As it’s developed now, users have a single tray of interesting courses from which they can toggle courses on and off to draft a semester schedule or multi-year path. The relationship between a tray and a path could benefit from additional clarification (e.g. should you be able to save a path -- or multiple paths -- independently from a tray? Should you be able to create paths that draw from multiple trays?)		==== Development tasks.====
	## User dashboard -- tray(s), courses i’ve taken		# As it’s developed now, users have a single tray of interesting courses from which they can toggle courses on and off to draft a semester schedule or multi-year path. The relationship between a tray and a path could benefit from additional clarification (e.g. should you be able to save a path -- or multiple paths -- independently from a tray? Should you be able to create paths that draw from multiple trays?)
	## Tag / color code / annotate courses within a tray		# User dashboard -- tray(s), courses i’ve taken
	## Multiple trays with names		# Tag / color code / annotate courses within a tray
	## Additional useful information that might be available from a user’s dashboard? E.g. goals, research interests.		# Multiple trays with names
	## Create a landing page to orient users to the platform. This would: give context for both advising and historical modes; provide a path for Harvard students to log in; provide a path for non-Harvard students to get a sense of the site without full access.		# Additional useful information that might be available from a user’s dashboard? E.g. goals, research interests.
	## Differentiate between at least two types of users: students (basic privileges, can view courses, create trays and paths) and professors (additional privileges to add information to their own courses).		# Create a landing page to orient users to the platform. This would: give context for both advising and historical modes; provide a path for Harvard students to log in; provide a path for non-Harvard students to get a sense of the site without full access.
	## How can we create more internal coherence between the search and tray views? One approach we’ve discussed is an accordion (something like this oriented vertically).		# Differentiate between at least two types of users: students (basic privileges, can view courses, create trays and paths) and professors (additional privileges to add information to their own courses).
			# How can we create more internal coherence between the search and tray views? One approach we’ve discussed is an accordion (something like this oriented vertically).

	===Search result visualization===		===Search result visualization===

BerkmanSysop at 18:30, 7 March 2017

2017-03-07T18:30:21Z

← Older revision		Revision as of 18:30, 7 March 2017
Line 3:		Line 3:
	The core of the project will take the form of a comprehensive experiment employing course-listing data from the Harvard Registrar’s office and Harvard Archive. These data will produce aggregate visualizations that reveal clusters, connections, cross-disciplinary themes and threads. The aim will be to establish what sorts of approaches yield the most interesting new ways to see, experience, and explore the curriculum with an eye to developing a platform that would leverage the power of curricular data to tell stories that help to orient, guide, and shape student choices in richer, more interactive and imaginative ways.		The core of the project will take the form of a comprehensive experiment employing course-listing data from the Harvard Registrar’s office and Harvard Archive. These data will produce aggregate visualizations that reveal clusters, connections, cross-disciplinary themes and threads. The aim will be to establish what sorts of approaches yield the most interesting new ways to see, experience, and explore the curriculum with an eye to developing a platform that would leverage the power of curricular data to tell stories that help to orient, guide, and shape student choices in richer, more interactive and imaginative ways.

	Potential projects for Summer 2017		==Potential projects for Summer 2017==


	User accounts and workflow		===User accounts and workflow===
	Problem statement. Curricle’s primary user base will be students seeking to assemble their class schedules for an upcoming semester. They need to be able to easily organize (and sort) classes they’re interested in. We’re looking for both the obvious solutions and the non-obvious, the functional solutions as well as the unconventional. As much as this is an exercise in practicality, it should also be considered as creative and exploratory.		# Problem statement. Curricle’s primary user base will be students seeking to assemble their class schedules for an upcoming semester. They need to be able to easily organize (and sort) classes they’re interested in. We’re looking for both the obvious solutions and the non-obvious, the functional solutions as well as the unconventional. As much as this is an exercise in practicality, it should also be considered as creative and exploratory.
	Development tasks.		# Development tasks.
	As it’s developed now, users have a single tray of interesting courses from which they can toggle courses on and off to draft a semester schedule or multi-year path. The relationship between a tray and a path could benefit from additional clarification (e.g. should you be able to save a path -- or multiple paths -- independently from a tray? Should you be able to create paths that draw from multiple trays?)		## As it’s developed now, users have a single tray of interesting courses from which they can toggle courses on and off to draft a semester schedule or multi-year path. The relationship between a tray and a path could benefit from additional clarification (e.g. should you be able to save a path -- or multiple paths -- independently from a tray? Should you be able to create paths that draw from multiple trays?)
	User dashboard -- tray(s), courses i’ve taken		## User dashboard -- tray(s), courses i’ve taken
	Tag / color code / annotate courses within a tray		## Tag / color code / annotate courses within a tray
	Multiple trays with names		## Multiple trays with names
	Additional useful information that might be available from a user’s dashboard? E.g. goals, research interests.		## Additional useful information that might be available from a user’s dashboard? E.g. goals, research interests.
	Create a landing page to orient users to the platform. This would: give context for both advising and historical modes; provide a path for Harvard students to log in; provide a path for non-Harvard students to get a sense of the site without full access.		## Create a landing page to orient users to the platform. This would: give context for both advising and historical modes; provide a path for Harvard students to log in; provide a path for non-Harvard students to get a sense of the site without full access.
	Differentiate between at least two types of users: students (basic privileges, can view courses, create trays and paths) and professors (additional privileges to add information to their own courses).		## Differentiate between at least two types of users: students (basic privileges, can view courses, create trays and paths) and professors (additional privileges to add information to their own courses).
	How can we create more internal coherence between the search and tray views? One approach we’ve discussed is an accordion (something like this oriented vertically).		## How can we create more internal coherence between the search and tray views? One approach we’ve discussed is an accordion (something like this oriented vertically).

	Search result visualization		===Search result visualization===
	Problem statement. One of Curricle’s main goals in its advising mode is to connect students with relevant classes the cross disciplinary boundaries (e.g. returning relevant philosophy courses to chemistry students). One way that we’ve approached this is through returning search results as both a traditional list of items as well as highlighting them within a visualization of the entire curriculum. In this way, students can explore both the macro and the micro simultaneously; ideally the holistic snapshot of the curriculum that the visualization provides will encourage broader and unexpected exploration.		====Problem statement. ====
			One of Curricle’s main goals in its advising mode is to connect students with relevant classes the cross disciplinary boundaries (e.g. returning relevant philosophy courses to chemistry students). One way that we’ve approached this is through returning search results as both a traditional list of items as well as highlighting them within a visualization of the entire curriculum. In this way, students can explore both the macro and the micro simultaneously; ideally the holistic snapshot of the curriculum that the visualization provides will encourage broader and unexpected exploration.

	===Development tasks.===		====Development tasks.====
	Design and implement multiple views for visualizing a set of search results within the context of the larger curriculum. Visualizations should be designed to support the search for relevant courses across departments. Emphasizing (invisible, unexpected) connections between courses is one approach.		# Design and implement multiple views for visualizing a set of search results within the context of the larger curriculum. Visualizations should be designed to support the search for relevant courses across departments. Emphasizing (invisible, unexpected) connections between courses is one approach.
	Develop an interface so that users can toggle between visualizations and adjust any necessary fields.		# Develop an interface so that users can toggle between visualizations and adjust any necessary fields.

BerkmanSysop at 18:19, 7 March 2017

2017-03-07T18:19:46Z

@@ Line 3: / Line 3: @@
 The core of the project will take the form of a comprehensive experiment employing course-listing data from the Harvard Registrar’s office and Harvard Archive. These data will produce aggregate visualizations that reveal clusters, connections, cross-disciplinary themes and threads. The aim will be to establish what sorts of approaches yield the most interesting new ways to see, experience, and explore the curriculum with an eye to developing a platform that would leverage the power of curricular data to tell stories that help to orient, guide, and shape student choices in richer, more interactive and imaginative ways.
-====Potential summer projects:====
+Potential projects for Summer 2017
-====Requirements:====
+User accounts and workflow
-* Experience with data visualization
+Problem statement. Curricle’s primary user base will be students seeking to assemble their class schedules for an upcoming semester. They need to be able to easily organize (and sort) classes they’re interested in. We’re looking for both the obvious solutions and the non-obvious, the functional solutions as well as the unconventional. As much as this is an exercise in practicality, it should also be considered as creative and exploratory.
-'''Mentor:''' Jessica Yurkofsky ([mailto:jessica@metalab.harvard.edu jessica@metalab.harvard.edu])
+Search result visualization

BerkmanSysop: Created page with "Curricle aims at developing a lively, interactive, playful mode of navigating curricular programming and choices not as a catalogue but as a landscape of intersecting paths; n..."

2016-02-19T16:34:06Z

Created page with "Curricle aims at developing a lively, interactive, playful mode of navigating curricular programming and choices not as a catalogue but as a landscape of intersecting paths; n..."

New page

Curricle aims at developing a lively, interactive, playful mode of navigating curricular programming and choices not as a catalogue but as a landscape of intersecting paths; not as an inventory of single items grouped into disciplinary pages and lists, but instead as a unified whole, a dense fabric woven together out of interdisciplinary connections.

The core of the project will take the form of a comprehensive experiment employing course-listing data from the Harvard Registrar’s office and Harvard Archive. These data will produce aggregate visualizations that reveal clusters, connections, cross-disciplinary themes and threads. The aim will be to establish what sorts of approaches yield the most interesting new ways to see, experience, and explore the curriculum with an eye to developing a platform that would leverage the power of curricular data to tell stories that help to orient, guide, and shape student choices in richer, more interactive and imaginative ways.

====Potential summer projects:====
* Develop schema to integrate archival and current data
* Develop interactive visualizations of curricula and their connections
* Explore approaches to recommending next courses in a sequence (e.g. based on past choices, interests, etc)

====Technologies involved:====
* Javascript / HTML / CSS
* Open to developers working with their preferred technologies as long as process and findings are well-documented

====Requirements:====
* Experience with data visualization

'''Mentor:''' Jessica Yurkofsky ([mailto:jessica@metalab.harvard.edu jessica@metalab.harvard.edu])