Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Process link cannot be deleted #3275

Closed
matthias-ronge opened this issue Mar 10, 2020 · 3 comments · Fixed by #5507
Closed

Process link cannot be deleted #3275

matthias-ronge opened this issue Mar 10, 2020 · 3 comments · Fixed by #5507
Assignees
Labels

Comments

@matthias-ronge
Copy link
Collaborator

A process link should be deletable by selecting the structural element which contains it, and then deleting it. This is not possible because the structural element of a link cannot be clicked on.

Cannot click the linked structural element

Goal: Allow clicking on linked structural elements again.

@matthias-ronge
Copy link
Collaborator Author

@solth, @oliver-stoehr What was the reason to disable the selectability of the linked structural elements? Can I just reactivate it? Or, what could a solution look like?

@oliver-stoehr
Copy link
Collaborator

This feature was disabled to prevent incompatibilities with other, existing features of the editor. Since linked structural elements don't have e.g. any metadata or media assigned these features might need some adjustments.
If you make sure that the existing features don't break in combination with selected linked structural elements you can reactivate it.

@matthias-ronge
Copy link
Collaborator Author

I think the procedure should be the other way around: This blocking deactivates working and required functionality. Simply deactivating a required and working function as a precautionary measure should never have happened and that must be withdrawn very soon. Then we have to check in detail whether operator actions are actually enabled that produce invalid (and not just uncommon, but in principle possible) results, and this must then be solved individually. If a result is valid (from a METS perspective), but is undesired, it should be possible to control this via permissions. But that should then be covered in a separate issue.

@matthias-ronge matthias-ronge self-assigned this Nov 3, 2021
matthias-ronge added a commit to matthias-ronge/kitodo-production that referenced this issue Nov 29, 2021
matthias-ronge added a commit to matthias-ronge/kitodo-production that referenced this issue Dec 6, 2021
matthias-ronge added a commit to matthias-ronge/kitodo-production that referenced this issue Dec 14, 2021
matthias-ronge added a commit to matthias-ronge/kitodo-production that referenced this issue Feb 7, 2022
@matthias-ronge matthias-ronge removed their assignment Apr 26, 2022
@solth solth removed the 3.x label Jul 7, 2022
@solth solth removed their assignment Oct 18, 2022
@solth solth pinned this issue Oct 18, 2022
@solth solth self-assigned this Jan 11, 2023
@solth solth added this to the Kitodo.Production 3.6.0 milestone Feb 6, 2023
@solth solth unpinned this issue Mar 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment