Some design choices documented about how hierarchy is decided
Some design choices documented about how hierarchy is decided

file:b/usage_notes.php (new)
--- /dev/null
+++ b/usage_notes.php
@@ -1,1 +1,22 @@
+Organisational Data Sources
 
+http://www.comlaw.gov.au/Browse/Results/ByTitle/AdministrativeArrangementsOrders/Current/Ad/0 defines departments
+Agencies can be found in the Schedule to an Appropriation Bill (budget), Schedule to FMA Regulations and/or Public Service Act.
+
+http://www.finance.gov.au/publications/flipchart/docs/FMACACFlipchart.pdf summarises these
+
+When defining the hierachy, this system is designed towards monitoring accountablity. Thus large agencies that have registered their own ABN 
+and have their own accountablity mechanisms/website recieve a seperate record as a child of their department.
+Some small agencies will choose to simply rely on their parent department's accountablity measures.
+
+This flows through to organisation name and other/past names. A department that accounts for an agency will list that agency as an other child name.
+As agencies themselves shift between departments, there may be scope for providing time ranges but typically the newest hierarchy will be the one recorded.
+A department/agency name will be the newest active name assigned to that ABN.
+
+Statistical information from http://www.apsc.gov.au/stateoftheservice/1011/statsbulletin/section1.html#t2total https://www.apsedii.gov.au/apsedii/CustomQueryx33.shtml
+
+Open Government Scoring
++1 point for every true Has... attribute
+-1 point for every false Has... (ie. Has Not) attribute
+
+