All products

Set AEM page metadata with AI

Define shared metadata for a section of an Edge Delivery Services site and keep exceptions visible. Check a typical page and an exception before release.

Set AEM page metadata with AI when a section of a site shares a common value. A product guide may use one social preview image across a hundred pages while a launch article requires its own. A handful of path rules is easier for an editor to inspect than a separate repeated entry for every page.

The bulk-metadata workflow helps structure an Edge Delivery Services metadata sheet. Broader matches go above specific overrides, and values supplied in the page’s own source can take precedence over sheet defaults. Seeing those layers together helps explain a preview that appears to ignore an edit.

What it does

  • Find paths that share a sensible default
  • Add a specific exception beneath a broader rule
  • Check where two path patterns overlap
  • Distinguish sheet defaults from page-level values
  • Select representative pages for a preview check

Install and use

  1. Use an authorised EDS site index or supplied path list and the relevant metadata sheet. Applying or publishing a change requires the appropriate editing permissions.
  2. Ask, “Propose one preview image for the guides section and a different one for the quick-start page. Show the rule order and give me two pages to check.”
  3. Inspect the ordinary page and the exception in preview. If a value differs, check the page source and later matching rules before changing the default.

FAQ

Source

Made by FocusGTS. Original skill: bulk-metadata, published on GitHub under the Apache-2.0 licence.

View on GitHub