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

Force tree definition filter in Taxon QCBX Query Builder search #6153

Open
sharadsw opened this issue Jan 24, 2025 · 0 comments
Open

Force tree definition filter in Taxon QCBX Query Builder search #6153

sharadsw opened this issue Jan 24, 2025 · 0 comments
Labels
1 - Bug Incorrect behavior of the product 1 - Enhancement Improvements or extensions to existing behavior geospecify
Milestone

Comments

@sharadsw
Copy link
Contributor

Follow up to #6142

#6142 adds a default mapping line to the query builder search which filters on the tree definition associated with the selected COT. Theoretically, this mapping line could be removed from the search after which the query would return Taxon names from all Taxon trees. This can lead to saving a CO with a Determination -> Taxon that is not associated with the selected COT.

Solution:
A solution to this would be to force the filter in the query builder search regardless of whether the default mapping line exists or not.

The QueryBuilder should have access to the COT's tree definition through the TreeDefinitionContext in QCBX.

<TreeDefinitionContext.Provider value={treeDefinition}>

@sharadsw sharadsw added 1 - Bug Incorrect behavior of the product 1 - Enhancement Improvements or extensions to existing behavior geospecify labels Jan 24, 2025
@sharadsw sharadsw added this to the GeoSpecify v2 milestone Jan 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1 - Bug Incorrect behavior of the product 1 - Enhancement Improvements or extensions to existing behavior geospecify
Projects
None yet
Development

No branches or pull requests

1 participant