So, because it is declared as a has_one in the Person model in Panorama, that means that we should never have a case of a personID having two PersonAccess records, correct?  So, I can change it to has_one in the merge and redo the code to use the singular name and to Not handle multiple person_access records, right?  :)