search

shcaba / FishPath-updates

Issue tracking repository for the FishPath software
0 stars 0 forks source link

Create additional screen for starting a new fishery #99

Closed dtdougherty closed 5 years ago

dtdougherty commented 6 years ago

Create an input screen that defines the fishery, before a questionnaire is started. It would have users define: species, area, gear, fleet, etc. This would help with 1. making this more formal and easy to walk through in a workshop and 2) would help to store this information for each fishery so that we could use it for things later (maps of all fisheries, analyses).

For now, we could just have a list of check marks, later have fill in that would be stored in database.

serenalomonico commented 6 years ago

Consider an optional field that asks users to state where they got the link. This would help ensure the FishPath team carefully documents all people they share the link with and understand how it's shared.

serenalomonico commented 6 years ago

Also add the time frame: specify if answers will be what you can do now, or what you can do in 5 years.

Additional comments from Natalie's notes: Provide instruction that users have to make an upfront decision about how they are going to assimilate their data, and how they use FishPath to confront their fishery, particularly given multiple fleets/sectors/gears/selectivities. Ideally, a whole-of-stock combined assessment approach across sectors/gears is recommended, using either combined or representative data from one sector, UNLESS the selectivities are incompatible. Generally, the monitoring and decision rule sections should be contemplated separately for each sector/gear/fleet, albeit with the acknowledgement that there will be significant overlap in the questionnaire responses (those that differ can be flagged within the FishPath software for easy reference).

serenalomonico commented 6 years ago

Consider adding: Some kind of ability to ID/state upfront what the current issues are? E.g. in Queensland net fishery, there are literally 100s of pages of input controls, whose sheer volume may undermine effective management.

dtdougherty commented 5 years ago

Based on MRAG report, ensure that the questions also help to categorize fisheries that is useful in the MSC process around categorizing the stock. See "FishPath as an output of a pre-assessment" section of report. Have MRAG or MSC review the questions to ensure they satisfy MSC classifications.

underbluewaters commented 5 years ago

@serenalomonico Can you get me the final list of questions by Feb 2nd? Please include which questions are optional.

underbluewaters commented 5 years ago

Steps:

underbluewaters commented 5 years ago

Something frustrating I'm noticing from this change is that it's going to be hard to consistently display a good title for each response. Right now when we list responses we do so with the "fishery" attribute, but that's made redundant by all this information and I don't think it makes sense to have that field anymore when starting a new fishery. Right now I'm using commonName + geography to form the title for lists and results, with a fallback to the fishery attribute if it's an old and un-updated response. I've made a makeTitle() function that is reused throughout the interface, so it should be pretty easy to change how titles are generated in the future. Depending on how things shake out we might want to generate titles from the commonName + gear type or something else.

dtdougherty commented 5 years ago

Thanks, Chad. Maybe we can just use the current field to populate commonName and then edit manually the first time anyone access that fishery again. They should be prompted to fill out the input form before getting back into the results.

On Tue, Feb 12, 2019 at 11:29 AM Chad Burt notifications@github.com wrote:

Something frustrating I'm noticing from this change is that it's going to be hard to consistently display a good title for each response. Right now when we list responses we do so with the "fishery" attribute, but that's made redundant by all this information and I don't think it makes sense to have that field anymore when starting a new fishery. Right now I'm using commonName + geography to form the title for lists and results, with a fallback to the fishery attribute if it's an old and un-updated response. I've made a makeTitle() function that is reused throughout the interface, so it should be pretty easy to change how titles are generated in the future. Depending on how things shake out we might want to generate titles from the commonName + gear type or something else.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/shcaba/FishPath-updates/issues/99#issuecomment-462900354, or mute the thread https://github.com/notifications/unsubscribe-auth/ALsbBjDiDaFNJ5273lxXqo3d5N7GURFsks5vMxYUgaJpZM4U2xyK .