C1 v9 Keyword Library Issue?

Douglas Lucock

• 1. Dezember 2015 09:08

So I upgraded to C1 v9 successfully (backed up Apple system, backed up catalog first), all looks fine. Then decided to try out the new Keyword Library function. First problem I had was how to get the existing hundred odd keywords into the library. When you only have one catalogue and try to import them, it tells you the catalog has to be closed. So I closed it but of course the tab where I import from/into is now also closed. So thought to myself, just create a new "Test" catalogue, close my real catalog and import them from my real catalogue into the "Test" catalogue. That seemed to work fine. I now had a Keyword Library, albeit in the "Test" Catalog. Then closed the "Test" catalog, went back to my real catalog and imported the keywords into the real catalog Keyword Library. All good so far. (if somewhat convoluted). Then decided to delete an unused keyword from the keyword library as a bit of a test, spinning beach ball and 108% CPU usage in activity monitor and 10 mins later.... it seems to have worked. Something strange is still going on here performance wise however. Macbook Pro i7 16GB RAM 1TB SSD (Catalog on SSD) with 35,000 referenced images on USB3 connected external drive.

So my questions are:-

1) Is that the only way(correct way) to populate the new Keyword Library from an existing catalog, or is there a simpler way?
2) Importing the keywords into the Keyword Library in my real catalog - are the actual keywords and keyword library linked correctly doing it this way? (Or have I created an orphan Keyword Library where even though the Keywords are same as what are attached to my image, they are actually separate unrelated entities?

Thx in advance.

0

• 

  harald_walker

  • 1. Dezember 2015 09:57

  See my comments in this thread.
  viewtopic.php?f=61&t=21334
  I have also addressed both issues and decided to go back to version 8. No time to play beta-tester.

  0
• 

  Douglas Lucock

  • 1. Dezember 2015 10:08

  Thanks Harold - I'm persevering as everything else seems solid both functionally and performance wise. It seems after the first one 1 or 2 deletes, performance is again acceptable and from what I can tell my method of setting up the Keyword Library has worked.
  
  Having said that I have another issue with keywords. I had a number of orphan keywords in my catalog and have been cleaning up. Now I have come across a number of items (JPGs and MOVs) that are not editable, but have keywords showing up in the Keyword Library. The problem is, I cannot seem to remove these keywords as it says "the action cannot be applied to any of the selected items". All I'm trying to do is remove a keyword. I'd normally ignore, but there are quite a few of these and by fluke they are the same keyword name as lower level hierarchical keyword. e.g. "Cars" might be attached to the MOV files and yet I also have(and want) Cars to be Hierarchical underneath "Transport" (e.g. Transport>Cars). Unfortunately being unable to delete these leaves me with a number (in my case 20-30) keywords in the lowest level of the hierarchy with a few dozen uneducable JPGs or MOVs which are duplicated with one in a higher level of hierarchy and no way to delete them either from the files or better still forget the file, just remove from the library and hence the filter would be sufficient. Its kind of like we need a force delete command to remove these types from the Keyword Catalog.

  0
• 

  Douglas Lucock

  • 1. Dezember 2015 10:40

  Update - Have an un-elegant fix for the orphaned keywords. Per my post above if you have uneditable files be it movies or small JPGs etc and they have a keyword attached. Simply "Remove them from Catalog" (File/Remove from Catalog) but don't trash them. Re-importing them then brings them back in without any keywords and you can then remove the keyword in question from the Keyword Catalog. Of course the only problem with this is now you have files sitting around with No Keywords and if you are checking to make sure you have all your images keyword of course you need to ignore these. Perhaps we need a standard keyword called "Un-Editable" or something thats get applied to these within C1's catalog but isn't ever attached (so to speak) to the file. That way they wouldn't show up as having no keyword.
  
  Cheers all.

  0

Post ist für Kommentare geschlossen.