Skip to main content
MediaBeacon University

Changing Type Validator and UI Element Settings with Metaforms

Changing Type Validator and UI Element Settings with Metaforms.

Metaforms allow abstraction of an XMP field's parameters, to alter the function of that field as displayed in that metaform. Below are some well-known combinations.

  • Upload Metaform Auto Metadata: Using this combination will enforce automatic metadata entry without the user's interaction or knowledge on an upload metaform. Using this method, a specific metadata value will be entered whenever an upload is made with that metaform.
    • XMP Field: Any Type/UI combo
    • Metaform field settings: Use UI element "Hidden", and enter a value in the "Default" parameter field. The entry must be valid for the type of field. For example, a valid dictionary value if the field is a Force Dictionary field.
  • Subset Dictionaries per Business Unit: These techniques can be useful if a different sets of users need to enter exclusive sets of values (dictionaries) in a single XMP field. An example of this might be a "Flavor" field. The first of the two business groups that use the field makes baby food and the second makes pet food. Thus, the dictionaries used by each group need to be different. To avoid having to create business-specific fields, we can use one of the techniques below.
    • Master Dictionary & Subsets: In this scenario, the XMP field in question will be a Force Dictionary field, with a "master" dictionary attached. When this field is used on a business-group specific metaform, it will be paired with a business-specific "subset dictionary". The master dictionary must contain at least all terms contained in all subset dictionaries, to avoid write errors.
    • Subsets Only: In this scenario, a non-dictionary XMP field would be used (Type Validator: String). The metaforms themselves ensure no business group user will enter an inappropriate term within their individual context. The major advantage here is that this eliminates the need to maintain a set of master/subset dictionaries. Metadata administrators may find the Search Filter's drag-and-drop tagging feature useful for metadata editing in this case.
    • Auto Updating Suggest Dictionary & Subsets: This scenario uses several configuration points in conjunction.
      • Create a "Master" Dictionary, and connect it to a Suggest Dictionary XMP field.
      • Enable the "Synchronize Dictionary to Field" option on that master dictionary.
      • Create subset dictionaries as normal, however, there is no need to add all terms into the master dictionary.
      • Add the XMP field to metaforms, but change Type Validator to Force Dictionary, and use a subset dictionaries as needed.
      • This method will cause the master dictionary to auto-populate with terms as they become tagged into assets.
  • View-Only Fields: While simple to set up, this technique makes it easy to control who can enter metadata and when on specific fields.
    • The UI element "View Only" isn't recommended for use with XMP field configuration, only metaform field configuration. This would create an uneditable field in the former case.
    • Do not use "View Only" in conjunction with the "Not Empty" option. This will cause the metaform to prevent any edits to all displayed fields.
    • On an upload metaform, a View Only field can be used with the "Default" value to show users values that are being auto-added.
  • Was this article helpful?