Skip to main content
View as Markdown

Metadata on Different Object Types - Content Management

Metadata on Different Object Types​

Entry Metadata (objectType=1)​

The most common type. Attach custom fields to media entries for classification, workflow tracking, and searchability via eSearch.

curl -X POST "$KALTURA_SERVICE_URL/service/metadata_metadata/action/add" \
  -d "ks=$KALTURA_KS" \
  -d "format=1" \
  -d "metadataProfileId=$PROFILE_ID" \
  -d "objectType=1" \
  -d "objectId=$KALTURA_ENTRY_ID" \
  --data-urlencode 'xmlData=<metadata><Department>Engineering</Department></metadata>'

Category Metadata (objectType=2)​

Attach structured data to categories for category-based filtering, routing rules, and MediaSpace category pages.

curl -X POST "$KALTURA_SERVICE_URL/service/metadata_metadata/action/add" \
  -d "ks=$KALTURA_KS" \
  -d "format=1" \
  -d "metadataProfileId=$CATEGORY_PROFILE_ID" \
  -d "objectType=2" \
  -d "objectId=$CATEGORY_ID" \
  --data-urlencode 'xmlData=<metadata><Region>EMEA</Region></metadata>'

User Metadata (objectType=3)​

Attach structured data to user records for user profile enrichment, department tracking, or role-based content routing.

Partner Metadata (objectType=4)​

Account-wide configuration stored as metadata on the partner object. Use for global settings like compliance flags or license information.

User-Entry Metadata (objectType=6)​

Per-user-per-entry data such as quiz answers, personal bookmarks, or watch progress. The objectId is a user-entry ID, not an entry ID.