Asset Types | IMI Life Science

Product Asset Types

Purpose: Manage shared library classifications, their labels and display order.

What You Can Do Here

  • Create a type: Select Add Asset Type (Ctrl+N). Enter a name; the code is suggested automatically and can be adjusted before saving. Codes must be unique, use letters, numbers, underscores or hyphens, and cannot be changed later. New types are added at the end of the list.
  • Edit details: Select a row to open the side panel. Change the name or description and select Save changes (Ctrl+S). Closing the panel with unsaved changes asks before discarding them.
  • Translate: Select the language badge on a row, or open the Translations tab. The badge shows how many languages are translated; hover it to see which are missing. Leave a language empty, or select Clear, to fall back to the source text.
  • Reorder library classifications: Drag a row by its handle, or use Move up / Move down in the row menu. The new order is saved immediately. Reordering is available only when no search or filter is active.
  • Find types: Search by name, code or description, and filter by Custom, System or Missing translations.
  • Other actions: The row menu copies the code or ID and deletes custom types after confirmation.

Key Concepts

  • Labels: Library classification labels use exact locale translations, then neutral language and source names. Product download labels use the saved attachment role.
  • Grouping: The unified catalog supplies product media labels and group order while preserving existing attachment assignments and file classification defaults.
  • System types: Names, translations and order are editable, but deletion is protected.

Node Media Asset Classification

  • Asset Type: In the node Media tab, choose the classification in each attached file's Asset Type column. The choices come from the Asset Types manager and follow its configured order.
  • Shared classification: Saving changes the asset wherever it is used. It does not change the attachment role, main image, chips or attachment order.
  • Attachment Role: Choose the saved role used for the storefront download group. Changing it affects this node attachment, not the shared library classification.
  • Downloads: The storefront groups by saved Attachment Role even when Asset Type is Unclassified. Groups follow first-attachment order; files retain their order within each role.
  • Recovery: Retry loading asset types if the list fails. A failed classification save keeps the previous value; select the desired type again after resolving the error. If saving succeeded but refresh failed, reload the node before another edit.

Attachment Role Download Groups

  • Grouping source: Use the single Media Type selector in the node Media tab. Managed types and compatible legacy roles share one catalog; existing file classifications remain a fallback for missing roles.
  • Ordering: Managed catalog order controls resolved groups. Unmatched legacy groups retain attachment order, and files retain their order within each effective type.
  • CHIPREG: Both manuals share User Manual. Case-study PDFs and the demo ZIP share Tech Note. The model uses 3D Model. The brochure uses Technical Datasheet because that is its saved role.
  • Shared files: A file attached under different roles can appear in each role group. Changing an Asset Type does not change those attachments.

Unified Media Types

  • One selector: The node Media tab uses one Media Type control instead of separate Attachment Role and Asset Type controls.
  • Compatibility: Existing known attachment roles retain their meaning. Exact codes and unambiguous historical aliases use the managed type's name, translations and order. Missing or orphaned roles fall back to a saved file classification.
  • Legacy definitions: Missing legacy definitions are added to the Asset Types manager without changing existing IDs, names, translations, priorities or attachment assignments. Ambiguous definitions are not guessed or merged by display name.
  • Saving: A node selection changes only that attachment. Compatible legacy identity creation and attachment changes save atomically; the shared file default is not overwritten.
  • Missing data: Empty GUID placeholders are never displayed as type labels. A file with no meaningful assignment stays Unclassified until an editor selects its type.