IT4Change/gradido
3
0
Fork 0
mirror of https://github.com/IT4Change/gradido.git synced 2025-12-13 07:45:54 +00:00
Code Issues Packages Projects Releases Wiki Activity

rework PR comments

Browse Source
This commit is contained in:
Claus-Peter Hübner 2022-04-21 01:42:16 +02:00
parent bcb584ba85
commit 6642abd4d3
1 changed files with 1 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
docu/Concepts/TechnicalRequirements/UC_Introduction_of_Gradido-ID.md
View File

@ -43,7 +43,7 @@ A new entity `UserContacts `is introduced to store several contacts of different
| --------------- | ------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| id | int | the technical key of a contact entity |
| type | int | Defines the type of contact entry as enum: Email, Phone, etc |
| userID | int | Defines the foreign key to the `Users` table |
| usersID | int | Defines the foreign key to the `Users` table |
| email | String | defines the address of a contact entry of type Email |
| phone | String | defines the address of a contact entry of type Phone |
| contactChannels | String | define the contact channel as comma separated list for which this entry is confirmed by the user e.g. main contact (default), infomail, contracting, advertisings, ... |
@ -135,7 +135,6 @@ A new mapping logic will be necessary to allow using unmigrated APIs like GDT-se
* alias -> email
* alias -> userID
#### GDT-Access
To use the GDT-servers api the used identifier for GDT has to be switch from email to userID.