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 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 →
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.
This DAMageTip is all about taming the Cumulus Desktop Client Menus. They’re a beast. There’s a ton of options and commands. Some, you — or your users — will use often, some hardly at all. Power users who love keyboard shortcuts can become frustrated by the lack of shortcuts for common functions.
Let’s get to work. To edit the menus you’ll need a text editor. An editor that can do syntax highlighting (such as TextWrangler on OS X) is helpful but not required. Continue reading →
A common scenario at work is that my team needs to direct users to specific parts of a a category hierarchy in Cumulus. The trouble is Cumulus doesn't readily display category information in a way that's conducive to a copy / pasting the full path of a given category. As a result my users and I usually end up writing it out by hand. (And that kinda kills my soul.) But there's a better way...