Custom Fields

Custom Fields enable the saving and searching of domain-specific metadata, such as information about business functions, digital rights, or whatever suits your needs. Custom fields are also a key function when integrating Media Pocket with other systems, as all inputted custom field data is accessible via Media Pocket API.

Creating Custom Field Groups

By default, the environment does not have any custom fields. Admins can create and delete Custom Fields from the More section found in Quick Menu. Admin must first create and name the group. 

Complex fields:

Field groups can be set to be complex, which means that individual fields are linked together and form one data record. With a complex field group, a certain field can be associated to same asset several times. This enables for example adding several time periods or dates, such as airdates or usage right periods.

Open by Default

Each group can be set to Open by default,  which means that the group is automatically opened if related to opened asset/project. This helps users to find the right metadata schema to fill or view when opening the asset.

Add by Default

Admins are able add Custom Field Group(s) by default to all assets by asset type/types (e.g., Image, Video, etc.). Once added, all existing assets and new assets will automatically have the created Custom Field Group(s) visible in the UI for easier data input. Admins may also update existing Custom Field Groups to be added by default. Note: Add by default do not count as null values and can therefore not be used in null search "Show only items that have values in this field group".

Edit group order

Editing the order of the custom field groups, i.e. how they are displayed in projects/assets, is possible by rearranging the list by dragging.

Adding Custom Fields

Once the field group exists, there can be added customized fields by editing the Custom Field group. Each group can have several distinctive fields. Each field must have a name and a type. The type determines what kind of data is collected.

Field types are:

• Date (yyyy-mm-dd)
• Datetime (yyyy-mm-ddThh:mm:ss)
  
• Integer (whole number)
• Textbox (single row)
• Textbox (multiple rows)
• Rich text (italic, bold, underlined, list, text type)
• Boolean (true/false)
• Dropdown (the values are created and deleted from the field’s edit tool)
• Timecode: Formats HH:MM:SS:FF or HH:MM:SS.ms. Frame rates 60,50,30,25,24,20,15,10,5,3,1. - Timecode fields have a validator that checks the input to ensure that it's not possible to add a value that doesn't fit within the specified frame rate
  - Via API it's possible to get timecodes in a different format by using /api/v2/assets/:asset_id/custom_fields?modifiers=timecode_with_framerate

The individual fields in a custom field group can be rearranged in the same way as the custom field groups (see above)

If the field is determined to be searchable, the assets can be searched and filtered based on the data filled in the custom fields.

 

Bulk editing custom field groups

You may bulk edit multiple custom field groups by swapping group from the dropdown. The edits you've made to a group will stay in place if you go back and forth to another group and edits are indicated with the pink dot. After all your editing is done, press save and all fields will be updated simultaneously. You are also able to discard all changes, individual changes or restore previous value.

Using Custom Fields

All users, including guests, can use custom fields to enrich their assets with needed metadata. Custom fields can be added from the menu on the right. The user must first add the custom field and then edit it to fill in the information. An asset can have several custom fields, but none of the fields are mandatory.

Custom Fields can be added for projects and assets. The custom fields used at a project level do not heritage to their assets.

Bulk editing custom fields

You may bulk edit custom fields of several assets at once with the bulk edit tool.

Note: If there is existing data on one or several assets, you will receive warning before saving.