Closed asajedi closed 1 year ago
It seems that when using arxiv and the user wants to resolve metadata the call to handle service metaresolver is slightly different from the usual one
Example:
landingpage: 21.T11973/MR@arXiv:2302.00338?landingpage
metadata: 21.T11973/MR@oai:arXiv:org:2302.00338?metadata
resource: 21.T11973/MR@arXiv:2302.00338?resource
Seems that for the metadata to call needs a oai:arxiv:org: prefix instead of simple arxiv:
This seems too specific in order to handle it in a generic way.
Do you think we can find another solution and handle it like we do with the other providers?
I resolved the problem by adapting the template handle to use arxiv instead of oai:arxiv:org, however, being able to resolve and display the metadata of the pid.
It seems that when using arxiv and the user wants to resolve metadata the call to handle service metaresolver is slightly different from the usual one
Example:
landingpage: 21.T11973/MR@arXiv:2302.00338?landingpage
metadata: 21.T11973/MR@oai:arXiv:org:2302.00338?metadata
resource: 21.T11973/MR@arXiv:2302.00338?resource
Seems that for the metadata to call needs a oai:arxiv:org: prefix instead of simple arxiv:
This seems too specific in order to handle it in a generic way.
Do you think we can find another solution and handle it like we do with the other providers?