Business Views Configuration

Business Views let administrators define how information about an entity is displayed to users. Instead of showing a fixed set of properties, Business Views allow for tailored layouts that focus on the most relevant data for a particular context, use case, or audience.

Each view is configured using a JSON file that specifies which information to display and how it should be structured on the page. Views can be created per class (e.g., Medicinal Product, Ingredient), and if an entity belongs to multiple classes, users can choose between different available views.

This page describes how to configure Business Views. For information about how users interact with them, see Viewing Business Views.

Accessing Business Views

Eligible users can configure Business Views by clicking the gear icon in the sidebar on the left to open the Admin page, and then selecting the BUSINESS VIEWS tab.

Creating a Business View

A Business View consists of sections. Each section defines a specific block of content, such as a list of properties, a table of related entities, or a set of images. Users can configure:

• The type of section (e.g., properties, table, image)
• The width of the section (e.g., full, half, third)
• The title shown to users
• What content is shown and how it behaves

The entire view is written as a JSON object with a top-level sections array.

Section Types and Examples

Below are examples of supported section types. These can be combined and customized within a single view.

1. Entity Properties Section

Displays selected properties from an entity.

{
  "sections": [
    {
      "type": "entity_properties",
      "title": "Basic Information",
      "width": "two-thirds",
      "properties": [
        { "uri": "http://example.org/ontology#name" },
        {
          "uri": "http://example.org/ontology#productCode",
          "customLabel": "Product Code"
        }
      ],
      "actions": [
        {
          "name": "Download PDF",
          "link": "https://example.com/file.pdf",
          "type": "primary"
        }
      ]
    }
  ]
}

2. Table Section

Displays a table of related entities using filters.

{
  "sections": [
    {
      "type": "table",
      "title": "Manufactured By",
      "width": "full",
      "table": {
        "searchTerm": "",
        "filters": [
          {
            "propertyUris": ["http://example.org/ontology#produces"],
            "valueTemplate": "{{ENTITY_URI}}",
            "operator": "IS",
            "includeHierarchy": false
          }
        ],
        "columns": [
          {
            "title": "Manufacturer Name",
            "field": "http://example.org/ontology#manufacturerName"
          },
          {
            "title": "Location",
            "field": "http://example.org/ontology#location"
          }
        ]
      }
    }
  ]
}

3. Image Section

Displays one or more images, either from static URLs or from an entity's image property.

{
  "sections": [
    {
      "type": "images",
      "title": "Product Images",
      "width": "third",
      "images": [
        {
          "uri": "https://example.com/image.jpg",
          "fromProperty": false
        },
        {
          "uri": "http://example.org/ontology#productImage",
          "fromProperty": true
        }
      ]
    }
  ]
}

Layout and Width Options

Each section can have a defined width:

• full: occupies the full page width
• two-thirds: occupies two-thirds of the page width
• half: occupies half of the page width
• third: useful for narrow content like images or short text

Sections will be arranged in rows according to their width. For example, three third-width sections will appear side by side.

Tips for Configuration

• Use custom labels to rename properties for better readability.
• Group related properties into separate sections with meaningful titles.
• Use actions to provide downloadable files or external links.
• Use the table section to show related data based on filters, such as linked substances or products.
• Users can create multiple views for the same class, depending on different user needs.