* Renamed verified to good
* Renamed no_data to bad
* Add failed status
* Remove unused data_not_verified
* Expose vetted status to API
* Simplify vetted status template markup
* Simplify vetted methods
* Utilize sass for vetted statuses
* Add option to undo vetting
* Fix call2action mobile behavior
* Make call2action a bit transparent
* Disable map panning on touch interfaces
* Hide Mapbox logo (attribution is enough)
* Add on_delete option to all ForeignKey fields
* Adjust all views
* Adjust initialize command
* Refactor tests
* Refactor API to make these changes transparent
* Adjust all templates
* UI refreshment on Observation tepmplate
* Add STRICT_TRANS_TABLES for mariadb
* Minor text changes to tle command
* Update requirements
The satellite modal that was tested in the observation view works
great! This commit adds the similar link everywhere else a
satellite is listed in a table so we have a consistent UX.
In the observation view there is only one satellite referenced,
making the modal a 1:1 mapping. As there are multiple satellites
in the table view we pull this modal in multiple times. To cut
down on possible load times getting out of hand I'm limiting the
number of rows you'll see in the home page and observations view.
I don't quite feel this iterative import approach is the best.
Feel free to decline this if there is a better way (.js it?)
Model change (with migration 0006) adds 3 fields to Data:
vetted_status (charfield with options for data status, default "unknown")
vetted_user (who vetted the data)
vetted_datetime (when it was vetted)
In addition, various boolean functions are added for the Data model
to check statuses. More functions are added to the Observation model
to check status of verification within an observation as well, assuming
multiple data entries in an Observation. With these, I also changed
"has_data" to "has_submitted_data" to be more specific alongside the
others.
For UX, we add a green check sign or red removal sign to the data
header in Observation view (along with green/red datetime in the footer)
if a data is verified good or bad, respectively. If there is an unknown
status, the data header is given a thumbs-up and thumbs-down button to
verify the data good or bad. These icons are only offered to is_staff,
the observation requestor, and any station owner in the observation.
These buttons trigger new URLs/functions in view:
data_verify(id)
data_mark_bad(id)
Returning the user back to the originating Observation page.
In the observation lists I changed the coloring of the ID button to be:
Future: light blue (same)
No uploaded data and/or all vetted bad data: red
Some or all unvetted data with no verified good data: orange
Some or all verified good data: green
These changes are reflected in the observations.html, home.html, and
user_detail.html templates.
solves satnogs/satnogs-network#171
Nikos Roussos