Bug #2007
closedWrong direction for P134
Description
I came upon a possible bug in the mapping of preceding/succeding events:
e.g. these events:
https://thanados.openatlas.eu/entity/196289 - The Novara sails from Saint Paul Island to Amsterdam Island
https://thanados.openatlas.eu/entity/196290 - The Novara sails from Amsterdam Island to Sri Lanka (Galle)
https://thanados.openatlas.eu/entity/196291 - The Novara sails from Sri Lanka (Galle) to Chennai (Madras)
They are listed in the UI correctly with preceding and succeding events.
So the correct mapping should be:
domain_id:196290 - property_code:P134 - range_id:196289 (the later event contiunues the earlier one)
and:
domain_id:196291 - property_code:P134 - range_id:196290 (the later event contiunues the earlier one)
However the links are the following:
property_code | domain_id | range_id |
P134 | 196289 | 196290 |
P134 | 196290 | 196291 |
If my assumption is right, the directions got mixed up. Actually the links in model.link table represent the inverse property. So an earlier event "is continued by" the later one. The UI labels the wrong direction to the correct meaning but it is stored wrong in the db.