OpenAtlas

Talked with Katharina today, we decided that it would be best to have an extra endpoint just for the event chain. It will be an Entitiy endpoint and the results are in a fixed order, how the events are chained in the database.

Since we came to problems with multiple chains, I will set up a complete new format to better display hierarchies. It will be something like:

{
  "name": "First",
  "id": 1111,
  "system_class": "move",
  "geometries": [],
  "children": [
    {
      "name": "Second",
      "id": 2222,
      "system_class": "acquisition",
      "geometries": [],
      "children": [
        {
          "name": "forth",
          "id": 4444,
          "system_class": "activity",
          "geometries": [],
          "children": []
        }
      ]
    },
    {
      "name": "Third",
      "id": 3333,
      "system_class": "event",
      "geometries": [],
      "children": [
        {
          "name": "fifth",
          "id": 5555,
          "system_class": "creation",
          "geometries": [],
          "children": [
            {
              "name": "sixth",
              "id": 6666,
              "system_class": "production",
              "geometries": [],
              "children": []
            }
          ]
        }
      ]
    }
  ]
}

This should be sufficient to bring the data to the visualisation, e.g. map, network or diagrams. For more information, the entity itself should be loaded. But we can for sure enrich the data with types, dates and description.