Open jasonaowen opened 1 year ago
We've discussed it a few difference places but evidently not here!
My intention with that element was to communicate to the user — currently all PDC stakeholders — "where did this particular proposal come from?" I thought that would be an easy question, but evidently it's not! There are technical data sources ("a GMS imported it via the API…") and conceptual sources ("…on behalf of their client, the foundation which runs the opportunity to which the proposal was responding"), and sometimes those are the same, and sometimes it's something else…
Before we worry about where this data comes from and how to express it, we need to re-state what questions the user is asking that the UI element is trying to answer. Basically, we need a user story here.
I expect we'll actually end up with multiple concepts here, and need to split "data source" into multiple tags for each purpose.
Good news everyone! Provenance is officially part of Phase 3.
That said, it isn't clear if there is going to be a UX implementation to show the provenance. For now I'll move this to the Phase project 3 though
If we do decide to show provenance in the UI, I'll want to take another pass at it, with a better understanding of what sort of provenance we're tracking and what questions the user wants answered. My original design implementation was naive.
Once https://github.com/PhilanthropyDataCommons/service/issues/116 is resolved, display that data in the UI.
In this example, the "Brighter Future Foundation" is the data source:
The designs have this in the proposal detail panel, below the proposal title, and to the right of the organization name.