Field Science issueshttps://code.cs.earlham.edu/groups/field-science/-/issues2019-08-23T10:03:20-04:00https://code.cs.earlham.edu/field-science/FieldDay/-/issues/29Drive API is deprecated by Google and will stop working in December2019-08-23T10:03:20-04:00Craig EarleyDrive API is deprecated by Google and will stop working in DecemberLast year Google deprecated the Drive API we use.
Unlike some deprecations, which scold you when you run "Inspect Code" but continue to work, Google is shutting this down on their side.
[Timeline from the Google Developers website](htt...Last year Google deprecated the Drive API we use.
Unlike some deprecations, which scold you when you run "Inspect Code" but continue to work, Google is shutting this down on their side.
[Timeline from the Google Developers website](https://developers.google.com/drive/android/deprecation):
```
* December 6, 2018: Deprecation is publicly announced. Existing clients will be able to access the API normally, but should immediately commence with migration efforts. New clients must not use the API.
* October 21, 2019: The Drive Android API is removed from the Google Play Services SDK distribution. Apps will be unable to build until removing the Drive Android API dependency, but existing builds will be unaffected. The Drive Android API public documentation will no longer be available.
* December 6, 2019: The Drive Android API is shut down and all connection attempts will be refused. Clients must migrate by this date.
```
There *are* ways to adjust the app to continue using Drive, but we must change it or we won't be able to use it at all in a few months.Craig EarleyCraig Earleyhttps://code.cs.earlham.edu/field-science/FieldDay/-/issues/30Update deprecated dependencies, themes, and environment settings2019-08-05T12:08:41-04:00Craig EarleyUpdate deprecated dependencies, themes, and environment settings[This is an issue to go along with !9 and its branch.][This is an issue to go along with !9 and its branch.]Craig EarleyCraig Earleyhttps://code.cs.earlham.edu/field-science/FieldDay/-/issues/31App crashes if you try to stream without selecting a sector2019-08-23T11:09:39-04:00Craig EarleyApp crashes if you try to stream without selecting a sectorIf you tap "STREAM" (using either internal sensors or Bluetooth platforms) without selecting a sector, Field Day crashes. (The expected behavior is that it does not crash...)
There are at least two possible solutions:
* Pre-populate the...If you tap "STREAM" (using either internal sensors or Bluetooth platforms) without selecting a sector, Field Day crashes. (The expected behavior is that it does not crash...)
There are at least two possible solutions:
* Pre-populate the site and sector fields with default values. This already appears to happen for the site field, although it does not follow up by populating the sector dropdown with a list of sectors associated with that site.
* On user tap of "STREAM", check for empty values in site and sector. Display a message prompting the user to select a value for each empty field. This adds friction but gives the user more transparent control. Similar logic exists already for "SAMPLE", which displays a message prompting the user to enter a spot number before taking a reading, if they have not already done so.Craig EarleyCraig Earleyhttps://code.cs.earlham.edu/field-science/FieldDay/-/issues/32Bring API usages in line with the requirements of Android 10 (SDK 29)2019-09-13T12:07:45-04:00Craig EarleyBring API usages in line with the requirements of Android 10 (SDK 29)Android Q (or 10 or 29 depending on your context) is here, and I want us to keep up rather than catch up.
Several API usage models are going away, and I think it's causing buggy-looking behavior on my Samsung device (though not yet on a...Android Q (or 10 or 29 depending on your context) is here, and I want us to keep up rather than catch up.
Several API usage models are going away, and I think it's causing buggy-looking behavior on my Samsung device (though not yet on a Nexus tablet). When I run a Lint report:
```
* 'getExternalStorageDirectory()' is deprecated
* 'insertImage(android.content.ContentResolver, java.lang.String, java.lang.String, java.lang.String)' is deprecated
* 'getBitmap(android.content.ContentResolver, android.net.Uri)' is deprecated
```
This matches some GIYF investigations on the same topic. Android 10 appears to be taking additional steps to secure user privacy, and one consequence is that we're going to have to fix the way we handle media and external storage.
I'll iterate on this over the next few weeks.Craig EarleyCraig Earleyhttps://code.cs.earlham.edu/field-science/FieldDay/-/issues/33Device rotation while streaming disrupts current data stream2021-02-13T11:16:03-05:00Craig EarleyDevice rotation while streaming disrupts current data streamRotation of the Android device during a stream is buggy.
To replicate this, open Field Day, configure your database, go to "Builtin Sensors", and observe the following:
* User action: Choose site and sector > choose a 1 sec interval > ...Rotation of the Android device during a stream is buggy.
To replicate this, open Field Day, configure your database, go to "Builtin Sensors", and observe the following:
* User action: Choose site and sector > choose a 1 sec interval > touch "Stream" > wait a few seconds > rotate
* Result: stream appears to stop: the button no longer blinks, and after pressing the button again it uses the default 3 sec interval rather than the (visually highlighted) 1 sec interval; control of streaming also becomes confusing, as the streaming entries counter on the Database Actions screen keeps increasing
* Desired result: after rotation, stream continues uninterrupted at the 1 sec interval, button blinks to reflect this, as if we hadn't rotated the screen at all
(It's true that other activities and fragments without so much dynamic content seem to handle rotation fine, but I'd still characterize this as a pretty significant bug - a real "other than that, Mrs. Lincoln..." situation.)
In the short term, we're fine to tell people to do a rotation lock on their device, which I'm guessing has been our pattern. For the long term, let's fix this.https://code.cs.earlham.edu/field-science/FieldDay/-/issues/34No indication when the GPS signal is lost2019-09-21T10:24:05-04:00Tamara BlagojevicNo indication when the GPS signal is lostThere should be some kind of indication when the GPS signal is lost so we know that the drone is not collecting dataThere should be some kind of indication when the GPS signal is lost so we know that the drone is not collecting dataTamara BlagojevicTamara Blagojevichttps://code.cs.earlham.edu/field-science/FieldDay/-/issues/35Rename and add information to the Protocols feature in Notebook2021-04-03T10:13:50-04:00Craig EarleyRename and add information to the Protocols feature in NotebookThere's a collection of features called "Notebook" in Field Day, and it includes Google Drive, "Note Pad", and "Protocols". Currently, "Note Pad" has minimal functionality and "Protocols" has none (for historic reasons that aren't releva...There's a collection of features called "Notebook" in Field Day, and it includes Google Drive, "Note Pad", and "Protocols". Currently, "Note Pad" has minimal functionality and "Protocols" has none (for historic reasons that aren't relevant to the current configuration). This issue is about Protocols.
I propose we add buttons pointing to a few pieces of read-only content to the Protocols section:
- a frequently-asked-questions page
- troubleshooting common problems
- our glossary of terms (currently in Drive)
- maybe move the About and Settings buttons here, off the valuable main screen
Since this strays from some strict lab definition of "protocols", consider renaming it as well.https://code.cs.earlham.edu/field-science/FieldDay/-/issues/36Aggregate the magnetometer data2019-11-19T12:40:25-05:00Craig EarleyAggregate the magnetometer dataThis topic is too broad for a single issue, but I wanted to flag it for discussion and initial script development.
We've talked for a few years about using the magnetometer data that Field Day gathers from the OS as part of the internal...This topic is too broad for a single issue, but I wanted to flag it for discussion and initial script development.
We've talked for a few years about using the magnetometer data that Field Day gathers from the OS as part of the internal sensors function. We should start doing this, as it has implications for several workflows.https://code.cs.earlham.edu/field-science/FieldDay/-/issues/37Consolidate all documentation for how to use Field Day2020-09-30T09:34:34-04:00Craig EarleyConsolidate all documentation for how to use Field DayWe have several documents to the effect of "how to use Field Day". That can get confusing. We should centralize those here - the README for general users, and maybe a CONTRIBUTING page for developer notes that are appropriate for public ...We have several documents to the effect of "how to use Field Day". That can get confusing. We should centralize those here - the README for general users, and maybe a CONTRIBUTING page for developer notes that are appropriate for public visibility - to simplify our lives.https://code.cs.earlham.edu/field-science/FieldDay/-/issues/38Add a trip-site-sector-spot on the fly2020-01-16T13:47:15-05:00Craig EarleyAdd a trip-site-sector-spot on the flyI could imagine a situation where we're in the field and discover we want to take a Field Day reading somewhere that doesn't match an existing trip-site-sector-spot.
Right now, I think we have to do that on the server side. It may be us...I could imagine a situation where we're in the field and discover we want to take a Field Day reading somewhere that doesn't match an existing trip-site-sector-spot.
Right now, I think we have to do that on the server side. It may be useful to do it in the field just like we do everything else.
One possible approach among many: "Add a site", for example, could be added to the site dropdown. (Adding a trip could be trickier.)https://code.cs.earlham.edu/field-science/FieldDay/-/issues/39Integrate ground control points into Field Day's location data2020-01-24T14:48:48-05:00Craig EarleyIntegrate ground control points into Field Day's location dataThis might be in the form of scanning a QR code, detecting it based on GPS location, or something else.This might be in the form of scanning a QR code, detecting it based on GPS location, or something else.https://code.cs.earlham.edu/field-science/FieldDay/-/issues/40Develop process for retrieving images from device2020-02-08T09:57:58-05:00Craig EarleyDevelop process for retrieving images from deviceWe should have a process for retrieving sample spot images in Field Day at the same time as a user uploads data or clears local storage. This includes documentation.We should have a process for retrieving sample spot images in Field Day at the same time as a user uploads data or clears local storage. This includes documentation.https://code.cs.earlham.edu/field-science/FieldDay/-/issues/41Sample spot image file names should be auto-generated, not user entered2020-02-11T09:11:17-05:00Craig EarleySample spot image file names should be auto-generated, not user enteredSample spot image file names should be auto-generated, not user entered, i.e. site-sector-spot-type-date.pngSample spot image file names should be auto-generated, not user entered, i.e. site-sector-spot-type-date.pnghttps://code.cs.earlham.edu/field-science/FieldDay/-/issues/42Database upload should check for sample spot images and upload those too2020-02-11T09:12:51-05:00Craig EarleyDatabase upload should check for sample spot images and upload those tooDatabase upload should check for sample spot images and upload those too, possibly via Postgres to an external file?Database upload should check for sample spot images and upload those too, possibly via Postgres to an external file?https://code.cs.earlham.edu/field-science/FieldDay/-/issues/43Test Slack integration2020-04-29T10:07:36-04:00Craig EarleyTest Slack integrationThis issue will test Slack integration. It will be closed immediately.This issue will test Slack integration. It will be closed immediately.https://code.cs.earlham.edu/field-science/FieldDay/-/issues/44Discussion and notes: user interface and feature ideas2021-02-08T11:05:33-05:00Craig EarleyDiscussion and notes: user interface and feature ideasWe need to sort these. Many of these bullet points could become issues, but I am mainly using this is a heap where I can dump the information.
Some of our ideas. Some have issues associated with them already.
1. Move the sampling stuff...We need to sort these. Many of these bullet points could become issues, but I am mainly using this is a heap where I can dump the information.
Some of our ideas. Some have issues associated with them already.
1. Move the sampling stuff to the front screen
2. Scrolling
3. Brighter buttons, more muted backgrounds (including gray rather than bright colors)
4. Bigger buttons
5. Less on any one screen? So split DB actions into multiple screens, for example
6. Linear user flow: database -> platform -> sample (or platform -> sample -> DB)
7. Gestures?
8. Rotation #33
Other stuff
dark mode?
```
setContentView(R.layout.activity_database_actions);
View someView = findViewById(R.id.databaseStatus);
// Find the root view
View root = someView.getRootView();
// Set the color
root.setBackground(getDrawable(R.drawable.background_dark));
```
Navigation (unordered)
* Get a toolbar that can take you to the things you rarely need:
* Settings
* About
* Sensors are the big-ticket items, they get most of the real estate under that
* Database setup and lab notebook are beneath them
* Other
* NavigationUI
* ActionBar
more ideas
* automated unit tests?
* revise data model/re-architect # some notes: two columns: headstream, varchar(5) - sampleunitid, integer (taking the place of spot or stream id)
* license
* take picture of spot, where a spot’s image includes the 3 flags where we’re digging - picture may also include surrounding area, want to correlate images to the data from microbial sampling
* bad idea to have CREATE statements in code a la ReadingsDatabase?
* 2. Fieldday_Streaming_GIS table, with geopoint, is not used
* Postgres fieldday_streaming_gis table
* We should add the geopoint to the fieldday_streaming table
* compute geopoint based on lat and long columns
* mutually_exclusive_group?
* document our testing
* Test elevation streaming
* Leave, walk downstairs, go to the rock, come back
* Or, leave, go to the first crack in the sidewalk at the 4-way stop at public safety where there will be the top of a 2x2 with a nail
* quality control
* rotations
* no sector is displayed but the device will still stream when the button is pressed
* maybe a display problem not a data problem? streaming data appears to be collected
* also the stream button doesn’t blink
* but we get a weird runaway streaming problem where I can’t seem to stop the streaming after a rotation
* Field Day crashes on erasing local database if you have already done so
* Can’t select a sector with the default site, have to change it to get the sector dropdown active
* Number of values each sensor returns
* some return 1,2,3, etc. values
* we don’t do a good job of detecting the number of values in-place
* UX questions
* What do people do? Is there an order?
* Display aggregates - what kinds? count of reads/streams? mean/median/mode/range? lat/long/times start/stop? can there be a map?
* Global settings, or settings changed rarely (e.g. databases)?
* What devices? Is this mainly a tablet app, phone app, or both? (I think both)
* Documentation: "As previously mentioned, the map() function uses integer math. So fractions might get suppressed due to this. For example, fractions like 3/2, 4/3, 5/4 will all be returned as 1 from the map() function, despite their different actual values. So if your project requires precise calculations (e.g. voltage accurate to 3 decimal places), please consider avoiding map() and implementing the calculations manually in your code yourself."
* [Storage Access Framework](https://commonsware.com/blog/2019/06/07/death-external-storage-end-saga.html)https://code.cs.earlham.edu/field-science/FieldDay/-/issues/45Fix the way we do uploads2021-02-08T11:10:28-05:00Craig EarleyFix the way we do uploadsGathering field data works, but we get a lot of buggy behavior around uploads.
After an upload of, say, X streaming and Y reading rows, we still see X and Y as the local database status. Our understanding should be that, once we’ve uplo...Gathering field data works, but we get a lot of buggy behavior around uploads.
After an upload of, say, X streaming and Y reading rows, we still see X and Y as the local database status. Our understanding should be that, once we’ve uploaded them to the central database, those rows are no longer "local" to the device only.
There are a few possible solutions, and we should discuss them:
1. Completely re-do database setup after each upload - we might then relabel “Upload” as “Upload and sync”. I mildly favor this approach over the others.
2. Auto-sync everything whenever we have Internet.
2. [I think this approach is rejected.] Re-sync the uploads database only. This presents challenges for consistency: on initial setup, we have a complete clone of the subset of the database that’s relevant to our chosen trip. If we merely bring back the timestamp, our uploads would be consistent but nothing else.https://code.cs.earlham.edu/field-science/FieldDay/-/issues/46Crash on tapping the bench sample picture button2021-03-10T10:27:00-05:00Craig EarleyCrash on tapping the bench sample picture buttonText of logcat message will be in the comments.Text of logcat message will be in the comments.https://code.cs.earlham.edu/field-science/FieldDay/-/issues/47Rearrange and rephrase UI buttons2021-04-03T10:12:40-04:00Craig EarleyRearrange and rephrase UI buttons[See this photo of the new layout (the whiteboard text on the right)](/uploads/0e2744b4a152f3d4bba5543fe14ea803/field-day-ui-revise.jpg)[See this photo of the new layout (the whiteboard text on the right)](/uploads/0e2744b4a152f3d4bba5543fe14ea803/field-day-ui-revise.jpg)https://code.cs.earlham.edu/field-science/images/-/issues/11Remove API key from web-image-display/imageThumbnails.php2021-12-08T08:49:46-05:00Porter LibbyRemove API key from web-image-display/imageThumbnails.phpShould be included in a config file or envShould be included in a config file or env