Hi!
Is it possible to evaluate the IPTC-Data to assign images to a predefined category and album?
I am thinking of the following fields:
Category
Supp Cat 1
Supp Cat 2
Supp Cat 3
These fields are mostly used by professional fotographers to sort them in a Database to find relevant images more easy.
What I am thing of in detail:
Upload Images into a folder, do a batch-add of this folder and the process looks into these data.
Category => Category (Mandatory)
Supp Cat 1 => Subcategory / if Supp Cat 2 is empty then Album
Supp Cat 2 => Sub-Subalbum / if Supp Cat 3 is emty then Album
Supp Cat 3 => Album if nothing from the above comes first.
Attached is a screenshot of the fields with content (just as an example)
I this Case the image will be placed into the following structure:
Natur => Pflanzen => 20100528
(CAT) (Subcat) (Album)
That sounds to me like an error-prone thing:
- What happens if there is no IPTC data?
- What happens if the appropriate categories/albums doesn't exist?
- What happens if you have the IPTC data, but also selected an album and want to add your pictures to that particular album instead of the automatic detection?
- ...
Maybe it's better to add new plugin hooks (if needed) and test this as a plugin in the first place. I assume not so much people will need that feature.
Quote from: Αndré on June 07, 2010, 08:39:23 AM
- What happens if there is no IPTC data?
- What happens if the appropriate categories/albums doesn't exist?
- What happens if you have the IPTC data, but also selected an album and want to add your pictures to that particular album instead of the automatic detection?
- ...
1.) continue as normal
2.) Create category and / or album
3.) showstopper :(
Close it pls and mark as invalid.
Quote from: taucher_0815 on June 07, 2010, 08:49:55 AM
3.) showstopper :(
Not necessarily. The default value of the album select box could be 'Determine by IPTC data'. I never worked with IPTC data, so I don't know which issues can occur. If the code is well designed, it should be possible. But the behavior should be thoroughly tested (ideally with a plugin for cpg1.5.x) before that feature will go to core (if at all).