Using the ModelAdmin I would like to implement one-to-one relations, but am unsure how to tell ModelAdmin the way to represent it.
The partial data model is:
Resumes --< Education +--- Address
So a resume could have many education records, and each of those records may have a single address of the establishment (university, school, college, etc.).
Using the standard ModelAdmin screens, the Education record is edited in a pop-up. However, the address is then selected in a drop-down of addresses, which effectively implements a one-to-many (addresses to education records). How would I go about making this one-to-one, perhaps having the address as a second tab on the education pop-up? Since there is a "Main" tab there, I assume it is possible to add further tabs.
How would saving the data then work? Would both records (education and address) be submitted and saved at the same time? What about clashes of field names - would the "Name" of the Address get mixed up with the "Name" of the education record?
Attached: screen shot of the education tab, showing the address drop-down that should actually be a single form.