This has two aspects:

• Raw files
• Groups/views of files

Raw files should capture these details:

• Camera type eg GF1 or Canon
• Date range 2009-12-31-to-2010-01-01
• Period/location coarse ID/desc eg "LondonWithNazAndJohn"
• Vids vs pics, GF1 has them in diff dirs, canon has them mixed with IMG_ or MVI_ prefix and .JPG or .MOV suffix
• SD/DCIM/?/* where ? is important to preserve for ordering and context information, eg 125_PANA or 257___07

Raw files should be simple/quick/easy to add to collection! Proposal:

2009-12-31..2010-01-01-LondonWithNazAndJohn-GF1/

Such that date order has precedence, ID has next and camera comes last. Below that will live the native camera structure untouched eg DCIM/125_PANA/ etc.

It's likely a good idea to nest it one more or arbitrarily more with stuff like:

• HomelessInNZ
• BigUSARoadTrip
• CanadaWeddingAndIsaVisit

With multiple dumps below each.

Thumbnails can be handled by the viewer app. Shrunk versions for rapid visual searching should be in a parallel dir structure with a consistent format such as 640x480 or 800x600 or 1024x768 or 1280x960 or a variety.

Groups/views should be light weight and consist of a dir structure with symlinks to the shrunk versions or originals whatever is desired.

In place exiftran -i rotation of originals shall be the only mod allowed to originals.

Scripts required:

• Generate thumbs of X size in a relative path when passed a dir or set of files.
• Symlink thumbs and/or originals from a source with regex to a destination. Maybe generate a template metadata file for later online gallery generation?

Also need some sort of video path/file to name/desc to yt-hash mapping.

Might add some more thoughts later.

Fred.

One more mod allowed to some originals: encryption using a hash that i don't know that is itself encrypted and stored in an online location that some trusted person gate keeps. IE, I don't know, and can't find out myself. This means border crossing are safe from personal stuff being seen by fuckwit border control agents.