Make venue_info a (configurable) select #109
Open
+192
−8
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Expecting users (even administrative ones) to look up a venue info code on a web page and then enter it into a blank-allowed field means we rarely get venue info completed.
This converts the venue_info fields into drop-town selects, based on the normative categories from IEEE Std 802.11-2020 table 9-65 (the latest publicly accessible version). It also changes the default value from blank to 0,0 (unspecified).
The VENUE_INFO data is placed in
djnro/settings.py
to make it easier for DjNRO admins to expand or localise the list if they need to. However, we probably shouldn't be encouraging people to change the IEEE values (or even translate them?). There's a note to that effect in settings.py, and the config is deliberately omitted from local_settings.py.