On 21/04/14 17:24, Bernhard wrote: Hi!
> Alexander Wagner schrieb am 21.04.2014 11:32: >> This gets even worse as I'd need to model some other entities (city, >> sublocation, state, country...) via keyword chains. > Is this the result of lacking IPTC-Support of Darktable? Yepp. Full IPTC however, is a piece of work. Worthwhile I think, cause clever people invented it to describe what we have, a photo, but it is a complex thing. Anyway, if you don't want to go for the full package, there're IMHO some tags that dt definitely should learn. If I go throgh the defs... I think the contact section would be appreciated if you need to sell your photos, otherwise, hm. From the image section in IPTC core, I think location is something quite important to most (you do want to describe where you took the photo, right? and it is also very helpful as a limiter if you search for a photo later on), while date created could be done via exif, and Genre/Scene-Codes are probably a bit over the top if your target are amateurs. From the content section some parts are currently modelled in DC, a copy would be nice (Headline, Description, Keywords). IPTC subject codes might again be a bit over the top. Status section again depends on your target audience. For an amateur it might be well to much. In Extensions / Image description there're nice location definitions, much more detailed than the core. Same for "Artwork objects" and "Models in images". Those might again be applicable even to the amateur. Overall, I think one could be quite pragmatic here. Move what is in DC right now to the larger IPTC namespace with a decent mapping (IPTC.Headline == DC.Title e.g.) But adding this to dt requires some additions to dts data model and some changes in the code. I think this is a larger project. > I think you mentioned this before: > http://sourceforge.net/p/darktable/mailman/message/29870585/ Yes. Well. Metadata is IMHO important if you want to search images. > I came across this problem recently when I started to tag and edit > metadata of my currently around 4000 RAW-Files. > In my view those information you mentioned above should NOT go to the > tag list You're right, of course. Adding them as keywords is a work around (if you're nice, and don't want to call it "hack" ;) for the missing fields. However, you can do it in a somewhat clean way by using keyword chains, e.g like: IPTC|Location|City|Hamburg IPTC|Location|Sublocation|Michel IPTC|Location|State|Hamburg IPTC|Location|Country|Germany First of all this adds some semantics, as it is now clear, that "Hamburg" in this context is not describing the image content but a location. Secondly, this allows to extract them easily later on and move them to their proper fields, once they exist. In a way you're just introducing the IPTC name space as a sub hierarchy of DC.subject. Not what DC.subject is meant to be, but it doesn't break just bend a bit. But I perfectly agree, it is a work around, and it results in longish chains and even many of them. > as it makes this very inconsistant (tags as far as I understand > them describe image CONTENT, not abstract maker infos) Agree. > but should go to > the specified fields instead like title, description and copyright infos > do also. Perfectly agree. But this requires the metadata fields to get extended. Unfortunately, there seems no one who'd like to tackle this, and my C++ is way to limited to do it myself. :S -- Kind regards, / War is Peace. | Freedom is Slavery. Alexander Wagner | Ignorance is Strength. | | Theory : G. Orwell, "1984" / In practice: USA, since 2001 ------------------------------------------------------------------------------ Start Your Social Network Today - Download eXo Platform Build your Enterprise Intranet with eXo Platform Software Java Based Open Source Intranet - Social, Extensible, Cloud Ready Get Started Now And Turn Your Intranet Into A Collaboration Platform http://p.sf.net/sfu/ExoPlatform _______________________________________________ Darktable-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/darktable-users
