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

Feature request: Add GPEDC and GB flags to Publisher Statistics summary table #524

Open
bill-anderson opened this issue Nov 6, 2018 · 3 comments

Comments

@bill-anderson
Copy link

Can we investigate ...

With reference to Discuss thread - https://discuss.iatistandard.org/t/gpedc-transparency-indicator/1548

  1. What is the best way of maintaining a list of publishers indicating their association with GPEDC Transparency Indicator and Grand Bargain?
  2. What would be involved to add 2 columns to the summary statistics table to flag these associations?
@andylolz
Copy link
Contributor

andylolz commented Dec 4, 2018

What is the best way of maintaining a list of publishers indicating their association with GPEDC Transparency Indicator and Grand Bargain?

One option would be for this to live in config.py. #499 could help with that.

However, I think it would be preferable for this list to live inside version control.

@andylolz
Copy link
Contributor

andylolz commented Jan 16, 2019

Can we investigate ...

Elsewhere in this repo, a spreadsheet is used to achieve something similar:
https://github.com/IATI/IATI-Dashboard/blob/8925fa23/dfi_publishers.csv

See #387 for details.

It’s good that this lives in version control, since it means errors are easier to spot (e.g. I wonder if that DFI list might need to be updated?)

I’d suggest the following:

  • Replace with a single, general spreadsheet for these sorts of publisher-specific settings. E.g. a column for "DFI?"; a column for "GPEDC?"; a column for "GB?" etc.
  • Add a note to the README reminding everyone to keep this spreadsheet up-to-date
  • Present this information in the frontend explicitly, so it’s more transparent how it works / less magic. This would also help with debugging.

@samuele-mattiuzzo
Copy link
Contributor

@bill-anderson maybe worth setting up a meeting next week when I'm back so we can discuss this internally.

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

No branches or pull requests

3 participants