You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
will have an entry like so in participant database:
name,d3rusername,guid,email
bob smith,bsmith,12345,bob@bob.com
In the example above if bob wants to submit twice for a given celpp week we plan to just create an additional shared folder with the following name: 12345_# where # is a number starting at say 2 so 12345_2 12345_3...
The above works fine for processing, but when calling get_participant_by_guid() from ParticipantDatabase with the the guid 12345_2 no entry will be found. The method get_participant_by_guid() needs to become smarter. It should first try an exact match of the guid and if that fails see if _# exists and if so strip it off and then look for a guid.
If found return that participant, but update a new getter/setter in the Participant object that is named submission number. By default this value will be None.
Once changes above are made code downstream needs to be examined to verify no bugs arise from this update.
No description provided.
The text was updated successfully, but these errors were encountered: