-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improvement suggestions regarding tag handling #3
Comments
Hello there, Thanks for using this little software 😄 The points about the improvements, I'll have a look at what I can do. Many of them are also on a to-do list of mine, but I didn't have time to implement them yet. |
Thank you for the fast response. "Time issues" is a very relatable thing :) I've continued tagging and found a couple of further suggestions but they might be over the top for now. For now, the biggest hindrance - at least to me - is the placeholder issue. |
Gonna leave the same comment as for the other tool "BooruDatasetTagManager": "Would like to define Dropdowns with a custom title and add Tags, in the "all" tag section, to them for easier navigation when looking for something. In case you find the idea useful for your tool. |
Yeah I was thinking about something like that as well. Somehow grouping or categorizing tags would allow for a far better experience of managing a dataset. Something that might make sense, is to create a local database for an image set, index the actual images and store the tag definitions inside the database. Once the actual captions are needed, you can export your tagged combinations to a specific directory. But I'm quite busy this month and will probably have a look at the entire thing in May. |
All of this seems to be very reasonable and useful. However, I'd argue that input flow and usability are currently more important than a powerful tag database:
But regarding the idea: grouping and hierarchies of keywords are pretty well implemented in many DAM-applications such as Lightroom. Maybe it’s possible to find some interesting ideas there? Let’s take, for example, the export/import of keywords. If I recall correctly, they export to a simple text file with indentations for hierarchical levels:
I think that something like this might be completely sufficient for the time being. Maybe something along the lines of:
I actually don't think that you need to keep persistent references between pictures and tags in your database. This is probably rather a task for a generic image management application and I actually appreciate that you focused your tool on the actually important task: tagging for AI training via side-car file. |
First of all: thank you for your work on this small tool which I accidentally found via reddit.
I did some testing and it appears to prove quite useful.
However, there were a couple of things which suprised me and kind of hindered the "usability flow":
Maybe some of those suggestions might be implemented in a future release?
The text was updated successfully, but these errors were encountered: