Pre-Verification Implementation for Candidates

Overview
In the Spring 2019 Release, there was a POC done to explore the capabilities of using blockchain technology to allow for Job Seekers/Candidates/Applicants to control their data that is within the CB ecosystem.

To accomplish this, there are three (3) aspects that need to be considered: 1) Verifying the Work and Education History of the Candidate, 2) Allowing them to control the data in regards to who can access and when, and 3) A way to display these controls and visibility of verification aspects from a Candidate and Employer side.

This Epic will cover working with CBES to get verification for Work and Education history tied to a Candidate.
 
Requirements:

1. Partner with CBES to allow for background screening that is done for a Candidate/Applicant  to be tied to that candidate moving forward.
   • This means that their verification of Work and Education history will be tied to their profile, so when the apply to another job (either concurrently or in a later time) that information is noted as verified.
     • This is only if that information was verified.
2. Only Work History and Education History can be deemed "verified" and tied to the Candidates Profile
   • This information never changes - a Candidate will always have the same historical Work and Education when they apply to any future job.
     • For instance, I will always have gotten a M.S. in Human Factors and System Engineering from Embry-Riddle, that will never change.
       • I will be able to continue by education, but the historical elements of Work and Education will never change.
3. The work on the DMS side will be to not only ensure integration with CBES for background screening requests/forms, but to then tie this back to the Candidate and add to their Profile.
   • The backend work needed for using Blockchain technology is also a driving factor that will be handled by this team.