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

Create new iati_publisher_frequency table #774

Open
akmiller01 opened this issue Jul 19, 2022 · 3 comments
Open

Create new iati_publisher_frequency table #774

akmiller01 opened this issue Jul 19, 2022 · 3 comments

Comments

@akmiller01
Copy link
Contributor

Create a new table in the database as a part of the IATI refresh/reload process such that it captures a timestamp every time a publisher updates their data. This will later allow us to quantify how frequently publishers are updating.

@akmiller01 akmiller01 added the ETL label Jul 19, 2022
@wakibi
Copy link
Contributor

wakibi commented Jul 20, 2022

Is this supposed to capture publisher, codelist and timestamp? Just in case we need to have these stats for other codelists in the future?

@akmiller01
Copy link
Contributor Author

If we want to imitate the current statistic, it would likely be publisher, most recent transaction date, and timestamp. And then the category is defined as how often they update their most recent transaction date: https://github.com/IATI/IATI-Dashboard/blob/master/timeliness.py

@stale
Copy link

stale bot commented Sep 21, 2022

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 Sep 21, 2022
@stale stale bot closed this as completed Oct 1, 2022
@edwinmp edwinmp reopened this Oct 3, 2022
@edwinmp edwinmp added pinned and removed wontfix This will not be worked on labels Oct 3, 2022
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

3 participants