Merrilee
---------- Forwarded message ----------
Date: Tue, 01 Dec 1998 08:28:26 -0800
From: Jerome McDonough <jmcdonou@library.berkeley.edu>
To: John Hassan <jhassan@library.berkeley.edu>,
Merrilee Proffitt <mproffit@library.berkeley.edu>,
MOA2 Workgroup <moa2wg@library.berkeley.edu>
Subject: Re: Re[4]: Scriptorium (fwd)
One additional comment on the issue of versions and filenames below:
>> 4. I don't understand how to make the database create more than one
>> derivative with different defaults. We generally create at least 2,
>> sometimes 3 or 4 derivatives for use online and in-house. I assume
>> others do also. I think I just haven't figured out how to do this.
>Response: Derivative Version code is the answer. By changing the Version
>code in defaults or in the forms, you change the file name by one or more
>characters. The version code is injected into the filename after the
>SObjID, and before the suffix. So you might have a group of derivatives for
>subobject 12345 like
> nypl00012345a.gif --thumbnail
> nypl00012345b.jpg --low res
> nypl00012345c.jpg --med res
> nypl00012345d.jpg --high res
> |
> <version> .
>
>This insures that a group of derivatives can be correlated with a given
>subobject, while each derivative has a unique file name.
>That said, there are a couple of real big best practices problems here. How
>do you name them, so that the program that packs all this stuff up in an
>XML document knows what to do with them, and what standard is required to
>insure that our tools can view your images, and vice versa? I suspect that
>Jerry and Rick may want to add more here, and that these will be issues
>that will have to be sorted out by the community down the road.
In addition to allowing a group of derivatives can be correlated with a
particular subobject, versions also allow image files correlated
with *different* subobjects to be associated with one another. If you
have a book object with 50 page subobjects, for example, with page images
in 600 DPI TIFF (Master images), 300 DPI JPG (Version A), and 72 DPI
GIF (Version B), the version flag associated with a file in the database
is what allows the program which creates XML documents from the database
to go through the files associated with all of the subobjects and group
them by version. This is important for allowing the MoA II browser to
be able to: 1. inform the user there are different versions of the object,
and 2. display images from just one version (so the user can page through
all of the 300 DPI JPG images, for example).
The moral of the story being: Please make sure that image files constituting
a particular version of the object have the same Version assigned to them
throughout your subobject tree.
Jerome McDonough -- jmcdonou@library.Berkeley.EDU | (......)
Library Systems Office, 386 Doe, U.C. Berkeley | \ * * /
Berkeley, CA 94720-6000 (510) 642-5168 | \ <> /
"Well, it looks easy enough...." | \ -- / SGNORMPF!!!
-- From the Famous Last Words file | ||||