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

Support additional fields usable by name matching #67

Open
adam-collins opened this issue Feb 29, 2024 · 0 comments
Open

Support additional fields usable by name matching #67

adam-collins opened this issue Feb 29, 2024 · 0 comments
Assignees

Comments

@adam-collins
Copy link
Contributor

Out of the box, after migration, this is not working as expected.

For example these dr18406 and dr18404 list items were not matched after migration. The initial assumption is because kvpValue "family" is not used in the search.

  • Andersonia sp. Mitchell River (B.G. Hammersley 925)
  • Cooktownia
  • Corybas
  • Cymbidium
  • Dendrobium discolor x D.nindii
  • Dendrobium kingianum x D.speciosum
  • Dipodium
  • Eutaxia sp. North Ironcap (P. Armstrong PA 06/898)
  • Helicteres sp. Beverley Springs (R.L. Barrett RLB 750)
  • Liparis
  • Luisia
  • Macrozamia lomandroides x M.pauli-guilielmi
  • Microtis
  • Orthoceras
  • Pachystoma
  • Phalaenopsis
  • Pholidota

This is important for sds consistency.

specieslist-webapp "family" kvpValue is exported with a duplicate column header by /downloadList. Maybe add prefix "raw." to distinguish between matched family and raw item family.

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