Acceptance Criteria
GIVEN a running server with and API key for a client's VAN account, and an Event in its database:
- WHEN a sysadmin issues a command from a running server:
- THEN the event, all of its rsvps, and all of the people who have RSVP'ed will be sent to VAN (in a format that VAN can read)
- IF POST FAILS:
- THEN the sysadmin will see an error message in the console
- IF POST SUCCEEDS:
- THEN the sysadmin will see a confirmation message
- AND the event's VAN id will be persistend in the DB
- AND the timestamp of the latest successful sync for all records will be recorded in the DB
Implementation notes
- we must sync events & people before attendances, so that we can use the event and people id's when creating new attendances in VAN
- (we could be more fine-grained than this, but we are trying to keep it simple up front...)
Definitions
[stub]
- VAN api is here: https://developers.ngpvan.com/van-api
- the affinity representation of an Event is: @@tdb@@
- the VAN representation of an Event is: @@TBD@@
- the VAN representation of an Attendance is: @@TBD@@@
- the VAN representation of a Person is: @@TBD@@
- sync status will be represented on the
Event model as follows: @@TBD@@
Out of Scope
Acceptance Criteria
GIVEN a running server with and API key for a client's VAN account, and an
Eventin its database:Implementation notes
Definitions
[stub]
Eventmodel as follows: @@TBD@@Out of Scope