Change Details

After {T254264} the [[ https://meta.wikimedia.org/wiki/Meta:Wikimedia_CH/Meta:Cronos | WMCH Cronos ]] supports federation but it should be able to handle the case of duplicated Events. == Use case == Maybe someone creates an Event in one calendar and then another user creates it in WMCH Cronos and it's not a good idea to just remove one of the two events. Instead, we should avoid duplicates. == Changes == We introduced a family of arguments acting as connectors between each federated calendar. In short, each Event now supports a cluster of `id something` identifiers. For example: * `id meta-fr`: identifier of this Event in the "[[ https://meta.wikimedia.org/wiki/Events_calendar | French Calendar ]]" Now, if a Cronos calendar has one of these identifier it should just skip it, assuming that another upstream event is present, imported and printed as-well.

After {T254264} the [[ https://meta.wikimedia.org/wiki/Meta:Wikimedia_CH/Meta:Cronos | WMCH Cronos ]] supports federation but it should be able to handle the case of duplicated Events. == Use case == Maybe someone creates an Event in one calendar and then another user creates it in WMCH Cronos and it's not a good idea to just remove one of the two events. Instead, we should avoid duplicates. == Changes == We introduced a family of arguments acting as connectors between each federated calendar. In short, each Event now supports a cluster of `id something` identifiers. For example: * `id meta-fr`: identifier of this Event in the "[[ https://meta.wikimedia.org/wiki/Events_calendar | French Calendar ]]" Now, if a Cronos calendar has one of these identifier it should just skip it, assuming that another upstream event is present, imported and printed as-well. Future idea: if one of these identifiers is found, Cronos may be able to merge the available information using some criterias.

After {T254264} the [[ https://meta.wikimedia.org/wiki/Meta:Wikimedia_CH/Meta:Cronos | WMCH Cronos ]] supports federation but it should be able to handle the case of duplicated Events. == Use case == Maybe someone creates an Event in one calendar and then another user creates it in WMCH Cronos and it's not a good idea to just remove one of the two events. Instead, we should avoid duplicates. == Changes == We introduced a family of arguments acting as connectors between each federated calendar. In short, each Event now supports a cluster of `id something` identifiers. For example: * `id meta-fr`: identifier of this Event in the "[[ https://meta.wikimedia.org/wiki/Events_calendar | French Calendar ]]" Now, if a Cronos calendar has one of these identifier it should just skip it, assuming that another upstream event is present, imported and printed as-well. Future idea: if one of these identifiers is found, Cronos may be able to merge the available information using some criterias.