Predict what prioritization to give a mission in a datalist

[MBARIMike]

From the Use Case document:

See what data or processing issues should be considered. Predict what prioritization to give a mission in a datalist.

Footnote:

For now, quality assessment is proposed as a comment field where a list of issues could accumulate. It also could be a suggested order of magnitude for datalist prioritization. Our issue tracking could be expanded to include specific metrics, as done by the Rolling Deck to Repository (R2R) database. A user can always change the prioritization for a survey in their own gridding datalist.

[jbpaduan]

To grab this auto-magically, use the prioritization for it that's used in a recent datalist (3rd column...1st is the path, 2nd is the format code, 3rd is priority for gridding). The awkward thing about this idea is that by default, prioritization is the value of 1. But when something is wished to be used at higher priority, we've been giving it orders of magnitude greater value, so a value of 1 might actually mean lower priority.

[MBARIMike]

Does this information populate a field in the database?

[jbpaduan]

I was just mulling about how to grab the info with a look-up script. Not sure it's a good idea to do so this way. The new Mission table booleans for "failed" "testing" etc could be increased to include some yes/no indication that a survey could be used but with caution. That would allow it to be a field by which one could filter a search or trigger a red alert on the Mission Details page, without requiring a specific value or string. The quality_comment field could be where the reason why the mission is to be used with caution is given.

[jbpaduan]

Building on the previous comment, for datalists (which should be structured like
survey_directory/datalistp.mb-1 -1 priority_value
where priority_value is how much priority the gridding algorithm should give the survey's data),
please assign to each quality_category the following priority_value:
production_survey = 10000.0
use_with_caution = 100.0
failed_survey and test_survey should not appear in the datalist unless it also has production_survey or use_with_caution associated with it.
The most recent repeat_survey should take the priority value of production_survey or use_with_caution, as appropriate
Older repeat_survey = 1.0
never_run obviously should not appear in the datalist.