Arachnolingua focuses its OWL expressions on the claim (= assertion, statement) of an individual behavior event or class expression and properties should start there and work out. Thus: courtship_event –has_participant–>palp–part_of–>male–has_type–>Habronattus sp. There may be consequences for this decision (especially for class level statements), but it is better to be consistent and document the design decision here for now.
This should eventually make it into the ‘primer’ documents for the curation tool and the database schema as well. I wonder if there are any tools in Protege for looking at graphs of individuals – maybe lego?
Writing lots of unit tests and associated refactoring. Part of this was inspired by reading though Martin’s (2008) Clean Code, which had been sitting on my shelf for a couple of years. Most useful thing I found was Martin’s admission that even he writes big ugly functions on the first pass. Definitely a lot of cleanup in the new arachcurator editor. Also triggering some simplification in the database – I’ve removed a many-to-many mapping table (participant2claim) since the relation is really many-to-one. I think there are a couple of other tables that will suffer the same fate.
I should get back to cleaning up my list of terms as well.