-
Notifications
You must be signed in to change notification settings - Fork 63
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
Setting the ORDERLABEL to excluded breaks the pagination #5220
Comments
I tried to find the root cause of this critical bug which makes Kitodo not really usable in a production environment. kitodo-production/Kitodo/src/main/java/org/kitodo/production/forms/dataeditor/EditPagesDialog.java Lines 255 to 260 in f3ccd64
The second On a side note: the logic in kitodo-production/Kitodo/src/main/java/org/kitodo/production/forms/dataeditor/EditPagesDialog.java Lines 242 to 243 in f3ccd64
is also different from the one in the kitodo-production/Kitodo/src/main/java/org/kitodo/production/forms/dataeditor/StructurePanel.java Lines 695 to 700 in f3ccd64
|
Hi Ikram, thanks for this. Here's how I did it: Kitodo_Pagination_Bug.mp4(I 'zoomed' in on the pagination form and structure tree, so the video looks a bit cut off) Version is 3.4.4-Snapshot. Pagination was done for a range of pages. Another "uncounted" page was added at the position of the last page of the previously paginated range, which is not visible in the video. |
After investigating i found out that this is not a bug in Kitodo but a configuration problem inside the ruleset on our side. Sorry for the confusion. As outlined in #4921 , we want to hide all metadata elements for pages because they tend to confuse the editors. So i ended up excluding the order label: This leads to the described pagination bug. I do not yet understand how exactly the ruleset setting effeccts the processing logic and why the behaviour exists. |
I'm impressed by your investigation - I can confirm the success of this tiny change ! |
Excluded metadata is removed from the metadata internally and kept aside, when saving it is added back before saving. Maybe this doesn’t work correctly for |
New issue description:
Describe the bug
When setting the
ORDERLABEL
-key to excluded in the ruleseta lot of pagination bugs occur in the metadata editor. See below. The only way to fix that is to not exclude the
ORDERLABEL
.Expected behavior
It should be possible to exclude the
ORDERLABEL
and still have a working pagination. A possible cause of this error is described below:#5220 (comment)
Old description:
When a object is already paginated in the editor
and you want to add a new logical element to one or multiple pages
The pagination of one or multiple pages is reset to "uncounted" and has to be redone. Example with one page.
If you associate a logical element to multiple pages the pagination is distorted as well:
The text was updated successfully, but these errors were encountered: