Fast loading pre-linked data
One scenario in linkage often requires the linking of new dataset to an existing pre-linked dataset. If this pre-linked dataset was linked in the same LinXmart instance, Project to Project linkage can be used to then link new data to this existing data. However, if this pre-linked dataset has been linked using another LinXmart instance, or even by another linkage tool, you do have the option of loading this pre-linked data into a new Linkage Project, joining records with the same "person key" together into groups without the need for any probabilistic or deterministic matching. From here you can add and link other data to this linked dataset in the standard way.
This is the fastest way of 'seeding' a linkage project with pre-linked population spine!
Dataset requirements
A pre-linked dataset is loaded in a similar way to other datasets. However, it does require the "person key" for the dataset be provided in the Jurisdictional Linkage Key field, defined by the Import Format of the Event Type.
There are no other requirements on the data itself. The Jurisdictional Linkage Key field will be used to join records into groups.
Linkage Project requirements
There are a number of requirements for the fast loading of pre-linked data to be available in a project:
- The Event Type must have a
Jurisdictional Linkage Keyfield - The Linkage Project must either be empty of data, or only contain data from the same Event Type
- The Linkage Project cannot link to other Linkage Projects
These limitations will allow you to seed the project with linked data for a single Event Type.
From here, normal ingestion of datasets can be followed.
Loading the data
Fast loading data can only be initiated directly from the Upload Data File link on the Linkage Project page, below the list of Event Types.
You are presented with a form where you will need to choose:
- the type of data to load - only
Linkageis supported for fast loading - the Event Type to classify the data - ensure this Event Type has a
Jurisdictional Linkage Key - the Data Source that defines the source and format of the data file
- the local delimited text file to upload for linkage (if required)
If a data file is required, you can specify a plain text file of the format required by the data source, or you can provide a zip file with the plain text file at the root within the zip. The zip file for linkages can contain multiple data files and all will be of the correct format.
Once each of these fields has been selected, click the Load button to upload the data ready to link. You will then be presented with a summary and confirmation form.
If the Linkage Project and Event Type meeting the requirements listed above, you will be presented with an option to Group by JLK. Set this to Yes to enable the fast loading.
Click on the Load button here to trigger the data load.
Once the loading of the data has completed, a special Grouping job will be run to create groups using the Jurisdictional Linkage Key for each record. No matching process of any kind will occur.