Bug #6151

Multiple terms added with the same name are inaccessible via taxonomy browse and treeview

Added by Dan Gillean over 8 years ago. Updated over 6 years ago.

Status:NewStart date:12/18/2013
Priority:MediumDue date:
Assignee:-% Done:

0%

Category:Taxonomy / Term
Target version:-
Google Code Legacy ID: Tested version:
Sponsored:No Requires documentation:

Description

1) Create a new place term, FOO. Add data to some of the additional fields (e.g. scope note, display note, etc.)
2) From the Places taxonomy page, click "Add new"
3) In the new place term edit form, enter "FOO" as the authorized form of name. Don't add any other data to the other fields. Save the record.

Resulting error
1) User cannot create a term with an identical name, even if other data is different.
2) User is given a warning upon save that "A term with this name already exists, but previous data is overwritten by the new data - i.e. the empty 2nd FOO will overwrite the data in the first FOO's additional fields
3) In the treeview browse, both records are still visible - URL points to /foo and /foo-2 - but clicking on either term will only bring up the most recently saved version of FOO. Hence, the problem is in the treeview.
4) When searching in the Places taxonomy, a user CAN get to each different term - each will include the warning Clearly both are being saved. However, when browsing, I could only find the most recently saved term.

As such, it seems it is a routing problem with the treeview, and possibly with browse (hard to test, since there are NO ways to sort places taxonomy (i.e. alphabetic or most recent) and the order is not apparent...

Expected result
Personally, I think keeping the warning visible is fine and will encourage better taxonomy management (e.g., in the use case of New York the city vs. New York the state, either a user should ideally make the city term a child of the state, OR the name should clearly distinguish it in the first place (e.g. New York State, State of New York, etc...) - but if both records are being created, the user should have easy access to both. This means both terms should appear in the treeview, and both should appear in browse results.

History

#1 Updated by Dan Gillean over 8 years ago

Note that there does not seem to be an issue when terms are NOT in the same hierarchical position in the taxonomy - i.e., I was able to add "Antartica" as a child term to "Antartica" without a warning.

#2 Updated by Jesús García Crespo over 7 years ago

  • Target version changed from Release 2.1.0 to Release 2.2.0

#3 Updated by Sarah Romkey about 7 years ago

  • Target version deleted (Release 2.2.0)

#4 Updated by Jesús García Crespo over 6 years ago

  • Assignee deleted (Jesús García Crespo)

Also available in: Atom PDF