Add option to set source priority for aggregation
R
Randolf Broer
I would like to have an option to prioritize one source system above another source system so that a person from the primary system ALWAYS becomes the primary person in case of (automatic) aggregation. This is especially the case when the secondary source system is only being used for source enrichment. Since person data in the source enrichment source systems is obviously not complete since it is not (really) an HR system (e.g. Student Information System like Somtoday or Magister), accounts cannot and must not be created from data from secondary systems. It must be prevented to do so at all times to prevent errors in HelloID and target systems.
Niek de Melker
I Guess it would be even better to mark a source system as 'enrichment system', this should only ever enrich the selected source system. This way you could also keep the aggregation for what it really is for: Detecting duplicate users and merging them.
R
Rick van den Dijssel
Hello Randolf Broer! I have a few more questions for you:
- What specific criteria should be used to determine the primary source system in case of conflicts?
- Are there any specific scenarios or examples where the current system has failed to prioritize the correct source?
- How frequently do you anticipate needing to change the priority of source systems?
R
Randolf Broer
Hi Rick van den Dijssel,
- It is not needed to determine the priority automatically. The consultant knows which source primary is and can always set it manually.
- Yes. Sometimes the person is already available in the secondary source and imported into HelloID, for example for historic reasons (HR and SIS does not necessarily have the same retention policy). When the person becomes available through HR, the secondary person becomes the primary person according to HelloID because it was there first. The assumption in HelloID that the first available person is the primary person is not (always) correct.
- Once, during implementation phase.