avoiding long keyword list in iView

[rob cardillo]

Just wanted to thank Peter for his informative talks at both the iView and Adobe booths at Expo on Friday.  Learned a lot for sure but still have questions.  Would love to come to one of his day long seminars but can't do it this week and Nov 8 is election day.  Hopefully, he'll schedule more.

Still trying to get around the non-hierarchical keywording that all these catalog systems use (BB, Portfolio, ACDC and iView).  I have a large collection of gardens and plant images and the keyword listing of geus+species, etc. would be excessively long to begin with.   Plus, other types of info I want to include such as botanical feature (i.e. flower, leaf, bark, etc.) or garden type (i.e asian, formal, rock, etc.) would be mixed throughout that long keyword list in alphabetical order. Not very useful.

I realize catalog sets would be helpful but they aren't tied back into the IPTC fields and would be lost if and when this catalog would need to migrate.

My one thought for now would be to "reassign" some of the other headings.  Make "Events" into botanic feature or "People" into garden type and so on.  Or should I be looking at a keyword compiler? 

Or, maybe version 3.0 has solved this problem....

[peterkrogh]

Rob,
iView 3.0 supports hierarchical keywords, I just have not had time to play with it.  Perhaps Shayne can help us here.  I'll check it out and see what I can find.
Peter

[peterm1]

Peter, I just started using iView Media Pro 3.0 (I used to use PS Elements and iMatch), and it does not appear that there are heirarchical keywords in iView in 3.0.  I posted a question about this on the iView forum, as have others, and it appears that I have to use Catalog Sets instead to get heirarchical organizing. 

I am looking forward to your book - does it contain much discussion about iView?  I would like to take a seminar on it but I live in CT.  Any chance of an on-line seminar or materials addressing iView specifically?

Thanks,

Peter

[peterkrogh]

Peter,
You're right that iView does not support hierarchical keyword organizing.  They support Controlled vocabluary and associated terms, but that does not get us all the way to where we need to be.  I'll keep hammering away, and I think this is something we can see pretty soon.  I'm pushing for some kind of XMP-based hierarchical syntax definitions, but it's going to mean bringing a number of interests together.

As to iView and the book, I use it as the example of DAM software, and show how it can do a number of important functions, but it is not an iView book (O'Reilly was pretty adamant about that.)  I'm looking at a number of other options for teaching DAM workflow in the near term: probably will be some kind of movies on DVD.

I will also be working to take the show on the road: stay tuned.
Peter