Performs the enrollment of an individual, by calculating and storing a biometric template for each trait represented by the given samples.
Storagewithin this class ID must exist, but the
ClassIDcan be unused yet, in which case the new class is created. Otherwise, the class is re-enrolled or enrolled anew, depending on the samples submitted.
true when the enrollment procedure finished successfully for all given samples, i.e. not a single error occurred.
As soon as a sample has been refused,
false is returned, even if the generation of the template(s) succeeded.
You have to refer to the messages for details in this case.
The enrollment method simultaneously trains all given samples, which can even represent multiple traits, e.g. face, periocular and voice samples. The training creates a so called biometric Template for each trait specified by the given samples, which can later on be used for verification and identification purposes.
Even if there are no samples given for a single trait, it is re-trained in case a template is already associated with the given classId for this trait. This allows the re-generation of the templates after the stored data has been modified for any reason, e.g. when already trained sample-data is removed from the storage.
This method also supports liveness detection. To activate live detection, simply use the flag EnrollmentFlags.LiveFaceDetection or EnrollmentFlags.LivePeriocularDetection with the flags parameter. Note that in this case the enrollment will only succeed, when it can undoubtedly determine that the given data is live data. In case that the liveness detection for the face or the periocular trait succeeds, the degree of the head rotation between two subsequent images is reported with the returned messages XML-string.
Internally this operation performs a QualityCheck (in BioID ExtractTokenData mode) for all submitted samples before they are forwarded to the liveness detection - in case a live-detection flag is set - and finally the enrollment is performed. Therefore you might get results from these operations as well together with the enrollment results.
This API has a fault contract of type BioIDWebServiceFault which is used for fatal errors like invalid arguments or missing service, etc. Messages, even error messages, generated by the enrollment procedure are reported via the messages output value, which contains an XML string according to the BWSMessages schema namespace.
The messages output XML string might contain operation specific errors as follows:
The following errors are typically internal problems that are not intended to be explicitly handled by clients.
The messages output XML string might also contain errors for the individual samples. Many of the errors can result from the initial quality-check that is performed before anything else is done. Please refer to the QualityCheck method for a list of sample errors that might have been generated by the quality-check.
Additionally the following errors can occur. With any of theses errors the sample is marked as unsuitable and is not considered in the enrollment process: