As documented in T364594, there are 5 cases when Citoid can fail. [i]
This task involves the work of investigating the extent to which we can implement logging that would enable us – the team responsible for maintaining Citoid – to which of these 5 cases [i] is causing a given failure.
=== Story
As a member of the team responsible for Citoid functioning in the way volunteers depend on it to, I need to know why Citoid is failing and the frequency with which Citoid is failing in this particular way so that I can determine how urgently we ought to prioritize a fix for said issue/improve the experience for people who are encountering it.
=== Open question(s)
- [ ] 1. With what level of specificity can we log/track why Citoid is failing and the frequency with which it is failing in a particular way?
-- //Where "log/track" here means doing so in a way that would enable us to generate a real-time graph similar to [what we currently do](https://grafana.wikimedia.org/d/NJkCVermz/citoid?from=now-2d&orgId=1&to=now&refresh=5m).//
=== Citoid failure cases
//Copied from T364594//
|Failure case|Description|Capable of being logged?|Logging implementation
|---|---|---|---
|**JavaScript loaded pages**|Metadata cannot be retrieved because JS is used to load the metadata and Citoid cannot interpret JS|!!TBD!!|
|**Wrong media type (.pdf, .mov)**| | {icon check color=green} Yes | See T214038, and T365583.
|**GDPR Pages**| |Difficult to detect programmatically| User reported an issue with that here: T359059
|**Paywalls with no metadata**| Citoid is not able to access the metadata someone is requesting because the page is hosted behind a paywall|!!TBD!!|
|**IP Blocked**|The publisher/entity hosting the content for which someone is seeking metadata has blocked the IP address from which Citoid is making a request|!!TBD!!|