Insufficient collection information when submitting an article #1602
Comments
PabloDeAlbu
added
needs triage
tdonohue
added
high priority
and removed
needs triage
|
Realized today this is semi-related to #2556 (because adding a collection submit button is another way to solve this issue). Also, it is worth noting that a workaround exists. If you browse to the collection first & then visit "New" -> "Item" sidebar menu, then the first entry in that list will always be the collection you've browsed to. In other words, that "New" -> "Item" sidebar menu popup already does detect which Collection you are currently viewing. See this comment for step-by-step instructions of this workaround: #2556 (comment) Nonetheless, I still agree it'd be useful to provide more collection information in the popup (to differentiate similar named collections) as it'd improve usability. |
|
Hi @tdonohue, We'd like to claim this. |
…ng an article.
|
@PitbaranK : Apologies for the delayed response, but I was out of the office for much of August. Assigning this to you. |
Describe the bug
Sometimes the collections returned by the collection browser cannot be differentiated because their name is exactly the same as another collection, as well as the name of their parents community.
For example, supose you have two communites named "Institution A" and "Institution B", and they have two subcommunities named "Reports" that have a collection called "Research reports" and I want to submit an item in "Institution B > Reports > Research reports"
When I search for the "Research Reports" collection, it is impossible to differentiate the "Reports" subcommunity collection in "Institution A" from the "Reports" subcommunity in "Institution B".
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Instead of displaying only the name of the parent community, the interface could display the full hierarchy as in xmlui
The text was updated successfully, but these errors were encountered: