art morgue, day 2

Last night on the train I started setting up the art morgue, and then wound up doing a little more on it last night and then today.
This is what I have done,
Got the following modules - which i will definitely use:
admin (improves user interface)
admin_message (cute message popups)
cck (content data structure)
content taxonomy (pointing to vocabularies as fields -- check the box when setting up field for mirroring terms in node in regular taxonomy structure - so that the taxonomy tools can be used)
context (required by spaces/features/ginkgo theme (from open atrium)
date (might use for making some advanced notes on when images were added...not sure though)
devel (for debugging)
emfield (for adding images from third parties (flickr, photobucket) - provide a url and it dumps image into your files folder)
features (seeing if it will be possible to share this project back)
feedapi (might try syndication experiment with this one)
feedapi_mapper
filefield (required for making an imagefield)
flickr (on the fence about this one - need to test imports with this vs. with emfield)
image (for handling images)
imageapi (required for imagefield)
imagecache (for making image preset sizes)
imagefield (provides field for uploading images from computer)
jquery_plugin (not sure if this is required by other modules)
jquery_ui (i might use tabs, depending on the layout)
lightbox (will use & integrate with views to make some layouts for views results for previewing sets of images in different ways)
link (for adding bookmarks about where images came from & other reference materials)
login_destination (redirect user after login)
pathauto (for customizing url aliases)
purl (required by open atrium modules)
spaces (part of open atrium)
tabs (for layout)
taxonomy_manager (for revising terms - since this whole project is very term based)
token (required by many modules)
translations (?, no idea)
transliteration (file name sanitizing)
views (for searching data)
views_bulk_operations (? required by open atrium?)
webform (for custom contact forms, maybe)
the following modules i am considering...and i might use them...but haven't decided yet:
community_tags
edit_term
faceted_search
img_assist (really there shouldn't be inline photos for this project)
nodehierarchy (will think about this...i tried out freemind, but it doesn't seem like it will work yet. i might want to group images in certain ways that are different from sets )
tagadelic (required by community tags)
Other settings:
cck: created one content type called 'graphic' (not image, which is already taken)
added many fields to this - image field, notes, links, emfield, content taxonomy
imagecache:
custom size formats - i created a bunch of different presets: tiny, thumbnail, preview, full, original, 2_up, 4_up, 8_up
theme:
ginkgo - from open atrium (i wanted something nice & useable straight out of the box while i develop this)
taxonomy: created 5 vocabularies
* project (freetag)
* keywords (freetag)
subjective vocabularies:
* quality (how great the content of the image is)
* size quality (notes about how big the image is)
note: it is not necessary to look at the actual file size of the images. These terms are more for noting if the image is a crappy web graphic where i could never get a better one, or if the image is the best it could be - raw digital camera output)
* printing (whether or not i have or should print the image)