hit the webpage itself
go to internet archive, see their DB if 404
go to google get pagerank score
User Story: “As a [type of user, who wants to accomplish something], I want to [perform some task],
so that I can [achieve some goal, why they want to accomplish that thing].”
Job Story: “When [some situation is happening], I want to [perform some task, motivation part]As a third-party reusers attempting to understand the quality of a new revision in its context, so I can achieve some goal,I would want to know if existing references/citation on an article are of quality as well. why they wantIf a URL is broken or goes to accomplish that thing 404 page on website, Expected Outcome].”it is a negative signal of quality for a page.
**Acceptance criteria**
# What is the expected result of this story?
# What else?
# What else?
We seek to understand if we can, in realtime, understand if an article has broken references.
**To Do**
- [ ] first thing[] hit the webpage itself
- [ ] second thing[] go to internet archive, see their DB if 404
- [ ] third thing
===== 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)?[] go to google get pagerank score
**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)Acceptance criteria**
* etc.
===== Description (optional) =====# Document options and feasibility in a doc, making a point of cost. Even if doable, would it worth doing given cost and any added latency?
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.