Note one issue you will face is that many smaller journals (~17k) don't have ISSNs and are currently invisible via the current /journals/ route. We are looking to publicly expose an internal container-id that will allow users to get at these and avoid the nonsense of juggling P-ISSNs and E-ISSNs. You can see a prototype in our labs API: https://api.labs.crossref.org/journals
We need some way of indexing things without ISSNs, as they currently are the primary ID we are using for journals, which in turn are the primary indexing system we have for tracking what metadata we'll crawl.
There are likely a smattering of other PIDs that they're using, like ARKs et al., and I imagine other projects like OpenAlex probably also deal with this problem.
Posing this as an open question for now since i don't have any good ideas for how to handle it aside from using crossref's labs API (which i don't think we're supposed to do).
More generally we probably want to add a one-> many table from journal to PID so we can handle various kinds of identifiers - currently the ISSN table is structured like this sort of key-value structure, so we might consider just making that a PID table.
@gbilder writes
We need some way of indexing things without ISSNs, as they currently are the primary ID we are using for journals, which in turn are the primary indexing system we have for tracking what metadata we'll crawl.
There are likely a smattering of other PIDs that they're using, like ARKs et al., and I imagine other projects like OpenAlex probably also deal with this problem.
Posing this as an open question for now since i don't have any good ideas for how to handle it aside from using crossref's labs API (which i don't think we're supposed to do).
More generally we probably want to add a one-> many table from journal to PID so we can handle various kinds of identifiers - currently the ISSN table is structured like this sort of key-value structure, so we might consider just making that a PID table.