Skip to main content
MediaBeacon University

Fields

Metadata schema and field configuration.

Under this tab you are able to create custom metadata schemas and configure their fields.

Add Schema

This field allows you to enter the name for a new data block you are about to create.

Fields_2.png

The name of the new data schema will show up in Asset View.

Schema_Example.png

Now you can attach the newly created metadata schema to any asset or a group of assets.

Do not autogenerate the M3taForm for this schema checkbox will tell MediaBeacon not to create a color tab at the bottom of asset view.

image205.png

Add Field

As soon as you enter the name of the new schema, you can start adding metadata fields to it. Above is an example of the new fields (Category, Description, Licensed, Origin, etc.) that were just added to schema Legacy Data.

To add multiple fields at once, enter their names, separated by commas.

image207.png

image209.png

Type Validator (Data validator)

Type validators allow you to check correctness of values that MediaBeacon users will enter into blank fields.

  • None: Allows any value. For instance, phone number instead of email in Email field.
  • Asset Reference: Lets the field contain clickable references to other assets.
  • Data Block: Lets the field contain multiple blocks of data from another schema, instead of just a single value. The specific schema is chosen in the adjacent drop-down menu. Data Blocks can be nested within other Data Blocks.
  • Date: Ensures that the format of the value entered is a date format.
  • Date Not Empty: Ensures that the format of the value entered is a date format and is required.
  • Email: Ensures that email is in a valid format and has an “@” sign.
  • Force Dictionary: Will require users to select metadata values from a controlled vocabulary.
  • Force Dictionary Not Empty: Will require users to select metadata values from a controlled vocabulary and won’t allow the field to be empty.
  • Integer: Makes sure the entered value is an integer.
  • Integer Not Empty: Makes sure the entered value is an integer and requires one be entered.
  • Not Empty: Ensures that the field is not left blank.
  • Phone: Makes sure the phone format is valid.
  • Phone Not Empty: Makes sure the phone format is valid and requires one be entered.
  • Positive Integer: Makes sure the entered value is a positive integer.
  • Positive Integer Not Empty: Makes sure the entered value is a positive integer and requires one be entered.
  • Positive Real Number: Makes sure the entered value is a positive real number.
  • Positive Real Number Not Empty: Makes sure the entered value is a positive real number and requires one be entered.
  • Real Number: Makes sure the entered value is a real number.
  • Real Number Not Empty: Makes sure the entered value is a real number and requires one be entered.
  • String: Makes sure that the value entered is in letters. String is up to 255 characters.
  • String Not Empty: Makes sure that the value entered is in letters and requires one be entered. String is up to 255 characters.
  • Suggest Dictionary: Will allow users to enter any value while dynamically suggesting possible results from a dictionary.
    • Fields set to Suggest Dictionary will be able to choose a dictionary called "SolrFacetSuggestions", which dynamically suggests possible results from the most used values.
  • Suggest Dictionary Not Empty: Will allow users to enter any value while dynamically suggesting possible results from a dictionary and requires a value be entered.

Hierarchy Checkbox

The hierarchy checkbox appears for all fields marked “Force Dictionary” or “Suggest Dictionary.” This must be checked to browse data hierarchically in the Search Filter widget.

Edit and View Levels

These columns allow you to specify what fields can be edited and seen by what users. You can set an individual user’s Edit and View Levels in their user profile under the Users tab.

UI Element

This column allows MediaBeacon administrators to specify in what form a given field is presented to end users.

  • String: A single line data input area.
  • Textarea: Same as above but allows users to add big blocks of text.
  • Advanced HTML: Allows users to add HTML data. Includes an HTML editor.
  • Simple HTML: Same as above, without the editor.
  • Date: Pops up a date selection box.

image213.png

  • Checkbox: Allows users to fill out metadata fields by clicking checkboxes.
  • Comma Separated Values: Allows users to add multiple values to a field.
  • Comma Separated Dates: Allows users to enter multiple dates separated by commas.
  • Comma Separated Textarea: Allows users to add several Textareas.
  • Cascade: Will attach cascading hierarchical metadata entry panel to the field.
    • This selection is only available for Force or Suggest Dictionary fields that have a hierarchical dictionary attached and the "Hierarchical" checkbox enabled.
  • Comma Separated Cascade: This option will enable multiple cascading entry panels.
    • This selection is only available for Force or Suggest Dictionary fields that have a hierarchical dictionary attached and the "Hierarchical" checkbox enabled.

      image211.png

  • Hidden: This option will hide the field in metadata panels.
  • URL: Displays a clickable URL. Commonly used in asset feeds.

Default

You can have MediaBeacon automatically pre-populate the given field with any value that you enter here. The idea is to have certain data pre-populated when a M3TAForm is applied to an asset.

Order

This column allows you to assign display position of the field. MediaBeacon’s metadata forms are dynamic, so fields can be re-arranged as necessary. By assigning “1” to a field you can ensure that it will be displayed first regardless of the alphabetical order of the other fields.

Index with SQL

Checking this button will tell MediaBeacon to index selected fields for multiple criteria searches using Advanced Search. This checkbox will also add selected data field to the Advanced Search interface.

By default, MediaBeacon allows up to 29 ‘String,’ 10 ‘Date,’ and 10 ‘Integer’-type fields to have the ‘Index with SQL’ checkbox checked. If an administrator tries to add too many, a warning will be printed on the page and the configuration won’t be saved.

A field is considered an ‘Integer’-type field if it has the ‘Positive Integer’ validator. A field is considered a ‘Date’-type field if is has the ‘Date’ validator. All others are ‘String’-type fields, except for fields with these validators or UI elements:

  • Asset Reference
  • Comma Separated Values
  • Comma Separated Dates
  • Comma Separated Textarea
  • Any field that’s multi-valued or hierarchic

These fields have dedicated indexed tables made on-the-fly during configuration that aren’t limited by the aforementioned ‘String’, ‘Date’, and ‘Integer’ limitations.

Index with R3Search

By default, all fields are indexed by R3Search and are available for use in R3Search widgets. To change the size of the R3Search index for a particular field or turn off R3Search indexing entirely, select a different value in this column. The default for this field can be set via the top right corner drop down titled “Index with R3Search Default.”

Allow Substring Searching

MediaBeacon ordinarily performs substring searches on file names only (e.g. searching for “hot” will return “jumpshot.jpg”). However, checking this box will allow substring searching on other fields as well. These substring searches are powered by R3Search, so “Index with R3Search” must be set to a non-zero value.

Locale Sorting

By default, all fields are set to sort by English rules. When the given field is used in the R3Search widget, or as a View Widget filtering criteria, and is set to Alphabetical, Reverse Alphabetical, Ascending or Descending, the field will sort based on the chosen locale sorting language rules. It is recommended that the use of this field match the primary language of the assets and users in MediaBeacon. The default for this field can be set via the top right corner drop down titled “Local Sorting Default.”

Synchronization Strategy

image213.png . 

MediaBeacon has a unique capability of storing data both in the database and embedded into the assets as XMP. Synchronization Strategy shown here allows administrators to configure behavior of MediaBeacon’s metadata fields.

We refer to it as “metadata volatility.” Individual fields can now be written to the database and assets in a way that makes the most sense for that particular field.

  • Synchronous: Data is written to the database and to assets in XMP. This is the state of all fields in older MediaBeacon systems by default.
  • Asynchronous: Instant database update and queued file system update. This option will allow very quick batch updates.
  • Volatile (Database Only): Only updates the database. Values in such fields are not written into assets until they are downloaded.
  • Bundle: If a given metadata field is set to either the “Bundle Volatile” or “Bundle Asynchronous” field type, values entered into a Transparent Bundle will inherited by assets within the bundle. See Below for more details. Values in such a field will not be editable as normal. Edits will only be allowed by Bulk Edit, M3TAForm Stamper, M3TAForm Upload, and M3TAForm Widget (although multiple assets must be selected).
Bundle Fields Settings
  • Bundle Volatile: Same functionality as Volatile fields, with the additional bundle functionality.
  • Bundle Asynchronous: Same functionality as Asynchronous fields, with the additional bundle functionality.
  • Overridable: When the Overridable checkbox is checked, assets within that bundle may have different metadata values than a containing bundle’s value. If an asset is not within a bundle, editing of the values is as normal. Overridable bundle fields can be edited on assets that are or are not part of a bundle.
  • Bundle fields in the Web UI: One or more bundle icons are presented to the right of bundle fields, allowing those with the privileges to perform the following actions
    • [Image] Bundle Field Settings
    • [Image] Reset Bundle Field
Adding Metadata to Multivalue Bundle Fields

When a field is set to “Comma Separated Value” and also to a Bundle Synchronization strategy, values added to the multivalue bundle fields will be added to any current values in assets (and bundles) contained in the bundle, rather than overwriting them.

Example:

Assets

Multivalue field contents before value change

After

/Bundle 1/

Test1

Test1, Newval

/Bundle 1/Bundle 2/

Test1, Test2

Test1, Newval, Test2

/Bundle 1/Bundle 2/Bundle 3/

Test1, Test2, Test3

Test1, Newval, Test2, Test3

/Bundle 1/Bundle 2/Bundle 3/Asset 1

Test1, Test2, Test3

Test1, Newval, Test2, Test3

Reset Field Options

Clicking this button returns all fields to their default state.

Clickable Column Headers

To change the values of a some columns for every field in a given schema, simply click the column header to cycle through its values.

  • Index with SQL
  • Index with R3Search
  • Allow Substring Searching
  • Synchronization Strategy
  • Was this article helpful?