Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

workaround: refer to data owners in Datahub as custodians in Find MoJ data #1014

Merged
merged 1 commit into from
Nov 4, 2024

Conversation

MatMoore
Copy link
Contributor

@MatMoore MatMoore commented Nov 4, 2024

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.

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.

At this point we will be able to distinguish between
different kinds of owners in Datahub, and we can 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 interesting 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.
@MatMoore MatMoore requested a review from a team as a code owner November 4, 2024 10:33
@MatMoore MatMoore merged commit 6ad34ed into main Nov 4, 2024
32 of 33 checks passed
@MatMoore MatMoore deleted the data-owner-workaround branch November 4, 2024 10:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants