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

csv download not in order of methodology #65

Open
stevieflow opened this issue Dec 21, 2021 · 0 comments
Open

csv download not in order of methodology #65

stevieflow opened this issue Dec 21, 2021 · 0 comments

Comments

@stevieflow
Copy link

stevieflow commented Dec 21, 2021

@michaelwood @Lathrisk huge thanks for the labelling and ordering of the test results in the DQT #52, and then the csv export of the results

Certainly, the DQT on-screen results are in order - with Indicator 24 ( #55 ) and 30 ( #56 ) in need of moving into the relevant section

In terms of the csv export, the tests are not presented sequentially - eg:

indicator_num name
  Organisational planning and commitments
4 Annual report is present
5 Allocation policy is present
6 Procurement policy is present
8 Audit is present
3 Organisation strategy is present
7 Strategy (country/sector) or Memorandum of Understanding
   
  Finance and budgets
10 Disaggregated budget
14 Disbursements or expenditures are present
11 Budget available forward annually
11 Budget available forward quarterly
12 Budget document is present
9 Organisation budget available one year forward
9 Organisation budget available two years forward
9 Organisation budget available three years forward
15 Capital spend is present
15 Publish detailed CRS purpose codes in the sector field
13 Commitment is present
   
  Project attributes
30 Implementing organisation
23 Location (sub-national)
23 Location (sub-national) coordinates or point
22 Sector is present
22 Sector uses DAC CRS 5 digit purpose codes
30 Participating Orgs
25 IATI Identifier is present
25 IATI Identifier starts with reporting org ref
21 Contact info is present
19 Actual start date is present
19 Actual end date is present
17 Description is present
17 Description has at least 80 characters
20 Current status is present
20 Current status is valid
18 Planned start date is present
18 Planned end date is present
16 Title is present
16 Title has at least 10 characters
   
  Joining-up development data
26 Flow type
26 Flow type uses standard codelist
24 Conditions data
24 Conditions document
29 Tied aid status
29 Tied aid status uses standard codelist
28 Default finance type
28 Finance type uses standard codelist
27 Aid type is present
27 Aid type is valid
31 Tender is present
31 Contract is present
   
  Performance
34 Pre- and/or post-project impact appraisal documents
35 Project performance and evaluation document
33 Objectives of activity document
36 Results data
36 Results document

Maybe this was because this functionality was implemented before #52 was completed? Would you be able to refactor the csv export so that it is in synch accordingly?

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

1 participant