| Adapps lango switcher macro | ||
|---|---|---|
|
| Table of Contents |
|---|
Description
Merging an offer is used to group the data sets of your Workspace Worksbench that you want to present.
...
The data contained in the merged data set is treated processed according to the following rules:
if an “equivalent” data (with same work signature) is fount found in merged data set, it will be conserved
if there is no “equivalent” data fountfound, it will be created in merged data set
The treated processed data is, in order:
routes and RCZs
journey pattern
notes from page bottomfootnotes
vehicle journeys, their (eventual) associations with RCZs or the notes from page bottomfootnotes
timetables
If the data set has been successfully merged, then there is:
an update of the merge datemerged data
change to “Archived” status
If the operation fails, the data set returns to the "Ready" statestatus.
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”.
...
For each merge, Status, Name, Date and time of creation, Duration, Date and time of aggregation, Operator, are displayed.
...
Manual merge
For each merge the star wheel allows to launch the accessible actions (see, see related data, rollback).
...
| Info |
|---|
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.
...
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.
...
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.
...
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.
...
Using 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.
...
One on the workbench level in the Settings > Workbench> Control Settings section. Here you select in the appropriate box 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 box 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.
...