rorads

rorads

<?xml version="1.0"?>
<!--
....APODS.Authenticity.Verification....
............................**%#.......
.............................,%,.......
......../%,..................*%........
......../%(%%%%%%%%%%%%%%%%%%%.%%%.....
......../%%%%%%%(.........../%.%.%/....
.........,.... %%%%..........%.%.%(....
.... %%%%%%%%% ..%%%.........%.%.%(....

rorads

import pandas as pd
import requests
import json

search_term = 'policy'

base_url = 'https://opendataservices.plan.io/projects/co-op/search?utf8=%E2%9C%93&wiki_pages=1'

# get all wiki pages with 'policy' in them somewhere; plug in your coop email and your plan.io password for conf
rq = requests.get(base_url + '&q=' + search_term + '&format=json&limit=50', auth=('my.name@opendataservices.coop', '5up3r53cr3tpw1234'))

rorads

IATI transaction traceability extension

Note: This file is being used in place of a formal .xsd extension, as I would like there to be more consultation before proposing a full technical solution. For now, this gist is meant to explain what is meant when an IATI publisher uses one of the following attributes in their data:

• iati-activities/iati-activity/transaction/provider-org/@trace:trans_id
• iati-activities/iati-activity/transaction/receiver-org/@trace:trans_id

Currently, the IATI standard doesn't allow for one transaction refer to another one by it's reference. Because of this certain things cannot be done, namely:

1. associating a disbursement in one organisation's data with an incoming fund in another's ('i.e the inter-organisation conception of 'following the money').