To add to the list: DSpace (www.dspace.org) for institutions that have at least one technologically skilled support person.By all means, do include my suggestion if you see fit. Since most image editing and processing is done in Photoshop (at least in my organization), Version Cue fits right into it. On Jan 6, 2006, at 9:00 AM, Mike Rippy wrote: The list I provided isnt exhaustive. There are a lot of various approaches and applications that can be used to manage digital files. And can be used at varous skill levels. If others have opinions of software that would work well in a workflow, please provide them.
>>> [email protected] 1/6/2006 10:46 AM >>>
I am surprised that no-one is looking into Adobe (Version) Cue.
On Jan 6, 2006, at 6:44 AM, Mike Rippy wrote: We havent purchased a system yet. We are still investigating different Digital Asset Management systems. Most of them have a way of creating derivatives as needed. I am not endorsing these products. Just letting you know of the systems I have heard of. and I believe the lower cost products do as well: Matt from concrete computing can probably give you some insight as well. And a more up to date selection. He posted the first reply to this topic. And as he said, "These systems go all the way from $0 to high six figures in cash, and take significant effort and time to implement and maintain." (my emphasis). Mike, May I ask what application you are using to create the each derivative on the fly?
Angela 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. We also keep each file seperated in a folder for that file type, raw, tif, jpg_screen, jpg_thumb. There's probably no perfect way to store images on a filesystem, so maybe it should just come down to personal preference. Unless you need specific security settings--for example, so some people can see/edit some files but not others. In that case, you might want to build the arrangement to mirror the security arrangement, which will make setup easier, and corrections a lot easier. There might also be other factors like that, that I'm not thinking of. Anyone else?The "right" way to store images is in some kind of databasing system that keeps image metadata alongside the image files so that you can always find them again by working your way down a hierarchical tree (bad but demonstrative example: Paintings--19th Century--Impressionism--American--Cassatt, Mary--The Cup of Tea) or by searching according to subject, artist, media, title, etc. It's hard to impossible to duplicate that with directories on disk and maintain it reliably. These systems go all the way from $0 to high six figures in cash, and take significant effort and time to implement and maintain.good luck,MattPerian Sully wrote: Hi all: I'm currently developing our digitization procedures and I was wondering what other institutions do to organize their content. I'm planning on photographing identification & database images in a fairly high resolution jpg and photograph in RAW for publication-quality. Once the images are downloaded, I'll be processing them in small, medium and large dpi (72/150/?) and saving the original. What I'm really sort of curious about is how many different file sizes people save in and if they keep file directories for each size or lump them all together. Hope you're all having some relaxing holidays! Perian Sully
Collection Database and Records Administrator
Judah L. Magnes Museum
2911 Russell Street
Berkeley, CA 94705
(510) 549-6950 ext. 335 ---
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] --- 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] --- 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]
You are currently subscribed to mcn_mcn-l as: [email protected]
To unsubscribe send a blank email to [email protected]
|
