Stemming from Toby Patterson's (CSIRO) email in which he says that he wants to set up R scripts (that will have to be updated regularly) to access data stored in the ATF database for a given project.
I pointed out to him that this kind of direct access to detection data is currently only possible for the QC'd dataset published on the AODN portal via Geoserver capabilities. Publishing the raw detections on the portal, as described in #249, would give users the ability to do so for public data.
An alternative approach would be to create three views in the database (one for detection data, one for tag metadata, one for receiver deployment/recovery metadata), and configure user access to those so that they can only query public data or data for projects they're member of.
Stemming from Toby Patterson's (CSIRO) email in which he says that he wants to set up R scripts (that will have to be updated regularly) to access data stored in the ATF database for a given project.
I pointed out to him that this kind of direct access to detection data is currently only possible for the QC'd dataset published on the AODN portal via Geoserver capabilities. Publishing the raw detections on the portal, as described in #249, would give users the ability to do so for public data.
An alternative approach would be to create three views in the database (one for detection data, one for tag metadata, one for receiver deployment/recovery metadata), and configure user access to those so that they can only query public data or data for projects they're member of.