Open ChristianLieven opened 6 years ago
Looks like the most efficient method to do this would be the /identifers/validate/{id} service described here: http://identifiers.org/restws
I'm not familiar enough with REST/associated internet protocols to know whether having users with models containing ~1,000s-10,000s of identifiers to validate might overwhelm their servers...
I'm not too familiar with this either. Would it be a good idea to reach out to the maintainers of identifiers.org about the implications of hitting them with quite a lot of requests?
An alternative solution could be to do only one online check, namely to compare the MIRIAM XML file's date at http://identifiers.org/download/ to one that MeMoTe could ship (or contain). If the online version is newer, download it. Afterwards, all identifier schemas can be validated against the local XML file's content. This may be faster and save a lot of resources or online requests.
Problem description
Namespaces/ Identifiers may change over time/ become deprecated! Warn the user for this possibility => False positives!
This would fall right through since both match the
kegg.compund
regex A test that parsesidentifiers.org
could verify the existance of each identifer. Could have it skipped by default, and users who know that they can spare the time can activate it specifically