# Invalid CSL-JSON record types
**URL:** https://community.crossref.org/t/invalid-csl-json-record-types/14332
**Category:** Interfaces for Machines
**Tags:** bug, content\_type\_advice, rest-api, metadata-retrieval
**Created:** [18 August 2025 19:06 UTC](https://community.crossref.org/t/invalid-csl-json-record-types/14332 "2025-08-18T19:06:07Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@larsgw](https://community.crossref.org/u/larsgw)
#### Post date: [18 August 2025 19:06 UTC](https://community.crossref.org/t/invalid-csl-json-record-types/14332/1 "2025-08-18T19:06:07Z")
I’ve encountered a few invalid CSL-JSON records returned by the REST API:
- `10.33915/datasets.1` (`https://api.crossref.org/works/10.33915/datasets.1`) (type `database`) returns an invalid CSL-JSON record with `"type"` set to `null` instead of `"dataset"`, `"document"`, or `"book"` (the de-facto “default” type before CSL 1.0.2). [copied from GitHub CrossRef/rest-api-doc#586]
- Several DOIs return records with `"type": "dissertation"`. That should be `"type": "thesis"`, optionally with `"genre": "Doctoral dissertation"` (or the like). [copied from GitHub CrossRef/rest-api-doc#580]
---
### Author:  [@mrittman](https://community.crossref.org/u/mrittman)
#### Post date: [19 August 2025 14:40 UTC](https://community.crossref.org/t/invalid-csl-json-record-types/14332/3 "2025-08-19T14:40:45Z")
Thanks for reporting these. We have a couple of tickets open to look into these issues, however they aren’t a high priority and I can’t promise that we’ll get to them soon:
[Normalize CSL type field](https://crossref.atlassian.net/browse/CR-2049)
[CSL JSON from content negotiation doesn’t validate](https://crossref.atlassian.net/browse/CR-2212)