Types of Data Processing Rules

For each area, a data processing rule must be selected. There are four data processing rules: Always Import, Always Put in Conflict, Import if Null else put in Conflict, Don’t Import.

• Always Import
  Incoming data will always be imported directly into One for the group (provided that all the incoming data is valid). The incoming data will overwrite the data that is held in the One, unless the same value is already held in the One, in which case the incoming data is ignored.

  In the case of an Address, it will only be imported and linked to a Student if this address exists

  The Date Processing Rules for the Student Attendance and Student School History Data Groups will be set to Always Import; although this will be visible it will not be possible for Local Authorities to change the Data Processing Rules for these Data Groups.

• Always put in Conflict
  If the incoming data is different from the data held in One, then the incoming Data Group and Data Items are placed in conflict. This requires the users to process this data specifically through the Matched with Conflicts area to resolve the issues and verify that they are happy to accept the incoming data prior to it being written to the One database. If the incoming data for that data item/data group is the same as the data in One, then it is ignored.

  By default the Data Processing Rules for all the data groups for a new B2B Student Base will be set to Always put in Conflict.

• Import if Null else put in Conflict Incoming data items will be imported as described in the Always Import section. If the One field contains different data, that item will be put into conflict; if the same value as is already held in One, it is ignored.
• Don’t Import
  The incoming information for this data will always be ignored by the system.
  There are various scenarios which affect associated data groups when one item is set to Don’t Import.
  Scenarios associated with Don’t Import
  For an unmatched student where all the data groups are set to Do Not Import, the unmatched student will be placed in the B2B People Match screen.
  If the user selects to Add the unmatched student as a new student and the Don’t Import data processing rule is selected for any of the Data Groups/Data Items, these will be imported provided that all the incoming data is valid.
  However, there is an option to also Match this student to an existing student. In this case when this student is matched to an existing student, where the data processing rule is set to Do not Import that data will be ignored.

With the current functionality of B2B:Student when this unmatched student is placed in the Unmatched area and the user selects to Add this student then all the incoming data sent for this student is also updated. When an Unmatched Student is ‘Matched’ to an existing student in the system then the data is processed as per the Data Processing rules and therefore if a Data Group is set to ‘Always Import’ then that data is imported and if a Data Group is set to ‘Always put in Conflict’ then this data is placed in the Matched with Conflicts.

Data Groups with different subset rules

Where a Data Group has a subset of Data Items, these can be set to different values if required. In this instance, the radio button for the Data Group will be unset to indicate that the subset has differing rules applied.