Add attributions for all data used.

[pserwylo]

Leaflet.js has built in support for showing attributions. However it may be better to actually include it in the footer of the main page (or at least something linked to from the footer). That way, a more comprehensive discussion of the data being used can be made available.

Currently, there is:

• Census data
• Amaze data
• ABS LGA data
• OSM data (already attributed in the map interface)

I believe that is all, but I may be missing something

[BenSpecht]

Within the JSON data, is there anything in there that we could use as an attribution so we don't have to manually write it for each set of data?

[pserwylo]

Your general principle is good. We'd have to have a table in the database, and then build our own methods in django for retrieving that data. There may well be a way in the geoJSON spec for returning attributions for geographic data, but we'd also want to attribute arbitrary other data, for which relying on an existing spec like geoJSON is probably not worth it.

It is all part of the process of making it easier for admin users to import datasets without manually munging the data directly into the database. Think a form that says:

• Click here to upload a new dataset
• Name your dataset
• Enter an attribution
• Select the columns of interest
• Name the columns and give them descriptions for users.

The whole process is quite large, but definitely worth it in the long run. In the mean time, perhaps staticly coding them in the template will suffice.

[logworthy]

We have the model in the Django database for Attributes. I think the purest approach would give Attributes a Table relation, and then Tables might have some attribution notes as a field -- or link to a Source object which had attribution notes. (Though we may want to review our architecture more holistically.. I might raise that as another issue.)

But yeah, I think just coding up a 'data sources' page is a good interim solution.