The pagecollectionmetadata API implementation was modified for performance reasons to only fetch metadata from parser cache instead of parsing the page every time. It appears that in some cases the metadata is not available in the cache. As a result, the recommendation API uses the page title as the collection name even if a different name may be provided in the name attribute of the <page-collection> HTML marker.

The specified name being ignored is the first problem.

The second, and more serious, problem is that different servers may know the same collection by different names, which means they may perceive a collection as unknown and therefore not returning recommendations for it.

Possible solutions include

• Reparsing the page in the API if the parser cache entry is not available

• Having both collection id and name in the model so that even if the display name differs, the ID, which could be the page title, is consistent

Derived Requirement

Ensure that page collections using the <page-collection> markup correctly display their custom name in the unified dashboard. If a custom name is not specified, the collection should default to the page title.

• Page collections with a name attribute should display the specified name in the unified dashboard.
• Page collections without a name attribute should display the page title.
• Collections in the User: and Event: namespaces should be excluded from verification.

Test Result - Beta|Prod

Status: ✅ PASS / ❓Need More Info / ❌ FAIL
Environment: beta/xyzwiki
OS: macOS Sequoia 15.4
Browser: Chrome 134
Device: MBA
Emulated Device: NA

Test Artifact(s):

Test Steps

Test Case 1: Verify That Changes to the name Attribute Reflect in the Unified Dashboard

1. Edit a page collection in the main namespace by modifying the name attribute inside the <page-collection> markup.
2. Refresh the unified dashboard and locate the collection.
3. ✅❓❌⬜ AC1: The updated name should be reflected in the unified dashboard.

Test Case 2: Verify That Page Collections in User and Event Namespaces Are Not Considered

1. Navigate to a page collection in the User: or Event: namespace that includes the <page-collection> markup.
2. Open the unified dashboard and locate the collection.
3. ✅❓❌⬜ AC2: The collection should not appear in the unified dashboard.

QA Results - Test Wiki