Open amandafrench opened 11 months ago
Hi @amandafrench,
I have just seen your post about v2. Would this feature be something that could resolve requests to v2?
Best,
Tobias
@tobiasschweizer Hi Tobias! No, I'm afraid we still don't support content negotiation in v2 of ROR -- it's mainly a new metadata schema, as documented at https://ror.readme.io/v2/docs/data-structure and https://ror.readme.io/v2/docs/rest-api. But we'll keep this feature request open for future consideration.
@tobiasschweizer Hi Tobias! No, I'm afraid we still don't support content negotiation in v2 of ROR -- it's mainly a new metadata schema, as documented at https://ror.readme.io/v2/docs/data-structure and https://ror.readme.io/v2/docs/rest-api. But we'll keep this feature request open for future consideration.
No worries, I understand. I guess with content negotiation you could just resolve to v2. Let me know when I should / could try out anything ...
Request from a software developer in Switzerland for content negotiation.
Describe the problem you would like to solve Currently, a client has to "write a specific piece of resolver for each registration agency (the REST APIs are all different)"
Describe the solution you'd like "As a software developer, I would find it very convenient if I could take any PID (DOI, ROR, ORCID) and resolve it to some common metadata scheme to be used for further processing." ... "So instead of requesting https://api.ror.org/organizations/00tjv0s33 the user would request https://ror.org/00tjv0s33 with some accept header, e.g. application/json, and would get a redirect to https://api.ror.org/organizations/00tjv0s33. This way the user needn’t know the ROR API structure."
Who would benefit from this feature? Developers