-
Notifications
You must be signed in to change notification settings - Fork 7
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
# Feat/Fix lat/long in CSV export and add new fields ## JIRA Ticket [BSS-380](https://jira.csiro.com/browse/BSS-380) ## Description CSV export extracts latitude and longitude for GPS locations as separate columns as well as including the JSON fragment. These values were switched in the current implementation. ## Proposed Changes - Fix the order of lat/long in GPS points - Add similar export code for map locations as long as they are points - Add GPS accuracy as a separate column (user request) - Add 'created' and 'created_by' fields in export - Fix a bug that hangs CSV export when there are no records (or all records are deleted) Note that the late of these involved making a change to an index used to access the database (the recordRevisions index) to include the created_by field (created was already there). This means that we won't see created_by for any existing notebooks unless we can update the indexes (not currently implemented). It will show for any new notebooks ## How to Test Create a new notebook (to get the new index) that includes GPS location and/or Map fields. Create some records in the app. Then go to the notebook page on Conductor and export the data as CSV. The resulting CSV file should include created, created_by and the lat/long/accuracy fields for your GPS points. Try exporting from a notebook with no records, should get a CSV with just a header line. ## Checklist - [x] I have confirmed all commits have been signed. - [x] I have added JSDoc style comments to any new functions or classes. - [x] Relevant documentation such as READMEs, guides, and class comments are updated.
- Loading branch information
Showing
4 changed files
with
53 additions
and
6 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters