Cohort: Difference between revisions

From Berkman Klein Google Summer of Code Wiki
Jump to navigation Jump to search
(New page: We're looking to continue our work on the Cohort CRM project started last year. See [http://cyber.law.harvard.edu/gsoc2009/Cohort_CRM this page] for an overview. [http://github.com/djcp/c...)
 
No edit summary
Line 1: Line 1:
We're looking to continue our work on the Cohort CRM project started last year. See [http://cyber.law.harvard.edu/gsoc2009/Cohort_CRM this page] for an overview. [http://github.com/djcp/cohort The source code repository lives here.]
We're looking to continue our work on the Cohort CRM. It's a tag-based CRM targetted to the needs of small teams in a non-sales environment - so non-profits and/or mission-based organizations looking to track their interactions and relationships with individuals and other organizations. It implements a hierarchical tagging system that allows for free tagging, where those tags live in a hiearchy as well. It's a modern Rails3 application targetted for ruby 1.8.7. The gems it's using include:


Specifically, we're looking to:
*Formtastic
*Sunspot
*A customized version of acts_as_taggable_on
*ancestry


* Create an AJAX API that allows folks to manage slices of their information stored in Cohort. This would allow users to sign up and leave a tag (or collection of tags) automatically. A tag might then propagate to a mailing list or be used to track RSVPs to an event,
It has a rich jquery / ajax interface and is around 15 engineering hours away from an early release. The source code repository lives here ( link to https://github.com/berkmancenter/cohort_ng  ).
* Make a richer de-duplication system,
* Make the application prettier. It's ugly.
* And generally improve the UI and make a better interface for adminstrators working within the system.


It's built in Rails. Your ideas are welcome!
Some possible directions include:
*Build a well modelled custom field system
*Build a rich de-duplication system
*Finish the mailing system from the Rails 2 version of cohort
*Create a lightweight "custom form" system that allows third parties to add and/or remove themselves from tags inside Cohort in a secure fashion.
*Build out a bulletproof suite of tests (rspec?) that test thoroughly against both Postgresql and MySQL

Revision as of 13:36, 4 March 2011

We're looking to continue our work on the Cohort CRM. It's a tag-based CRM targetted to the needs of small teams in a non-sales environment - so non-profits and/or mission-based organizations looking to track their interactions and relationships with individuals and other organizations. It implements a hierarchical tagging system that allows for free tagging, where those tags live in a hiearchy as well. It's a modern Rails3 application targetted for ruby 1.8.7. The gems it's using include:

  • Formtastic
  • Sunspot
  • A customized version of acts_as_taggable_on
  • ancestry

It has a rich jquery / ajax interface and is around 15 engineering hours away from an early release. The source code repository lives here ( link to https://github.com/berkmancenter/cohort_ng ).

Some possible directions include:

  • Build a well modelled custom field system
  • Build a rich de-duplication system
  • Finish the mailing system from the Rails 2 version of cohort
  • Create a lightweight "custom form" system that allows third parties to add and/or remove themselves from tags inside Cohort in a secure fashion.
  • Build out a bulletproof suite of tests (rspec?) that test thoroughly against both Postgresql and MySQL
Retrieved from "http://cyber.harvard.edu/gsoc/?title=Cohort&oldid=121"