Follow-up Comment #12, task #13769 (project health):
Hi, team !
At this point, we have the way of having multiple person names for a single
individual, as well as different uses and name representation formats.
The final touches would be:
- Single source : When name of type "official" is updated, the party.name
attribute will also be updated (with the person_name.given attribute. If the
family name is updated, the party.lastname will also be updated.
- The party.name is a Tryton required field, so we will leave it like that
keep compatibility. This requires to update the value whenever the PersonName
official given name is updated (should be minimal)
- Have a functional field in the main party form, to display the person name
as in rec_name, with the format used in name_representation.
- The party.name will become invisible and read-only. The new place to enter
the person names will be in the identifier section.
- The party.lastname will become a functional field (it will no longer exist
at DB level) and its value will be retrieved from the PersonName family
field.
- In the register section, the current DB party and lastname will be copied or
update PersonName . This will happen only if there is no person name of type
"official".
Let me know your thoughts and have a great weekend !
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/task/?13769>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
