Can see provenance of data source

[pmackay]

As a user I can see where data on the system has originated from, so I can track it to its origin.

[GreenCChampion]

I think this is high priority. It is also important for people to be able to identify who has the contacts ie who is the network owner as they too are an asset and we want to encourage people to use existing networks rather than start new conversations with the same people regardless.

[pmackay]

One of the challenges with this of course is when there are duplicates. Which entry or data source is considered most important?

[pmackay]

Some very good questions posted by the Ohana team, which should be considered by us:

• Why is it important to know the source of the data? What does this information allow you to do?
• Is it necessary to know the source of the data at any given time, or is it only useful at the beginning, when consolidating data from various sources?
• If a single deployment will consist of data from multiple sources, once the data is imported, is it necessary to continue keeping track of where the data came from? If so, why?
• Does the source of the data need to be visible in the admin interface for every single entity (organization, location, service, program, etc.)?

The 3rd one also should be considered in the context of where updates are made and who has ownership of the data.

cc @GilesGibson

[pmackay]

Assigning to @GilesGibson to input into questions above - deciding this stuff will determine how provenance would be implemented. We might need to discuss in a bit more detail first.