OpenAtlas

Thank you for reporting. I will look into this.

You were right, a good catch again ;)
I fixed the code and added an SQL to fix existing entries in the branch feature_fix_2007. With merging to develop we will wait till shortly before the next release to not complicate the SQL updates.

@ Bernhard: can you check if the API needs adaptions for fixing P134 by reversing it? In case no adaptions are needed (or made in this feature branch) you can assign it back to me. But please keep this issue as resolved and code changes in the branch feature_fix_2007.

From the view of a 2nd Event:

LOUD

"continued": [
    {
      "id": "http://127.0.0.1:5000/api/entity/186218",
      "type": "Activity",
      "_label": "1. Event" 
    }
  ],
  "continued_by": [
    {
      "id": "http://127.0.0.1:5000/api/entity/186220",
      "type": "Activity",
      "_label": "3. Event" 
    }
  ]

LPF

"relations":[
   {
      "label":"1. Event",
      "relationTo":"http://127.0.0.1:5000/api/0.3/entity/186218",
      "relationType":"crm:P134 continued",
      "relationSystemClass":"activity",
   },
   {
      "label":"3. Event",
      "relationTo":"http://127.0.0.1:5000/api/0.3/entity/186220",
      "relationType":"crm:P134i was continued by",
      "relationSystemClass":"activity",
   }
]

This looks correct to me. So no adaptations needed.

Fixed in develop and the database update script will take care of existing entries.