Keywording
So, time for a rant... Looking through the new manual for v 12, I cannot find any improvements to keywording. I possibly missed it, or the manual is not updated yet. All some of us needed was a way to exclude some keywords on export.
If I have a hierarchical list like so: -
~attributes
> ~colors
> > red
> > blue
> > yellow
and I have red selected, I don't want the words ~attributes or ~colors to show up in the exported keywords for the image. It is a fairly simple and basic requirement of a keywording system to be able to filter keywords on export.
Even if PhaseOne did not implement this as well as LR, where one can designate each keyword as exportable or not, plus have synonyms, the very least and easily implemented improvement they could have made to C1 was to allow a word filter on export, just one extra field in the Export Panel that says: -
Do not export keywords containing characters: ~
... where one could enter any character(s) which, if contained within a keyword, would not be exported. In the example above, I would use the tilde to avoid the export of any word containing it. As an ex-software engineer, from a software standpoint, the level of programming needed to implement this would be very basic, and yet, I find no such improvements in C12. What is going on PhaseOne?
This means currently that for every image I export, I must use another editor to delete irrelevant keywords, and I can tell you that it is a right pain in the...
As this has been asked for now for at least three versions, this leads me to NOT upgrade, and if I find an alternative, or even back to LR, I guess I will have to do so. Such a shame, as for me, it is the weakest and most frustrating part of the library management system.
However, if I missed it, and these facilities have been included/improved, I am happy for someone to let me know... 😄
If I have a hierarchical list like so: -
~attributes
> ~colors
> > red
> > blue
> > yellow
and I have red selected, I don't want the words ~attributes or ~colors to show up in the exported keywords for the image. It is a fairly simple and basic requirement of a keywording system to be able to filter keywords on export.
Even if PhaseOne did not implement this as well as LR, where one can designate each keyword as exportable or not, plus have synonyms, the very least and easily implemented improvement they could have made to C1 was to allow a word filter on export, just one extra field in the Export Panel that says: -
Do not export keywords containing characters: ~
... where one could enter any character(s) which, if contained within a keyword, would not be exported. In the example above, I would use the tilde to avoid the export of any word containing it. As an ex-software engineer, from a software standpoint, the level of programming needed to implement this would be very basic, and yet, I find no such improvements in C12. What is going on PhaseOne?
This means currently that for every image I export, I must use another editor to delete irrelevant keywords, and I can tell you that it is a right pain in the...
As this has been asked for now for at least three versions, this leads me to NOT upgrade, and if I find an alternative, or even back to LR, I guess I will have to do so. Such a shame, as for me, it is the weakest and most frustrating part of the library management system.
However, if I missed it, and these facilities have been included/improved, I am happy for someone to let me know... 😄
0
-
I hoped for some upgrading of the keyword library functionality as well. The biggest problem I have is the missing of synonym support. I put a lot of effort in keywording within LR building hierarchies and using synonyms (Latin names, several languages etc)
I lost almost everything in my existing catalogues and keyword lists when moving to C1. Within C1 there seems to be no alternative and here I am limited to adding some basic keywords.
I prefer C1 far above LR but this might force me to revert to LR...0 -
Yes, I know exactly what you mean. I don't quite understand that it is a section of the software that has had no real change since I believe version 7. It is not awful, allowing for hierarchical keywording, but lack of support for synonyms and selecting whether the keyword is exported or not is a big omission, especially coming from LR.
With the latest release showing no signs of improvement, I am actually exploring what other possibilities I have, including going back to LR, although that has to weighed up with its flaws too of course. Keywording is one of the biggest parts of my image data cataloging, and it is a shame that it is lacking in such a good piece of software as C1.0 -
Yeah! This is the third time I'm trying capture one ( have owned it for several years and never used it because of this) But the extensive keyword hierarchy I'm working with in LR just don't import over to C1. So no matter how good C1 is on all the other fields I NEED better keywording system and possibility to EXACTLY import the hierarchy I use on LR... If they implement this I can finally start to use C1 which I have been paying for all these years. 0 -
[quote="NNN636396995446904833" wrote:
...I NEED better keywording system and possibility to EXACTLY import the hierarchy I use on LR... If they implement this I can finally start to use C1 which I have been paying for all these years.
Yep, I hear ya...0 -
[quote="NNN636396995446904833" wrote:
...the extensive keyword hierarchy I'm working with in LR just don't import over to C1.
Could you possibly describe how you go about this? I am not aware of problems in this area.
[quote="NNN636396995446904833" wrote:
So no matter how good C1 is on all the other fields I NEED better keywording system and possibility to EXACTLY import the hierarchy I use on LR... If they implement this I can finally start to use C1 which I have been paying for all these years.
As far as keywording is concerned I believe the COP database layout is woefully inadequate. The layout is basically the same as 5 years ago, thus doesn't seem to be a priority with Phase One. Things will likely remain as they are for a foreseeable future.
You will find my analysis of the problem here:
MLI0
Post ist für Kommentare geschlossen.
Kommentare
5 Kommentare