Easier tag organization and usage #592

New Issue

OVERLORD · 2026-02-04T21:21:11+03:00

OVERLORD commented

2026-02-04 21:21:11 +03:00

Originally created by @jtjosvold on GitHub (Mar 9, 2018).

Desired Feature
As our BookStack is growing I'm seeing multiple variants of tags being created because people do not know that a similar tag has been created (capitalization, abbreviations, etc.). It would be helpful to have a page showing an index of tags so that editors can see what tags exist and, in addition, the tags could be linked to searches showing pages that are using that tag. This would also help us with individuals that are not as comfortable with using proper search syntax.

Originally created by @jtjosvold on GitHub (Mar 9, 2018). **Desired Feature** As our BookStack is growing I'm seeing multiple variants of tags being created because people do not know that a similar tag has been created (capitalization, abbreviations, etc.). It would be helpful to have a page showing an index of tags so that editors can see what tags exist and, in addition, the tags could be linked to searches showing pages that are using that tag. This would also help us with individuals that are not as comfortable with using proper search syntax.

OVERLORD added the 🛠️ Enhancement label 2026-02-04 21:21:11 +03:00

OVERLORD closed this issue

2026-02-04 21:21:13 +03:00

OVERLORD commented

2026-02-04 21:21:18 +03:00

@ssddanbrown commented on GitHub (Mar 12, 2018):

@jtjosvold Thanks for the suggestion, So like a tag-overview page?

I can see the benefit. I think this would be worthwhile once Books and Chapters support tags.
Thinking about this I should really increase the priority on Book/Chapter tags just to finish the base tag system off.

Somewhat related to #121.

@ssddanbrown commented on GitHub (Mar 12, 2018): @jtjosvold Thanks for the suggestion, So like a tag-overview page? I can see the benefit. I think this would be worthwhile once Books and Chapters support tags. Thinking about this I should really increase the priority on Book/Chapter tags just to finish the base tag system off. Somewhat related to #121.

OVERLORD commented

2026-02-04 21:21:23 +03:00

@jtjosvold commented on GitHub (Mar 12, 2018):

Precisely. It would help to keep them organized and make searching easier for our users.

Thanks for looking into it.

@jtjosvold commented on GitHub (Mar 12, 2018): Precisely. It would help to keep them organized and make searching easier for our users. Thanks for looking into it.

OVERLORD commented

2026-02-04 21:21:30 +03:00

@Cave-Johnson commented on GitHub (Jan 19, 2020):

Would just like to add my plus one to this. I love the way bookstack uses tags and it makes the search feature really powerful.
This would be really useful for managing large instances of bookstack. I like the way that its been done in the pull request. It would also be neat if there was the ability for an admin to combine tags so that multiple similar tags can be cleaned up. As an example, 3 tags for Jan2020 currently appear as jan-20, January2020 and jan2020. It would be really neat functionality to merge the 3, selecting a master tag and then updating the other tag throughout bookstack.

One other thing that would make using tags much easier is to show all tags that have currently been used within that book or that shelf to avoid users creating a new version of that tag. For example show tags currently used in this book under the add tag box.

@Cave-Johnson commented on GitHub (Jan 19, 2020): Would just like to add my plus one to this. I love the way bookstack uses tags and it makes the search feature really powerful. This would be really useful for managing large instances of bookstack. I like the way that its been done in the pull request. It would also be neat if there was the ability for an admin to combine tags so that multiple similar tags can be cleaned up. As an example, 3 tags for Jan2020 currently appear as jan-20, January2020 and jan2020. It would be really neat functionality to merge the 3, selecting a master tag and then updating the other tag throughout bookstack. One other thing that would make using tags much easier is to show all tags that have currently been used within that book or that shelf to avoid users creating a new version of that tag. For example show tags currently used in this book under the add tag box.

OVERLORD commented

2026-02-04 21:21:33 +03:00

@Klemet commented on GitHub (May 23, 2021):

I'd really love this to be implemented too. Right now, I kinda feel in the dark about the tags that exist in the Bookstack. It seems like the only way I could find them would be to look at each element of the Bookstack one by one, and make a manual list. To help users search for particular resources, a "all tags" page would be wonderful !

@Klemet commented on GitHub (May 23, 2021): I'd really love this to be implemented too. Right now, I kinda feel in the dark about the tags that exist in the Bookstack. It seems like the only way I could find them would be to look at each element of the Bookstack one by one, and make a manual list. To help users search for particular resources, a "all tags" page would be wonderful !

OVERLORD commented

2026-02-04 21:21:35 +03:00

@ssddanbrown commented on GitHub (Sep 28, 2021):

Potential alternative implementation offered here: https://github.com/BookStackApp/BookStack/issues/2943#issuecomment-927850224

@ssddanbrown commented on GitHub (Sep 28, 2021): Potential alternative implementation offered here: https://github.com/BookStackApp/BookStack/issues/2943#issuecomment-927850224

OVERLORD commented

2026-02-04 21:21:37 +03:00

@ssddanbrown commented on GitHub (Sep 28, 2021):

In regards to the original issue, there seems to be a desire for something like a tag exploration page but the use-cases and requirements would need to be clear. This is something I've hard trouble defining. Don't want just a plain list of tag names.

I'm thinking:

Purpose: To explore usage of tag names and values in the system.
Implementation:
- View would primarily be a paging list of tag names
- List item for the tag name would show:
  - Count of pages/chapters/books/shelves assigned a tag using that name.
  - Count of unique values used with this tag name.
  - Count of all values used with this tag name.
- List item could be expanded to show all unique name=>value options used for the tag of the specific name.

This would provide a view that's primarily orientated around usage via the instant visibility of counts, which could be expanded to understand tag application. No pages|chapters|books|shelves would be displayed in that view specifically but you'd click through to a tag search for entity views.

Would be good to know if that specific implementation would meet people's requirements here. I'd want to keep the scope quite focused.

@ssddanbrown commented on GitHub (Sep 28, 2021): In regards to the original issue, there seems to be a desire for something like a tag exploration page but the use-cases and requirements would need to be clear. This is something I've hard trouble defining. Don't want just a plain list of tag names. I'm thinking: - **Purpose:** To explore usage of tag names and values in the system. - **Implementation:** - View would primarily be a paging list of tag names - List item for the tag name would show: - Count of pages/chapters/books/shelves assigned a tag using that name. - Count of unique values used with this tag name. - Count of all values used with this tag name. - List item could be expanded to show all unique name=>value options used for the tag of the specific name. This would provide a view that's primarily orientated around usage via the instant visibility of counts, which could be expanded to understand tag application. No pages|chapters|books|shelves would be displayed in that view specifically but you'd click through to a tag search for entity views. Would be good to know if that specific implementation would meet people's requirements here. I'd want to keep the scope quite focused.

OVERLORD commented

2026-02-04 21:21:43 +03:00

@jtjosvold commented on GitHub (Sep 28, 2021):

I like your idea. We had been using #1354 as a solution (that was one of my developers) so that we had a better idea and had found it helpful but lacking. I like your idea of incorporating the count and the ability to expand it to see more details.

@jtjosvold commented on GitHub (Sep 28, 2021): I like your idea. We had been using #1354 as a solution (that was one of my developers) so that we had a better idea and had found it helpful but lacking. I like your idea of incorporating the count and the ability to expand it to see more details.

OVERLORD commented

2026-02-04 21:21:47 +03:00

@ssddanbrown commented on GitHub (Nov 7, 2021):

Implementation as per my comment above has now been merged as per #3042.
This will be part of the next feature release.
Hopefully should cover the core requested case here, so will therefore close this off.

@ssddanbrown commented on GitHub (Nov 7, 2021): Implementation as per my comment above has now been merged as per #3042. This will be part of the next feature release. Hopefully should cover the core requested case here, so will therefore close this off.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/BookStack#592