ToDo

ToDo List

• Single login for the main web site and the phppsqladmin site (Wiki already shares the login) (april 2011)

• Guest account: we shoud have a guest account with password "guest" with very restricted access, but who can see for example birdview with the tracks of one or two ('donated') birds. (may 2011)
  • Note: this account should have very limited rights, and should not be able to change the own password (otherwise one guest could make it impossible for other guests to see the site)

• BirdView: I noticed that the upload option for kml files from a local directory includes kml only, can we extend the support to kml and kmz files? The http upload does actually support both. (april 2011)

• List of access rights: user's rights must be set consistently to make sure that all users have the correct rights to see data (april 2011);
  • add a description of the user's rights fields, instead of the database names for rights (may 2011)

• Quality control: How do we flag datapoints in the quality control field of the GPS data (april 2011)

• QC & functions: If I query only a subset of data (say data approved from QC), will the distance and direction functions work on the subset, or will they still use all points? (april 2011)

• Can we upload tables to the database (for example to our personal schemas?). For example, we would like to flag gps points with behaviour classes based on our accelerometer data and then store this information so that it can be reused. Is there any way you can facilitate this process. Otherwise analysis has to be rerun locally every time, which is very time consuming. (april 2011)

• Initial view should be Waddenzee, not The Netherlands or Europe (march 2011)

• Accelerometer data: We need to discuss the accelerometer data, based on the current data model, we cannot properly sort accelerometer measurements that are not coupled with a GPS fix, thus I think we need to add an extra field in the accelerometer table. (march 2011)

• View/function to identify foraging trips

• Update speed function to account for userflag (december 2010)

• Create Flagging facility for invalid tracking data (december 2010)

• Fix UvAGPS KMZ generator (color range, symbol selection) (november 2010)

• Make a readonly copy of Flysafe Wiki on public server (september 2010)

• Improve UvA GPS parser to log errors such as CRC8 in database (september 2010)

• Implement service to create graphs for UvAGPS devices according to Willem's Matlab scripts ( october 2010)

• Import UvAGPS log files via standard storage facility ( november 2010)

• Implement generate KML service for for UvAGPS on public server (october 2010)

• Define and implement service to flag invalid GPS tracks (november 2010)

• Add accelerometer calibration factors to uva_device (september 2010)

• Import UvAGPS metadata. (november 2010)

Finished

• Data upload: Birds are starting to return from migration and we have a lot of new data to upload to the database from our various base stations. Currently data can still be uploaded manually via winSCP as we did last year. However we discussed that we need to automate this procedure. How should we handle the data upload now and in the coming period. Our new field season is also beginning. Will digital drop box work or do we use iRODS, please let me know what is best. If we need a separate short and long term solution that’s fine, but I really need this new data uploaded to the database. (26/04/2011) iRODS is currently running and being monitored by Lykle, is a temporary solution an replacement is being sought

• Student access: We have several students that need access to the flysafe server for their thesis projects, specifically to the GPS and ECMWF schemas. I think you mentioned that people with a user name and login can access the server from any of the IP addresses in IBED, is this still the case? Below are the student names, their e-mail address and the period they should be provided access. If you need any additional information let me know. I can distribute their user names and passwords to them if you like. (26/4/2011 will be arranged by Lykle)

• Metadata: How should metadata be uploaded and updated. Currently excel files are sent to SARA, should we continue this way or is there another solution. How do we update these files once they are uploaded? (march 2011)

• List of user's rights: a script was written to quickly produce an overview of all users and their rights (12-05-2011)