Adobe DAM Taxonomy

Location: REMOTE

• Global Taxonomy (~20%) Overarching taxonomy applicable across the organization
• Local Taxonomy (~80%) The majority of the work, supporting multiple Business Units (BUs) including US-based BUs, and medical business units

• Taxonomy Enablement & Migration Translate and adapt the existing Veeva taxonomy into Adobe DAM, ensuring alignment across all BUs and stakeholder groups
• Metadata Governance Own and maintain the current taxonomy/metadata master, which lives in an Excel spreadsheet. Any taxonomy or metadata changes must be reflected and kept current in this document
• Downstream Impact Assessment Evaluate and communicate the ramifications of any taxonomy updates across connected systems, which may include:
• Email deployment platforms
• Banner/creative production tools
• Workfront (project management & workflow)
• Intake brief and content recommender tools
• Librarian Oversight Monitor and guide DAM librarians who are responsible for tagging and filling out metadata on individual assets; ensure accuracy and consistency, and augment processes where needed
• Stakeholder Engagement Field requests from internal clients across the organization who may ask for taxonomy additions or updates; assess the downstream impact of those requests before any changes are made
• New System Onboarding As new systems are brought online, assess whether metadata models within the DAM need to be augmented to support proper asset flow
• Intake & Asset Hierarchy Support Ensure that intake briefs and content recommender products align with the same taxonomy and metadata models; support blank asset setup with correct metadata at the point of creation