Backlog of Outstanding DPG Full Submissions:

[nathanbaleeta]

The following nominated projects made full submissions but have not yet been reviewed:

• Good Here Add DPG: Good Here #656
• Project Simoy Add nominee: Project Simoy #550
• Somleng Add DPG: Somleng  #149
• Geomancer Add DPG: Geomancer #148
• AI Powered Poverty Estimation Add DPG: AI Powered Poverty Estimation #645
• Wonder Tree Add DPG: Wonder Tree (Issue #555) #644
• African Terrestrial Fibre Network Mapping Project (AfTerFibre) Add DPG: African Terrestrial Fibre Network Mapping Project (AfTerFibre) #643
• openIMIS Add DPG: OpenIMIS (Issue #555) #654
• Cboard Add DPG: Cboard #559
• Translation Initiative for Covid-19 (TICO-19) Add DPG: Translation Initiative for Covid-19 #648
• Oky Add DPG: Oky (Issue #555) #655
• An Open Multipurpose Extensible Aerial Platform (a.k.a Open Drone Suite) Add DPG: Open Drone Suite #651
• The Atrium Add DPG: The Atrium (Issue #555) #649
• Juniper Add DPG: Juniper (Issue #555) #657
• Project Connect Add DPG: Project Connect (Issue #555) #650
• VivoosVR Add DPG: VivoosVR (Issue #555) #646
• high resolution population density data Add DPG: High Resolution Population Data for Humanitarian Operations #653
• Hive: Drone Monitoring and Management System Add DPG: Hive #658
• Delve Add DPG: Delve  #345
• OpenAgro Add DPG: AI Agro #346
• Glific Add DPG: Glific #660
• Collect Earth Add DPG: Collect Earth #647
• Immunization Calculation Engine (ICE) Add DPG: ICE (Immunization Calculation Engine, Issue #555) #659
• Kiva Protocol Add nominee: Kiva Protocol #518
• EduNOSS Add nominee: EduNOSS #537 Add DPG: EduNOSS #582
• Project Konko Add nominee: Project Konko #548 Relegate DPG: Project Konko #997
• Powwater Water Demand and Consumption Database Add nominee: Powwater Water Demand and Consumption Database #549
• Safe YOU Add DPG: Safe YOU #560
• OpenLMIS Add DPG: OpenLMIS (Issue #555) #652
• Standard for Public Code Add DPG: Standard for Public Code #639

[Ainali]

As far as I can see, none of the projects above are available to review yet. Is there any way one can help on this?

[lacabra]

Hi @Ainali, thanks for your offer to help; very much appreciated: The short answer to your question is Yes 🙂

Here's some background: We started accepting submissions with an inadequate Google Form that did not integrate nicely with this repo, and we would store their answers on a spreadsheet, which would then need to be manually encoded into json files and added to this repo.

We recently (April 2021) upgraded our submission form (repo, live form), and that integration now happens automatically, so we can keep up with any submissions we receive through the new form, but we are behind encoding and reviewing the ones that we received with the old Google Form. Thus, the first step would be to encode those entries into JSON, and @nathanbaleeta will do the first pass at reviewing them, and reaching out to the project contact if additional information is required from them.

Because that spreadsheet contains some personal information, I don't feel comfortable giving anyone else access directly, but (option A) I can copy/paste the info that we received from any of the above projects into plain text, and you can encode it into JSON We could also look into scripting it (option B), and converting from CSV into JSON, but it will require some additional work, it may or may not be worth it. I can provide a "cleaned up" version of that spreadsheet that contains all of the projects above, with the personal information removed. The script would look like a more complex version of this related one.

Let me know if you are interested in helping out with Option A or Option B. Also, @nathanfletcher may be able to help.

[Ainali]

Thanks @lacabra! Me and my colleague @ericherman could have a go at option B.

[lacabra]

@Ainali & @ericherman: Amazing! 🙌

Here is a copy of the spreadsheet that contains the submissions from the projects listed above not yet encoded into JSON (and linked to their respective PR). I count 19 of them. My recommendation is to export it as CSV.

Take a look and let us know what you think. 3 observations:

• Assume that all these projects are already nominated, what is missing is the full submission matching the data in this schema, and placing the corresponding JSON file in this folder
• Once you have your first encoded JSON file, please run all the checks described here, to make sure the file is compliant, and the CI will pass.
• When the encoded JSON files are ready, they should be added one per PR to align with our current workflow.

Happy to answer any questions. If you need a real time chat, we can chat here.
FYI, @nathanbaleeta is based in GMT+3, and I'm based GMT-7

[Ainali]

Just commenting to let you know that we are about halfway through scripting the conversion.

[lacabra]

Thanks for the update @Ainali, and thanks for your efforts on this front 🙏

[ericherman]

@lacabra we have a rough draft now ( https://github.com/ericherman/dpg-csv-to-json ). We have not yet tried to run the checks, nor split the data into separate submission files.

[lacabra]

@ericherman Cool, cool; let me know when you do the split and run the checks, eager to take a look then.

[ericherman]

@lacabra seems to pass the checks now.

I believe all you need to do is:

git clone -o upstream [email protected]:ericherman/dpg-csv-to-json.git
cd dpg-csv-to-json
npm install
node ./dpgs-transform-main.js

And the result files should be in the out subdirectory.

[ericherman]

The docs at https://github.com/unicef/publicgoods-candidates/blob/master/docs/development.md#ci---continous-integration say

./scripts/check-filenames.bash checks that all data files are named consistely, that is by using the field name in kebab-case, in which punctuation is removed and spaces are replaced by single hyphens.

but ./scripts/check-filenames.bash expects parenthesis to remain, and everything after a colon to be removed.

We aligned the file naming with the expectations of script, rather than the docs.

[Ainali]

@lacabra I created #639, did I get it right?

[lacabra]

@lacabra I created #639, did I get it right?

@Ainali, yes, it looks very good to me, and as you can see the CI passes, which is also a very good sign. I would like to get confirmation from @nathanbaleeta, who is the person who will review and processes PRs like that for final confirmation, and then you can submit all the rest. This is very exciting 🙌

[nathanbaleeta]

@lacabra I created #639, did I get it right?

@Ainali this looks nice and clean. Great job! Please proceed with submitting the remaining submissions.

[Ainali]

@lacabra I created #639, did I get it right?

@Ainali this looks nice and clean. Great job! Please proceed with submitting the remaining submissions.

@lacabra We believe we added all of the ones that were in the csv file. They still might need some cleanup since some of the data had freeform format.

[lacabra]

This looks great @Ainali, thanks a lot, you and @ericherman both rock! 🙌

I have updated the description of this issue to link to all the PRs, and as you can see they are all covered, and @nathanbaleeta has already started working on the one you submitted yesterday.

Much appreciated! 🙏

[ericherman]

Pleasure to be able to contribute. Keep up the great work! <3

[nathanbaleeta]

Closing this issue as the new tracker board serves as the current single source of truth for all projects previously existent in the backlog list. Thanks.