Open Azurab opened 3 months ago
We assume that we are talking about the group distribution flow. --> We need an improvement to compile requirements on groups.
It is important not only for group bookings (I believe it is appropriate to discuss in other topic the creation of a specific controller for organized group applications in OSDM API), but in the case of PKP for almost any booking with the option of security in data fulfillment, where personal data are required, but not for each passenger, but only for the ticket holder. Next Friday I will try to attend your meeting.
TODO: add comment to the passenger list in the data sructure: The first passenger in the list elegible to be a group leader (e.g. adult) is the group leader in case a group leader is needed.
TODO: add PKP to list in "Interlude: Requested Information per Process Step" for group leader name
@Azurab I have created a proposal of documentation for this feature. You can review and comment the linked pull request.
Text for Requested Information per Process Step in PKP distribution:
Pre-booking step:
Birth date may be required for offers selection that are subject to age restrictions (e.g. children or seniors).
Booking step:
The lowest possible level of sensitive data is required. In general, fulfilments with "in-data" control security type and also multiride products only require the first and last name of the ticket holder.
A proposal could be to have the notion of buyer and passenger. That would be also useful in context of a travel agent processing the booking on behalf of the passengers. That would match with the needs of differentiating the various role:
Hi, the buyer is a purchaser in OSDM.
pon., 17 cze 2024, 14:23 użytkownik Odile Angeras < @.***> napisał:
A proposal could be to have the notion of buyer and passenger. That would be also useful in context of a travel agent processing the booking on behalf of the passengers. That would match with the need DuckDuckGo removed one tracker. More https://duckduckgo.com/-SdGi3VDNP9Gbopm1jyV875lWXS-FWHRF3oCBRYgBqVzYMTEwcSlImJ7D26qDRwbaDGgYS45GFZqZrKmjfDUQ4AnKY6lFZZSI1DQQAkc3J3S4gQaNEdtqhsAmCCL3XkCHYiNe_v9N-D7Inmqf3ryGyNEzOZ2ozrUBb3pQ8NBEB7TRdyb-Tjh5TvPPGuVM8AwECWfx-laXjeWo5GRvBWYNBdUcj9oTq1XsQ4fpZzVEKKeYpYhno5fyWJHHUxJBuBpwML4IDYzzLjKiILFF49CrOM-wEcLYoRJKHnc0QNFJh1DmVJ0bSkNZmxDGbQqQUtZm0pDVcWHH7omp8M0jv8CZ1QX1p8nsgubLw-bXefJ2L2DeHzhfCvRWHWbX3g-yyd80kmIIoTWG7P_dbQBY7cdxRIbSJ2s_6gf-Bo9MAhmt_cdXBLXABydAp0SBI3HlYVHf_8KktQr1Xd073Fhfspo8VWJqzCCcIU66AA Report Spam https://duckduckgo.com/-SdGi3VDNP9Gbopm1jyV875lWXS-FWHRF3oCBRYgBqVzYMTEwcSlImJ7D26qDRwbaDGgYS45GFZqZrKmjfDUQ4AnKY6lFZZSI1DQQAkc3J3S4gQaNEdtqhsAmCCL3XkCHYiNe_v9N-D7Inmqf3ryGyNEzOZ2ozrUBb3pQ8NBEB7TRdyb-Tjh5TvPPGuVM8AwECWfx-laXjeWo5GRvBWYNBdUcj9oTq1XsQ4fpZzVEKKeYpYhno5fyWJHHUxJBuBpwML4IDYzzLjKiILFF49CrOM-wEcLYoRJKHnc0QNFJh1DmVJ0bSkNZmxDGbQqQUtZm0pDVcWHH7omp8M0jv8CZ1QX1p8nsgubLw-bXefJ2L2DeHzhfCvRWHWbX3g-yyd80kmIIoTWG7P_dbQBY7cdxRIbSJ2s_6gf-Bo9MAhmt_cdXBLXABydAp0SBI3HlYVHf_8KktQr1Xd073Fhfspo8VWJqzCCcIU66AA
A proposal could be to have the notion of buyer and passenger. That would be also useful in context of a travel agent processing the booking on behalf of the passengers. That would match with the needs of differentiating the various role:
- the buyer is the one who manage the booking and the fulfilment. He/she could also be one of the travelers.
— Reply to this email directly, view it on GitHub https://github.com/UnionInternationalCheminsdeFer/OSDM/issues/554#issuecomment-2173257048, or unsubscribe https://github.com/notifications/unsubscribe-auth/BIFDHUARB4QUKJCTT2MFMDDZH3INHAVCNFSM6AAAAABIE66LKWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZTGI2TOMBUHA . You are receiving this because you were mentioned.Message ID: @.***>
Hello.
I need advise on how to proceed with a booking when the passenger personal data constraint is applied only to the ticket holder. Is it possible to indicate a "leading" passenger in offer or booking request?