DAM Glossary Update

It’s nearly two months since we launched the updated DAM Glossary with a dedicated website: http://damglossary.org.  As promised, I will report back on any updates.  To date, these include:

  • New feature to request an editor account (more about this below).
  • Proper workflow approval controls for new terms.
  • Editor and user comments.
  • Suggest a term feature for non-editors.
  • Extended contributor profiles.
  • JavaScript plug-in to use DAM Glossary on external websites and auto-link matched terms.

The first version only allowed editors by invite only, i.e. you had to contact us to get an editor account set up.  We have now added a new feature where registered DAM Glossary users can request an editor account which allows them to add or modify DAM terms all from within the Glossary system itself.  To get upgraded, you are required to provide some basic details in support of your application, this is more spam protection to ensure we don’t get lots of people who want to post up stuff about weight loss pills etc.  Ideally if you want to assist with DAM Glossary, you will be able to provide some links to documents that demonstrate some knowledge of Digital Asset Management.

The first edition had no workflow/approval controls and editors could publish anything without it being verified.  We have changed that now so each edit or new submission will get checked prior to approval (with all the usual email confirmations that you would expect with the features).

Editors can now leave comments for each other that are only visible to other editors, not to general users.  This should assist with procedural discussions about certain terms.  The same user discussion facility about each remains and is accessible to anyone who has a registered user account (not just editors).

An option for non-editors to suggest a term has been added since we got a few emails from people with ideas for definitions we should add.  That is all managed via the DAM Glossary system now.

The contributor profiles can now include your LinkedIn and Twitter profiles as well as a blog URL (in addition to website and basic profile that we already had).

As you may have seen on DAM News, we now have a feature to display glossary terms on third party websites.  This uses an auto-match feature to find matching terms and then display a definition for them.  In the next update, we will enable other sites to get access to this with some configuration options to allow changes to the presentation style, colours etc.

We are planning further enhancements to the DAM Glossary in the forthcoming months.  Some innovations suggested by Henrik de Gyor, David Diamond (who have both been closely involved in the earlier stages) and others include:

  • Alternative definitions with user voting on the best one.
  • Options to add more obscure or contentious terms, but with the ability to filter them in/out.  This might include some DAM vendor definitions.
  • Arbitrary tags (and filtering upon them) to allow users who have a specific interest in a given area (e.g. photos) to show a subset of the glossary.
  • XML and JSON exports of the terms.

The second item has (itself) proved somewhat contentious with discussion about what to include or leave out.  My own opinion is that it would preferable to include as many terms as possible, but to ensure they come with the appropriate health warning that they may not be in widespread use (especially where a commercial interest has proposed them).

Probably the biggest issue at present is lack of other contributors.  At present, there is just myself and David Diamond who have submitted terms.  It’s starting to feel a bit like being the first ones to start dancing at a wedding reception or office party etc and without even having had the benefit of an alcoholic beverage (or two) beforehand.  So, to save our embarrassment and before I am obliged to start enthusiastically ‘throwing shapes’ (to use the vernacular) your participation would be much appreciated.

Share this Article:

Leave a Reply

Your email address will not be published. Required fields are marked *