You are here: Home » DAM For Librarians » The Undervalued Role Of The Corporate Digital Asset Librarian

The Undervalued Role Of The Corporate Digital Asset Librarian

by Ralph Windsor on June 12, 2015

On CMSWire, yesterday, there was an article by Elizabeth Keathley from Atlanta Metadata AuthorityDAM Positions Are Going Unfilled.  The item is about the difficulties some firms are finding hiring Digital Asset Managers to take charge of their DAM initiatives.  Elizabeth identifies three different causes of this problem:

  • Lack of expertise by HR departments and/or recruiters
  • Unreasonable expectations of prospective employers
  • Compensation not commensurate with the requirements of the post

This is from the second point:

In at least two of the jobs that went fallow, the corporations really needed to hire a full DAM consulting firm — not just one employee. The description for one position asked that the person hired launch a full system in four months, complete with metadata dictionary, new taxonomy, and global access to an audience that sounded like it needed at least six access control lists defined and maintained. The company — which has thousands of product lines — expected the newly hired digital asset manager to do all of this with the support of an existing team of four other people, who would be learning DAM in the process. I’m assuming the job applicant should also be able to walk on water.” [Read More]

The fundamental issue appears to be that the role of a Digital Asset Librarian is still undervalued by many organisations, even though such staff typically offer superior ROI when measured up against related investments, e.g. software. The situation a few years ago (which is only just starting to change now) was that there existed an implicit assumption that DAM software obviated the need for a dedicated employee.  I can recall reading ROI cases for DAM where the costs saved by being able to dispense with a media librarian (usually for photos or videos) were at the foundation of the business case.  Indeed, in the earlier stages of corporate DAM, circa 2000-2005, this point was often highlighted by vendors in their marketing as a valid reason to buy their products.

Usually after a system gets deployed and the level of adoption is not as great as was first hoped there tends to be a gradual acceptance that you need a human being to pick up all the numerous finer points of DAM initiatives that the software isn’t flexible or smart enough to cope with.  I know of a few people who formerly had job titles like ‘photo library manager’ who were fired and then subsequently re-hired after a few months freelancing back at the firm who previously dismissed them (but with the new job title, ‘digital asset manager’ instead).   No matter how many times they are told, it seems executives responsible for DAM initiatives are pre-destined to make this mistake themselves before the folly of it finally sinks in.

In a similar vein to Elizabeth’s article, there was a post in April by Lisa Grimm on her personal blog where she noted that positions involving ‘librarian’ in the job title (or anything that might be construed as having a relationship with the same subject area) tend to be lower-paid than technical roles, even though the skill sets and level of responsibility might be similar:

I’ve experienced the disparity between IT and library-land salaries first-hand – I began my career in IT, building websites and managing content back when it had to be done by hand, before DAM and CMS solutions existed. Even as software to help corral and catalog content and digital assets came into being, my salary working with those tools remained quite comfortable. Then I went back to library school, with a view toward using my IT background, augmented by my new taxonomy and knowledge management skills, in the heritage/academic sector – libraries, museums and archives. Despite having additional skills and experience, moving into that world reduced my pay by more than 50%; at the time, it was a manageable reduction, and I had a fantastic work environment and great colleagues, but it wasn’t sustainable in the long-term. I returned to IT, and immediately more than doubled my salary – using the same skills, but with a different job title and cost center. While part of that jump was down to non-profit vs corporate budgets, even in the for-profit world, I know other DAM ‘librarians’ and ‘archivists’ who have found that a change in job title made a vast difference to them in terms of salary. It’s anecdotal, to be sure, but it seems that those whose titles are more ‘techie,’ and less ‘librarian-y,’ often have higher incomes, albeit for the same sort of work – and good luck figuring out who is more junior or senior, if job title is your guide! Clearly, we have some work to do.” [Read More]

I would agree with all this.  Part of the problem is the perceived ‘manual labour’ element related to anything associated with libraries and the staff who work in them.  The role invokes images of people carrying armloads of books, standing on stools next to shelving and carrying out mundane, filing-related tasks.  There is a perception among too many corporate managers that anyone with a basic level of education can do it.  As with the discussions about cataloguing from some our previous articles in the last few weeks, the intellectual aspects (or ‘thinking about what you have to do’ in plainer terms) are still complex undertakings that are not properly understood by anyone who has not done this themselves, or at least worked closely alongside a librarian.

Corporate understanding of this issue seems to traverse a number of distinct and identifiable points, which I can summarise as follows:

  • We need something to manage all our stuff.  Let’s get a system to do it.
  • The vendor promised us we just have to plug cash in and their system will take care of everything.
  • Now we’ve got this thing, we can just get everyone to upload and catalogue everything themselves during their ‘spare’ time and sack person x [if they were employed to start with] because we don’t need them any more, right?
  • We can’t find many useful assets on this system, it must be broken.
  • It isn’t broken, we can’t afford to get a new one and they’re all fairly similar anyway.
  • We need to hire person x to catalogue all the assets on behalf of everyone else, find stuff for them because they can’t/won’t do it themselves, train staff how to use the system, re-design our taxonomy, manage metadata entries, advise on format conversion and batch media processing, hassle the vendor support people for us, conduct user feedback and focus groups, plan integration with other IT systems, write requirements specifications for upgrades and make the coffee for everyone.
  • There must be loads of suitably qualified people who would jump at the chance to do this and are prepared to work for a super-cheap  salary too, right?

The job market (like any other) will eventually mediate a mutually acceptable level of remuneration for digital asset librarians, but in the interim period while that process works itself out, the cost to businesses will be limited ROI from their investments into DAM technology.  If I were contemplating a DAM initiative now, I might be thinking about how to get ahead of the curve by anticipating this issue and planning (in advance) what kind of HR implications it may have rather than running sequentially through my earlier list of points over a period of a year or two.

One final point for anyone hoping to locate digital asset managers who are not getting brilliant results from their regular recruiters, DAM Guru offers a matching service to connect employers with prospective staff for both permanent and freelance positions (and free of any costs also).

Related posts:


{ 2 comments… read them below or add one }

E Keathley June 12, 2015 at 6:25 pm

Your bulletpoint list there is a timeline story I hear over and over again!

Spencer Harris July 27, 2015 at 3:10 pm

I have experienced this with my current and soon to be previous employer. They are under the impression that they can get someone for less than $70K a year to manager their custom system which cost them hundreds of thousands of dollars to put in place. Before turning in my notice to move on to another company I asked about having a FT support role to my position and they said that automation would do enough to offset the need for FT staff. It will be interesting to see what happens over the next several months.

Leave a Comment

Previous post:

Next post: