Change Details

This is a direct customer request. Because we already ingest disambiguation pages in the article namespace, we should tag them as such as they are created or revised. Currently, this is assumed to be low hanging fruit. Is this correct?

User Story: “As a PM, I want us to be able to make disambiguation pages distinguishable in realtime for the reuser" Job Story: “When the reuser is indexing new pages or creating a graph of existing new pages and want to use disambiguation pages to differentiate two or more articles that have the same name" Example: Jaguar (the car, the animal) **Acceptance criteria** # Document that explains how to use the category **ToDo** - [ ] Write a document that explains how to use the category - [] share document ===== Test Strategy ===== How I'm planning to test this? Can I do integration testing or this should be tested manually? Where this testing should be happening (what environment, local or dev)? What this can influence (what can be broken by this feature)? **Checklist for testing** - [ ] check if this thing is active - [ ] check if another thing is active ===== Things to consider: ===== * Will this work need new alarms/monitoring added. * Do we need to update any documentation (playbook or public documentation for this work) * etc. ===== Description (optional) ===== If possible add information on how this story/epic will contribute to the bigger picture or how it relates to the milestones being aimed for. This is a direct customer request. Because we already ingest disambiguation pages in the article namespace, we should tag them as such as they are created or revised. Currently, this is assumed to be low hanging fruit. Is this correct?

User Story: “As a PM, I want us to be able to make disambiguation pages distinguishable in realtime for the reuser" Job Story: “When the reuser is indexing new pages or creating a graph of existing new pages and want to use disambiguation pages to differentiate two or more articles that have the same name" Example: Jaguar (the car, the animal) **Acceptance criteria** # Document that explains how to use the category **ToDo** - [ ] Write a document that explains how to use the category - [] share document ===== Test Strategy ===== How I'm planning to test this? Can I do integration testing or this should be tested manually? Where this testing should be happening (what environment, local or dev)? What this can influence (what can be broken by this feature)? **Checklist for testing** - [ ] check if this thing is active - [ ] check if another thing is active ===== Things to consider: ===== * Will this work need new alarms/monitoring added. * Do we need to update any documentation (playbook or public documentation for this work) * etc. ===== Description (optional) ===== If possible add information on how this story/epic will contribute to the bigger picture or how it relates to the milestones being aimed for. This is a direct customer request. Because we already ingest disambiguation pages in the article namespace, we should tag them as such as they are created or revised. Currently, this is assumed to be low hanging fruit. Is this correct?