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

Inconsistent behavior in Term editor vs. Add to target vocabulary #64

Open
olufine opened this issue Feb 11, 2022 · 1 comment
Open

Comments

@olufine
Copy link

olufine commented Feb 11, 2022

I have a multilingual vocabulary configured not to accept duplicate terms. Multilingualism is managed using internal target vocabularies.
Sometimes preferred terms are identical across languages. This has caused no problem, as the function Relations between vocabularies does allow the addition of a term, even when it is identical to the corresponding term in some other language. This is as it should be: The no-duplicates setting should only restrict terms within each separate language.

However, if for some reason the term in some language becomes identical to its corresponding term in another language through trying to use the term editor, an error is thrown.

Example case: The genre Festschrift has the same preferred term in both languages nb and nn: Festskrift

  • During registration, the nn term is misspelled 'Festsskrift', and saved.
  • Later, the error is discovered, and the user tries to correct the nn term in the Term editor. This is denied with reference to duplicate terms.

This is in my opinion a bug in the Term editor.

@tematres
Copy link
Owner

Hi @olufine :) I'm agree with your model about duplicated terms :) and Tematres follow the same model: duplicated terms are terms who occurs more than one time in the same language.

Please check here in our sandobx Tematres implementation (the login is open in this instance): https://r020.com.ar/tematres/demo/index.php?tema=38142

Can you provide an URL about the problem? (may be there are other problem :/)

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