troughc
commented
1 year ago @IPlouffe we have a workaround for this scenario that you can use until we implement the GROUP feature (see note at end of comment).
The workaround is to give your user the log in information for the GUEST aggregator user profile (ex. you give Caroline Desrochers the log in credentials for the GUEST Ville de Gatineau aggregator). The steps would then be as follows:
- Caroline logs in to the aggregator profile.
- Caroline reviews an event and then sends it for review. Once an event is sent for review, the AGGREGATOR can no longer update the event. IMPORTANT: To stop the aggregator from updating the event at the next import, Caroline MUST send the event for review (saving isn't enough). If Caroline doesn't send her edited event for review her changes would be overwritten by a new import from the aggregator.
- Caroline continues editing and sending events for review.
- Next, you or one of your Editors (maybe Scott) log in to Footlight.
- You review and publish the Ville de Gatineau events from the aggregator that have been SENT FOR REVIEW. The event will no longer be updated by the aggregator and will be published on your website.
This would be the same process for Salle Odysee
NOTE: we plan to do the "Group" feature after we complete the CMS. At that point, you would be able to create groups so that different users in the group could edit events created by other users in the group, i.e. an human user could edit an aggregator user (like salle odyssee and ville de gatineau.
IPlouffe
Once we receive the Salle Odyssée et Ville de Gatineau events from Artdata they are in a draft form. Then only admin can edit them and I would like the organisation to be able to edit their ouwn events coming from Artsdata. Ex. Caroline Desrochers from Ville de Gatineau should be able to add info or modify an events imported from Artsdata. Thanks!