Digital Library Implementation, Low-Resolution Image Content Model
Digital Library Implementation Home
> Content Models
|
Input Master
Low resolution JPEG or TIFF images that do not meet
the UVa Library 400 or 600 ppi 24-bit color or 8-bit grayscale uncompressed
TIFF image standard
Datastreams
-
Static 24-bit color or 8-bit grayscale JPEG preview,
120x120 pixels constrained
-
Static 24-bit color or 8-bit grayscale JPEG screen,
800x600 for documentary images, or 650-850 pixel width range as appropriate
to achieve readability on screen
-
No max available, mapped to same datastream as screen
Phase 2 content for this model: Fowler,
Jefferson Country
uvaLowRes Image Content Model
- uvaDefault Disseminator / uvaDefaultLowRes Mechanism
- getPreview – returns the thumbnail resolution of the image.
- getLabel
- getDescription
- getFullView(pid)
- getDefaultContent
- uvaMeta
- getDescMeta
- getAdminMeta
- getDC
- viewDescMeta(style)
- viewAdminMeta(style)
- viewDC(style)
- uvaImage Disseminator / uvaImageLowRes Mechanism
- getPreview – returns the thumbnail resolution of the image.
- getScreen - returns the screen-sized resolution of the image.
- getMax - returns the screen-sized resolution of the image.
- getImageViewer - returns the screen-sized resolution of the
image within the ImageViewer Applet.
- uvaDownload Disseminator / uvaImageDownload Mechanism
- getDownload – initiates a download of the screen datastream
through the browser.
- uvaOKI
- getAssetDefs (childPid, parentPid)
- Other
- getDeliveryMaster - returns the TIFF/MRSID master or a page
describing where the master is located. for Phase 2, returns
a statement describing the offline location of the master. The
non-Fedora version does NOT exist in Phase I; Fedora-ized version
will require writing a new script to handle this behavior.
Meant to return the TIFF/MRSID master or a page describing where
the master is located. Still to be implemented?
Recommendation: All collections that do not currently contain static
jpeg preview, static jpeg screen, and Mr. Sid max files should be regenerated
to match that datastream model. When no master is avaialble to meet the
image standards, it is possible to map screen and max to the same physical
file in the image object to cover the missing files.
Recommendation:
The getDeliveryMaster behavior will point to an element in
the administrative metadata where the offline location of the Delivery Master
is located, once that element is in use.
February 18, 2004; revised April 27, May
19, July 23, August 27, and September 17, 2004
|