Isn't that overly ambitious (especially as we're talking about DAM, where there are so many choices and options)?LucLL wrote: I know Im maybe driving this a bit far, but this time i want to know that im making the right choice and that I'm doing the right thing and do it the right way.
That seems more realistic.Or at least have myself convinced that its as close and as good i can currently do it.
For the sake of accuracy, I would say that the specific event is John's 40th Birthday, while Event::Birthday::John's Birthday would actually be a class of individual events like that one. OTOH, I agree that could be silly and impractical - so the pragmatical and sensible choice may be to go with Event::Birthday::John's Birthday as the (recurring) event that you want to record, even if it doesn't allow you by itself to discriminate the underlying specific year events.Keyword wise, im still wondering what to do with - let me stay with the Birthday example - the sublevel (if any) of the Birthday label. Im pretty sure I would not use something like Event::Birthday::Johns 40th Birthday as to stay consistent with this I would have a separate event for each and every birthday. With a huge family every year the number of Birthday labels would be a bit silly as I think that the "labels" should still be possible to be used then just at one single event or moment in time. For that singel event or moment in time I would see this more as a function of a collection.
That seems a reasonable cut to me, although you could also cut it one level up or down. The way I see it, it's all a matter of personal tradeoff between how complex a label or portfolio hierarchy you want to maintain and how accurate/specific/discriminating you want to be.Nevertheless, I still think that I would maybe not stop at the Birthday level but use Event::Birthday::John Smith's Birthday.
Exactly my point.It of course still leaves for each event a bit of a question to what level to go, and I believe that might be differently answered by each of us depending probably if,where and how you actually want to use the catalog.
Accordingly one could question, should I distinguish Summer Holiday from a Hiking Trip or is the Hiking Trip also just a summer holiday, assuming of course that you do the hiking trip in summer. Therefore if you would be doing the hiking in summer and winter, it might actually be more useful to have a classification of Event::Holiday::Hiking::Summer Hiking Trip// Winter Hiking Trip, instead the other way around, being Event::Holiday::Summer:: Summer Holiday // Hiking Trip.
At the risk of being pedantic, I would note (regarding the 2nd choice) that summer is neither a holiday nor an event, so I would also go with Event::Holiday::Hiking::Summer Hiking Trip or directly with Event::Holiday::Summer Hiking Trip (or even Event::Summer Hiking Trip - or simply Event::Hiking). No matter what level of detail you want to capture in your label hierarchy, chances are that at some point it's not going to be enough - so you may want to somewhat limit your specificity ambitions from the outset.
That seems reaonable to me.In this later case I would probably go for Event::Holiday::Family Summer Holiday // Family Skiing Holiday // Hiking trip with Louisa // Family Bike Holiday SO I would not have a Family Biking Holiday in France and Family Biking Holiday in Czech Republic as two different Events. The collections and potentially the location field can help me sufficient to distinguish that and at the ent the event is a Biking Trip, so selecting the event would give me all pictures of all biking trips we ever did, while for an individual trip I have the collection (which would be stored in the headline of the image too) and/or the location and date to filter it out.
Haha, don't overthink it too much (...like I usually do it )!Oh... one more thing.... what about Event::BBQ and what if the BBQ was actually on someones Birthday ???? multiple Events
... question will be whats the main event I think ... Are we doing the BBQ because its his birthday or are we having a birthday because we do a BBQ.... Hmmm interesting