Closed torrin47 closed 7 years ago
So we know that this is likely to be problematic in any browser: https://edg.epa.gov/metadata/catalog/search/resource/details.page?uuid=DOI:10.1002/rcm.7367 What if we created a new webapp called: https://edg.epa.gov/doilink/DOI/10.1002/rcm.7367 that acts as a redirect service to the corresponding record in the EDG... Still need to decide on official syntax for including DOI in EDG.
Test records. DOI_Test.txt
Some stakeholders are wanting to switch to use DOIs (https://en.wikipedia.org/wiki/Digital_object_identifier) as their unique IDs, which seems to be ok in the database, but isn't supported as a direct link to the record using the standard syntax A custom Identifier may be used to return a record via an indexed field: https://edg.epa.gov/metadata/rest/find/document?f=dcat&searchText=fileIdentifier:A-280j-22 or by pretending it's the UUID: https://edg.epa.gov/metadata/catalog/search/resource/details.page?uuid=A-280j-22 https://edg.epa.gov/metadata/rest/document?id=A-280j-22
But if the custom ID includes a / which is part of the DOI specification, those direct linkages seem to break. Is there anything we can do, or is this a problem with how browsers parse URLs?