Red Hat Bugzilla – Bug 1001824
[RFE] WebAdmin: distinction between bookmarks and tags not clear
Last modified: 2017-05-15 01:55:21 EDT
Description of problem: Customer is confused about the distinction between Tags and Bookmarks. They have questions like - “Can bookmarks have multiple tags?” “Are bookmarks profile specific but not tags?” Customer doesn't use tags as a result.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
While this may be a customer education exercise, we may need to update any documentation or make info icons/ guide me available for these areas and also consider renaming Bookmarks to 'Saved Searches'
einav - thoughts?
I honestly don't understand the user's confusion here. to me, this is similar to someone confusing Gmail labels with the browser's bookmarks - there is absolutely no relation between the two, so it is hard to outline a 'distinction' between the two (there is a need for 'distinction' between two items when there is some commonality between them; this is not the case here).
Maybe refer the bookmarks as 'bookmarked search' to make this more clear?
Bookmark is a general term.
(In reply to Yaniv Dary from comment #4)
> Maybe refer the bookmarks as 'bookmarked search' to make this more clear?
> Bookmark is a general term.
maybe "Saved Searches" which is more popular, I think [http://i.imgur.com/lCCaBWP.jpg , http://i.imgur.com/t6gfdWq.png , http://i.imgur.com/TGCt6U9.png], but this means that we need to get rid of the 'Bookmark' term throughout the application ('Add Bookmark' dialog title, error messages e.g. 'Cannot add bookmark, bookmark name already exists', etc.), including the REST-API.
re: schedule: As long as it is OK REST-API-wise to replace the 'bookmarks' resource collection with a 'savedsearches' resource collection before 4.0 (or add a 'savedsearches' resource-collection next to the existing 'bookmarks' one, which will simply be clones of each other until 'bookmarks' will be deprecated in 4.0) - I'm OK with making this change for 3.6. Otherwise - I recommend waiting for the next major release (4.0) in which we can break things.
I also don't see much room for confusion here.
Closing this as wontfix.