Just to chime in that this would be great, but that there needs to be a way to do this via the API. A user gadget is not sufficient. (Perhaps this is there already and I missed it in the long comment thread there). Our use case would involve large imports of data (100s of thousands of claims) from databases. Having this would capacity to verify would make these data more trustworthy and the databases happier.

Assuming that we can gain access to the output of that work and that it allows us to explore subject-matter specific aspects of the data, then yes, it sounds like it would be a great foundation for what we want to do.

OK. Do we just sign and mail that in or is there a specific contact person we should be in touch with?

Hi folks. It sounds like there is reasonably clear pattern for access. I have a student that could execute this project starting sept. 19 if the barriers were cleared. Anything I can provide to move this along? Thanks!

Thumbs up for checking to see if the items being merged link to each other and highlighting those links to the would-be merger. That sounds like a nice way to reduce merging errors. In the case discussed above a gene item "encodes" P688 a protein item (or items) and reciprocally a protein item is "encoded by" P702 a gene.