SFMS API: Clarify public access requirements
- Dominant language
- Python
- Stars
- 65
- Forks
- 11
- Avg merge
- 21h 25m
- Merged PRs (30d)
- 70
Description
**The task**
Research focused on the business area. Determine whether members of the public should have any access to SFMS/SFMS Insights outputs, and if so, what subset of data and what access model. This has come up as an unresolved in prior research efforts.
**Acceptance Criteria**
- [ ] Relevant business or program stakeholders identified and consulted
- [ ] A clear answer obtained of either: no public access, full public access, or a defined public type.
- [ ] Any determined public-facing view needs are scoped
**SME/User Contact**
A contact with authority over public data access decisions (ie. not an end user of the map interface itself).
**Additional context**
This is a scoping question, not a usability question, and affects whether any future design ticket needs to account for a public-facing, unauthenticated view.
Contributor guide
Assessment
This issue has not been assessed yet.