Reassess the `closeMatch` mappings between OEO and ENVO terms

[LillyG901]

Description of the issue

The use of the closeMatch mapping relation often does not describe the match as accurately as possible. Therefore it would be helpful to reasses the usage of it within the OEO.

Ideas of solution

The entity pairs currently connected through close match can be found within this table. It would make sense to add suggestions for the type of match(i.e. exactMatch. broadMatch, ...) in a separate column together with a justification for using the suggested type.

Workflow checklist

• [ ] I discussed the issue with someone else than me before working on a solution
• [ ] I already read the latest version of the workflow for this repository
• [ ] The goal of this ontology is clear to me

I am aware that

• [ ] every entry in the ontology should have a definition
• [ ] classes should arise from concepts rather than from words