search

inception-project / inception

INCEpTION provides a semantic annotation platform offering intelligent annotation assistance and knowledge management.
https://inception-project.github.io
Apache License 2.0
585 stars 149 forks source link

Automatic (and manual) merging doesn't work #4852

Closed s2fische closed 1 month ago

s2fische commented 3 months ago

Currently, no completely similar annotations are merged automatically at all, in both curation modes. Trying to manually merge them did also not work.

1 Clipboard - 5 Juni 2024 15_06

Please complete the following information:

reckart commented 3 months ago

As with https://github.com/inception-project/inception/issues/4822 it would be great if you could provide me with a project that allows me to reproduce this. You can send it privately by email.

reckart commented 2 months ago

@bgittel @s2fische Thank you for providing data to investigate. Since we could both no longer reproduce the issue, I am closing this now as cannot-reproduce. If the problem re-appears, please comment or open another issue.

s2fische commented 2 months ago

The problem re-appeared in another document:

Screenshot 2024-07-03 151018

Screenshot 2024-07-03 151358

Screenshot 2024-07-03 151505

Screenshot 2024-07-03 161512

reckart commented 2 months ago

Could you please try opening the JavaScript developer console of your browser and check if you see and error messages there when you view one of these sentences?

reckart commented 2 months ago

When you log out and log back in, does the problem persist?

When you restart the server, does the problem persist?

reckart commented 1 month ago
Screenshot 2024-07-19 at 11 07 06

So, I have looked into this issue (see screenshot above). The problem ist that the system considers this configuration as being stacked - and stacked annotations are not merged by the default merge strategy.

Currently, the system looks at the configuration and sees two links between the annotations labeled Auerbach... and moralisch... - each of which having a different role. So it says that the user can apparently not decide which role is correct for the relation between these endpoints and it will say it is stacked. The system calls this LINK_ROLE_AS_LABEL mode.

In principle, the system also supports another mode, namely LINK_TARGET_AS_LABEL. In this case, it would see two slots (gewertete Entität and codierte Entität) and see that their slot fillers agree and then merge.

Probably, the way that a link feature is treated (LINK_TARGET_AS_LABEL or LINK_ROLE_AS_LABEL) should be configurable in the feature settings. However, doing this is quite a bit of refactoring.

reckart commented 1 month ago

With https://github.com/inception-project/inception/issues/4956 you will be able to configure the multiplicity of link features. The multiplicity option Target can be linked in multiple different roles or Target can be linked in multiple roles (same or different) should both be able to deal with the scenario from the previous post and hopfully will be useable for you.