Based on your CSV, it looks like there's about 200 feeds that don't have any real value (don't return a dataset). From a quick glance, I think half of these probably are legitimately "deprecated" (meaning I can find a replacement feed for them), but there will also be some where we have no idea if the feed has truly been replaced or if it's just down.
We might need an additional issue to return some kind of "non-fetchable" message in the API response and in the website, for this use case.
Proposed solution
Ideally, we could add a new status enum like "unfetchable" to the catalogs schema, and then update this status enum for the feeds that we have never been able to return a valid dataset for. It could also be a separate field.
Describe the problem
Extension of #471:
Based on your CSV, it looks like there's about 200 feeds that don't have any real value (don't return a dataset). From a quick glance, I think half of these probably are legitimately "deprecated" (meaning I can find a replacement feed for them), but there will also be some where we have no idea if the feed has truly been replaced or if it's just down.
We might need an additional issue to return some kind of "non-fetchable" message in the API response and in the website, for this use case.
Proposed solution
Ideally, we could add a new status enum like "unfetchable" to the catalogs schema, and then update this status enum for the feeds that we have never been able to return a valid dataset for. It could also be a separate field.
Alternatives you've considered
No response
Additional context
No response