>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #1736622. --> Reported by: [yautja_cetanu](https://www.drupal.org/user/626050) >>> <p>We decided to investigate a real life case for one of our clients in order to handle a specific case where a user may want to obtain their party that has already been entered into the system. The issues can be picked up by the programmers when they start working on it.</p> <p>In our situation we're handling a booking system where a Drupal User creates a "Booking Entity". The Drupal User then adds "Tickets" which are also entities that contain contain information. </p> <p>Bell and Bill = B for Booking Manager<br> Tim = T for Tickets<br> Paul = P for Generic Party<br> Sarah = S for Generic Staff member using Party<br> Oscar = Grouch, he's mean</p> <p><strong>Scenario 1 - Basic Party Acquisition</strong><br> <em>Bell starts a booking in the system and books a ticket for Tim<br> 6 Months later, Tim starts a booking for himself and buys his own ticket.</em></p> <p>Bell starts a booking (entity) and adds a ticket (entity). A ticket is an entity in its own right from the booking system in a similar manner to a commerce order. However there is some information that would be useful for a party on the ticket such as name and Date of Birth and e-mail.</p> <p>So the booking system would check if a party with that e-mail has already been created. If none is found it automatically creates a party and fills it with the relevant information from the Ticket.</p> <p>ISSUE: Allow other systems to create a party if there isn't a party with that e-mail<br> <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/party/issues/1742772" title="Status: Closed (fixed)">#1742772: PartyQuery - API to help find parties...</a></span></p> <p>Then when Tim starts a booking for himself later he logs into the website with the same e-mail that Bell used. When he creates a new Drupal User, AFTER the e-mail verification process he is presented a screen that asks him to confirm if the details the system has about him belong to him. If they do he clicks "accept" and acquires the party.</p> <p>(Note: this e-mail verification process could become more secure and complicated: <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-1"><a href="https://www.drupal.org/project/party/issues/1742646" title="Status: Active">#1742646: [Doc] Party Acquisition Security issues</a></span>)</p> <p>ISSUE: Create an automatic party acquisition configuration UI selecting the field on a data set that is used for mergers and acquisitions.<br> ISSUE: Create a UI so that Drupal Users can confirm and edit their details.<br> ISSUE: Make it so that the merging e-mail field can be synced with the Drupal User E-mail.</p> <p><strong>Scenario 2 - Automatic Party Updating based on e-mail</strong><br> <em>Bill starts a booking in the system and books a ticket for Tim<br> 6 Months later, Bell starts a booking in the system and books a ticket for Tim<br> 6 Months later, Tim starts a booking for himself and buys his own ticket.</em></p> <p>This requires Bill and Bell's information to impact Tim's party before he acquires it. The tickets are entities that are stored in their own right. We think that we should make it so that when a ticket is added it also updates Tim's party. This means that when Tim acquires his party he will see whatever information was the latest and he'll see all the previous tickets that have been attached to his party. We could potentially use party revisions but that is probably not necessary in this situation.</p> <p>ISSUE: Enable other systems to update party information based on the e-mail used for merging.</p> <p><strong>Scenario 3 - Manual Party Input - Automatic Party Acquisition </strong><br> <em>Sarah a staff member enters Paul's information into the system<br> Paul signs up on the site and wants to claim it.</em></p> <p>This is the more generic scenario and is essentially the same. However, because the party is manually entered into the system we need:</p> <p>ISSUE: To make sure the process of adding a Party is easy<br> ISSUE: Make it possible to require e-mails to be unique.<br> ISSUE: Make it so that e-mail have to be verified by being input twice</p> <p><strong>Scenario 3b - Manual Tutor Party Input - Automatic Tutor Party Acquisition</strong><br> <em>Sarah, a staff member at a university, enters a module tutor, Ted's, information into the system so his profile is shown against the module he teaches.<br> Ted signs up on the site and the university want him to claim it and fill out his missing profile information.</em></p> <p>This is a current real life version of Scenario 3 and there is currently nothing more Ted does.</p> <p><strong>Scenario 4 - Post - Party Acquisition </strong><br> <em>Tim books a ticket for himself and creates a Drupal User and Party<br> Bell starts a booking and adds a ticket for tim.</em></p> <p>Tim needs a party to be created automatically with this ticket information stored in it.<br> Issue: Allow parties to be created automatically when a user signs up (already done I think)<br> Issue: Allow Tim to access his own party information</p> <p>Then when Bell adds a ticket she is adding information to a party that already exists. This hasn't been fully discussed yet:<br> - Do we make it so that bell just types in the information and it automatically adds tim's ticket information to the party without her knowing?<br> - Do we allow her to explicitly add parties to her booking (Data protection issues here)<br> - If Bell adds tim's information but spells his name "Timothy", does it change anything on the party? Does it notify tim of something or does it do nothing (and just stay as Timothy on the ticket)<br> - <a href="http://drupal.org/project/email_confirm">http://drupal.org/project/email_confirm</a> This may be important if we do some form of automatic merging at a later date.</p> <p>----------------</p> <p>Just thought I'd give you a heads up. We have a mini-party week next week. We're going to try and get a basic version of our "User integration" sorted. This is the issue where someone needs to "claim" their own party information when they register on the website at a later date or:</p> <p>"Person A has their name, e-mail, address and number in Charity X's website set up by a staff member in a Party called Party A<br> Person A comes along and signs up to become Drupal User A<br> Person A gets access to update their own information in Party A<br> Nasty Person B has also tried to obtain Party A's information but they can't</p> <p>We're going to talk about it on monday and start writing up issues of how we could potentially solve this. I'm feeling that Joachim had some ideas about this where making sure we have a verified e-mail address is something that is really important with making this work.</p> <p>So I think the assumption we can make it "If Person A has access to Party A's primary E-mail account then Person A should have full access to Party A as if they set it up themselves"</p>