Continuing from part 1, such a simple example as 12 images paginated 1 through 12 introduces MagickNumbers, but does not showcase the extensible nature of the file naming standard. The next example shows how the files for  a hard cover book with end pages, title page, and 14 pages (4 Roman numerals, 10 numbered) totaling 22 scans is named followed by the pagination info displayed in our page turning system. The pagination info is derived from the 4 character pagination code.

000100fc.tif - Front Cover
000200fi.tif - Front Inside
00030000.tif - 
00040000.tif - 
000500tp.tif - Title Page
0006r002.tif - II
0007r003.tif - III
0008r004.tif - IV
00090001.tif - 1
00100002.tif - 2
00110003.tif - 3
00120004.tif - 4
00130005.tif - 5
00140006.tif - 6
00150007.tif - 7
00160008.tif - 8
00170009.tif - 9
00180010.tif - 10
00190000.tif -
00200000.tif -
002100bi.tif - Back Inside
002200bc.tif - Back Cover

The following new pagination codes are introduced above:

####00fc - Front Cover
####00fi - Front Inside cover
####0000 - unnumbered page that displays no information
           in the drop-down list of page numbers
####00tp - Title Page
####r### - Roman numeral
    r002 - II
    r003 - III
    r004 - IV
####00bi - Back Inside cover
####00bc - Back Cover

Note in the example the Title Page is numbered Roman numeral I in the book, but instead of ####r001 the file has the special pagination code ####00tp. This is because we assume most users prefer having the ability to jump directly to the title page of a book.

Still to come RE: MagickNumbers:

  • a complete list of our current pagination codes
  • possible additions to the pagination codes I have been considering suggesting
  • common problems easily solved with how MagickNumbers are created and used
  • common problems MagickNumber novices make which reduce file naming consistency
  • programmatic possibilities for writing and validating MagickNumbers
Advertisements