OpenAtlas

This is again a problem with P74_has_current_or_former_residence which links to E53 Location of Meteora and not actual E18 Meteora. You can see in this request https://mamems.openatlas.eu/api/0.4/network_visualisation/?linked_to_ids=1073 there is the link to Location of Meteora (ID: 357), since this is the link provided by the database.

Since it makes what it should do, I took the freedom to change it from Bug to Feature, because it is a request, to change correct but unsuspected behavior. I will look into it right away.

Ok, looked into it. It will take some time to figure it in a way that cost not so much performance.

If it is not terrible important, I will postpone it until I return.

Now there should be additionally to the object_location ("Location of Meteora") the place "Meteora" which has all links which the location also have. You can easily ignore the object_location with ?exclude_system_classes=object_location

Example result:

...
    {
      "id": 356,
      "label": "Meteora",
      "systemClass": "place",
      "relations": [
        1073,
        1322,
        357,
        361,
        329,
        330
      ]
    },
    {
      "id": 357,
      "label": "Location of Meteora",
      "systemClass": "object_location",
      "relations": [
        356,
        1073,
        1322
      ]
    }
...

Changes are already up-to-date in MAMEMS.

• In the example of Meteora, it seems that the group Meteora (1073) doesn't know about the place (356)
• There is a problem, if the network of a type (e.g. Case Study) should be shown, but type is excluded, then no objects will return. Maybe just show only the Case Study type and exclude all other types. But then e.g. MAMEMS would be the center of the network, which would also be confusing.

Fix both issues. Will be in develop next week, need to refactor.

In develop.