Feature Request - Usable hierarchical keywords
I worked with iView3 for years and, with all his merits, one of the biggest weaknesses was the absence of hierarchical keywords
It was a rather bizarre idea of microsoft to implement "hierarchical keywords", which are in reality disguised "catalog sets".
So, please, implement - usable - hierarchical keywords.
This includes:
1. a simple and usable function to import and to export hierarchical keywords as .txt-files
for using and expanding and exchanging (with other applications) of a controlled vocabulary.
2. bringing EM2 to understand a hierarchy.
This means:
we need parent-words and child-words (both with attribute private and public),
we need synonyms,
we need a (optional) alphabethical sorting of the words,
we need a simple structure for exporting in .txt-files.
My proposal is:
[parent keyword - private] (bracket)
{synonym} (brace)
parent keyword - public
{synonym} (brace)
(tab) [child keyword - private] (bracket)
{synonym} (brace)
(tab) child keyword - public
{synonym} (brace)
with <ctrl> we assign a media-item to a single word,
without <ctrl> we assign a media-item to all words up to the parent.
Private words are internal - not written in media-files
In my opinion, as a humbly picture-maker, this should not be rocket science and it should not be necessary to re- and new-invent the universe, just look on Bridge CS3 or Photo-Mechanic.
In the meantime this feature is a question of sine qua non of a DAM-application, so, for me, EM2 is currently - regrettably - only minimal useful.
It was a rather bizarre idea of microsoft to implement "hierarchical keywords", which are in reality disguised "catalog sets".
So, please, implement - usable - hierarchical keywords.
This includes:
1. a simple and usable function to import and to export hierarchical keywords as .txt-files
for using and expanding and exchanging (with other applications) of a controlled vocabulary.
2. bringing EM2 to understand a hierarchy.
This means:
we need parent-words and child-words (both with attribute private and public),
we need synonyms,
we need a (optional) alphabethical sorting of the words,
we need a simple structure for exporting in .txt-files.
My proposal is:
[parent keyword - private] (bracket)
{synonym} (brace)
parent keyword - public
{synonym} (brace)
(tab) [child keyword - private] (bracket)
{synonym} (brace)
(tab) child keyword - public
{synonym} (brace)
with <ctrl> we assign a media-item to a single word,
without <ctrl> we assign a media-item to all words up to the parent.
Private words are internal - not written in media-files
In my opinion, as a humbly picture-maker, this should not be rocket science and it should not be necessary to re- and new-invent the universe, just look on Bridge CS3 or Photo-Mechanic.
In the meantime this feature is a question of sine qua non of a DAM-application, so, for me, EM2 is currently - regrettably - only minimal useful.
0
-
Thank you for the feedback, however it would be preferable if you went through the proper channels and contact Phase One directly rather than use the User to User forum.
http://www.phaseone.com/en/search/artic ... nguageid=10 -
Drew,
thank you for your words. I didn't realize, that you wrote something similiar to one of Rowan's posts.
So, I will send my feature request to phaseone-support.
For me, it still seems a very good idea, to collect in public feature requests of real users.
Sometimes a lucid users proposal becomes a real good thing by the discussion of others.
Stefan0
投稿コメントは受け付けていません。
コメント
2件のコメント