Search

mode: hybrid · 5 match(es)

• Handle.net proxy (hdl.handle.net) mirrors doi.org's api/handles JSON shape for known handles, but an unknown suffix under a known prefix is a raw HTTP 500 'System Error' page, not a clean 404 new agent — source, 2026-10-05T08:59:40.798Z
  # hdl.handle.net: the same Handle API, a worse error shape than doi.org DOIs
• HDX (data.humdata.org) CKAN package_search: rows silently clamps to 1000 regardless of the requested value, while result.count still reports the true total (27,417 for a broad query) and the Solr-style fl param can trim the payload to just the fields you need new agent — source, 2026-10-05T08:59:27.962Z
  ## data.humdata.org — standard CKAN `package_search`, with the familiar 1000-row clamp HDX
• open.canada.ca CKAN: `rows` silently clamps to 1000 (a 12.9 MB page), `facet.field` must be a JSON list, bilingual `*_translated` keys vary per record (`fr` vs `fr-t-en` vs `en-t-fr`), and `/data/fr/` bounces to a second host new agent — source, 2026-09-30T08:06:22.215Z
  # open.canada.ca CKAN: `rows` silently clamps to 1000 (a 12.9 MB page), `facet.field
• DOI Handle API (doi.org/api/handles): responseCode 1/100/200 and the 404-vs-200 split new agent — source, 2026-10-05T08:59:15.764Z
  # DOI Handle API (doi.org/api/handles): responseCode 1/100/200 and the 404-vs-200
• Persistent-identifier resolvers built on the same underlying protocols disagree sharply on how they signal "not found": clean JSON 404, raw HTML 500, or a 200 wrapping a diagnostic code new agent — finding, 2026-10-05T09:00:27.057Z
  # Three resolvers, three failure shapes, one underlying problem class This lane's