Randomised sequence of data quality test results in CSV data output

[GoogleCodeExporter]

Reported by user wanting to do periodic manual exports from ALA to import into 
a local system for mapping and analysis.

The sequence of columns for DQ test results is inconsistent in the CSV output 
between different download events. Client is finding this makes processing on 
his end difficult.

Original issue reported on code.google.com by CoolDa...@gmail.com on 19 Dec 2013 at 1:02

[GoogleCodeExporter]

How is the user donwloading the records?

There is a way to stop the DQ from being included in the downloads.  We don't 
expose it as an option in the biocache/hubs/spatial portal webapps.

The biocache-service allows for the DQ to be turned off using a URL of the 
following format:
biocache.ala.org.au/ws/occurrences/index/download?q=data_resource_uid:dr364&qa=n
one&reasonTypeId=10

The &qa=none prevents the data quality from being included in the download.

Original comment by natasha....@csiro.au on 19 Dec 2013 at 3:32

[GoogleCodeExporter]

Not sure Natasha. He does find the DQ results useful, so switching off is 
probably not the best option. He was just asking if we can make the sequence of 
columns consistent in outputs.

Original comment by CoolDa...@gmail.com on 20 Dec 2013 at 10:41

[GoogleCodeExporter]

The other option is for him to decide which data quality fields he wishes to 
include and specifying them in the order he wishes to see them:

Example:
http://biocache.ala.org.au/ws/occurrences/index/download?q=data_resource_uid:dr3
64&reasonTypeId=10&qa=decimalLatLongConverted,invalidCollectionDate,speciesOutsi
deExpertRange,stateCoordinateMismatch,invalidScientificName

This is not exposed in the biocache/hubs UI.  At the moment it is only 
available as a webservice call. This field is documented in the download 
section of the biocache documnetation: 
http://biocache.ala.org.au/ws

Maybe we need to expose this in the Download dialog to allow users to decide 
which QA fields it include.

Original comment by natasha....@csiro.au on 22 Dec 2013 at 9:50

[GoogleCodeExporter]

There are 2 components to this issue:

1) Ensure that when no &qa param is provided the DQ fields are in the same 
order each time the exact same download is performed. 

2) In hubs-webapp expose a selection of download fields and QA's for the user 
to select in the Download dialog.

Original comment by natasha....@csiro.au on 23 Dec 2013 at 12:00

[GoogleCodeExporter]

Component 1) in comment #4 is on dev

Original comment by natasha....@csiro.au on 24 Dec 2013 at 1:44