it is fundamentally great that the Koken database exchanges data with the Lightroom (LR) database. Wonderful. The endless possibilities Koken offers to publish images and more is also really great.
BUT, I wonder why Koken NOT taking in more data from LR like Labels and Rating for example?
How about Categories and possibly other extremely useful IPTC data?
More than the basics functionality is place and has proven to perform well, so why hesitate? It's all there!
No I do NOT expect data manipulated in Koken-DB to be returned to LR. It is perfectly fine going one way, But then the right way, following some established standards.
Recently I came across a posting by a person named Paul asking whether selected featured content in Lightroom can be exported to Koken (see also: "http://bit.ly/2xAuzlh"). To my surprise and I hardly can believe it, Paul has not received an answer and worst of all any posting to his request is blocked. It bluntly says: "This question has received the maximum number of answers.". What the heck?
If Koken continues ignoring such useful customer requests then Koken shouldn't be surprised to fall off the market pretty soon.
I am willing to pay 100U$D for a image publishing service interacting with Lightroom provided I am able to export the carefully annotated data for images in an efficient way. As of today there isn't such a tool available yet.
Koken is already providing a very good starting base. Once we (the customers) can get our hands on our data, then there will be lots of great opportunities to develop really useful themes and templates.
Not like the recently released <koken:search> function that only spits out linked tags. Still today there is no decent search function available in Koken! Currently Google's user defined search engine is probably the best bet as it allows any easy implementation into a Koken template.
I'am certain many photographers / publishers / developers do agree with me in principle.
Just let us suck in our data into the Koken-DB!!
Greetings and thanks for your attention, Hans.
This question has received the maximum number of answers.