In 2018, we asked Keen Design to take a close look at the collaboration flows we need to support in the SCZ. After interviewing a number of participants, they designed a number of flows that cover most of the use cases we would like to support in de SCZ. This design was presented during a meeting on December 18th (meeting notes). The scenarios that were detailed in a design:
Scenario 8 - Create collaboration
(PDF-version in case the online scenario's don't work: scenario1-login.pdf, scenario2-request-access.pdf, scenario3-accept-invitation.pdf, scenario4-add-autorisations.pdf, scenario5-granting-access.pdf, scenario6-CO-sends-invitation.pdf, scenario7-view-profile.pdf, Scenario8-Create-Collaboration.pdf, scenario9-Accept admin-rights.pdf)
Keen did a presentation on their process and findings on dec 19th 2018 (sheets).
Based on these flows, the (preliminary) data model is as follows:
Which evolved to the following when we started building SBS ourselves (see below):
In 2019, we have started a Proof of Concept (GitHub sources) to determine if it is viable to implement these above mentioned flows in a new Membership Management System that we've written from scratch. The user stories for this development can be found on Pivotal. This system is called SBS, an abbreviation for the Dutch words for collaboration management system.
SBS should be available online, but as we're developing, for other reasons, it might not be available . But if you want to try: check out this DIY demo script: SCZ demo SBS . Some words before you dive in:
Feel free to check it out. And let us know what you think, or when you have questions etc!