Metadata Model Development
To develop a metadata model for the new DAM system, we worked closely with project stakeholders. We streamlined the existing metadata model by cutting one third of the fields without sacrificing functionality. Mindful of their busy schedules, we created the new schema iteratively in working sessions and in tandem with the DAM vendor when possible.
We made sure to create all deliverables in formats that would be compatible with the new DAM system. The schema included element names, element types, data source, definitions, and metadata attributes.
Through a series of discovery workshops and the development of a taxonomy framework, we identified a set of requirements for the new DAM system. We evaluated each of the existing taxonomies against these requirements (search, asset browse, workflow, etc.).
We then adapted the existing taxonomies to suit user needs and the chosen platform, and developed new taxonomies that we had identified in the metadata schema.
To enable the client to migrate existing metadata and taxonomy from the existing DAM system to the new one, we developed a cross-mapping table for migration planning and scripting.
We mapped existing metadata fields to new fields, where possible, and mapped existing taxonomy values to new one as needed. We also facilitated conversations between the client and the DAM vendor to ensure the content architecture was successfully deployed during implementation.