Sorting Many Journal Entries (characters)

OK, I've been moving a BUNCH of mobs (mostly monsters, etc...) from one of my games to a new one using the transmogrifier.  (uggh, doing them all one by one... like 150 of them so far...) So, now I have a huge list of characters that I need to deal with in some way. 1) How can I sort them?  I know there's a directory command to "Sort A-Z" but these are all in the "root" level of the journal and I can't find a way to get them to sort? 2) How about moving more than one item in the journal at a time?  Am I missing something here?  How would I grab 2 (or 2 dozen) "characters" and put them in another folder?  This would be even better, plus I could put the root items in a folder and THEN get access to the Sort A-Z function. Currently, I guess I import all the characters by hand using the transmogrifier (can't transmogrify more than one item at a time, can i?)  Then, I guess I move them from root into a folder, one by one by hand again.  This is obviously VERY untenable when we're talking like 500+ tokens here...  Note, some are semi-duplicates (not the same ID, but the same monster), but they're scattered throughout, so that's another reason why I want to be able to sort them (to weed out duplicates.) Thanks in advance to anyone who can tell me what I'm missing here in the interface...

I'm not sure you are missing anything.  This is part of the reason I set up a "base game" for any game system I want to run, but never run any games with that "base game".  I organize everything there, and then copy that game any time I start something new.  Then, if I add anything, it is usually a fairly small batch of additions, making it much easier to handle.   Basically, I have no real advice beyond "try to make a way that you only have to do this once".

Matt Carlson said: Note, some are semi-duplicates (not the same ID, but the same monster) Is there a reason for the duplicates? Also, 500 is a pretty large number, that would tax most games. Have you considered using a  Library Campaign  to keep them in, and only transmogrifying at need? Your games should run much more smoothly.

I am actually trying to make a "library game" as you suggest,  I hadn't intended to play this "game" as a campaign.  I will take a look at your link to see if it gives any additional advice before I go much farther... (I'm toying with making a couple library games... one for monsters/npcs, one for maps, etc...) As for duplicates, I have several instances of "giant spider" or "orc" scattered around my games, and rather than fact check each one, I'm just pulling from all my other games indiscriminately and sorting it all out later. Looks like I have to just buckle down and copy everything over by hand twice (1x to transmogrify in, 1x to put in a folder so I can alphabetize and remove duplicates...) and then be done with it.

The advantage to having maps and creatures in the same library campaign is that if you transmogrify creatures into the new campaign first, then any maps, any creature tokens on those maps should retain their associations. I haven't actually tested this extensively, but I know it breaks if you do it the other way around.

So you're saying I should keep my both my maps and my token/creatures in the same "Vault" campaign? And what are you trying to say about the tokens on maps?   If I transmogrify a map into another campaign, the tokens come over but no "character/stat" links do?  But if I transmogrify the character/monster tokens over first, they will remain linked to the tokens on the map??

Let's say you have five goblin tokens on a map page. If you transmogrify that into a game that has no "Goblin" character sheet, they will come though as unassociated tokens: no character sheets were transferred. If you do have a "Goblin" character sheet, the goblin tokens on the transmogrified page "know" that they go with a sheet named "Goblin" and will retain that association. They will be working goblin tokens. Hence, transmogrify character sheets first, so the tokens have something to associate with. They can't make the association if you bring in the sheet afterward, since they have already lost it and become unassociated tokens. At least, that's how I think it works. I haven't done extensive testing.