Create AssignedPerson class

[pendingintent]

Will require the AssignedPerson class entity to support work in the DTA workstream.

[pendingintent]

add ability to create 0 to many AssignedPersons to an soa

• Move Organizations and Roles cards from http://localhost:8008/ui/soa/{soa_id}/edit to their own, dedicated UI page located below "Study Cells" in the navigation menu
• Add fields on the new UI page in a new card below the "Roles" card for managing Persons
• Creating a Person will require the PersonName entity class
• An uid Person_{n} is automatically generated following the exact monotonic max+1 pattern (checking both live table and audit table)
• The user enters the name, label, Description, jobTitle values
• A new dropdown select field is required for "Roles" that allows the user to choose from a list of "Person" values in the soa_id. The selects persons will populate roles.assignedPersons New database object(s) will be required
• Update generators and include in src/usdm/generate_usdm.py
• Ensure the output matches the requirements and rules of schema/USDM_API_v4.0.0.json
• Use the skill usdm-modeler
• use ui-design skill
• If low confidence, prompt me for clarification

[pendingintent]

Some feedback regarding:

There is an USDM rule that indicates that either an assignedPerson or an organization should be linked to a role. For StudyRole-2 you have now both but the organization can then be linked via the assignedPerson.

[pendingintent]

Core ID: CORE-000997
CDISC rule ID: DDF00190
Description: A study role must not reference both assigned persons and organizations.

[pendingintent]

Need to check the logic of this conformance rule as implemented currently.

The description reads that if the assignedPerson has an organizationId assigned, then the role should not have an assigned organizationId.

However, the logic in the workbench seems to be both an organizationId and a assignedPersons can currently exist in the USDM JSON.

[pendingintent]

roles.py

• Added _assert_no_role_org_person_org_conflict helper — queries for persons-with-org in the submitted person list, raises 422 if any are found when role also has organizationIds
• Called in create_role (JSON API), ui_roles_add, and ui_roles_update (inside try/except, before any DB writes)
• Fixed ui_roles_update to wrap all writes in try/except so conn is always closed

persons.py

• Added _assert_no_person_org_role_org_conflict helper — queries for roles-with-orgs that the person is assigned to, raises 422 if any are found when setting organization_uid on the person
• Called in ui_persons_update inside a try/except

[pendingintent]

Updates made in branch pi-assignedPerson-role-org-rule and merged with branch release-v-1.4.