VEuPathDB / EdaNewIssues

0 stars 0 forks source link

Stand alone map - finalize mockups #543

Closed danicahelb closed 9 months ago

danicahelb commented 1 year ago

Bob's mockups: https://docs.google.com/presentation/d/17Yg4Kz00pW6wbNo3bK0DpQjW4cVEzrq0VQ75pw1xZNc/edit#slide=id.g1c88f1f301b_0_62

Danielle's mockups: https://www.figma.com/file/gKYVrWu6qfDTUgYKQuvaIy/SAM?node-id=6%3A42&t=IQy4Erjcg1BaaXtr-0

danicahelb commented 1 year ago

Discussed in 12/15/2022 map WG

standalone FSM that does NOT allow the user to escape to the regular EDA.

Here standalone does not mean “open source, easy to deploy”. It just means that there is no “regular EDA” as part of the UX.

It will in fact have regular EDA data models (e.g. user data) and back end services etc under the hood. (So there’s a path in the future to re-marry them if needed.)

The only downside to standalone FSM (which was glossed over a bit in the meeting) is that datasets with mixed geolocated and non-geolocated data won’t be handled. The legacy map had the same issue - nobody seemed to complain, and the number of non-geolocated data points was extremely small (a dozen or so lab colonies maybe?)