just a word about lua here...
DT core might only work with a subset of the metadat available, but it
would make sense to give access to all metadata to lua so users can use
them for their own need. So whatever solution we use, it would be nice to
have some primitives to fetch/enumerate any metadata in DT core. Writing
would be nice too but is of a lower priority....
On Thu, Jul 18, 2013 at 11:55 AM, Tobias Ellinghaus <[email protected]> wrote:
> Am Donnerstag, 18. Juli 2013, 09:05:31 schrieb Willem Ferguson:
> > In all fairness to the dt developers, users, note that the metadata and
> > tagging issues are currently listed in the Developer's Wiki as 'Features
> > under consideration' in the section 'Versions and Roadmap'. The question
> > is whether there is any interaction possible between users and
> > developers that can at this stage help so that these features become a
> > reality.
>
> I have been reading the discussions about metadata handling for some time
> now.
> Since you finally moved it to the developers list I feel that the time has
> come
> to start getting some input from you.
>
> Currently dt has only a hand full of fields that mostly come from dublin
> core.
> However, we mix the semantics up somehow and treat them like XMP fields,
> it's
> all quite messy.
>
> So the first question that needs to be sorted out is "is supporting IPTC
> enough?" or do we also need all the exif and XMP fields? And if we decide
> that
> IPTC is all we need, are there standardized translations to/from exif and
> xmp?
> Because, if we get fed an image (or sidecar file) that contains relevant
> information in those metadata sets, we surely want to keep them. The
> alternative would be to support all possible data sets, however, that would
> mean that we
> 1) have to decide what to do when the user changes the "Author" value in
> exif.
> Shall it be changed for IPTC, too?
> 2) have to find a way to not make the GUI too cluttered and ugly,
>
> I personally would favour limiting ourselves to IPTC in the GUI and when
> finding some other data sets while reading the image we should translate
> these
> to IPTC.
>
> The next step after deciding what we actually need is to find a suitable
> way to
> store that in the database and sidecar file (some of these are trivial
> decisions, I just wanted to write them down once).
>
> TL;DR:
> [0] alone will probably not be enough, but what about also supporting [1]?
> Is
> our current set completely supported by that?
>
>
>
> > Kind regards,
> > wf
>
> Tobias
>
> [...]
>
> PS: You might have noticed that I don't intend to add all the technical
> exif
> data to the list of editable things in the GUI. If someone intends to
> change
> the aperture, well, go ahead, but not from inside dt. <-- Comments welcome
> ;)
>
> [0] http://www.exiv2.org/tags-xmp-iptc.html
> [1] http://www.exiv2.org/tags-xmp-iptcExt.html
>
> ------------------------------------------------------------------------------
> See everything from the browser to the database with AppDynamics
> Get end-to-end visibility with application monitoring from AppDynamics
> Isolate bottlenecks and diagnose root cause in seconds.
> Start your free trial of AppDynamics Pro today!
> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
> _______________________________________________
> Darktable-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/darktable-users
>
>
------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
Darktable-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/darktable-users
