Lulu Poetry

Lulu Poetry or Poetry.com, announced on May 1, 2011 that they would close four days later on May 4, deleting all 14 million poems. Archive Team members instantly amassed to find out how to help and aim their LOIC's at it. (By the way, I actually mean their crawlers, not DDoS cannons.)

Site Structure

The urls appear to be flexible and sequential:
(12:13:09 AM) closure: http://www.poetry.com/poems/archiveteam-bitches/3535201/ , heh, look at that, you can just put in any number you like I think
(12:15:16 AM) closure: http://www.poetry.com/user/allofthem/7936443/ same for the users
There are apparently over 14 million poems. The numbers go up to http://www.poetry.com/user/whatever/14712220, though interspersed are urls without poems (author deletions?).

Strategies

Currently people are using wget in various ways.

Because the urls are sequential, you can call wget with a nano-bash script:
for x in $(seq 1 100000); do wget http://www.poetry.com/poems/archiveteam/$x/ -O poem$x.html; done
Or you can just make a text file containing a list of incrementing urls and feed that to wget as a source of urls (may be faster than the above).
A quick command to build a list of urls: perl -e 'print "http://www.poetry.com/poems/archiveteam/$_/\n" for 100000...14500000' > biglist

Coordination

Who is handling which chunks of urls?
IRC name	starting number	ending number	Progress
closure	0	999,999	in progress
Awsm	x,000,000	x,000,000	in progress
underscor	x,000,000	x,000,000	in progress
BlueMax	x,000,000	x,000,000	in progress
d8uv	x,000,000	x,000,000	in progress
jag	x,000,000	x,000,000	in progress
SketchCow	x,000,000	x,000,000	in progress
Qwerty01	7,000,000	7,999,999	in progress
[yourusernamehere]	x,000,000	x,000,000	in progress