Ellie 7.10 extends the custom metadata system for entities beyond simple text fields. Data architects can now define structured metadata types — including enumerations, boolean flags, and numeric fields — giving teams the ability to capture richer governance context for each entity. This is particularly valuable for organizations with complex classification requirements: regulatory categorization, data sensitivity levels, business criticality ratings, or domain ownership flags can now be captured consistently in structured form rather than as free-text annotations that are difficult to query or govern.
Ellie 7.10 enhances your metadata management experience considerably.
While administrators could already manage “entity” metadata fields as simple text inputs, we’ve now significantly expanded this functionality.
Here's what's new:
Custom Entity Metadata Types
Admins can now configure entity metadata fields with the following new “types”:
Text: Continue using text inputs for general metadata needs.
Chips: Enable metadata fields as “chips”. Choose between:
Free-form chips that allow flexible, user-generated entries.
Predefined chips that enable admins to set standard values for the field.
People: Simplify collaboration by creating fields where users can select colleagues.
Technical: A read-only metadata field designed specifically for integrations and API usage. It won’t be editable even when creating a copy of an entity.
Important to Remember
You can only set the “type” and “values” for a metadata field when creating it. It is not editable.
If you need assistance changing your metadata fields or have questions about this, please reach out to us at support@ellie.ai—we're always happy to help!
Clickable Links
We've also introduced support for links in metadata fields. Any URLs added to your text-based metadata fields will now be clickable to an external resource.
How to Add New Fields
Admin users of your organization can set up and manage entity metadata fields by navigating to Admin Tools → Entity Settings.
By default, new metadata fields are set as Text field type, but you can change the type to Chips, People, or Technical.
When selecting the Chips type, admins can specify whether users can input free-form entries or choose from predefined values. The values have to be set when creating the field, and are not editable.
Example Use Cases
Here are practical examples of how you can leverage these new metadata fields:
Source Systems (Chips): Use predefined chips to standardize naming of your data sources, like "Salesforce," "SAP," or "Google Analytics," making it easy to filter and manage metadata consistently.
Tags (Free-form Chips): Employ free-form chips for tagging entities flexibly according to specific projects, teams, or initiatives—such as "GDPR Compliance", "Marketing Analytics”, etc.
Owner (People): Set a "Data Owner(s)" or "Project Lead(s)" metadata field using the People type, ensuring clear accountability and facilitating direct contact by easily tagging the responsible team members.
Integration ID (Technical Field): Store IDs used by external integrations or APIs securely in a read-only technical field, avoiding unintended modifications or duplication during metadata copying.
Documentation (Clickable Links): Add direct links to external documentation or internal wikis right within your metadata, providing immediate access to detailed context or resources without switching platforms.
.jpg)
