Asset Search/Filtering by Metadata

Put Simply:
Users need a better way to browse, filter, and organize assets during the scoping and delivery planning process. Instead of seeing a long, flat list of unstructured assets, they should be able to filter based on metadata (e.g., region, asset type, industry) and optionally sequence assets for use in scope or delivery workspaces.

Why It Matters:

Improves discoverability: Helps users find the right assets faster, without scrolling through hundreds of irrelevant items.
Supports curated engagement planning: Filtering to “Golden Assets” or practice-approved content increases confidence in what's being used.
Enables relevance by context: Filtering by tech enabler, industry, or region ensures assets match client needs and delivery context.
Streamlines scoping and workspace setup: Aligns asset inclusion with scoped work and provides structure for downstream tools like Jira.

User Insights:

“Being able to filter and sequence assets within Concourse and Jira (instead of getting a list of 100 assets at a L5).” – Jeff
“Leverage metadata from Connected Source to filter in/out relevant assets… group assets by likeness.” – Erika

What’s Needed:

Integration with Connected Source that pulls back full asset metadata, beyond just PDM.
Filters in Concourse and Jira for:
- Golden Assets vs. public
- Region (e.g., global vs. US-specific)
- Type (template, AI, playbook, sample)
- Industry
- Tech Enabler (S/4, Ariba, Concur, etc.)
UI for filtering and grouping assets in the scope flow and/or delivery view.
Optional user action to sequence assets (e.g., reorder or assign to specific steps in a flow).
API updates to support new filters and metadata fields from Connected Source.
Governance and tagging strategy.