GUI should be able to read the provenance for driving dynamic UI elements

[schristley]

tags on the entities are used to annotate files (so that we don't have to hard code file names). For example, here is the entity object for the clone report from igblast. By searching through the entities and looking at "vdjserver:tags", can extract the relevant files. The actual file name is given by "vdjserver:project_job_file"

      "vdjserver:project_job_file:clone_report.csv": {
        "vdjserver:type": "app:outputs",
        "vdjserver:project_job_file": "clone_report.csv",
        "vdjserver:tags": "clone_report",
        "vdjserver:description": "Clonal Assignment Summary Report",
        "vdjserver:format": "csv"
      },

It's possible that we aren't creating provenance entries for all of these, in which case that is a bug and needs to be fixed.

• Output archive zip file (archive)
• Job error and log files
• VDJpipe summary report
• Igblast summary report (igblast_count_statistics, makedb_count_statistics, fail-makedb_count_statistics)
• igblast clone report (clone_report)

[schristley]

@swollenburg this is what I'm referring to about loading the provenance_output.json file that output by a job and put in the archive directory

[schristley]

vdjpipe provenance errors #135
igblast provenance errors #137