Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update README - Project Audience and Project Goal #11

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update README - Project Audience and Project Goal #11

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,6 +25,7 @@ We aim to build best-fit Event Management architecture and features within the N

Nonprofits have myriad needs related to Event Management, and continue to reinvent the wheel locally when creating their architecture, often needing to make revisions or complex work-arounds in order to connect to leading event management platforms that connect to Salesforce or which they aim to extract data from.

### Project Audience
Our product is intended for nonprofit organizations with one-time or templated/recurring events with complexity that includes:
* Event Seating/Table Seating considerations and capacity per seat type/seat inventory
* Event role tracking for individuals that are not in the "audience" of the event
Expand All @@ -45,6 +46,7 @@ Our product is intended for nonprofit organizations with one-time or templated/r
* Task management for event management
* Outbound communications to participants records

### Project Goals
While our current goals include just gelling on a best-fit schema and common fields, our future goals include:
* revision of these objects and architecture to accomodate more common data points or "add-in" objects than anticipated
* data sets to help users leverage NPSP Data Import Batch architecture/features for loading data into the schema
Expand Down