someone said:
4. Each page image should be a separate file and named with the page number within the set; e.g. 001.tif, 002.tif, etc. Separate, non-page images, such as covers or color images scanned separately from the pages, should have suitable names, such as "cover.jpg" or "072-image.tif"
this is a bad policy. a wonky naming convention screws everything up. (and an inconsistent convention is a wonky one.) also, it's absolutely imperative that a library have _unique_filenames_ for every single file within it. naming files "001.tif" and expecting their _folder_ to differentiate them is a disaster-in-the-making. for a better way of doing things, check any of the links to the .html files i gave in an earlier message. all of them incorporate the image-scans. you want an alphabetical sort of the filenames to give you the _exact_ order in which the p-book pages were bound...
All page images for the book will be zipped into one file
this is a bad policy too. you need to have each image individually accessible. it is _tremendously_ important that this be the case...
we will not post separate page images in that directory, since that would double the space used, and we believe that people who want to consult the images will probably want them all.
that's a bad assumption. there are all kinds of situations where people want a single scan. (ponder your own experience...) and these scans _need_ to be accessible via the web, not just as a download package. again, very important! if it comes down to a choice between saving them in a zip file and saving them individually, toss the zip file _immediately_... *** your policy on the way in which the scans are saved simply must reflect the realities about how those scans will eventually be used. spend some time analyzing those uses so you make good decisions. -bowerbird p.s. here are those links again, straight into their subdirectories:
http://snowy.arsc.alaska.edu/bowerbird/mabie/ http://snowy.arsc.alaska.edu/bowerbird/myant/ http://snowy.arsc.alaska.edu/bowerbird/tolbk/ http://snowy.arsc.alaska.edu/bowerbird/sgfhb/ http://snowy.arsc.alaska.edu/bowerbird/henty/ http://snowy.arsc.alaska.edu/bowerbird/bachwm/ http://snowy.arsc.alaska.edu/bowerbird/ahmmw/
the .html files are on another machine; you can't see them as a group, but you can view-source on any one of them to see how they operate. in each case, the .html files were auto-generated from the .zml file, and the image-file is spliced in to facilitate "continuous proofreading".
http://www.greatamericannovel.com/ahmmw/ahmmw.zml http://www.greatamericannovel.com/ahmmw/ahmmw.html
http://www.greatamericannovel.com/mabie/mabie.zml http://www.greatamericannovel.com/mabie/mabiep001.html
http://www.greatamericannovel.com/myant/myant.zml http://www.greatamericannovel.com/myant/myantc001.html
http://www.greatamericannovel.com/sgfhb/sgfhb.zml http://www.greatamericannovel.com/sgfhb/sgfhbc001.html