How to get rid of the Smaller-Sign in the keywords.
I work with keywords and keyword-hierarchies.
Usualy C1 does display and store each keyword in a single tag.
Now suddenly I get a Smaller-Sign inbetween the tag, but only in one single keyword.
I have this structure:
Tier<Vogel<Milan<Rotmilan -> here I get the desired result (Tier Vogel Milan Rotmilan)
Tier<Vogel<Milan<Anymilan -> here I get the desired result
Tier<Vogel<Milan<Schwarzmilan -> here the tag of picture is filled with: Tier Vogel Milan<Schwarzmilan !!!???
I tried deleting and renaming the keyword but did not succeed.
Exporting and importing the keywords did not help.
I work with Capture-one Build 11.1.1.11
What can I do? I need it as single tag.
Usualy C1 does display and store each keyword in a single tag.
Now suddenly I get a Smaller-Sign inbetween the tag, but only in one single keyword.
I have this structure:
Tier<Vogel<Milan<Rotmilan -> here I get the desired result (Tier Vogel Milan Rotmilan)
Tier<Vogel<Milan<Anymilan -> here I get the desired result
Tier<Vogel<Milan<Schwarzmilan -> here the tag of picture is filled with: Tier Vogel Milan<Schwarzmilan !!!???
I tried deleting and renaming the keyword but did not succeed.
Exporting and importing the keywords did not help.
I work with Capture-one Build 11.1.1.11
What can I do? I need it as single tag.
0
-
After a lot of clicking and moving my keywords around finaly I got the desired effect (Schwarzmilan appears as single tag).
Still wondering if someone has a stuctured solution when this problem appears again.0 -
How did you create that particular hierarchy?
How did you fix it?0 -
I built the hierachie by rightclicking the item and added a subitem. (I have the german version so i suppose it is named like this).
I could work around by adding my Item in the root-structure and moving it to the point I wanted to have it.
by the way: Exporting the keywords/structure seemed ok. (no idea what was stored in the backgroud).0 -
[quote="NNN636428017489683868" wrote:
I built the hierachie by rightclicking the item and added a subitem. (I have the german version so i suppose it is named like this).
I could work around by adding my Item in the root-structure and moving it to the point I wanted to have it.
by the way: Exporting the keywords/structure seemed ok. (no idea what was stored in the backgroud).
Strange.
The effect is what might be expected if the hierarchy was loaded from a file where the hierarchy structure column indent had not been applied for some reason.
It's possible it might be an obscure language/character set related problem when loading a hierarchy by typing in a line with separator characters. If so it should be repeatable and if repeatable it would be worth reporting it to the Capture One Support Team using a Support Case.
Of course it might also be some sort of one-off glitch in the definition file as it was before you edited it.
The important thing is that it is OK now!
Grant0 -
Hi Grant
I will keep an eye on it.
Working as programmer myself I know how tricky it is to reproduce some cases.
Until then thanks for caring
Markus0 -
Hi Grant
still interested in what causes this phenomen? I think I found out:
Assuming we have this structure:
Cars
-- Audi
-- BMW
-- Jeep
I create a new stucture:
Motocycles
-- Ducati
-- Aprilia
-- BMW
here I think the System realizes that BMW is already used in Cars, so It generates the keyword: Motocycles < BMW but shows it like that only in the Picture but not in the catalogue.
Perhaps Capture-One should show a message: Keyword already used (or something like that), instead of creating a hidden stucture.
I hope that helps you. I have to find a workaround. BMW is tricky, as I do not want to specify more at the moment.
Kind regrds Markus0 -
Ah!
Ok, now I understand as I have seen the same with some of my hierarchies (for similar reasons that you have - duplicate needs in the hierarchies for some words and phrases). So you have identified the situation exactly.
What it is advising, of course, is which hierarchy it sees as the source of individual KW. So in your example the KW is from the Motorcycle top level hierarchy rather that the Car top level.
This might be important to know if making changes to KWs or if you needed to further refine search or filter for example.
An example:
A sports event where all participants are identified by a number might offer something like
Number>Class>Competitor Name (Or Number>Competitor Name>class)
Nice and easy and people can be identified for KW activity from any numbers found in the image.
However if the event had Unique competition numbers - for a vehicle for example - but that vehicle may take part in multiple races then "Class" or some sort of equivalent categorisation may not always be valid and that would, possibly, make the use of the hierarchy less efficient.
If the vehicle not only appeared in different races but also with different or multiple drivers it gets more complicated again.
Or the vehicle may have more than one number during the course of the event.
In most multiple race events with different types of vehicles there are often instances of the same number being used for different vehicles in different races with, usually but not always, different drivers or riders. So for a given top level of the hierarchy - the number is useful because it is likely to be visible in the image and so makes selection from the library easy - there may be several possible hierarchical KWs to choose from. Therefore the trace back to the originally selected hierarchy is likely to be useful information from time to time.
The initial selection and any maintenance and administration of KW's in a session or, perhaps worse, a catalogue, may suggest a need for several approaches for keywording, in particular hierarchies, depending in the image genres one works with.
However the use of the words (or partial words) in searches and filters most likely does make much use of hierarchies for any purpose since the search or filter definition needs to address the variable needs explicitly - unless one prefers always the Google "we know what we really want to push to you" search results approach.
Just my opinion of course.
Grant
However the use of the keywords0 -
Hi Grant
thanks for this throughout explanation.
Lets say this problem is solved so far.
Just a pity that the Keywords in the metadata of exported JPG the smaller-sign has included. As I pull it out on a other place (my homepage - picture-description). But now I see where it comes from (and is not a fault) I might be able to filter it, so the user is not confused.
have a nice week
Markus0 -
[quote="NNN636428017489683868" wrote:
Hi Grant
thanks for this throughout explanation.
Lets say this problem is solved so far.
Just a pity that the Keywords in the metadata of exported JPG the smaller-sign has included. As I pull it out on a other place (my homepage - picture-description). But now I see where it comes from (and is not a fault) I might be able to filter it, so the user is not confused.
have a nice week
Markus
Hi Markus,
I'll check the processed jpgs of a session I have been working on recently. I do not recall seeing this effect - but then I ave not specifically checked for anything strange in the keywords of the jpgs as far as I recall and I guess I should.
Grant0 -
Hi Markus,
I have looked at my processed jpgs from a session and the "tags" that Windows (7) shows in the Properties screen are the individual keywords separated by semi-colons. (;) C1 V11.2.
Reviewing the image through C1 certainly offers some hierarchy source information but after output processing there are just individual words.
Is that different compared to what you see for the output jpgs?
I am processing rather than exporting.
With a session if I use a KW to search I can find the expected "processed out" files and all of the .cos files that have that KW associated. Which is quite useful for simple discoveries across all sessions without creating a catalogue. It helps with speed of course if the files on the PC are indexed. The same applies to my NAS.
Grant0
Post ist für Kommentare geschlossen.
Kommentare
10 Kommentare