The obsolete disease ‘obsolete primary Spirochaetales infectious disease’ (DOID:2257) has an alternate_id (DOID:0060034) that points to the active disease ‘dropped head syndrome’ (DOID:0060034). This DOID IRI has apparently been reused. This is similar to other diseases that duplicated IRIs (fixed in #1227) but the newly active disease was not caused by the Protege-related DOID duplication, instead being created last year in 4161c66c880d8ad5a93e4e60e99829745b6476cc.
I was able to find the original disease the alternate_id points to in the old SVN respository: ‘Spirochetes infectious disease’ (DOID:0060034). It appears that disease only existed in the HumanDO.obo file for two days, created on 2010-06-08 in revision 1277 and deleted on 2010-06-10 in revision 1293.
Since there’s a very slim chance anyone will use an alternate_id that existed for only two days from when the ontology was in an alpha state prior to regular release cycles and the new disease with the duplicate IRI has been active for almost a year, I’m going to handle this differently from #1227. I'll keep the new disease and remove DOID:0060034 as an alternate_id from DOID:2257. I'll also add a comment noting the old alternate_id and providing some of the details included in this issue.
The obsolete disease ‘obsolete primary Spirochaetales infectious disease’ (DOID:2257) has an alternate_id (DOID:0060034) that points to the active disease ‘dropped head syndrome’ (DOID:0060034). This DOID IRI has apparently been reused. This is similar to other diseases that duplicated IRIs (fixed in #1227) but the newly active disease was not caused by the Protege-related DOID duplication, instead being created last year in 4161c66c880d8ad5a93e4e60e99829745b6476cc.
I was able to find the original disease the alternate_id points to in the old SVN respository: ‘Spirochetes infectious disease’ (DOID:0060034). It appears that disease only existed in the HumanDO.obo file for two days, created on 2010-06-08 in revision 1277 and deleted on 2010-06-10 in revision 1293.
Since there’s a very slim chance anyone will use an alternate_id that existed for only two days from when the ontology was in an alpha state prior to regular release cycles and the new disease with the duplicate IRI has been active for almost a year, I’m going to handle this differently from #1227. I'll keep the new disease and remove DOID:0060034 as an alternate_id from DOID:2257. I'll also add a comment noting the old alternate_id and providing some of the details included in this issue.