Summary: Data dashboards - Revision history

Jeddcohen at 22:34, 10 June 2016

2016-06-10T22:34:41Z

← Older revision		Revision as of 22:34, 10 June 2016
Line 1:		Line 1:
	''Written by Mica Pollock, Jedd Cohen~~, and Josh Wairi~~ for the dashboard project, with initial dashboard development by Somerville technologist Seth Woodworth and next development for piloting by David Lord of San Diego		''Written by Mica Pollock and Jedd Cohen for the dashboard project, with initial dashboard development by Somerville technologist Seth Woodworth and next development for piloting by David Lord of San Diego

	Click here for the '''[[Overview and key findings: Data dashboards\|<font color=#0000FF>Overview and key findings</font>]] '''on this project; click here for the '''[[Expanded story: Data dashboards\|<font color=#0000FF>Expanded story</font>]] '''on this project.		Click here for the '''[[Overview and key findings: Data dashboards\|<font color=#0000FF>Overview and key findings</font>]] '''on this project; click here for the '''[[Expanded story: Data dashboards\|<font color=#0000FF>Expanded story</font>]] '''on this project.

Jeddcohen at 22:29, 10 June 2016

2016-06-10T22:29:12Z

← Older revision		Revision as of 22:29, 10 June 2016
Line 56:		Line 56:
	Contact point people for the dashboard project directly at:		Contact point people for the dashboard project directly at:

	Jedd Cohen (jic378@mail.harvard.edu~~); Josh Wairi, teacher co-designer (jwairi@k12.somerville.ma.us~~); Mica Pollock (mica.pollock@gmail.com)		Jedd Cohen (jic378@mail.harvard.edu); Mica Pollock (mica.pollock@gmail.com)

	Click here for the '''[[Overview and key findings: Data dashboards\|<font color=#0000FF>Overview and key findings</font>]] '''on this project; click here for the '''[[Expanded story: Data dashboards\|<font color=#0000FF>Expanded story</font>]] '''on this project.		Click here for the '''[[Overview and key findings: Data dashboards\|<font color=#0000FF>Overview and key findings</font>]] '''on this project; click here for the '''[[Expanded story: Data dashboards\|<font color=#0000FF>Expanded story</font>]] '''on this project.

Micapollock at 03:50, 20 July 2012

2012-07-20T03:50:52Z

← Older revision		Revision as of 03:50, 20 July 2012
Line 1:		Line 1:
	''Written by Mica Pollock, Jedd Cohen, and Josh Wairi for the dashboard project, with initial dashboard development by Somerville technologist Seth Woodworth and ~~further~~ development for piloting by David Lord of San Diego		''Written by Mica Pollock, Jedd Cohen, and Josh Wairi for the dashboard project, with initial dashboard development by Somerville technologist Seth Woodworth and next development for piloting by David Lord of San Diego

	Click here for the '''[[Overview and key findings: Data dashboards\|<font color=#0000FF>Overview and key findings</font>]] '''on this project; click here for the '''[[Expanded story: Data dashboards\|<font color=#0000FF>Expanded story</font>]] '''on this project.		Click here for the '''[[Overview and key findings: Data dashboards\|<font color=#0000FF>Overview and key findings</font>]] '''on this project; click here for the '''[[Expanded story: Data dashboards\|<font color=#0000FF>Expanded story</font>]] '''on this project.

Micapollock at 03:48, 20 July 2012

2012-07-20T03:48:54Z

← Older revision		Revision as of 03:48, 20 July 2012
Line 1:		Line 1:
	''Written by Mica Pollock, Jedd Cohen, and Josh Wairi for the dashboard project, with initial dashboard development by Somerville technologist Seth Woodworth ~~with Evan Burchard,~~ and further development for piloting by David Lord of San Diego		''Written by Mica Pollock, Jedd Cohen, and Josh Wairi for the dashboard project, with initial dashboard development by Somerville technologist Seth Woodworth and further development for piloting by David Lord of San Diego

	Click here for the '''[[Overview and key findings: Data dashboards\|<font color=#0000FF>Overview and key findings</font>]] '''on this project; click here for the '''[[Expanded story: Data dashboards\|<font color=#0000FF>Expanded story</font>]] '''on this project.		Click here for the '''[[Overview and key findings: Data dashboards\|<font color=#0000FF>Overview and key findings</font>]] '''on this project; click here for the '''[[Expanded story: Data dashboards\|<font color=#0000FF>Expanded story</font>]] '''on this project.

Micapollock: /* What communication challenges did this project address? */

2012-07-16T01:41:01Z

What communication challenges did this project address?

← Older revision		Revision as of 01:41, 16 July 2012
Line 17:		Line 17:
	[[Image:IndivDashSummary.jpg\|IndivDashSummary.jpg]]		[[Image:IndivDashSummary.jpg\|IndivDashSummary.jpg]]

	On the OneVille Project, the dashboard was one of six subprojects and our first effort to create a tech tool totally from scratch with young local technologists. Development with our Somerville colleagues took more budgeted hours than any of us originally anticipated, and after some excellent pro bono work by David Lord of San Diego, by Spring 2012 we were about 60 development hours from pilot-readiness on the admin and teacher views (and roughly 300 hours from pilot-readiness on the individual view). Remaining work: to finish tweaking the final programming "tubes" linking the dashboard to Somerville's Student Information System. The "code" for all of the dashboard views is linked on the '''[[Overview and key findings: Data dashboards\|<font color=#0000FF>Overview and key findings</font>]] ''' page and to date is the core "product" of this pilot. Open source code also means that any developer anywhere can develop on the product we made. For example, community youth-serving and university outreach orgs needing to view and sort youth- and student-related data have expressed interest in a similar free product developed for their specific needs. See the '''[[Overview and key findings: Data dashboards\|<font color=#0000FF>Overview and key findings</font>]] ''' and '''[[Expanded story: Data dashboards\|<font color=#0000FF>Expanded story</font>]] ''' pages for the full story of developing this tool.		On the OneVille Project, the dashboard was one of six subprojects and our first effort to create a tech tool totally from scratch with young local technologists. Development with our Somerville colleagues took more budgeted hours than any of us originally anticipated, and after some excellent pro bono work by David Lord of San Diego, by Spring 2012 we were about 60 development hours from pilot-readiness on the admin and teacher views (and roughly 300 hours from pilot-readiness on the individual view). Remaining work: to finish tweaking the final programming "tubes" linking the dashboard to Somerville's Student Information System so that data could be displayed 100% glitch-free. The "code" for all of the dashboard views is linked on the '''[[Overview and key findings: Data dashboards\|<font color=#0000FF>Overview and key findings</font>]] ''' page and to date is the core "product" of this pilot. Open source code also means that any developer anywhere can develop on the product we made. For example, community youth-serving and university outreach orgs needing to view and sort youth- and student-related data have expressed interest in a similar free product developed for their specific needs. See the '''[[Overview and key findings: Data dashboards\|<font color=#0000FF>Overview and key findings</font>]] ''' and '''[[Expanded story: Data dashboards\|<font color=#0000FF>Expanded story</font>]] ''' pages for the full story of developing this tool.

	===Why is it important to improve communications?===		===Why is it important to improve communications?===

Micapollock: /* What communication challenges did this project address? */

2012-07-16T01:34:13Z

What communication challenges did this project address?

← Older revision		Revision as of 01:34, 16 July 2012
Line 17:		Line 17:
	[[Image:IndivDashSummary.jpg\|IndivDashSummary.jpg]]		[[Image:IndivDashSummary.jpg\|IndivDashSummary.jpg]]

	On the OneVille Project, the dashboard was one of six subprojects and our first effort to create a tech tool totally from scratch with young local technologists. Development with our Somerville colleagues took more budgeted hours than any of us originally anticipated, and after some excellent pro bono work by David Lord of San Diego, by Spring 2012 we were about 60 development hours from pilot-readiness on the admin and teacher views (and roughly 300 hours from pilot-readiness on the individual view). Remaining work: to finish tweaking the final programming "tubes" linking the dashboard to Somerville's Student Information System. The "code" for all of the dashboard views is linked ~~below~~ and to date is the core "product" of this pilot. Open source code also means that any developer anywhere can develop on the product we made. For example, community youth-serving and university outreach orgs needing to view and sort youth- and student-related data have expressed interest in a similar free product developed for their specific needs. See the '''[[Overview and key findings: Data dashboards\|<font color=#0000FF>Overview and key findings</font>]] ''' and '''[[Expanded story: Data dashboards\|<font color=#0000FF>Expanded story</font>]] ''' pages for the full story of developing this tool.		On the OneVille Project, the dashboard was one of six subprojects and our first effort to create a tech tool totally from scratch with young local technologists. Development with our Somerville colleagues took more budgeted hours than any of us originally anticipated, and after some excellent pro bono work by David Lord of San Diego, by Spring 2012 we were about 60 development hours from pilot-readiness on the admin and teacher views (and roughly 300 hours from pilot-readiness on the individual view). Remaining work: to finish tweaking the final programming "tubes" linking the dashboard to Somerville's Student Information System. The "code" for all of the dashboard views is linked on the '''[[Overview and key findings: Data dashboards\|<font color=#0000FF>Overview and key findings</font>]] ''' page and to date is the core "product" of this pilot. Open source code also means that any developer anywhere can develop on the product we made. For example, community youth-serving and university outreach orgs needing to view and sort youth- and student-related data have expressed interest in a similar free product developed for their specific needs. See the '''[[Overview and key findings: Data dashboards\|<font color=#0000FF>Overview and key findings</font>]] ''' and '''[[Expanded story: Data dashboards\|<font color=#0000FF>Expanded story</font>]] ''' pages for the full story of developing this tool.

	===Why is it important to improve communications?===		===Why is it important to improve communications?===

Micapollock: /* The Next Layer: Connecting to Folks Doing Similar Work in Other Communities. */

2012-07-16T01:33:31Z

The Next Layer: Connecting to Folks Doing Similar Work in Other Communities.

← Older revision		Revision as of 01:33, 16 July 2012
Line 56:		Line 56:
	Contact point people for the dashboard project directly at:		Contact point people for the dashboard project directly at:

	Jedd Cohen (jic378@mail.harvard.edu); Josh Wairi (jwairi@k12.somerville.ma.us); Mica Pollock (mica.pollock@gmail.com)		Jedd Cohen (jic378@mail.harvard.edu); Josh Wairi, teacher co-designer (jwairi@k12.somerville.ma.us); Mica Pollock (mica.pollock@gmail.com)

	Click here for the '''[[Overview and key findings: Data dashboards\|<font color=#0000FF>Overview and key findings</font>]] '''on this project; click here for the '''[[Expanded story: Data dashboards\|<font color=#0000FF>Expanded story</font>]] '''on this project.		Click here for the '''[[Overview and key findings: Data dashboards\|<font color=#0000FF>Overview and key findings</font>]] '''on this project; click here for the '''[[Expanded story: Data dashboards\|<font color=#0000FF>Expanded story</font>]] '''on this project.

Micapollock: /* How do you know if your school could improve communication? */

2012-07-16T01:32:56Z

How do you know if your school could improve communication?

← Older revision		Revision as of 01:32, 16 July 2012
Line 39:		Line 39:
	:➢ To support young people, what “data” should show up on any data display, and why?		:➢ To support young people, what “data” should show up on any data display, and why?
	:➢ How does your school make data on students visible to school administrators, classroom teachers, and afterschool providers? And how about parents? Which necessary data is readily available, and which isn't?		:➢ How does your school make data on students visible to school administrators, classroom teachers, and afterschool providers? And how about parents? Which necessary data is readily available, and which isn't?
	:➢ What infrastructure would support actual conversations ~~ABOUT~~ "data," between the people who share young people?		:➢ What infrastructure would support actual conversations ''about'' "data," between the people who share young people's lives?
	:➢ Which conversations about data should happen in person and which could be supported online? Could you do an experiment to test which works for what?		:➢ Which conversations about data should happen in person and which could be supported online? Could you do an experiment to test which works for what?
	:➢ What data isn’t found in any “student information system” but should still be known?		:➢ What data isn’t found in any “student information system” but should still be known? By whom?
	:➢ Is your district spending tons of money on data display tools to get basic data in front of people?		:➢ Is your district spending tons of money on data display tools to get basic data in front of people?
	:➢ If so, how might low cost tech development or professional development on the tools you already have support such information-sharing?		:➢ If so, how might low cost tech development or professional development on the tools you already have support such information-sharing?

Micapollock: /* What communication challenges did this project address? */

2012-07-16T01:30:14Z

What communication challenges did this project address?

← Older revision		Revision as of 01:30, 16 July 2012
Line 17:		Line 17:
	[[Image:IndivDashSummary.jpg\|IndivDashSummary.jpg]]		[[Image:IndivDashSummary.jpg\|IndivDashSummary.jpg]]

	On the OneVille Project, the dashboard was one of six subprojects and our first effort to create a tech tool totally from scratch with young local technologists. Development with our Somerville colleagues took more budgeted hours than any of us originally anticipated, and after some excellent pro bono work by David Lord of San Diego, by Spring 2012 we were about 60 development hours from pilot-readiness on the admin and teacher views (and roughly 300 hours from pilot-readiness on the individual view). Remaining work: to finish tweaking the final programming "tubes" linking the dashboard to Somerville's Student Information System. The "code" for all of the dashboard views is linked below and to date is the core "product" of this pilot. Open source code also means that any developer anywhere can develop on the product we made. For example, community youth-serving and university outreach orgs needing to view and sort youth- and student-related data have expressed interest in a similar free product developed for their specific needs. See for the full story of developing this tool.		On the OneVille Project, the dashboard was one of six subprojects and our first effort to create a tech tool totally from scratch with young local technologists. Development with our Somerville colleagues took more budgeted hours than any of us originally anticipated, and after some excellent pro bono work by David Lord of San Diego, by Spring 2012 we were about 60 development hours from pilot-readiness on the admin and teacher views (and roughly 300 hours from pilot-readiness on the individual view). Remaining work: to finish tweaking the final programming "tubes" linking the dashboard to Somerville's Student Information System. The "code" for all of the dashboard views is linked below and to date is the core "product" of this pilot. Open source code also means that any developer anywhere can develop on the product we made. For example, community youth-serving and university outreach orgs needing to view and sort youth- and student-related data have expressed interest in a similar free product developed for their specific needs. See the '''[[Overview and key findings: Data dashboards\|<font color=#0000FF>Overview and key findings</font>]] ''' and '''[[Expanded story: Data dashboards\|<font color=#0000FF>Expanded story</font>]] ''' pages for the full story of developing this tool.

	===Why is it important to improve communications?===		===Why is it important to improve communications?===

Micapollock: /* What communication challenges did this project address? */

2012-07-16T01:29:07Z

What communication challenges did this project address?

← Older revision		Revision as of 01:29, 16 July 2012
Line 17:		Line 17:
	[[Image:IndivDashSummary.jpg\|IndivDashSummary.jpg]]		[[Image:IndivDashSummary.jpg\|IndivDashSummary.jpg]]

	On the OneVille Project, the dashboard was one of six subprojects and our first effort to create a tech tool totally from scratch. Development with our Somerville colleagues took more budgeted hours than originally anticipated, and after some excellent pro bono work by David Lord of San Diego by Spring 2012 we were about 60 development hours from pilot-readiness on the admin and teacher views (and ~~xxx~~ hours from pilot-readiness on the individual view)~~, with remaining~~ work ~~being~~ to finish tweaking the final "tubes" linking the dashboard to Somerville's Student Information System. The "code" for all of the ~~dashboards~~ is linked below and to date is the core "product" of this pilot. Open source code also means that any developer anywhere can develop on the product we made~~, for next uses~~. For example, community youth-serving or university outreach orgs needing to view and sort data have expressed interest in a similar product developed for their specific needs.		On the OneVille Project, the dashboard was one of six subprojects and our first effort to create a tech tool totally from scratch with young local technologists. Development with our Somerville colleagues took more budgeted hours than any of us originally anticipated, and after some excellent pro bono work by David Lord of San Diego, by Spring 2012 we were about 60 development hours from pilot-readiness on the admin and teacher views (and roughly 300 hours from pilot-readiness on the individual view). Remaining work: to finish tweaking the final programming "tubes" linking the dashboard to Somerville's Student Information System. The "code" for all of the dashboard views is linked below and to date is the core "product" of this pilot. Open source code also means that any developer anywhere can develop on the product we made. For example, community youth-serving and university outreach orgs needing to view and sort youth- and student-related data have expressed interest in a similar free product developed for their specific needs. See for the full story of developing this tool.

	===Why is it important to improve communications?===		===Why is it important to improve communications?===