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 status field for vascular plant species records #275

Open
Sam-Amy opened this issue Mar 8, 2024 · 6 comments
Open

Add status field for vascular plant species records #275

Sam-Amy opened this issue Mar 8, 2024 · 6 comments
Milestone

Comments

@Sam-Amy
Copy link

Sam-Amy commented Mar 8, 2024

On the iRecord website vascular plant form (https://irecord.org.uk/enter-vascular-plants) we currently have the option to record a 'Status' against each species record. Could this be implemented on the app alongside the existing vascular-plant specific fields?

The options provided in a dropdown list should be:

not recorded
native - origin unknown
introduced - accidental
introduced - accidental - regenerating
introduced - intentional
introduced - intentional - regenerating
introduced - origin unknown
introduced - origin unknown - regenerating

@kazlauskis
Copy link
Member

The mobile app has a Plant Survey feature that uses the same web form. It appears that the terms have been updated. Do you want us to update the Plant Survey choices to match the new terms, or is this ticket regarding the addition of these stage options to the general survey in the app?

@Sam-Amy
Copy link
Author

Sam-Amy commented Mar 14, 2024

Yes please to update the Plant Survey choices to match the new terms; the ones above are BSBIs current preference. Thanks

I think it would be ideal if the vascular plant-specific fields came up in the general survey in the app when a species is selected (as they do for bryophytes), but @DavidRoy would have to confirm how much of a priority. Would this be a big job to implement @kazlauskis? Thanks

@kazlauskis
Copy link
Member

No, this is a small task if we bundle it with some other changes to the app. Note, I won't have the capacity to work on the app any time soon.

@Sam-Amy
Copy link
Author

Sam-Amy commented Apr 18, 2024

Are there any implications when you update these for data already entered in this survey under the previous terms? @kitenetter I think you said at least for similar changes on iRecord website surveys there might be? Thanks

@kitenetter
Copy link
Collaborator

@Sam-Amy I think it depends on how things are changing, e.g. if existing terms are being edited, or new terms are being added, or old terms are being deprecated. All those options are possible but there may be different implications depending on what is being proposed.

@Sam-Amy
Copy link
Author

Sam-Amy commented Apr 18, 2024

In this case, we want to add new terms and deprecate the old ones (so they are not available for data entry any more), but of course keep any previous data containing those original terms.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants