Data Problems

*** This checklist applies to the current (or old depending when you are reading this) ***

• Is the file available from the IATI registry?

  • No: Ask John Adams to annoy someone in IATI or publishers

• Is the file available for selection from the Org/Activity Sources in the Admin app?

  • No: Refresh Sources in Admin app

• Is the file selected in the Org/Activity Sources in the Admin app?

  • No: Select it

• Is the file valid? You can test the validation of the file via the IATI Validator for both well-formedness and against the XSD

  • No: Currently the file must be valid to be accepted into our pipeline. Ask John Adams to annoy someone in IATI or publishers

• Is the file correctly mapped into the Neo4J instance. You can run the neo4j web admin app on a dev machine and check if the data is in there (e.g. search for some of the activity data contatined in the file is a good way)

    START n=node:entities(type="activity")
    WHERE n.`iati-identifier` = '<AN_IATI_IDENTIFIER_FROM_THE_FILE>'
    RETURN n
  

  • No: Seriously go back and check the questions above cause thats weird. Alternatively ensure the logs aren't complaining about something

• Is the data aggregated into Mongo as expected? DFID project data goes into projects collection, other UK org projects go into other-org-projects and partner projects go into partner-projects.

  • No: Check the aggregators, grab the cypher queries from the aggregators and run them in the neo4j web admin to make sure things aren't failing for some weird data reason. If it is an other UK org check that the OtherOrgAggregator.scala has the appropriate Organisation Code in the list of applicable org codes.