Metadata Profiles

Introduction

The term metadata profiles refers to https://mediahaven.atlassian.net/wiki/spaces/CS/pages/3273949212 of type Base or Classification linked with a record of type Classification that functions as top of the https://mediahaven.atlassian.net/wiki/spaces/CS/pages/4062412801 .

Linking metadata profiles and top records

Profiles are linked with top records in an ordered manner
Top records are of record type Classification
The order in which profiles are linked with a top record determines the order in which the profiles should be shown in the UI
A profile is only applicable to certain record types
- All record types
- Specific record types, e.g. [Mh2Collection, Record]
- Optionally with wildcards, e.g. [Mh2Collection, Media*]
- Top records are the top objects in the https://mediahaven.atlassian.net/wiki/spaces/CS/pages/2291466251
  - MediaHaven 2.0 → Classification
  - DigiHaven → Series

Record Tree

Records have a metadata field Profiles which describes which profiles are linked to it
The content of this field is copied from the parent when a child record is created in the
The content of this field describes which profiles are applicable depending on the record type

"Profiles": {
  "Record": [
    "634656ef-265f-4a9a-b853-1b38dbfbbdcf",
    "5b2591b7-719f-40c2-b7c9-da92076ac2fc",
    ],
  "Mh2Collection": [
    "634656ef-265f-4a9a-b853-1b38dbfbbdcf"
  ]
}

Example MediaHaven

Take two example profiles

Profile “Descriptive metadata” linked with record type “Mh2Collection” and “Record”
Profile “Technical metadata” linked with record type “Record”

Example DigiHaven

Take two example profiles

Profile “Adres extensie”
Profile “Bouwaanvraag extensie”

Take two series

Series “Bouwaanvragen Stad Gent” linked with profiles
1. “Adres extensie” for Dossiers and Documents
Series “Bouwaanvragen Stad Mechelen” linked with profiles
1. “Adres extensie” for Dossiers
2. “Bouwaanvraag extensie” for Dossiers

Note that the record types for the profile “Adres extensie” differ depending on the top record Series.

Profiles Rights Management

Permissions on a profile field can be set using the Scope property of a Classification profile
A user can view/edit fields depending on their functions:

Scope	Required functions	Note

Scope	Required functions	Note
Public	None	Default scope The user “public” will lack the functions `VIEW/EDIT_ADVANCED_FIELDS` and `VIEW/EDIT_STANDARD_FIELDS` → Portal will not show these fields
Standard	`VIEW_STANDARD_FIELDS` `EDIT_STANDARD_FIELDS`	Use this scope to shield certain fields
Advanced	`VIEW_ADVANCED_FIELDS` `EDIT_ADVANCED_FIELDS`	Use this scope to shield certain fields even further