Anthologize lets you be as picky as you like about the content you use
with it. Essentially you create multiple Anthologize 'projects', then add
the whatever subset of content you need (native local WordPress content or
content imported via a feed) to the project. The Anthologize content is
added as copies, preserving the originals and allowing for editing
specific to your output needs.
Eric's right that it *is* manual and a bit tedious, but it's (hopefully)
getting less so. You do need to created a 'part' structure within your
project to organize your content. But when adding content you can filter
by Tag/Category/Date Range/Post Type. And with the last release you can
add more than one post at a time.
The Anthologize dev team would certainly be interested in the code4lib
journal committee's take on the tool and ways it could be improved.
(Support for automated project creation and output generation would an
interesting feature to see on the roadmap).
On 1/4/11 10:45 AM, "Eric Lease Morgan" <[log in to unmask]> wrote:
>On Jan 4, 2011, at 11:40 AM, Jonathan Rochkind wrote:
>> ...Is there any easy way to get it to, for instance, make an anthology
>> all the posts with a certain WordPress tag or category instead?...
>Based on my (poor) recollection of playing with the Anthologize plug-in,
>the process is a bit manual. Initialize epub. Drag postings to it.
>Annotate/tweak titles. Click 'Go'. Get epub file. The process is not
>laborious, just a bit tedious. I would definitely recommend the "Journal
>Committee" experiment with Anthologize.