Merge

Description

Merging an offer is used to group the data sets of your Worksbench that you want to present.

Each data set has a precise scope of intervention:

  • one or more company’s lines

  • one or more periods

When you merge a data set, only the data on its perimeter will modify the transport offer of its Workbench.

Let's take the example of the integration of 3 data sets in the transport offer of the initially empty Workbench.

The first data set will feed Lines 1, 2 and 3 over the period from 01/01 to 01/03.

Then we create a second data set. This one contains an offer on Line 1 and 2 for part of the period of the first one’s and extends the operating period for one more month.

We merge it and get a finalized offer, with a part rewritten over the old data and a new part.

The same principle will apply to each new merge, as in the example below with a third data set :

A data set that has been merged cannot be unarchived or deleted because the finalized offer keeps a reference to this data set.

The data contained in the merged data set is processed according to the following rules:

  • if an “equivalent” data (with same work signature) is found in merged data set, it will be conserved

  • if there is no “equivalent” data found, it will be created in merged data set

The processed data is, in order:

  • routes and RCZs

  • journey pattern

  • footnotes

  • vehicle journeys, their (eventual) associations with RCZs or the footnotes

  • timetables

If the data set has been successfully merged, then there is:

  • an update of the merged data

  • change to “Archived” status

If the operation fails, the data set returns to the "Ready" status.

After the merge, the whole “useless” data is deleted from the new merged offer you get. The data is considered as useless if it has :

  • empty calendar

  • vehicle journey without calendar

  • journey pattern without vehicle journey

  • route without journey pattern

Consult merged data sets

You can view the list of merged data sets in “Current offers” - “Organization offers”.

It is also possible to access the merge list from the Dashboard page by clicking on “Merged data”.

For each merge, Status, Name, Date and time of creation, Duration, Date and time of aggregation, are displayed.

Manual merge

For each merge the star wheel allows to launch the accessible actions (see, see related data, rollback).

You can merge a ready data set by going to the “Organization offers” section and clicking on “Merge data sets” button.

In the merge form, you select one or several data set from the “Available Data sets” and click on “Submit”.

 

During the merge process the chosen data sets change their status from “Ready” to “Pending”.

When the merge is complete and “Successful”, the data sets move to the “Archived” status.
If the operation fails the data set comes back to status “Ready”.

Merged data set can’t be unarchived or deleted, but you can clone it.

Automatic merge after import

You can configure the automatic merge of your data sets directly after an import.

In the form for creating a new import, select the “Automatic merge” option.

If your import is successful, the merge will start automatically on the created data set.

Urgent data

For each Workbench, if a data set marked as “urgent” is merged, then the current offer is categorized as urgent. It will thus be taken into account quickly in the offer of the Workgroup, as described in https://enroute.atlassian.net/l/cp/hv28XQeU.

Rollback to the previous merge

To undo a merge that has already been executed, there is a rollback function available in the list of actions on previous merge.

You should click on the star wheel of one of the previous merges and click on “Rollback”. After this manipulation, all the data sets that have been merged later will be grayed out and will no longer be taken into account in the current offer of your organization.

Validation before the merge

You can define the control sets that has to be used to control each data set before the merge.

Two control sets can be defined:

  • one by the Workbench team

  • another by team of workgroup owner and associated to Workbench

If an error of validation appears on a data set, the merge is considered as failed.

Purge of past merged data

Chouette keeps the last 10 merged offers by default. Automatic cleanup takes place after each successful merge.

You can manage the settings of the purge in the Workgroup section.

Here you can enable the purge of past merged data by indicating its age.

Validation before the merge

In the settings section you can set up the sets of controls to run before merge for each data set.

By using this function, when you launch a merge, Chouette will automatically launch the control set that you have configured on the data sets selected for the merge. The merge will start normally.

The launch of a control set before merge can be configured in 2 ways:

  • One on the workbench level in the Settings > Workbench> Control Settings section. Here you select in the appropriate field the control set you want to run before each merge.

  • Another one on the workgroup level in the Settings > Workgroup> Control Settings and associated with workbenches. You select the workbench to control, and in the appropriate field the control set you want to run before each merge.

If an error is detected during the control on one of the data sets, the merge is “Failed”.

Validation after the merge

You can define as well the control set that has to be used after each new merge in order to control the merged data sets.

This control set can be defined by:

  • team of the workbench

  • team of the workgroup owner and associated to each workbench.

If an error of validation appears on a new merged data set, the merge is considered as failed.