Closed danicahelb closed 2 years ago
We discussed in 10/15 UX meeting:
Purpose of the pin is to identify things the user wants to come back to repeatedly over time, but when a user opens up a public analysis, it will get imported into their “My analyses” table
Decision: We do NOT want to add pins to the public analyses table
As mentioned in: https://github.com/VEuPathDB/web-eda/issues/448
Check in with the UX group to see if they agree to add user-specific "pinned public analyses" to the UI.
this would be a pure client change (no user service updates required).
@steve-fischer-200: i suppose this could be a soft user preference managed by the client? it could be a list of analysis IDs?
@jtlong3rd: Yup, makes sense. We could also make use of the EDA user service preferences. (Currently, those preferences are a JSON string with a single optional pinnedAnalyses property, which consists of a list of analysis IDs. The client could be updated to save/read an optional pinnedPublicAnalyses field that behaves similarly.)