Confusing provenance information displayed in the dashboard when run with `--provenance`
The current dashboard gives information about provenance data, but does this with the following behavior:
First, identify what is known in the archive (using the api/1/known endpoint) using a random sampling algorithm (to statistically minimize the number of /known query required to have the full picture),
Then if the --provenance option is set when scanning, all the provenance information for known object is queried, not querying the provenance for anything in a known directory but use the provenance info for said directory instead.
If the --provenance option is not set during the scanning phase, then provenance queries are made on demand; in which case the provenance info retrieved and displayed is the one of the object itself (not the provenance of a directory above).
The issue is there is no visual indication in the dashboard where the provenance information displayed in view for an object (directory or content) comes from, nor there is the possibility to explicitly ask for the provenance of the displayed object when there is already a provenance information shown (possibly for a directory above the object).
