Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add and Expose Export field for Plant Species #220

Closed
blcampbell opened this issue Jan 27, 2021 · 2 comments
Closed

Add and Expose Export field for Plant Species #220

blcampbell opened this issue Jan 27, 2021 · 2 comments
Assignees
Labels
enhancement Issue is a new feature for the application/database/project

Comments

@blcampbell
Copy link
Contributor

tlu_PLANTS lacks a clear field for identifying which species should be exported in annual data closeout exports.

Add an Export field and expose it in the plants form so that the field can be edited from the database.

@blcampbell blcampbell added the enhancement Issue is a new feature for the application/database/project label Jan 27, 2021
@blcampbell blcampbell added this to the 2021 Pre-Season Updates milestone Jan 27, 2021
@blcampbell blcampbell self-assigned this Jan 27, 2021
@blcampbell
Copy link
Contributor Author

Implemented as a bit-wise (1 or 0) field where 1 means export and 0 means don't export.

Displays as a toggle in the plants form along with a hint which checks for a situation where TSN = TSN_Accepted and Export = 0 which suggests that the species might need to be exported as it is either a single species or species which is a default synonym (i.e. the synonym we want other species to point to).

Here's how this currently looks:

EXPORT
image

DO NOT EXPORT
image

Values are populated based on what is in tlu_PLANTS.

@johnpauls, @abrolis, @lizmatthews03 -
Does this meet the need to provide access to changing which species are exported in end of year exports and should Accepted Found be hidden or made read-only?

@johnpauls
Copy link
Member

This looks great, I like the interface. If I understand how this works, Accepted Found will be determined based on what other data is in tlu_Plants - so it would make sense that it should be read only. For the plants form (not necessarily the underlying tlu_Plants) could there maybe be a different label for Accepted Found - I think it might be confusing to users who aren't familiar with the fields in the table. Maybe Other Accepted Name Found or something like that, so it is reminiscent of the table, but a little clearer as to what it means.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Issue is a new feature for the application/database/project
Projects
None yet
Development

No branches or pull requests

2 participants