Also, I strongly recommend using a gender-neutral Association like “Godparent” (rather than Godfather/Godmother) or “Godchild” (rather than Godson/Goddaughter) since the Gender information is already stored for each Person. It makes searches so much more simple to only have 1 type.
@emyoulation agree with you about “gender-neutral Association”. I also would like make mass-renaming of Association input. Its also because I want translate my data from Ukrainian into English. Is it possible? Thanks
@emyoulation, personally for me remembering the last association will be unconviniant feature because when I add godparent on one side I also add godchild on the second side, so, I switch each time. It also would be great to solve this extra job by adding associations to the second person automatically. For example, if I add godparent to person1, then association godchild will be added to the person2 automatically. And vise versa.
Wouldn’t it be even better to share the association record, i.e. the PersonRef object?
Associations relate two persons to each other. This relationship is almost always asymmetric (godperson → godchild versus friend ↔ friend). All there is to do is enhance a little PersonRef to hold two person handles instead of one (the ref field). By “splitting” this field into “antecedent” and “subsequent” and doing the same on rel (unless the relation type string itself hints at the asymmetry like “godparent/godchild”), the object can be shared between both parties in the relation (or even larger when considering other types of interpersonal relationships like fraternities or clubs – in which case the “subsequent” attribute does not make sense). Then updating the PersonRef object automatically updates in both parties.