> Yes, I had some ideas and started working on it but I am kind
> of stuck. I still have to evaluate some things before I can
> proceed. Current plan is to import basically every bit (*) of metadata
> into the db (so it can be used to find images which wouldn't work if
> it gets read on demand). I am still not sure if all that data should
> be put into the XMP, too. Or just if it has been changed in dt from
> its original value.
[...]
> (*) this will most likely be limited to a curated set of fields which
> should however be big enough for almost everyone.
My entirely personal view is that there should be a hook in the
code for extracting truly arbitrary exiv2-supported fields from the
underlying file. Camera makers seem to be endlessly inventive about what
data they put into their files, so regardless of what you do to the code
now I think that sooner or later people are likely to hit another case
where there's some piece of data that has not been pre-imported into the
database.
(And as you say, you're intending a curated set of fields which should
be big enough for 'almost everyone'.)
While I'm dreaming, it would be really great if one could literally
specify the fields to display by exiv2 name and thus get at arbitrary
fields as long as their format was known by the underlying code, but
I suspect that that's way, way beyond the bounds of what people are
contemplating as far as metadata display and customization goes.
- cks
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
_______________________________________________
darktable-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/darktable-devel
