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

Pick LocID in data entry fills only Specific Locality #307

Open
cjconroy opened this issue May 2, 2024 · 3 comments
Open

Pick LocID in data entry fills only Specific Locality #307

cjconroy opened this issue May 2, 2024 · 3 comments

Comments

@cjconroy
Copy link

cjconroy commented May 2, 2024

Someone I work with created a locality ID, used that number in data entry and was confused when only the specific locality populated on the screen, even though the locality has higher geography, elevation, lat longs, etc. Is it a glitch that they don't populate? Or could that be done?

@cjconroy cjconroy added the bug label May 2, 2024
@dustymc
Copy link
Contributor

dustymc commented May 6, 2024

@cjconroy
Copy link
Author

cjconroy commented May 6, 2024

I'm not sure exactly what I am supposed to get from that link. I see the text "Use the pull/sync locality button to view the data that is included in the Locality. If you find that you have chosen the wrong locality name, then you can use the clear all locality button to remove any Locality data and start over." I don't have that button on my data entry screen. Should I?

@dustymc
Copy link
Contributor

dustymc commented Jul 2, 2024

Ah thanks.

Pick by the (ephemeral) ID is there for horrible legacy reasons. It shouldn't be used for any purpose by anyone.

Turn on locality name and you'll get both a stable handle and some more controls.

@dustymc dustymc removed the bug label Jul 22, 2024
@dustymc dustymc transferred this issue from ArctosDB/arctos Aug 20, 2024
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

2 participants