Enhancement: People added at Series level vs…

Enhancement: People added at Series level vs single session level * system should prevent a person from being added at both series and single session level...i can't think of a use case why a person would be in a session multiple times. This may be even more critical when volunteers can sign up for open shifts, or there are more people working at manager level in the system. * since you can have a mix of both (people added at series and at the single level) there should be an indicator that a person is part of the recurring series- similar to what shows on the sessions calendar overview **use case: if you (accidentally) add a user at single level, and also add them at the series level, it's unclear which one to delete. Also, as the Team Captain, Instructor, or Staff on Duty, it's helpful to know at the start of a shift if someone is just helping out for the day, or if they've been added on an ongoing basis, or if a participant is doing a make-up session. (the latter rarely happens but it does happen, especially with Sat EFL lesson) --- 🔎 Behavior to mitigate: Sessions and series individually already disallow addition of the same person more than once in the same session or series, but the below use case is a loophole that creates a duplicate and needs to be mitigated: - There's a series with sessions - a person is added at the individual session level - that same person can be then added at the series level - the series level change propagates to all sessions - the person is displayed twice for that session - admins/managers don't know which instance of the duplicate to remove to clean up the session 💡 possible solution: - create an exception check in series>session propagation that checks to see if that person is already assigned to that session - if they are already assigned, the propagation skips that session but propagates everywhere else - there may be more than one session where people were added manually, so should work for more than one skip when needed - why? closes the loop hole without needing extra intervention from a user to remove the duplicate (annoying for users), avoids validation which might require removing the session-person in order to add them to the series to propagate equally across all sessions in a series (annoying for users)

Enhancement: People added at Series level vs single session level * system should prevent a person from being added at both series and single session level...i can't think of a use case why a person would be in a session multiple times. This may be even more critical when volunteers can sign up for open shifts, or there are more people working at manager level in the system. * since you can have a mix of both (people added at series and at the single level) there should be an indicator that a person is part of the recurring series- similar to what shows on the sessions calendar overview **use case: if you (accidentally) add a user at single level, and also add them at the series level, it's unclear which one to delete. Also, as the Team Captain, Instructor, or Staff on Duty, it's helpful to know at the start of a shift if someone is just helping out for the day, or if they've been added on an ongoing basis, or if a participant is doing a make-up session. (the latter rarely happens but it does happen, especially with Sat EFL lesson) --- 🔎 Behavior to mitigate: Sessions and series individually already disallow addition of the same person more than once in the same session or series, but the below use case is a loophole that creates a duplicate and needs to be mitigated: - There's a series with sessions - a person is added at the individual session level - that same person can be then added at the series level - the series level change propagates to all sessions - the person is displayed twice for that session - admins/managers don't know which instance of the duplicate to remove to clean up the session 💡 possible solution: - create an exception check in series>session propagation that checks to see if that person is already assigned to that session - if they are already assigned, the propagation skips that session but propagates everywhere else - there may be more than one session where people were added manually, so should work for more than one skip when needed - why? closes the loop hole without needing extra intervention from a user to remove the duplicate (annoying for users), avoids validation which might require removing the session-person in order to add them to the series to propagate equally across all sessions in a series (annoying for users)