Closed caprenter closed 10 years ago
Using http://iati-datastore.herokuapp.com/api/1/access/activity.xml?limit=1&recipient-country=BD to get a single activity for Bangladesh.
<iati-activity default-currency="USD" xml:lang="en">
<reporting-org ref="US" type="10">United States Government</reporting-org>
<description>
United States Population Migration and Refugee Assistance, Appropriation 1143. Protection and assistance needs of refugees, migrants and conflict vicitms worldwide. [ACF International]
</description>
<iati-identifier>US-11-2010055676</iati-identifier>
<title>
Nutritional and Mental Health Support for the Registered Refugees in Kutupalong and Nayapara Camps and Surrounding Communities in Ukhyia and Teknaf Upazilas
</title>
<activity-date iso-date="2010-12-31" type="end-planned">2010-12-31</activity-date>
<sector code="72010" vocabulary="DAC">Material relief assistance and services</sector>
<recipient-country code="BD">Bangladesh</recipient-country>
<participating-org ref="US-1" role="funding" type="10">United States of America</participating-org>
<transaction>
<transaction-date iso-date="2010-12-31">2010-12-31</transaction-date>
<transaction-type code="C">Commitment</transaction-type>
<value currency="USD" value-date="2010-12-31">613,514</value>
<description>2010 CRS Commitment</description>
</transaction>
<activity-date iso-date="2010-01-01" type="start-planned">2010-01-01</activity-date>
<participating-org ref="US-11" role="extending" type="10">Department of Labor</participating-org>
<activity-status code="2">Implementation</activity-status>
<participating-org ref="21000" role="implementing">ACF International</participating-org>
</iati-activity>
I'm currently designing a single activity view to display the information above so we can iterate on that once I have something up. The main objective is to use content we already have and convert it easily to front-end.
I'm also including http://iati-datastore.herokuapp.com/api/1/access/activity.xml?limit=1&recipient-country=BD&reporting-org=GB-COH-871954 in the design as this has various transactions under one activity.
<iati-activity default-currency="GBP" xml:lang="en">
<reporting-org ref="GB-COH-871954" type="21">Practical Action</reporting-org>
<transaction>
<transaction-date iso-date="2012-06-30">Unrestricted</transaction-date>
<transaction-type code="E">Expenditure</transaction-type>
<value value-date="2012-06-30">21620</value>
</transaction>
<description>Practical Answers - BD</description>
<iati-identifier>GB-COH-871954-188</iati-identifier>
<title>Practical Answer</title>
<activity-date iso-date="2013-03-31" type="end-planned">2013-03-31</activity-date>
<recipient-country code="BD">BANGLADESH</recipient-country>
<activity-date iso-date="2012-04-01" type="start-planned">2012-04-01</activity-date>
<recipient-region code="798">Asia, regional</recipient-region>
<activity-status code="3">Implementation</activity-status>
<transaction>
<transaction-date iso-date="2012-06-30">Unrestricted</transaction-date>
<transaction-type code="C">Commitment</transaction-type>
<value value-date="2012-06-30">15000</value>
</transaction>
<transaction>
<transaction-date iso-date="2012-09-30">Other Donors</transaction-date>
<transaction-type code="E">Expenditure</transaction-type>
<value value-date="2012-09-30">-5267</value>
</transaction>
<transaction>
<transaction-date iso-date="2012-09-30">Unrestricted</transaction-date>
<transaction-type code="E">Expenditure</transaction-type>
<value value-date="2012-09-30">33480</value>
</transaction>
<transaction>
<transaction-date iso-date="2012-09-30">Unrestricted</transaction-date>
<transaction-type code="C">Commitment</transaction-type>
<value value-date="2012-09-30">15000</value>
</transaction>
<transaction>
<transaction-date iso-date="2012-12-31">Other Donors</transaction-date>
<transaction-type code="E">Expenditure</transaction-type>
<value value-date="2012-12-31">5266</value>
</transaction>
<transaction>
<transaction-date iso-date="2012-12-31">Unrestricted</transaction-date>
<transaction-type code="E">Expenditure</transaction-type>
<value value-date="2012-12-31">8423</value>
</transaction>
<transaction>
<transaction-date iso-date="2012-12-31">Unrestricted</transaction-date>
<transaction-type code="C">Commitment</transaction-type>
<value value-date="2012-12-31">15000</value>
</transaction>
<transaction>
<transaction-date iso-date="2013-03-31">Unrestricted</transaction-date>
<transaction-type code="E">Expenditure</transaction-type>
<value value-date="2013-03-31">7320</value>
</transaction>
<transaction>
<transaction-date iso-date="2013-03-31">Unrestricted</transaction-date>
<transaction-type code="C">Commitment</transaction-type>
<value value-date="2013-03-31">15000</value>
</transaction>
</iati-activity>
Compare and contrast with: http://devtracker.dfid.gov.uk/projects/GB-1-202180/
This is a Bangladesh project - might be worth also pluging that into your design and seeing if it works
Can you point me to the raw data of this in the datastore? Thanks.
Ha - apparently not. Ben has a fix ready to go to allow you to call an activity by it's identifier. We'll get a dev server set up with this fix in it soon.
is a rough wireframe which I will be putting online with content from the datastore.
You can preview the progress of this online on my personal dev server. The final iteration of this will be pushed to github when it becomes reliable.
http://esyou.com/mock3 - SIngle Activity View 0.1 http://esyou.com/mock3a - SIngle Activity View 0.2 http://esyou.com/mock3b - SIngle Activity View 0.3 http://esyou.com/mock3d - SIngle Activity View 0.4 http://esyou.com/mock3c - List of Activities View 0.1 http://esyou.com/mock3e - List of Activities View 0.2
Most of the work done focused on displaying current data in the best way possible (visually and legibility). All of the examples used the raw data from the datastore with applied CSS.
Flexibility was compromised due to the structure of the data so the best I could do was make sure the design was clean and generously laid out.
So I guess you want some feedback on these views. I guess we need to choose one or decide on the merits of each one and come to some amalgamation.
For now I suggest people send feedback in whatever way works for them, and Shi can work through and collate all suggestions.
Can we all find a bit of time to give some feedback please - the sooner the better, but by Wednesday lunch at the latest.
Thanks, David but I'm not requiring any feedback for this particular project (Single Activity View) at the moment, I'm just showing you progress of what I'm building and have built up to this point. The versions you see above are in running order with the latest being the most up-to-date (best) version, more like an evolution to the final design.
Feedback for the main Country Tracker website, however, is very much appreciated.
see #28 also
consider showing total project cost / spent to date / balance remaining
and either national/subnational/unknown
Some thoughts on prioritisation of elements in the Single Activity view ... https://docs.google.com/spreadsheet/ccc?key=0AjcB8bJJzWppdDR4WWxuTGZaMEp4cG4tWlMwOF9qMlE#gid=0
Are we including the IATI Identifier / Activity Status / Related Documents anywhere on the page or does this go under (etc) at the bottom of the page?
Be good to know what people think - I'm not sure the IATI identifier is of enough interest to users to go at the top/above the fold, but might be worth having lower down? Similarly with activity status, especially if start and end date are prominent? I think related documents should be there in that section lower down
should we make the names of organisations into links to their websites (as/if published in their data)? having a flick through it might be useful in directing users, to help them know who organisations using acronyms are?
Are we talking about the "Who's involved" section?
There are plenty of publishers that fill up activities with links and these are automatically turned into actual links. I totally agree that having links to websites of organisations will be very useful and helpful for directing users but am concerned that this would mean having a separate list of links that needs maintaining and curating in the first place. At least, those are my first thoughts.
We're going to end up drilling down into a single activity at some point. let's try to get some ideas around what this will look like. use the devtracker as an example/starting point. We could start this now.