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

List the main person(s) working in each ETL step #2465

Open
4 tasks
pabloarosado opened this issue Mar 27, 2024 · 1 comment
Open
4 tasks

List the main person(s) working in each ETL step #2465

pabloarosado opened this issue Mar 27, 2024 · 1 comment

Comments

@pabloarosado
Copy link
Contributor

pabloarosado commented Mar 27, 2024

Problem

We currently have no easy way to know who has worked in a particular ETL step or grapher dataset.

If, for example, something odd is found in the data, we don't know straight away who the contact person is, to tag in an issue or in slack.

Hence, it would be convenient to have that information both in the ETL dashboard and in the grapher admin.

Possible solution

Add a metadata field

One possible solution would be to have owid_authors (or some other name) as a new field (list of literals) in the snapshot metadata, which would be automatically propagated (by doing the union of authors). As with any other metadata field, this field could be manually overwritten at a later step.

Use git metadata

We could check who's committed to a step. It would have the benefit of filling this in historically, but we also have bots that commit, and many ingredients on the way to a step. But it also might pick up people who are not the main contributor, e.g. Mojmir gets tagged on EVERYTHING 🎉

What's in scope

  • Create a metadata field
  • Ensure it gets populated automatically (e.g. in Wizard, or from previous data version)
  • Ensure that it propagates, e.g. from snapshot onwards
  • Telling people about it

Out of scope

  • Backfilling it somehow is just nice to have
Copy link

stale bot commented May 27, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix This will not be worked on label May 27, 2024
@pabloarosado pabloarosado removed the wontfix This will not be worked on label Jun 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants