purl method generates URLs that result in 404 Not Found about ontologies_api_ruby_client HOT 1 CLOSED

Most cases of PURLs resolving as 404 Not Found errors have been fixed by a separate process where @alexskr ran a newly created Rake task in the ncbo_cron project called purl_management.rake to fix existing PURLs.

However, we still have a problematic case with the purl method.

For ontologies where class IDs have "purl" in the string, we simply return the class IDs. This is probably the desired behavior for classes in the UMLS format ontologies that we generate in-house. For example, the PURL for the "Body structure" class in SNOMEDCT is:

http://purl.bioontology.org/ontology/SNOMEDCT/123037004

... which correctly resolves to a page in BioPortal.

It's not the desired behavior though when the class ID has "purl" in the string and it's not a BioPortal PURL. One example is the "disease" class in the Human Disease Ontology where the class ID is:

http://purl.obolibrary.org/obo/DOID_4

... which resolves to a page outside of the BioPortal application. This isn't a 404 error as per the issue title, but the purl method should be adjusted to generate a URL that resolves to a page in BioPortal, i.e.:

http://purl.bioontology.org/ontology/DOID?conceptid=http%3A%2F%2Fpurl.obolibrary.org%2Fobo%2FDOID_4

from ontologies_api_ruby_client.