Difference between revisions of "Merging Existing Systems"

From Charitylog Manual
Jump to: navigation, search
Line 15: Line 15:
  
 
The solution to this when merging systems is to increment the ID numbers of one system, whilst retaining the ID numbers on the other. This would typically be done by adding simple values to ID's. For example, if the first system has 560 clients, we may add 10,000 to the ID's in the second system. This means client 56 in the first system would remain as 56, and client 56 in the second system would be 10056.
 
The solution to this when merging systems is to increment the ID numbers of one system, whilst retaining the ID numbers on the other. This would typically be done by adding simple values to ID's. For example, if the first system has 560 clients, we may add 10,000 to the ID's in the second system. This means client 56 in the first system would remain as 56, and client 56 in the second system would be 10056.
 +
It is also possible for both sets of ID numbers to be incremented. Making the first set of ID's 10056, and the second set of ID's 20056. This can help Users distinguish between older and more recent ID's.
 +
 +
* Project names, User names, and field options are key examples of unique identifiers within text.

Revision as of 16:54, 24 January 2020

We understand that organisations may sometimes be a need for Charitylog or Crossdata systems to merge together into one single system.

The purpose of this page is to provide a general overview of the merge process.

If you are considering merging and would like to make a further enquiry, please call the Dizions office on 0333 222 5957, and request to speak to a member of our Data team.


Merging Process

Our priority at Dizions is ensuring data integrity. Our data team will predominantly manage this for you, and ensure all data is handled appropriately.

A notable example of this is the handling of "unique identifiers". Unique identifiers are used in Charitylog and Crossdata systems, and inevitably you will have the same referral or client ID number on your system as the system you will be merging with.

  • Referral ID numbers and client ID numbers are key examples of numerical unique identifiers.

The solution to this when merging systems is to increment the ID numbers of one system, whilst retaining the ID numbers on the other. This would typically be done by adding simple values to ID's. For example, if the first system has 560 clients, we may add 10,000 to the ID's in the second system. This means client 56 in the first system would remain as 56, and client 56 in the second system would be 10056. It is also possible for both sets of ID numbers to be incremented. Making the first set of ID's 10056, and the second set of ID's 20056. This can help Users distinguish between older and more recent ID's.

  • Project names, User names, and field options are key examples of unique identifiers within text.