What Are Orchestry Property Bags?
As described by the great folks over at the PnP Modern Search community project, a property bag:
“...could be useful to store information about a SharePoint site or other element that can’t be tagged with a taxonomy value directly.”
Put simply, it’s a method used in web development to apply metadata to something, such as a SharePoint site. There are many ways we can then leverage these properties to help us identify sites correctly.
How Does Orchestry Create Property Bags?
During provisioning, Orchestry will automatically grab the following elements and provision them as property bags on your SharePoint site:
- Orchestry Template ID
- Orchestry Metadata
These property bags are included as "indexable", meaning that Microsoft Search will immediately pick them up and generate crawled properties for them.
To keep these property bags easy to identify, we always prefix them with 'Orchestry'. This is especially handy when it comes to mapping these property bags
How to Use Property Bags?
Typically, the first step in using any crawled property is to map it to a Managed Property so that its content can be queried. Once mapped, they can be used for custom search solutions, Microsoft Purview Content Search queries, or used to drive automated compliance rules with the help of Adaptive Scopes.
Check out this Orchestry blog post for some great examples of how to use property bags.