You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* add upstream and downstream lineage to getDatasetDetails graphql query
* refactor parse_relations() helper to handle more relations
* add upstream and downstream lineage to RelationshipType enum
* update parse_relations() input args
* update parse_relations() input args in search
* add has_lineage and lineage_url to dataset details context
* add lineage link to details_table template
* remove redundant block in query for data product relationships
* return entity name for lineage
* have only 1 RelationshipType for lineage
* simplfy `parse_relations()` helper function
* update DatasetDetails to use single lineage type
* align url to rest of table
* update tests
* add default value for url
* design suggestions for lineage label, from Alex and Jess
* spell it right
* suggestions from Mat
<pclass="govuk-body">The schema for this table is not available.</p>
80
80
{% endif %}
81
-
82
-
83
-
</div>
81
+
{% if has_lineage %}
82
+
<h2class="govuk-heading-m">Lineage</h2>
83
+
<divclass="govuk-body-m" >
84
+
If you are interested to find out what data were used to create this table or if this table is used to create any further tables, you can see that information via the lineage.
0 commit comments