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

Import of vernacular names not working #6628

Open
poospiza opened this issue Feb 28, 2023 · 0 comments
Open

Import of vernacular names not working #6628

poospiza opened this issue Feb 28, 2023 · 0 comments
Labels
status: triage this needs sorting and proper labelling type: bug this describes something that isn't working

Comments

@poospiza
Copy link

poospiza commented Feb 28, 2023

Describe the bug
Vernacular names of taxons are displayed incorrectly on the page Overview in the section Nomenclature

To Reproduce
As an example I want to add the vernacular names in Italian and English to an existing taxon page in Scratchpads.
I use the excel file template downloaded from Scratchpads. I have added one row with metadata, including vernacular name in two languages of one species (Canis lupus). I import into the taxonomy "Fauna Checklist La Selva":

I navigate to Import--> Taxonomy --> Excel File Import-->Select vocabulary-->Fauna Checklist La Selva
I browse to the attached file Taxon_Canis_lupus.xlsx and run the import.
The import completes without any problem. Message: Updated 1 taxonomy term.

See error
Using the species Wolf/Lupo, Canis lupus as example
https://ethoikos.myspecies.info/fauna-checklist-la-selva/canis-lupus
The vernacular names in Italian and English are displayed incorrectly on the taxon page. see also screenshot1.

I can correct the display of vernacular names only by manually clicking on Edit left of the vernacular name Lupo --> In the drop-down menu I choose Italian as language-->Save. Doing the same with the name in English. And then I have to delete the two blocks where it is only written
"Language: Italian" and "Language: English" (screenshot2 illustrates the correct display after these corrections)

Screenshots
see screenshots 1-3

Your setup:

Impact
One purpose of our Scratchpads site is to document the local fauna to local inhabitants who are most likely to know vernacular names of the fauna. It is major inconvenience for us that we cannot display the vernacular names in two languages of more than one thousand species. It would take a long time to add and update these data manually on every single taxon page. Especially considering we have all the names ready in an Excel file template. The import function for the excel template and the display of vernacular names used to work fine ca pre 2019. Back then the issue with vernacular names was raised by various users. Would it be possible to look into it again at some point?

My manual corrections are reset i.e. the vernacular names are displayed incorrectly again, if I subsequently update the taxon data with the excel template. If the vernacular names are removed from the rows in the template file before running an import, the vernacular names are wiped from the taxon page on the site.
This means that if we decide to manually add the vernacular names to the taxon pages we will no longer be able to use the import function because that will reset my manual updates. I cannot choose to only update the other taxon data because it would delete the vernacular names on the site if they are not in the excel sheet.

The vernacular names are also displayed incorrectly in the module for editing taxons in the taxonomic tree view (screenshot3). In the case of Canis lupus eight sections for vernacular names are displayed only some of them has content (screenshot3).

Anything else?
I will be happy to help any way I can in solving this problem. Thanks.
Nicholas Williams

#6054
#5802

Screenshot1
Screenshot1

Screenshot2
Screenshot2

Screenshot3
Screenshot3
Taxon_Canis_lupus.xls

@poospiza poospiza added status: triage this needs sorting and proper labelling type: bug this describes something that isn't working labels Feb 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: triage this needs sorting and proper labelling type: bug this describes something that isn't working
Projects
None yet
Development

No branches or pull requests

1 participant