workaround: refer to data owners in Datahub as custodians in Find MoJ data #1014
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a temporary workaround. Once the next version of Datahub is released, we will be able to reenable the meta_mapping in the dbt ingestion, which will allow us to store data custodians as data custodians in Datahub and remove this workaround.
The ability to distinguish between owners and custodians is not essential at the moment, but it's desirable, because the data improvement team are introducing data owner/data steward/data custodian roles, and it's very likely that data owners and stewards will also interact with the Find MoJ data and/or Datahub.