DAM for higher education: fit criteria and candidate vendors

Asset types in higher education

A higher education DAM holds campus photography, event media, recruitment content and departmental brand assets, and many of them show identifiable students and staff. Universities, universities of applied sciences and business schools share this pattern.

Typical asset families:

• Campus and student life photography, shot by staff and freelance photographers.
• Event media: open days, graduations, conferences, lectures by guests and sports events.
• Recruitment content: prospectus imagery, programme videos and social media assets for international students.
• Brand assets: the central identity plus faculty, institute and research group sub-brands.
• Research communication: lab imagery, research visualisations and press images.
• Heritage: historic photographs and documents, often owned by the library or archive.

The metadata model decides whether the institution can answer consent and reuse questions. DAMSelection assessment: make these fields mandatory at upload: photographer, shoot date, event or location and faculty owner. Add consent status, consent scope (web, print, social, recruitment abroad), consent expiry and the people shown where consent is personal. Design it with the Metadata Model Builder.

Regulation that shapes the DAM

Higher education DAM requirements come mainly from data protection law and public sector accessibility law. Both apply to the content the DAM stores and distributes.

Data protection

Fact: photos and videos of identifiable people are personal data under the GDPR, Regulation (EU) 2016/679, Article 4(1). Where an institution relies on consent, Article 7(3) lets the person withdraw it at any time. Article 17 gives data subjects a right to erasure in defined cases. The DAM must find every asset showing a person and act on a withdrawal.

Accessibility

Fact: Directive (EU) 2016/2102 requires public sector bodies to make websites and mobile applications more accessible. Article 4 names four principles: perceivability, operability, understandability and robustness. Many public universities fall under it. Article 12(3) set application dates of 23 September 2019 for new websites, 23 September 2020 for other websites and 23 June 2021 for mobile applications.

The directive excludes some content under Article 1(4), including pre-recorded time-based media published before 23 September 2020 and content that qualifies as archives. Article 1(5) lets Member States exclude websites of schools, kindergartens and nurseries, so check the national transposition for your institution. A DAM supports compliance by storing alt text, captions and transcripts with each asset. See the accessibility and alt text guide.

Fit criteria and weights

Higher education buyers should weight decentralised administration, consent tracking and user pricing highest. The table uses the twelve DAMSelection scoring criteria.

Score candidates with the scoring matrix, and compare with other sectors in DAM by industry. The candidate table on this page lists platforms from the enterprise content platforms and European specialists segments. Smaller institutions should also read the mid-market fit page, because their user and asset counts often match it.

Pricing for many casual users

Pricing archetype matters more than list price in higher education, because user counts are high and usage per user is low. A per-seat model charges for every lecturer who downloads one photo per term.

Worked example: an institution with 15 central communication staff, 120 faculty communicators and 900 staff who download a few assets per year has 1,035 potential users. Under a pure per-seat model all 1,035 count. Under a model with free viewer or guest access only 135 contributor seats count.

Ask each vendor to quote three user types: administrators, contributors and viewers. Model five-year cost in the TCO Calculator, including storage growth from event video.

Scenarios to script

Higher education demos should test consent handling, delegated administration and event speed on your own assets. DAMSelection assessment: generic vendor demos carry no selection value, so send the scripts and sample assets two weeks ahead. Build them in the Demo Script Generator.

Scenario 1: Consent withdrawal

A student withdraws consent for recruitment use. Ask the vendor to find every asset showing the student within three steps, restrict the assets to permitted uses, list where they were downloaded or published and record the action in the audit trail.

Scenario 2: Thirty faculties, one brand

Configure two faculties as separate spaces with their own administrator. Each administrator manages uploads and sub-brand templates but cannot see the other faculty's unpublished assets. The central brand team sees everything. Ask the vendor to set this up live from your organisation chart.

Scenario 3: Graduation day

A photographer uploads 800 photos from a phone and a camera during the ceremony. Ask the vendor to show auto-tagging, consent defaults for the event, selection by the press officer and publication of 20 images to the press portal within the same afternoon.

Integrations

A higher education DAM connects to identity, web and social channels and sometimes to the library. Single sign-on with the institutional identity provider is the first test.

Fact: the eduGAIN interfederation service connects identity federations around the world and lists over 80 participant federations. Ask whether each vendor supports your national federation for SAML single sign-on.

Rollout across faculties

A higher education DAM rollout works best in waves, starting with the central communication team and two pilot faculties. DAMSelection assessment: data, then process, then people, then tooling holds here as well, so the schema and consent process come before the faculty launch.

1. Agree the metadata schema, consent fields and faculty structure with central communication, legal and two pilot faculties.
2. Migrate the central photo library and clean consent records for assets used in recruitment.
3. Configure SSO, user types and delegated administration for the pilot faculties.
4. Train faculty administrators on upload rules, sub-brand templates and consent handling.
5. Launch to the remaining faculties in groups of five to eight, with a named administrator in each.
6. Review adoption after one term with the DAM KPIs: active users per faculty, search success and assets reused.

DAMSelection rule of thumb: plan one term for the central team and pilots and a second term for the remaining faculties. Use the user adoption guide for the faculty launch.

Pitfalls

Higher education DAM projects fail most often on adoption across faculties and on consent records stored outside the DAM. Five pitfalls recur in DAMSelection practice:

• Per-seat pricing pushes faculties back to shared drives, which recreates the problem the DAM was bought to solve.
• Consent forms stay in a separate folder, so no one can act on a withdrawal.
• The library's heritage collection and the marketing library share one schema that suits neither.
• Alt text and captions are left out of the upload form, so the web team adds them later or not at all.
• Faculty administrators receive full admin rights, and the taxonomy drifts within a year.