SORIDs could include special characters like / (eg ORCID IDs), but the use of GET URLs makes this complicated. The SORID should be opaque to the API (and Match Engine), so perhaps this can be addressed by guidance for encoding. eg: SORIDs could be htmlencoded, or insignificant portions (https://orcid.org/) could be truncated.
The text was updated successfully, but these errors were encountered:
SORIDs could include special characters like
/
(eg ORCID IDs), but the use of GET URLs makes this complicated. The SORID should be opaque to the API (and Match Engine), so perhaps this can be addressed by guidance for encoding. eg: SORIDs could be htmlencoded, or insignificant portions (https://orcid.org/
) could be truncated.The text was updated successfully, but these errors were encountered: