Some work best as delivering a library of information, these have the metadata, one set image size and provide easy search technique such as a museum’s out reach/ education groups might use on your web site and in the museum itself. And example of this type is Luna’s Insight or your own web developed system.
Other’s have been developed for production and publication workflow such as your promotional, PR, exhibitors etc, might need that can deliver the right size image image for a unique use with the critical data such as copyright, version control, and past use, as well as people, activities or concepts etc. Artesia ($$$$) is an en example of this.
Then there are the Collection management systems, which may or may not require digital images.
In the medium price range, there are those systems that are trying to do both such as Canto’s and Extensis’s programs. Interestingly Extensis’s Portfolio offers you the option to save your screen images and speed up imaging. It is also a nice safety measure as these images are saved somewhere other than where your originals are.
I recommend that you think of the components of the system, define them and then see which programs might provide them.
The components might be
Cataloger – could be in Access, FMP, or Portfolio, Adobe
Publisher – independent web development, Luna, Portfolo/Canto
Presentation - for lectures etc - Power Point, Luna
Distribution – could be Artesia, adding on Adobe Image Server to your publisher as eMotion does http://www.emotion.com/ . It has become a Corbis company I see very interesting. Anyway there are several that us the Image server to deliver formats on the fly.
Digital Repository – Dspace
I also support Mike’s recommendation for using TASI and NARA, though TASI is much easier to read.
--
Trudy Levy
Consultant for Digital Imaging Projects
Image Integration 415 750 1274 http://www.DIG-Mar.com
Membership Chair, Visual Resources Association http://vraweb.org
Images are information - Manage them
On 1/6/06 10:16 AM, "David Marsh" <[email protected]> wrote:
Hi Mike, everybody…
A couple of observations re “on the fly” derivatives from a techie perspective:
1) I would expect JPEG derivatives, particular if at substantially lower resolution, to be very much smaller than the master TIF, even with TIF compression. Makes me wonder about the exact nature of the storage space limitations you mention.
2) Generating and a derivative on-the-fly implies loading and processing the (very) bulky original file.
My instinct is that the I/O and processing burden of doing this is a high price to pay for the small proportion of storage space likely to be saved.
Interesting idea tho …maybe a compromise could work well. Have a few strategically sized derivatives ready made for 90% of anticipated needs, and have an on-the-fly facility to generate more specialised versions, avoiding the need to store a derivative for every conceivable purpose.
I suspect that’s the line you’re already thinking along.
David Marsh
-----Original Message-----
From: Mike Rippy [mailto:[email protected]]
Sent: Friday, January 06, 2006 6:25 AM
To: [email protected]
Subject: Re: MCN-L Digitization procedures
Oh, by the way. Our plan here for our collection photography is to store the raw file, create a master tif file (that has been corrected for dust, color, etc.) and from that make various jpg derivitives (as needed). However, do to storage space limitations, we are considering using a new system that uses an application to generate derivatives on "the fly" to be delivered to our users. Saving the cost of storing each derivative file
===========================================
David Marsh
System Administrator
H.R. MacMillan Space Centre
1100 Chestnut Street, Vancouver, BC V6J 3J9
E [email protected]
T (604) 738 7827 ext. 255
C (604) 813 9667
===========================================
---
You are currently subscribed to mcn_mcn-l as: [email protected]
To unsubscribe send a blank email to [email protected]
---
You are currently subscribed to mcn_mcn-l as: [email protected]
To unsubscribe send a blank email to [email protected]
