Article written by Henrik de Gyor on Digitalassetmanagement.org.uk
Before I mention DAM jobs descriptions themselves, many of these positions require experience, but what are the levels of experience in Digital Asset Management? How do you qualify the experience or even rank experience with DAM?
There are several levels of DAM experience from basic (1) to increasing in complexity (7). These levels include:
1. Simple DAM user (this is often the majority of DAM users)
2. Power user (aka Super user)
3. Practitioner in DAM Operations
4. DAM Administrator
Before I mention DAM jobs descriptions themselves, many of these positions require experience, but what are the levels of experience in Digital Asset Management? How do you qualify the experience or even rank experience with DAM?
There are several levels of DAM experience from basic (1) to increasing in complexity (7). These levels include:
1. Simple DAM user (this is often the majority of DAM users)
- Searching
- Collaborating
- Downloading
2. Power user (aka Super user)
- Applying metadata to assets
- Uploading (Import)
- Downloading (Export)
3. Practitioner in DAM Operations
- Establishing and evolving workflow
- Training
- Create documentation to be openly shared
- Support
4. DAM Administrator
- Possibly network maintenance
- Possibly maintaining servers
- Maintaining database(s)
- Working with API
- Running reports from DAM
5. Configuration
6. Implementation
7. Customization
Read the full article at digitalassetmanagement.org.uk
- Understanding the relationship of DAM system options, implications of the decisions made and configuring those system options to best suit business/workflow needs
- Testing configurations to make sure they work the way they are intended to
- Setting up roles
- Setting permissions per role
- Setting users within those roles
6. Implementation
- Roll out of the DAM solution
- Train users
- Support users
- Document the best practices
- Increase user adoption
7. Customization
Ultimately, the best would be to have experience in all of these hands-on experience at one point or another. If this is not an option, try to experience the most number of levels available.
- Identify and understand what is missing from the system which your organization may need
- Explaining what is missing from the system with written documentation
- Explaining the value of adding the customization since it will cost extra (time and/or money)
- Possibly draft a vision what the customization may look like and how it could work
- Possibly even coding the solution
- Thorough testing of solution
Read the full article at digitalassetmanagement.org.uk
Leave a comment