Page Comparison

...

• Changes versus Metadata 17.1:
  • Renamed family Standard Fields to family Descriptive Fields
  • Renamed family Read-Only Fields to family Administrative Fields: this family provides information to help manage a resource, such as when and how it was ingested, file type
  • The administrative fields are now also exposed in the export sidecar metadata under the tag Administrative
  • New administrative field Workflow: describes through which workflow a file was ingested (if applicable)
  • New administrative field IngestTape: describes on which ingest tape the file was provided (if applicable)
  • New technical field OriginalFilename (same meaning as before but now in the correct family Technical)
  • New family Structural Fields which describe the ensembles the file belongs to and the related files
  • New internal field DeparmentId: uuid of the department the file was published with, the administrative field DepartmentName provides the human readable name.
  • Newly exposed internal fields HasKeyframes, IsFragment and ContainsGeoData
  • The search keys have been renamed for:
    • Keywords: {{MediaObjectFragmentKeyword}} → {{MediaObjectFragmentKeywordsKeyword}}MediaObjectFragmentKeyword → MediaObjectFragmentKeywordsKeyword
    • Catergories: {{MediaObjectFragmentcategory}} → {{MediaObjectFragmentCategoriescategory}}MediaObjectFragmentcategory → MediaObjectFragmentCategoriescategory

Legend

• Profile: If you fill this value out in a MediaHaven Profile this metadata will appear in the user interface
• Search / Searchable / Sortable: In the MediaHaven REST API you can search for it using this value if it is searchable and optionally sort the results (sortable).
• Read-only: This field cannot be modified in the user interface or API calls

...