[KPhotoAlbum] order criteria for a family photo collection

[jedd]

 Hi Heinz,

 I think I'm with Tero on his observation.

 On Thursday 08 February 2007 3:19 am, Tero Tilus wrote:
 > KPA is saying "Describe me your taxonomy and I'll be following that".
 > Have you even tried to create categories and organize them to
 > hierarchies?  You do not have to do anything time-related with KPA.

 I rarely use time, and when I do it's usually as a last sorting
 criteria only -- that is, I've used KPA to narrow in on my set
 of photos that I'm interested based on other meta-data.

 Many of my photos, because they're scans, or came from people
 who get confused about setting the time on their camera, etc,
 have innaccurate date information.  For me this just further
 reduces my interest (and historical reliance) on date information.

 If you want to grab information programmatically out of KPA, as you
 indicated here:

 On Thursday 08 February 2007 3:57 am, Heinz Kohl wrote:
 ] I was doing some such actions using some regular expression hack directly 
 ] modifying the index.xml file and was adding some categories in that manner.
 ] But that's not enough.

 Note that there's a plan to shift away from the XML backend, and into
 a database proper, at which point your scripts become a lot easier
 and useful (I'd imagine) to do this semi-automated shifting of meta
 data.  Regexps should be easy to pick up the number from your files,
 particularly if you've stuck with \-[0-9].\.  (is that right?) all
 the way through your scanned set.

 I think the problem is that you've pushed a lot of *information*
 into the filenames you've created, and you aren't yet familiar with
 the way that KPA can handle (if not automatically accept) the same
 volume and types of information.

 ] Sorry - KPA is forcing to drive only one single archive.

 I still don't see why this is the case.  If you have lots of disparate
 sets of data that happen to share similar keywords, then it would
 be easier to separate them into discrete chunks (and discrete
 index.xmls) but that would be the only limitation I think.  Oh, you
 may also have accessibility issues (multiple users, etc) -- again the
 shift to the database backend will (has?) resolved this particular
 problem.

 ] And it is lacking a method to implement other than explicitely defined 
 ] enumeration data.
 ] That's not the right way to build a complete taxonomy.

 I'm not sure Jesper's original goal was to build a complete taxonomy.

 I'd suggest most KPA users (and yes, the ones that don't use it may
 have been driven away by perceived short-comings as you're now
 describing) don't want a complete taxonomy.  Or rather, they can
 build a perfectly functional, sensible, manageable taxonomy via
 the existing toolset.

 I'd really encourage you to try a paradigm shift away from date-as-key
 and put a modest number of images (say a hundred or so) into a dev
 system, then manually enter all the relevant meta-data .. use it for
 a while, and then make an evaluation.

 Jedd.