|
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, Matt Perian Sully wrote:
|
"matt 8.vcf" (missing attachment)
--- You are currently subscribed to mcn_mcn-l as: [email protected] To unsubscribe send a blank email to [email protected]
