While Danbooru Downloader is good for initially downloading images of booru-like boards and placing them where you want (most of the time), it’s not very good at shifting a file already existing locally if it’s downloaded again under different tags. I.E. the image was new and untagged or tagged wrong, but the second time it’s downloaded it was tagged properly. But now you have 2 copies of the same file locally, one in the ‘misc’ or other folder, and one where it’s supposed to be. The firefox Danbooru Downloader add-on kind of does do this, but the standalone program to grab the images does not.

It’s already possible to download the tag list databases from many of those services, but you need a script or program of sorts to parse them into something useable. If I could, I would reorganize my archives to have less directories for the whole thing, and reasonably short file names. Because it seems too many directories slows down accessing any files and searches. Also consolidating directories that have the same names, but with other names appended to them, to be consolidated into the largest one to keep the number of sub-directories down would be nice.

Also, having a image duplicate search engine would help things, but I’m sure it would take a heck of a lot of resources to go through one’s entire image collection to find said images. But not impossible to do, after all, there is an online resource that does it. Why not be able to do it on your own machine?

Basically, I want something that will parse my download logs from Danbooru Downloader, the aforementioned tag database lists, file search and matching, file moving/renaming/appending/prepending, and auto-sorting whole directory structures based on easy to understand and modifiable criteria. So being able to try out different directory/file structures without having to re-download the whole thing all over again, and costing the board(s) downloaded from valuable bandwidth, it’s more worthwhile to do such experiments on your own hardware.

Vista’s tagging doesn’t work for me.

If I tag an image from PSWG with “Panty & Stocking” and “Stocking Anarchy” and then do a search for “Panty Anarchy” then it will pull the words from both tags, and the image will pop up even if it doesn’t have the tag “Panty Anarchy.”

I hate it. So much. Tagging becomes pointless, especially if you’re dealing with a series that has the same name as a character. Take “Sonic the Hedgehog” for example.

If I had tagging software that worked like tumblr’s multisearch I’d be golden.

If a stand-alone browser does end up being in the works, I agree about allowing it to pull data locally, not only for the performance increase but also simply so you can get your existing collection up to speed. It would be feasible for it to access any or all of the main databases (Sankaku, Danbooru, etc., just switch them on or off when scanning) to see which files you’ve downloaded come from where.

Another feature that would suit this project really well would be including the tag types information in the browser. This is something normal image browsers like Picasa can’t do, but it’s really useful in this kind of image collection. You want to know what’s an artist tag, and what’s a copyright tag for example. laser

The IPTC field allows cross-software, cross-system access of tag information, because the data is stored inside the image. This is ideal.

ACDSee has a hierarchal tag system, but only within its own database, and images tagged in that way cannot be moved from their location outside of ACDSee without losing that information. Picasa and other programs simply display a barf-list of every tag, which becomes very cumbersome, very quickly. The IPTC tags are not inherently structured, but a defined syntax COULD BE arranged that could be read and displayed in the tagging program as a manageable tree.

A unified tagging system would be ideal as a base from which to grow, and add one’s own custom tags, rather than having a scattershot ‘to each his own tagging method’, which is suboptimal for sharing images with others via imageboards, as what is effectively the same tag will show up in the same image five times, entered by five different people. This standardised tagging scheme is probably the MOST IMPORTANT aspect for allowing optimal finding and sharing of images.

As a novelty more than a necessity, it would be preferred for the image tagger to read the file’s datestamp, write the tag, then restore the datestamp to what it originally was.

Currently I use ACDSEE pro 2 to manage image on my local server
It has tagging & category, DB management and tonnes of functions.
But since it’s not codable, automation depends on it’s built in function.

http://www.windsorinterfaces.com/photomesa.shtml

http://www.itagsoftware.com