Open Questions
- What are the phases of deployment?
- What are CRM best practices?
- How can we prevent people from 'blasting' their lists too much?
- How can we meet the needs of a wide variety of users (ex. some groups need narrow lists, some much wider ones)
- How does the Civi relate to NYCGA.net in terms of single user sign on, etc.
- What are the best workflows for the various use cases?
- Are there additional permissions modules that need to be installed?
- Are there known issues with Civi that make this kind of complexity more difficult to use out of the box?
 SME Requests
We're looking for the following subject matter experts to assist us with this project:
- Database/Load Balancing
- Mobile Interface
- Event Attendance
- Manage Cases
- Building Forms with Dependencies
- Campaign Fundraising Tools
If you're a specialist in any of these fields, please email devin[at]nycga[dot]net.
 Donations and Payments
- mobile event management
- case management
- for housing
- for volunteering
- for resourcers
- front end user and occupation directories
- funding channel administration
- mailing lists for group tags
- permissioned groups
- membership based recurring donations
- fundraising by:
- Occupations (Lists and Permission)
- View/Edit all contacts
- Send Mailings
- Create Campaign Pages (pending authentication)
- Form building (optional)
- Tag Groups (List)
- access profiles with tag
- permsissionable fields
- no export function
- invite to events
- send emails
- filter by participation level (donation history?)
- Working Groups (Components)
- Case Tracking
- Space/Event Management
- Generating Forms
- Case Tracking
- Event Management
- Front End Maintenance
- Account Management
- Case Tracking
- Payment Administration
- Volunteer (Front-End)
- Group Admin (Permission 1)
- View/Edit/Add/Remove Group Contacts (only group contacts)
- Segment group into multiple lists
- Mail full group list
- Mail segmented group lists
- Access Group Templates
- Import but can't export
- Can't see donation information
- Ability to blast "announce list" through email without accessing Civi
- Create events
- Email attendees
- Donor Admin (Permission 2)
- Edit/View/Add/Remove donor profiles of all contacts
- Receive automatically generated daily reports
- General Admin (Permission 3)
- Edit/View/Add/Remove all contacts (no donor profiles)
- Output list of all admins with date of last login
- Configure email limitations (size, frequency, etc) and monitor email blasts
- Upload and modify templates (FB, twitter, pls)
- Permission group admins
- Mail all contacts
List of top twendy
- Volunteers can sign up with info about interests, and get assigned to meaningful opportunities
- Ability to allow admins for any single Working Group to administer multiple lists; but all those lists will not be shared with (peer) admins from other groups.
- Allow admins from each working group to mail at least one, but maybe multiple defined lists, as specified
- Have mandatory email template for each admin that cannot be removed or edited.
- Email blast functionality for each working group that includes mandatory template, privacy for groups, inability to export list, and smart groups that add people to lists automatically based on certain criteria.
- For each working group, thre shall be a 'main announcement list' that is comprised of nycga.net membership, upload/migration from other sources, signup page, and manual entry. It shall be possible to message this list by sending an email to a certain address from a certain account, so that access to civi isn't necessary anymore.
- Information about donors shall be hidden from most admins. This includes whether or not someone is a donor, donation amount, donation records, and which donation appeals they may have responded to (which might appear as tags)
- Donations made via a page will trigger an automated email with information about the donation. A report will be emailed automatically to accounting with each day's total of online donations.
- Event RSVP pages that trigger automated responses.
- Email templates that include links to 'official' FB, twitter accounts
- Ability to print list of all admins together with date of last login, and description of permissions.
- Prevent emails from going out if they are above a certain memory size, to prevent inexperiences users from using massive graphics.
- Automate the process of become an admin with a form, drop down menu, followed by an approval on the back end.
Messaging Volunteers with Specific Skills
- Tech Ops tells us they need Drupal developers for a hackathon style final push on, say, FGA. We need to be able to sort a list of volunteers who are in NYC and have Drupal experience. We would contact only those people.
- You'd do a custom search, probably a proximity search, with people tagged with the terms, 'web design', 'drupal', etc and then add them to your on the fly group. Once they're in your group/list you'd use the mass mailing tool to send out a message to the group with whatever subject line/info you'd like. When you're done, you could keep the contacts in the group for future mailings or clear it to do another on the fly mailing. You can also save searches which would allow you to see an update list of folks with the criteria for which you've searched so you'll be able to add them all to a group/list in two clicks.
Messages Volunteers with Specific Availability
- Kitchen tells us they need 5 people to help serve food and 2 people to transport it to different locations, at lunchtime on a certain day. We would need to sort a list of people who have daytime availability, send an email asking them for help, schedule them when they respond and then maybe give them a reminder/confirmation call or email the night before they are scheduled. We would also like to be able to confirm whether people actually show up for shifts they are scheduled for, and mark that in the system somehow.
Messaging Volunteers with Specific Experiences
- Finance needs people for data entry. It can be any time, but they need to come to the office because we cant be emailing the info the be entered around, so we need a list of people who are in NYC, and when they email and respond whether they can do it we need to follow up with them about when, and put it in some sort of scheduling system so that we can make sure that whoever is point person for the project can be sure to meet and train them at that time.
Message People Who Attended a Specific Event
- We want to pull the list of people who volunteered at a certain event so that we can send them a 'thank you for helping' email, or a list of people who have ever volunteered at an event so that we can invite them to a volunteers night out.
Occupy Student Debt
"Our group is collecting pledges from student debtors who agree to stop paying their student loans after one million others do the same. We also have two other pledges for faculty and non-debtors who want to support debtors in this action. In addition to the pledgers (we have almost 5,000 in total at this point), we also have our NYC working group which consists of dozens of people. A much smaller number, however, actually runs the campaign on a daily basis. I am interested in exploring ways to improve communication for our campaign. We want to allow everyone to participate on a more or less equal footing even though some people have much more time to give than others. We also want to engage the people across the country who have signed pledges already. Of course, we need to be able to mass email. But I'm thinking of something like a social network for student debtors. For example, if you sign the pledge and you live in Arizona, we would like to provide you with a way to find other people who live near you who have also signed the pledge. That way we can grow our campaign from the working group in NYC to a series of working groups around the country. We could all congregate in a central meeting place online to coordinate. We are really interested in dumping clunky google email lists and docs."
- Threshold pledging
- Find and connect with nearby pledgers
- Central online meeting place
- Statement of Autonomy
- Rachel and Amy are writing content.
- Olivia is creating event lists.
- Ravi is helping groups organize volunteers.
- Charles is coordinating and helping with content.
- David Judd is helping set up campaign components.
- Dana is coordinating with Civi developers.
- Devin is helping incubate a news team for OWS.net that will provide news items.