When merged IDs occur in filter queries, can they also be redirected?

[Tijmen Altena]

Hi Everyone,

As the data in OpenAlex improves, I think we can expect to see more and more deduplicated/merged IDs. It's neat that they're already redirecting in the API, but we noticed that in the queries we most often use (selecting multiple IDs), they don't forward to the new ID. E.g.:
https://api.openalex.org/authors?filter=openalex_id:A2224836008 as the old collapsed ID for Jason, yields nothing.

Can these redirects also be implemented in more complicated queries? There are usecases on our side where a user could store an ID that later is merged, yielding empty results. Alternatively, we would have to implement some sort of periodic replacement of those static IDs in our databases.

Warm regards,

Tijmen 

[Casey Meyer]

Hi Tijmen,

I see what you mean and how this is useful. We'll have to think about this one. The proper way to handle it would be to add the old IDs onto the merged record, then adjust our queries to look for those old IDs when filtering. I'll add it to our requested features list so we can discuss it the next time we get together.

Thanks,
Casey  

--
You received this message because you are subscribed to the Google Groups "OpenAlex users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openalex-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openalex-users/8029f38c-e015-4939-99a1-2b47d0be6ad3n%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Casey Meyer

Developer - OpenAlex, Unpaywall

OurResearch: We build tools to make scholarly research more open, connected, and reusable—for everyone.