Users can distinguish between tiers of pipelines in the HCA

[kbergin]

dcp ticket

secondary-analysis ticket

Copied from SA ticket:

Per our agreement with the AWG, we are allowed to run contributed or beta pipelines in the DCP and store the results in the DSS if they are distinguishable from our HCA standard outputs. An example of this type of pipeline is the SS2 SE pipeline we have created. The analysis outputs that come out of this pipeline should be labeled as beta pipeline in the analysis metadata. As all outputs coming from any given version of the pipeline will be contributed, beta, or HCA, I think this field makes sense in the metadata file that describes the pipeline, happy to discuss more.

The change to this metadata should be discussed with the metadata team. Schema change blocks the changes to the pipeline.

As a user I am interested in knowing whether data has been produced with a pipeline that has been signed off by the AWG and thus can be included in a release of the HCA vs data that is not when I access and download that data.

AC:

• Metadata on this difference is available to be faceted on in the browser, let the browser team know of the change when complete
• Is added to schema and is created in our submissions
• Field is either "Contributed", “Beta”, or "HCA" so all pipelines that output data will have this field filled in
• Updated tests
• Metadata dictionary is updated to reflect new field

┆Issue is synchronized with this Jira Story

[kbergin]

[~jkaneria] ticket I mentioned making