License Count for Manually Refined Profiles (PRS)License Count for Manually Refined Profiles (PRS)

For those clients who subscribe to the Profile Refinement Service (PRS), you will want to keep an eye on and understand how the Manually Refined Profiles license works in Pure. For clients without PRS please refer to details in License Count.

How Persons are counted

The 'Manually Refined Profiles' license is a count of persons who are being PRS-ed. The PRS license count does not only include those that are currently being profiled, but also includes those who have been profiled within the last 10 months but are no longer marked as profiled. You can get this count by using these two filter settings:

• Currently profiled: Filter on Profile Refinement = true
• Past profiled within 10 months: Filter on Profile Refinement = false & Profile Refinement Date = xx/xx/xxxx

Adding persons

Persons can be added into Pure and labeled for Profile Refinement (PRS) through the Master list or the Person synchronisation.

• Master list: This is added through the Personstab via the column entitled profiled. This column, once uploaded into Pure, will tell the system which profiles will be counted/pushed to the QABO during a PRS request and which will not. The Manually Refined Profiles license, in this case, will look at the number of profiles with yes here.
  
  
  • No: These profiles will not be submitted for PRS and will not be pushed to the QABO when a PRS request is made. These profiles, therefore, will not be counted towards the PRS license.
  • Yes: These profiles will be submitted for PRS and will be pushed to the QABO when a PRS request is made. These profiles, therefore, will be counted in the PRS license.
• Person Synchronisation: This will be added through an XML file and noted in the element entitled profiled as a boolean value (yes/no or true/false).
  • These values are counted and handled the same as with the master list import (please see above for specific descriptions when using yes/true or no/false).
    

Recognizing Errors with the 'Manually Refined Profile' license

If you get an error message that is referencing a license count discrepancy (e.g. with the master list import), make sure you check if this is referencing a PRS license or academic staff license. In the below example, the error references the 'Manually Refined Profiles' license. The issue was resolved by confirming that the client did not buy PRS (you can always reach out to an implementation manager or sales consultant to confirm if a client has bought PRS) and therefore, the license for this client was 0 and causing the error. To fix the error, the client had to update the 'profiled' column on the persons tab > profile column to say 'no' for all persons.