All Datanodes have a State that indicates if the content of the Datanode have been verified. Among other things, this can be used to indicate if the content of an Email Address IE Base Type (so an email address in this case) or a Phone Number IE Base Type (so a phone number in this case) have been validated.
Major version change on a Datanode reverts verification to None
When a Datanodes primary content is updated, a Datanode will always have it’s Version bumped up by +1. This will also clear the Verification State and reset it to state: Not verified
Verification States
The following states can be set when calling the Set Verification State API endpoint.
| Name | Namespace | Description |
|---|---|---|
| Not verified | dk.realequity.verification.none | This is the default state when a Datanode is created. This state indicates that the content have not been thru an explicit validation flow. |
| Verification requested | dk.realequity.verification.requested | This state indicates that a verification process have been requested, but that the system have not yet started the verification process. |
| Verification pending | dk.realequity.verification.pending | This state indicates that the verification process is ongoing and waiting for input from a user or specific validation step. |
| Verified | dk.realequity.verification.verified | This state indicates that the content of the Datanode have been verified. |
Execution time
The execution time, should describe when the validation found place and not when the information about the validation was saved in the system. So if the verification was done manually by a human or by an external verification process by another system, it is the actual time where the verification took place that should be registered as the Execution time.
Verification and new versions of a Datanode
When the primary data is changed on a Datanode, the Version number is always stepped up by +1. At the same time, the Verification State will be reverted to: Not verified. If the data can still be considered to be verified, the verification will need to be set again using the Set Verification State API endpoint.