-
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
Lists tool - Supplied vernacularName, CommonName not retained on upload #246
Comments
Uploaded lists will always have additional columns added. There will always be a problem when the upload file has columns with the same names as the columns added by lists. It would be worthwhile noting this issue on the upload page after a UI review The solution is to rename the conflicting columns before uploading. Please confirm that this works. |
Hi @rosemaryjoconnor - can we close this issue, as I note the related 1004 has been closed? |
@nickdos I'll have a word with Amanda Buyan and see if this is still an issue. |
@nickdos Amanda has done some testing for authoritative lists. As long as vernacularName is used to represent the common name the state gives a species, and then the Common Name (Matched) is what the ALA comes up with. Not the most ideal but is a workaround. She has updated her code and documentation accordingly. |
Lists tool is removing supplied fields such as vernacularName (Vernacular name) and CommonName (Common name) if they are supplied in the upload file. Common name is populated via matching and if either of the above are supplied they are not being retained.
This is problematic for our authoritative lists as supplied fields may be specific to the local region for Conservation or Sensitive data and need to be retained.
Could this please be investigated.
The text was updated successfully, but these errors were encountered: