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.

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

Handle co-organized but non-publicized special events on Mobilize #76

Closed
brotskydotcom opened this issue Nov 28, 2020 · 1 comment · Fixed by #77
Closed

Handle co-organized but non-publicized special events on Mobilize #76

brotskydotcom opened this issue Nov 28, 2020 · 1 comment · Fixed by #77
Assignees
Labels
enhancement New feature or request

Comments

@brotskydotcom
Copy link
Owner

Occasionally, there are Mobilize events that are co-organized by STV folks but which are not from publicized partners of STV. In this case, the event data will be exported to a separate spreadsheet which doesn't include the other Mobilize events, so importing that spreadsheet will wipe out all the Mobilize events. (This, in turn, will wipe out all the event links for the shifts for those events.) So we need two enhancements:

  1. Provide a way of marking an event as one of these special events in the imported spreadsheet, and
  2. If the spreadsheet without marking is accidentally imported, find a way of force re-linking all the shifts to their correct events once those have been re-imported.
@brotskydotcom brotskydotcom added the enhancement New feature or request label Nov 28, 2020
@brotskydotcom brotskydotcom self-assigned this Nov 28, 2020
@brotskydotcom
Copy link
Owner Author

brotskydotcom commented Nov 28, 2020

So here's how the solution works:

  1. To mark an event as special, change its "visibility" field in the spreadsheet to be PERMANENT. This will come in as an "Event Visibility*" of PERMANENT on the Airtable side, and the import containing this event will not delete any events on the Airtable side. Also, the events marked in this way will not be deleted during a regular event import run.
  2. To force all the shifts to be re-updated when imported, do a shift import with the environment variable FORCE_SHIFT_UPDATES set to a truthy string value.

brotskydotcom added a commit that referenced this issue Nov 28, 2020
This fixes #76.  See the issue for details.
brotskydotcom added a commit that referenced this issue Nov 28, 2020
* Handle co-organized but non-promoted events.

This fixes #76.  See the issue for details.

* Remove unintended change.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant