...

Open Questions

1. Should the publisher tool and contact trace tool be combined in the UI but functionality responds to user privileges (i.e. Admin vs contact tracer)?

   1. Originally joined them into 1 tool with role-based features, but since we aren’t doing roles in MVP1 they need to be 2 tools again even though they look exactly the same

2. How will redacted data points be handled? Are they just flagged as “deleted” or will they auto delete at some point?

Decided + Feature Deferment

1. Should we use the React component styling already being used (https://cdn.wfp.org/guides/ui/v1.4.0/docs/?path=/story/*) or force styling to match Safe Paths?

   1. This is going to depend on if we can get a Figma component library already made

      1. Decision: we will use the Safe Paths component library!

2. Load/Save from both a local file and a server-hosted database are both valid. The UX and code needs to handle both.

   1. Decided: only using DB data

3. An HA admin that also does contact tracing will need a “contact trace” login in addition to their admin login

4. Need to at some point add a “day by day” interaction on Safe Places for a contact trace

   1. Done!

5. Don’t show “traveling” points just yet since we need to understand that metatag a little bit more before implementation

6. “Bulk” location points into meta-duration will happen for MVP1 and it will only be on the front-end, duration will not make its way into the actual data

7. We will not develop the ability for HAs to combine entities in Safe Places (e.g. multiple HAs registering as 1 master HA) - they can do this manually or “on paper” but can’t technically “combine” as a feature in SPL

8. For MVP1 we aren’t handling role-based account login - Trace and Publish will be accessible for any logged in user

9. For MVP1 a Publisher can’t edit/add/delete points - only review before publishing