[GH-ISSUE #60] Feature request, include tag popularity count next to tag name in list #44

Closed
opened 2026-10-30 21:17:46 +00:00 by bsakaguchi · 8 comments
Owner

Originally created by @thojmr on GitHub (Nov 1, 2022).
Original GitHub issue: https://github.com/DominikDoom/a1111-sd-webui-tagcomplete/issues/60

Originally assigned to: @DominikDoom on GitHub.

I think it would be very useful to have the tag count next to the tag name when selecting from the list. This would allow us to select a tag based on its popularity when there are multiple similar tags to choose from.

Not sure how much extra work that would be though.

Originally created by @thojmr on GitHub (Nov 1, 2022). Original GitHub issue: https://github.com/DominikDoom/a1111-sd-webui-tagcomplete/issues/60 Originally assigned to: @DominikDoom on GitHub. I think it would be very useful to have the tag count next to the tag name when selecting from the list. This would allow us to select a tag based on its popularity when there are multiple similar tags to choose from. Not sure how much extra work that would be though.
bsakaguchi 2026-10-30 21:17:46 +00:00
Author
Owner

@DominikDoom commented on GitHub (Nov 1, 2022):

The coding work in this plugin would be very little, the bigger problem is getting the data.
At least the program I used to build the tag file (Grabber) sadly doesn't include the tag count in the offline tag database you can build. So I would have to replicate its functionality using the official API.
It's definitely possible and I agree that it would be useful, but not quick to do for now.

Just for choosing which tag is more popular, it's a lot simpler though: Tags in the default tag files are ordered by count, and since the script doesn't sort them at any point, tags higher in the list will always be more popular than those below. You just can't compare by how much.

<!-- gh-comment-id:1298714804 --> @DominikDoom commented on GitHub (Nov 1, 2022): The coding work in this plugin would be very little, the bigger problem is getting the data. At least the program I used to build the tag file ([Grabber](https://github.com/Bionus/imgbrd-grabber)) sadly doesn't include the tag count in the offline tag database you can build. So I would have to replicate its functionality using the official API. It's definitely possible and I agree that it would be useful, but not quick to do for now. Just for choosing which tag is more popular, it's a lot simpler though: Tags in the default tag files are ordered by count, and since the script doesn't sort them at any point, tags higher in the list will always be more popular than those below. You just can't compare by how much.
Author
Owner

@DominikDoom commented on GitHub (Nov 2, 2022):

Small update:
I have found the official danbooru tag dump on its public cloud console in the meantime, which contains post count and a few other interesting infos.
I'll have a look at it and see if I can process it to work with the script.

<!-- gh-comment-id:1299957264 --> @DominikDoom commented on GitHub (Nov 2, 2022): Small update: I have found the official danbooru tag dump on its [public cloud console](https://console.cloud.google.com/storage/browser/danbooru_public/data) in the meantime, which contains post count and a few other interesting infos. I'll have a look at it and see if I can process it to work with the script.
Author
Owner

@byzod commented on GitHub (Nov 3, 2022):

There's some tag builder have similar feature on github, for example this one, if it helps

<!-- gh-comment-id:1301847562 --> @byzod commented on GitHub (Nov 3, 2022): There's some tag builder have similar feature on github, for example [this one](https://tags.novelai.dev/), if it helps
Author
Owner

@DominikDoom commented on GitHub (Nov 3, 2022):

I was already able to convert the data to the form the script needs, so now I only need to implement it. Since the public data also included the tag aliases, I am currently trying to add those too, which would be very useful as well. Just need to make it work alongside translations now.

<!-- gh-comment-id:1301871720 --> @DominikDoom commented on GitHub (Nov 3, 2022): I was already able to convert the data to the form the script needs, so now I only need to implement it. Since the public data also included the tag aliases, I am currently trying to add those too, which would be very useful as well. Just need to make it work alongside translations now.
Author
Owner

@byzod commented on GitHub (Nov 3, 2022):

Since the public data also included the tag aliases, I am currently trying to add those too, which would be very useful as well. Just need to make it work alongside translations now.

1

You mean this? It is useful, can't wait to see that implemented :D

<!-- gh-comment-id:1301879026 --> @byzod commented on GitHub (Nov 3, 2022): > Since the public data also included the tag aliases, I am currently trying to add those too, which would be very useful as well. Just need to make it work alongside translations now. ![1](https://user-images.githubusercontent.com/848607/199694411-936d7f89-d309-4e61-92cb-b20815997530.jpg) You mean this? It is useful, can't wait to see that implemented :D
Author
Owner

@DominikDoom commented on GitHub (Nov 3, 2022):

Yes, exactly. It already works similar to the translation feature, so I think it'll be possible without much reworking. I just need to be careful to not break existing translations.

<!-- gh-comment-id:1301884716 --> @DominikDoom commented on GitHub (Nov 3, 2022): Yes, exactly. It already works similar to the translation feature, so I think it'll be possible without much reworking. I just need to be careful to not break existing translations.
Author
Owner

@DominikDoom commented on GitHub (Nov 3, 2022):

Small preview:
image

At least for danbooru tags the work is almost done, just need to do a bit of cleanup and update how translations are handled. I tried to find similar public tag data for e621 tags, but wasn't able to get anything so far. So I'll have to get them using the API, which will probably take a bit longer.

<!-- gh-comment-id:1302638438 --> @DominikDoom commented on GitHub (Nov 3, 2022): Small preview: ![image](https://user-images.githubusercontent.com/34448969/199820121-eba51ed1-e91b-44f7-8d16-c1aab90ab9cc.png) At least for danbooru tags the work is almost done, just need to do a bit of cleanup and update how translations are handled. I tried to find similar public tag data for e621 tags, but wasn't able to get anything so far. So I'll have to get them using the API, which will probably take a bit longer.
Author
Owner

@thojmr commented on GitHub (Nov 6, 2022):

This has been working great, thanks for the work

<!-- gh-comment-id:1304703558 --> @thojmr commented on GitHub (Nov 6, 2022): This has been working great, thanks for the work
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
DominikDoom/a1111-sd-webui-tagcomplete#44
No description provided.