As define here:
https://www.hl7.org/fhir/datatypes.html#HumanName

Also interesting: https://www.w3.org/International/questions/qa-personal-names

started here:
https://github.com/OpenG2P/openg2p-program/tree/improve-id-dedup-query
Need to add the creation of the duplicate objects.

Allow to add a member with its kind on the list without saving first then adding the kind after.

Add a max level, to 10.

Take the icons from the website: https://openspp.org/features/
If you need modifications or new ones, ask Lit
To set the icons, do this in OpenSPP repository. We will need another set for OpenG2P

Following items need to be removed:

• Remove “Salesperson”, “Company”, “Country” (both “Individuals” and “Groups”) (# 1 in linked document)
• Remove “Individuals”, “Companies” (both “Individuals” and “Groups”) (# 2 in linked document)
• Remove filters not in use under Custom filters (both “Individuals” and “Groups”) (# 3 in linked document)
• Remove irrelevant “Tags” (# 5 in linked document)
• Remove “Duplicate” on “Group” (# 25 in linked document)

Linked document for screenshots: https://docs.google.com/document/d/18qaLelNUjKHcBlH0JtukIG8_Y6-2Q_C5ldjP6HKAH4Q/edit

This model is going to represent data that evolve over time. It can be the result of a household visit, a water survey...

https://miro.com/app/board/uXjVPRVlIMI=/

We need to define a clear order in which calculated fields are re-calculated.

Change the SQL query generated by the _query_members_aggregate:

SELECT res_partner.id AS id, count(*) AS members_cnt FROM "res_partner" LEFT JOIN "g2p_group_membership" AS "res_partner__id" ON ("res_partner"."id" = "res_partner__id"."group") LEFT JOIN "res_partner" AS "res_partner__id__individual" ON ("res_partner__id"."individual" = "res_partner__id__individual"."id") LEFT JOIN "g2p_group_membership_g2p_group_membership_kind_rel" AS "res_partner__id__id" ON ("res_partner__id"."id" = "res_partner__id__id"."g2p_group_membership_id") LEFT JOIN "g2p_group_membership_kind" AS "res_partner__id__id__id" ON ("res_partner__id__id"."g2p_group_membership_kind_id" = "res_partner__id__id__id"."id") WHERE (((("res_partner"."active" = true) AND ("res_partner"."is_registrant" = true)) AND ("res_partner"."is_group" = true)) AND "res_partner"."disabled" IS NULL) AND ("res_partner__id"."end_date" IS NULL AND ("res_partner__id"."group" in (106501, 104456, 100361, 102409, 100364, 106511, 102419, 100372, 100335, 100339, 102388, 104436, 100346, 106491, 104446, 100351))) AND ("res_partner__id__individual"."birthdate" < '1957-09-25 17:11:50.997224') GROUP BY res_partner.id;

with this:

SELECT res_partner.id AS id, count(*) AS members_cnt FROM "res_partner" LEFT JOIN "g2p_group_membership" AS "res_partner__id" ON ("res_partner"."id" = "res_partner__id"."group") LEFT JOIN "res_partner" AS "res_partner__id__individual" ON ("res_partner__id"."individual" = "res_partner__id__individual"."id") LEFT JOIN "g2p_group_membership_g2p_group_membership_kind_rel" AS "res_partner__id__id" ON ("res_partner__id"."id" = "res_partner__id__id"."g2p_group_membership_id") LEFT JOIN "g2p_group_membership_kind" AS "res_partner__id__id__id" ON ("res_partner__id__id"."g2p_group_membership_kind_id" = "res_partner__id__id__id"."id") INNER JOIN ( VALUES (106501), (104456), (100361), (102409), (100364), (106511), (102419), (100372) ) vals(v) ON ("res_partner__id"."group" = v and "res_partner__id"."end_date" IS NULL) WHERE (((("res_partner"."active" = true) AND ("res_partner"."is_registrant" = true)) AND ("res_partner"."is_group" = true)) AND "res_partner"."disabled" IS NULL) AND ("res_partner__id__individual"."birthdate" < '1957-09-25 17:11:50.997224') GROUP BY res_partner.id;

The addition of new computed fields on res.partners would be quite common in our system. So we need to make it easy to use.
Right now, if you have a large amount of data, it often fails to install an app.

So we need to:

• Do not recompute additional fields when installing an app but store them to be run in a queue using Celery ( newlogic/newlogic-g2p#1 )

• Recompute directly only if few records are impacted (Less than 10)

• Use celery to re-compute them

Following items need to be modified:

• Rename “Birthdate Not exact” to “Approximate birth date” (#7 in linked document)
• Ensure that camel case is used everywhere. "Reason for disabling" should be replaced by "Reason For Disabling" (#14 in linked document)

Linked document for screenshots: https://docs.google.com/document/d/18qaLelNUjKHcBlH0JtukIG8_Y6-2Q_C5ldjP6HKAH4Q/edit

We need a new app that allows the following flow:

• A User creates a request for a card to be printed (a new CardRequest object is created and it is put in a queue of cards to be printed)
• Another user takes the CardRequest from the queue and click on print (PDF is generated and print is launched using the browser UI)
• The user marks the card as printed
• The beneficiary comes pick up his card, the CardRequest is marked as distributed and an option proof can be uploaded.

Notes:

• the CardRequest is related to the registrant
• The PDF is not attached to the registrant

1. Rename area kind: Home Address to Admin Area
2. Check the searching of Area Kind

This should be a valid SQL formula so it can be easily re-calculated.
This field is calculated after the criteria fields.

When there is no translation, we should default to the default area name

In English:

When switching to French:

• rename registrant1 and registrant2 to from to @emjay0921: do this ASAP
• Automatically generate the reverse relation and keep it updated with the other one: @jeremi will work on it.
• Update the UI @emjay0921

Some minor fixes on the G2P Registry Base

Remove it also from the demo project.

We need to support multiple types of areas in parallel, so we need to add a field kind to store them.

It should be possible to add a field to a registrant that allows selecting an area of a particular type.

Create Bank Module
Add Test

@edwin can you confirm if this is needed?

It is currently possible to add birthdates in the future. This should not be possible.

Explore enhancements to optimize massive data loads and processing.

The score can be calculated based on a formula that leverages the registrant fields or the calculated fields. Hence, it needs to be calculated after all the other fields have been saved.

• Define fine access right for each method:
  • GET
  • POST
  • PUT

(To do in openg2p_registry)

When presence_only=True it will allow the setting of a boolean instead of the number. It will simply do :
value = cnt > 0
instead of
value = cnt

http://localhost:15069/web#id=1&cids=1&menu_id=113&model=spp.event.data&view_type=form