The right way to do batch uploads is to upload posts first, and then tag them on the site, but then you end up spamming the index with untagged posts until you're done.
Put the metatag @hold@ in your tags when you batch post (with or without other tags). This will flag the posts as held; they won't show up in the index (even if you search for them--unlike child posts, they won't show up with a plain search).
Then, view your held posts (a link will appear on the left side of the post index) and do all the tagging/rating/pooling/PC you want.
Once you're ready, hit the "activate all posts" button, and it'll release the posts to the index.
You can only activate your own posts. Held posts aren't completely hidden; if you search for @holds:true@, it'll show everyone's held posts, and they'll still show up in any pools.
You can activate individual posts with a link that'll show up in post/show, or with the @-hold@ metatag. Also, you can use the @hold@ metatag to hold an existing post, but this only works shortly after it's posted; you can't retroactively hold posts (you should really do it when uploading).
There's no rush to activate posts. If you take a day or two to finish tagging a batch and activate it, the post will still show up at the front of the index once you do, not at the place it would have gone when you originally posted. If you upload a pool with more than 30 posts in one day, you must use the hold feature on all of them and release 30 of them each day.
More advanced: "Activate all posts" only activates held posts in the current search results, so you can pool everything when you upload (the @pool:123@ metatag), and then add @pool:123@ to the held post search. When you activate the posts, only held posts in that pool will be affected.

(copypasta'd from petopeto's original post)

Updated by Aurelia over 15 years ago