-
Notifications
You must be signed in to change notification settings - Fork 21
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
Missing taxons, genus, phylum, class, order etc when importing list from a file #279
Milestone
Comments
qifeng-bai
added a commit
that referenced
this issue
Oct 9, 2023
qifeng-bai
added a commit
that referenced
this issue
Oct 9, 2023
qifeng-bai
added a commit
that referenced
this issue
Oct 10, 2023
qifeng-bai
added a commit
that referenced
this issue
Oct 24, 2023
qifeng-bai
added a commit
that referenced
this issue
Oct 25, 2023
qifeng-bai
added a commit
that referenced
this issue
Oct 25, 2023
qifeng-bai
added a commit
that referenced
this issue
Oct 25, 2023
qifeng-bai
added a commit
that referenced
this issue
Oct 25, 2023
qifeng-bai
added a commit
that referenced
this issue
Oct 25, 2023
1, Bump up to 4.5.3 snapshot 2, Use original vernacular name in KVs 3, Store original taxon to KVs
qifeng-bai
added a commit
that referenced
this issue
Oct 26, 2023
1, Bump up to 4.5.3 snapshot 2, Use the header names (vernacular name)in uploaded file as key of KVs 3, Fixed issues caused by missing values
qifeng-bai
added a commit
that referenced
this issue
Feb 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@charvolant reports a number of columns missing in KVPs when uploading a species list.
For example:
When a name is matched,
Scientific Name (matched)Common Name (matched) | Family (matched) | Kingdom (matched) will be replaced
other fields which currently are missing, e g.
Taxon Rank | Genus| raw Phylum | raw Class | raw Order etc
Also expected to see:
raw Kingdom | raw Family etc
See examples:
Doug's workaround:
https://lists-test.ala.org.au/speciesListItem/list/dr21996?max=10
Other changes
Store the original header names as keys, no more camelcase conversion, (Required by Doug) e.g.I
In previous version,
"commName" is also converted to "vernacular name"
"profileNo" is converted to "profile no"
And we accept the different variants of "vernacular name", such as "commonName, common, vernacular..". In new version, we still interpret this way, we store the 'original name' as key of KVs.
The text was updated successfully, but these errors were encountered: