Is the present implementation of the doi filter endpoint redundant?

Metadata Retrieval
,
1

We can filter on doi as so: filter=doi:{doi} and the result is essentially the same as /works/{doi} for example:

https://0-api-crossref-org.libus.csd.mu.edu/works?filter=doi:10.1002/adma.201404892
https://0-api-crossref-org.libus.csd.mu.edu/works/10.1002/adma.201404892

To me the doi endpoint filter seems to be redundant.

Why not use this filter to retrieve a particular DOI anywhere in the metadata e.g. in references of other works so we can resolve the cited-by DOIs from the REST API?

Cheers,

Dave

2

Hello Dave,

You can use both in the same way yes, but the /works/{doi} returns just one DOI but you can use multiple filters for the DOIs albeit not the most efficient way to return DOI metadata.

e.g. https://0-api-crossref-org.libus.csd.mu.edu/works?filter=doi:10.1002/adma.201404892,doi:10.22234/recu.20190701.e425

We are working on a new matching API which will help with the things you have mentioned. We will probably be releasing more information on these in the coming year, be sure to follow our blog for more updates: Blog - Crossref

Many thanks,
Paul

1 Like
3

Thanks again Paul,

Nice example which I will adopt for my use cases.

Looking forward to reading about the new API functions in future.

Cheers,

Dave

1 Like