Saturday, April 26, 2008

ISFDB post-migration status update

The ISFDB has been fully migrated to our new server and the correct version of should be visible by everybody on the Internet. We are currently being re-indexed by Google, Yahoo and MSN, so database performance may be sub-par, but we expect the re-indexing process to complete in a few days.

Saturday, April 12, 2008

ISFDB migration update

The ISFDB has been now migrated to (and is editable at) . If you go to tonight, you will see a read-only version of the database as of earlier today. Hopefully, the address will be re-pointed to the new location in the next day or two.

ISFDB Wiki is down -- ISFDB migrating to another server

The ISFDB Wiki is currently down and the ISFDB database is in read-only mode. We are in the middle of migrating to a new hosting company and hope to be back up by the end of the day, although it may take some time for the site to be fully visible by everybody on the internet (aka DNS changes).

Monday, March 17, 2008

It's back

7:16 a.m. Monday March 17. And the submission that has been sitting in my browser for the last week was accepted.

Sunday, March 16, 2008

ISBN Prefixes and Publisher Ranges

I stumbled on this useful resource today and remembered some discussions in the area. We may already have it linked somewhere in the Wiki but just in case we haven't I thought I'd record it here:

ISBN Prefixes and Publisher Ranges

Saturday, March 15, 2008

ISFDB status

The ISFDB server went down on Saturday 2008-03-08 some time after 9pm (Texas, i.e. Central US time, used throughout this post). It came up on Sunday night shortly before midnight and went down again on Monday around 4pm. It has been down ever since except for its static pages which can be found at (Note that these pages are often obsolete.)

At this time we expect the ISFDB to remain down until at least Monday (2008-03-17) morning.


ISFDB Blog created

As per Swfritter's suggestion, I have created this blog as a supporting tool in case the ISFDB and its Wiki are down. Now we just need to figure out how to use it and how to give our users access to it.