A quick jot down draft/draft. Please expect this page to change soon, and become far more detailed/formal after a few more discussions with project participants)
This is connected to threads in GDO CiviCRM/Education group and a CiviCRM Forum.
Here is a quick draft use-case:
Users:
- Site adminsitrators
- Parents
- Taxpayers (people who pay taxes but do not have students in school)
Parent Use Cases:
- Share date/knowledge information (enabled via http://drupal.org/project/og, http://drupal.org/project/wikitools, custom content types http://drupal.org/project/cck, http://drupal.org/project/userlinks, and taxonomy)
- Organize events (presumably enabled via CiviEvent)
- Organize letter-writing/email writing/calling, or other political action campaigns (enabled possibly by http://drupal.org/project/signit module, http://drupal.org/project/civinodes, CiviMail, other ?? still researching, suggestions appreciated, will be rolled into future drafts of this document and shared)
- Collect donation moneys (presumably enabled by CiviContribute)
- Participate in collective decision making about group activities (probably enabled via http://drupal.org/project/advpoll and http://aboutus.org/ConsensusPolling method)
Site Administrator Use Cases:
- Monitor site content according rules/guidlines
- Assist users with technical issues.
Site admin responsibilities enabled by Drupal's built in core tools, possible add-on modules (to be detailed in new draft)
Taxpayer Use Cases:
- Share date/knowledge information (enabled via same as above)
- Organize events (presumably enabled via CiviEvent)
- Organize letter-writing/email writing/calling, or other political action campaigns (enabled by same as above)
Open questions
(some of which will be answered upon testing CiviCRM with Drupal)
- How will Drupal's Built in profile system work with the personal data collected via CiviCRM? (it's possible we might use Advanced Profile, with Panels/Views, too)