Project

General

Profile

Actions

Bug #2616

closed

Irrelevant entries linked to actor and event entries

Added by Nicholas Melvani 4 months ago. Updated 2 months ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Target version:
Start date:
2025-09-11
Estimated time:
Found in version:

Description

In the Event entries and in the Actor entries there is a large number of unrelated entries linked (which are not linked in the backend):

Event example: https://approaching-byzantium.openatlas.eu/entity/1360

Actor example: https://approaching-byzantium.openatlas.eu/entity/1620


Related issues 1 (0 open1 closed)

Related to OpenAtlas - Bug #2621: API: Irrelevant entries in entity_presentation_viewClosedBernhard Koschiček-Krombholz2025-09-16Actions
Actions #1

Updated by Katharina Wünsche 3 months ago

  • Status changed from New to Acknowledged
  • Target version set to 0.10.0
Actions #2

Updated by Bernhard Koschiček-Krombholz 3 months ago

It looks like that the additional Events at https://approaching-byzantium.openatlas.eu/entity/1360 comes from the connection to the place.
And for https://approaching-byzantium.openatlas.eu/entity/1620, it comes from the place of Residence and from the group (https://mamems.openatlas.eu/entity/645), where 1620 is member from.

If it is an API issue, please let me know.

Actions #3

Updated by Katharina Wünsche 3 months ago

Indeed, it seems to be an API issue. The entity_presentation_view endpoint returns the additional entities in the relations object: https://mamems.openatlas.eu/api/0.4/entity_presentation_view/1360 Should I create a separate issue for this?

Actions #4

Updated by Bernhard Koschiček-Krombholz 3 months ago

If you are so kind, please create an issue in OpenAtlas for that problem.
I fear, that this has to do with the location/place complexity.

Actions #5

Updated by Katharina Wünsche 3 months ago

  • Related to Bug #2621: API: Irrelevant entries in entity_presentation_view added
Actions #6

Updated by Katharina Wünsche 3 months ago

  • Target version changed from 0.10.0 to 1.0.0

Since this issue mostly affects the api and isn't something we need to fix in the OpenAtlas Discovery codebase, we will move this issue to the next version and close it once the related API issue #2621 is closed.

Actions #7

Updated by Katharina Wünsche 3 months ago

  • Status changed from Acknowledged to Closed
Actions #8

Updated by Katharina Wünsche 2 months ago

  • Target version changed from 1.0.0 to 0.11.0
Actions

Also available in: Atom PDF