Metadata

metadata represents context data you define the schemas that give tags their contextual structure in the metadata tab each schema is stored as a versioned json schema file that declares the fields a tag can hold metadata buckets are configuration entities that model a related set contextual data access cloud tags in cloud management > metadata view a list of metadata buckets with their current version, bucket type, and any associated pack to filter the list to the latest version of each bucket, select only latest note for more information on metadata, see metadata https //docs cloud google com/manufacturing data engine/docs/concepts/metadata in the mde documentation bucket types each metadata bucket has a type that determines how its data is used type description tag holds contextual attributes directly on the tag, such as location or asset classification record holds structured records associated with the tag's data lookup provides reference data used to resolve or enrich tag values creating a metadata bucket to add a new metadata bucket click add new metadata bucket this opens the edit metadata bucket version panel fill in the following fields bucket name a unique name for the schema, for example, assethierarchy or alarminst version the version number for this bucket definition tag the tag category this bucket applies to instance update mode controls how updates to the schema are applied to existing tag instances instance override replaces the existing instance data with the updated schema values in the schema section, enter the json schema that defines the fields for this bucket the schema follows the json schema specification and declares the properties, types, and descriptions for each field note once a bucket version is saved, its schema is read only to modify the schema, create a new version of the metadata bucket existing tags that reference the previous version are not affected until you update their type to point to the new version versioning metadata buckets are versioned so that schema changes can be introduced without immediately affecting tags that depend on the current version when you need to update a schema, create a new version of the bucket rather than editing the existing one you can then update the relevant types to reference the new version and control when the change takes effect