Finding Duplicates

I really, really want to find duplicate records/assets by some useful identifying information aside from less-than-helpful options Cumulus Desktop Client currently provides. I've never had good luck with File Data Size or Asset Creation Date. The first option in the Find Duplicates dialog box arguably holds the most unrealized promise but, like many features was myopic in conception and implementation. "Compare Names Using Field... [drop-down list of Record Name or Asset Name]".

Give the option of expanding that to include other fields or add an entirely new option to pick a filed to compare. The prime candidate would be "XMP Original Document ID"... or any of the XMP fields Cumulus Captures from the XMP Media Management Schema, for that matter... oh heck, IPTC Date Created too (as it also captures the time).

As I write this I'm resorting to several hacks to determine the duplicate assets one of my photographers placed into a cataloging hot folder. The asset are automatically renamed so I can't rely on the Record Name or Asset Name options.

To Delete $Sources Categories or Not Delete $Sources Categories

To Delete $Sources Categories or Not To Delete $Sources Categories?, that is the question. Specifically, should the ability to restrict or implicitly allow an action be hard-coded into the DAM client? Or should that fall to the realm of the permission framework in the DAM system? Recently, I think Canto overstepped a bit by trying to answer that for everybody. Back when Cumulus 8.5.1 came out there was a "bug" in the Desktop Client that prevented all users except for the Cumulus SuperUser to delete or rearrange/reorder $Sources Categories.

A $Sources Category, FYI, is more involved than simply being under the $Sources Category Tree. There are three distinct types of Source categories. Directory Category Mac, Directory Category Windows and URL Directory Category. Continue reading

DAMageTIP: Remote Deploy Cumulus Desktop Client on Mac OS X

I mostly deal with Mac OS X at my "day job", so I'm a bit platform biased. But I can tell you, as a Cumulus Systems Administrator one of the single most frustrating things to do is a large-scale Desktop Client installation or upgrade. Why is that, you may ask? Well to be perfectly blunt, the InstallAnywhere installer is a piece of garbage; yet another product of misguided cross-platform mediocrity. (OK, that may have been a bit harsh. But, this is my blog and my rules. So there.) Fear not, there is a solution.

Here's why I'm so down on the installer Canto chose. The OS X version is incapable of being deployed to multiple computers remotely. Since I work at a Macintosh centric publishing house, that's pretty much a deal breaker for me. Until I decided to take matters into my own hands. The following details my adventures in creating an Apple Installer Package to be used with Apple Remote Desktop for remote deployment of Cumulus Desktop Client.

Continue reading

DAMageTIP: Customize Cumulus Menus

This DAM­ageTip is all about tam­ing the Cumu­lus Desk­top Client Menus. They’re a beast. There’s a ton of options and com­mands. Some, you — or your users — will use often, some hardly at all. Power users who love key­board short­cuts can become frus­trated by the lack of short­cuts for com­mon functions.

Let’s get to work. To edit the menus you’ll need a text edi­tor. An edi­tor that can do syn­tax high­light­ing (such as Tex­tWran­gler on OS X) is help­ful but not required.
Con­tinue read­ing

Bug or Feature? you decide…

Somewhere between Cumulus 8.5.2 and 8.6.1, Canto made a change to the way User Live Filtering works in the Native (Desktop) Client. At my "day-job" as a DAM admin, I put in an inquiry with Canto to see if this new behavior was really the intended one or if it was a bug. They had asked if it was possible for me to screen cast the differences between the features functionality in the two client versions.  Continue reading

Pro tip: check your client groups!

Here's a pro tip for you. When upgrading to a new dot release of Cumulus (8.5.x to 8.6.x in my case). Check your client groups restrictions you've previously setup and include the new version!! It will save you lots of headaches. 
I literally spent hours trying to figure out why several groups of users couldn't log into my Cumulus Server. Then it dawned on me. I had previously setup client groups to allow various catalogs to only use WebClient or Sites. I feel kinda silly.

Cumulus 8.6.0 for Mac OS X adds launchd support (finally)

Canto has apparently gotten the message: Apple wants developers to stop using things like cron and "StartupItems" and instead use launchd. A message they've been trying to get though developer's heads since Mac OS X Tiger (10.4) came out. This is a huge and welcomed change to manage the startup and shutdown of the various Cumulus system components on Mac OS X. Continue reading

RoboFlow: PITA to configure, awesome when it works

I’ve spent the bet­ter por­tion of the last few weeks fight­ing with RoboFlow. My main gripe is the doc­u­men­ta­tion is next to non-existent. What’s there is spotty and you can’t be sure it’s even accurate.

After going back and forth with Canto Sup­port for a few days, I’m pleased to say I’ve got some nifty work­flows in place that would have been next to impos­si­ble with­out cus­tom EJP devel­op­ment work. 

Bot­tom line: This Cumu­lus Add-on has the promise to be an essen­tial cog in your DAM work­flow design if Canto can pro­vide some robust doc­u­men­ta­tion. More to come on RoboFlow later.