In Wannabe, a function can be switched on where crew members input their allergies and needs in regards of food. This is later on used for CrewCare to ensure that they can provide safe food alternatives for the crew members to enjoy.
Scenarios
Scenarios are described in a The Gathering context.
CrewCare needs complete list of what allergies crew members at The Gathering has. To support this, key members of CrewCare can access a list containing crew members, their crew and allergies:
id
name
crew
allergies
13
Olle Nordis
Crew Crew
Nøtter, Melk, Pollen
14
Olga Søris
Le Crew
Melk, Sjokolade
The Tech crew is having a Tech-meeting to ensure that they once again can create interwebs, and they'll be ordering som delicious pizza. However, the meeting will be attended by over 30 members, and they need an easy way to get the allergies of the relevant Tech crews to ensure that they order alternatives for those members with allergies.
Problems
Data like allergies are to be treated as sensitive data per GDPR and should be handled with care.
Solving the issue with NDAs don't lead to anything good. It solves the problem legally, but it does not solve it in a user friendly way. It may also lead to an NDA losing its power.
Solution proposals (concepts in no specific order)
1:
A certain crew may get information about both the user information and its allergies. As well as a per-crew summary. The reasoning behind this is that the main crew handling food for large events like The Gathering might need extra granularity to ensure they provide safe food for everyone.
For all other crews, the chief for a crew can list out the allergies for its specific crew.
Note: There's a big network of cross allergies, and allergies might still be easy to connect to a person. This may also lead to extra fuzz if there's an individual with a certain allergy not attending the event, but is still reported to the planning chief.
2:
A certain crew may get information about both the user information and its allergies. As well as a per-crew summary. The reasoning behind this is that the main crew handling food for large events like The Gathering might need extra granularity to ensure they provide safe food for everyone.
For all other crews, the chief is informed that they will be handling the information in a safe manner, and will see the information in the same way as above mentioned crew, except it's filtered down to its own crew
Note: Some individuals are chiefs for multiple crews. These should have access to summarise all the crews they are chief for.
Please add more suggestions in the comments down below. Don't forget to like and subscribe
Plan of attack
This is a problem that with a good solution, could gain a lot of crews. For instance with multiple crew gatherings throughout the year, functionality for getting information about relevant members will ease the planning of these events. Not to forget, this will also make the handling of allergies a lot easier and safer for individuals participating.
After deciding on a solution, a practical proposal should be made. This proposal should describe how to implement this both in the backend, but also creating a good frontend for the solution.
Context
In Wannabe, a function can be switched on where crew members input their allergies and needs in regards of food. This is later on used for CrewCare to ensure that they can provide safe food alternatives for the crew members to enjoy.
Scenarios
Scenarios are described in a The Gathering context.
CrewCare needs complete list of what allergies crew members at The Gathering has. To support this, key members of CrewCare can access a list containing crew members, their crew and allergies:
The Tech crew is having a Tech-meeting to ensure that they once again can create interwebs, and they'll be ordering som delicious pizza. However, the meeting will be attended by over 30 members, and they need an easy way to get the allergies of the relevant Tech crews to ensure that they order alternatives for those members with allergies.
Problems
Data like allergies are to be treated as sensitive data per GDPR and should be handled with care.
Solving the issue with NDAs don't lead to anything good. It solves the problem legally, but it does not solve it in a user friendly way. It may also lead to an NDA losing its power.
Solution proposals (concepts in no specific order)
1:
A certain crew may get information about both the user information and its allergies. As well as a per-crew summary. The reasoning behind this is that the main crew handling food for large events like The Gathering might need extra granularity to ensure they provide safe food for everyone.
For all other crews, the chief for a crew can list out the allergies for its specific crew.
Note: There's a big network of cross allergies, and allergies might still be easy to connect to a person. This may also lead to extra fuzz if there's an individual with a certain allergy not attending the event, but is still reported to the planning chief.
2:
A certain crew may get information about both the user information and its allergies. As well as a per-crew summary. The reasoning behind this is that the main crew handling food for large events like The Gathering might need extra granularity to ensure they provide safe food for everyone.
For all other crews, the chief is informed that they will be handling the information in a safe manner, and will see the information in the same way as above mentioned crew, except it's filtered down to its own crew
Note: Some individuals are chiefs for multiple crews. These should have access to summarise all the crews they are chief for.
Please add more suggestions in the comments down below. Don't forget to like and subscribe
Plan of attack
This is a problem that with a good solution, could gain a lot of crews. For instance with multiple crew gatherings throughout the year, functionality for getting information about relevant members will ease the planning of these events. Not to forget, this will also make the handling of allergies a lot easier and safer for individuals participating.
After deciding on a solution, a practical proposal should be made. This proposal should describe how to implement this both in the backend, but also creating a good frontend for the solution.