Updates for 5 tickets for December work

[JamesBisese]

This contains updates for issues 160, 172, 182, 189, and 192.

I have sent status reports elsewhere, but I am copying them here

#1 Usability suggestions Usability

#160

There are 3 separate items in this issue. 2 of the 3 are completed.

On the tab 3. Flag the table displayed can be sorted by any column
Moving between tabs - an improved 'Back to Top' button has been added that users can hit to cause the tab-bar to come back into view.
'Add visual separation' - This is NOT addressed. This one is open-ended. I can easily make suggested UI improvements, but I'm not a designer and don't see an obvious fix.

#2 Add feature so a user knows their download is coming and they should not to hit the button more than once

#172

This issue is fixed. The application locks the screen during download of files to the users computer and prevents the user from being able to hit download while a file is being downloaded.

#3 NA MeasureQualifierCode

#182

This issue is fixed. The original error no longer occurs.

But a new error now happens. I created the new ticket

Fatal error when uploading XLSX file "object 'TADA.MultipleOrgDupGroupID' not found"

#199

#4 Testing and UI update required to display effect of applying Over-Detect censor to data frame.

#189

This issue is not resolved. Changes made by Christina seem to interfere with what I had previously completed, and although I merged the changes successfully the behavior is not stable.

I added screenshots and explanations to the ticket.

#5 Explore Tab will crash if too many sites are selected

#192

This issue is fixed. I just needed to change the data source of a select list to 'server' - which is how many other lists in the app are configured.

In addition, I created 2 other issues for things I found during my work

Fix CSS that is causing left-side of TADA Shiny app to touch left-window margin

#198

This is a simple fix to improve the layout of the app

Re-running 1. Load > Query Now results in instable session state

#196

This is a bigger issue - that the UI allows loading new data but does not handle the state of all the tabs and buttons and charts to reflect the change in processing status.

[wokenny13]

#182

In regards to this issue, I am also seeing the issue with
TADA.MultipleOrgDuplicate = ifelse(is.na(TADA.MultipleOrgDupGroupID), "N", "Y")

when loading in other example datasets

[wokenny13]

For usability issue #160, if a user selects any Flag Reason to Switch 'On' to flag for removal, and if a user then proceeds to try to sort by any column. For example, if a user wants to toggle on "Coordinates are imprecise (less than three decimal digits) (see TADA.SuspectCoordinates.Flag)" and then they sort by 'Results affected', that toggle then gets deselected.

I think it would be good if it's the case when a user selects to toggle a flag, if they were to then sort, the toggles that they've chose would stay the same.

[cristinamullin]

For usability issue #160, if a user selects any Flag Reason to Switch 'On' to flag for removal, and if a user then proceeds to try to sort by any column. For example, if a user wants to toggle on "Coordinates are imprecise (less than three decimal digits) (see TADA.SuspectCoordinates.Flag)" and then they sort by 'Results affected', that toggle then gets deselected.

I think it would be good if it's the case when a user selects to toggle a flag, if they were to then sort, the toggles that they've chose would stay the same.

I agree - I created a separate issue to address this later: #201