Oct 9, 2023 14:00-15:00 CET

About this document: Agenda and notes are kept in the same document, a separate copy of the document is maintained for each meeting. Please add agenda points before the meeting. Action items created in previous meeting and all other unresolved action items are kept in the document. Please tick off any completed items.

Attendees

@Benjamin Balder Bach (note keeper)
@George J Padayatti
@Lal Chandran (14:00-15:00)

CC: @PSRAMKUMAR @Philippe Page @Ain Aaviksoo

Meeting Notes

Agenda	Presenter	Discussion

Agenda	Presenter	Discussion
API endpoint alignment w/ iGrant team		See “Decisions” section below Notes: We leave opt_in implicit (as True) for NEW Consent Record creation.. This means that creating a new consent record will be the same as opting in, always. We had a longer discussion around what to do with the Individual for pre-registration. We should add this to the roadmap. The workflow for the pre-registration is quite complex around drafts - we need to be very explicit about why we chose the Draft approach. We possibly need further discussions around https://govstack.gitbook.io/bb-consent/v/development/9-workflows

Action items

@Benjamin Balder Bach Can we complete a ConsentRecord update in 2 API calls rather than 3?

Decision

Current POST methods for LIST endpoints can be ignored. They are there in order to accommodate for a common filtering schema, but we'll have a look at adding that as querystring parameters for GET method endpoints. This means ULTIMATELY (soon-ish), we can remove the POST methods for LIST endpoints.
API endpoint change: We need opt_in to be explicit for endpoints that create new Consent Records on top of old Consent Records.

GovStack

2023-10-09 - Work meeting #2

Attendees

Meeting Notes

Action items

Decision