Improvements for pagination editor

[solth]

Description

As described in #6359 the usability of the pagination editor could be improved by adjusting various aspects of it (taken from the discussion mentioned above):

• remove page selection - not required anymore once multiselection in the structure tree is enabled by Drag & drop multiple tree nodes in structure tree #6340
• realign pagination editor fields from lines into grid to make better use of available space
• add option to show logical pagination in gallery
• sheetpagination starting with Verso-Pages (Metadata-Editor: sheetpagination starting with Verso-Pages #6270
• add alphabetic pagination type (Metadata-Editor: Pagination Option -> Alphabetic #6279)
• paginate pages only selected structure (paginate pages only selected structure #6458) - this should probably be implemented as a way to select all pages of a structure element via a new context menu option and then apply a pagination to the selected pages
• save default pagination type in user settings (Default pagination type in user settings #6045)
• add link to advanced pagination documentation in Github wiki
• rename button "Cancel" to "Reset" or some other more appropriate label
• dynamically adjust available options depending on selected pagination type (for example hide "start value" and other additional options when selecting "uncounted")

@subhhwendt & @SonjaGellert please add further points were needed!

Related Issues

#6045
#6270
#6279
#6457
#6458

Expected Benefits of this Development

Improve usability of pagination editor.

Estimated Costs and Complexity

• medium ~ less than 10 working days

[SonjaGellert]

In the User Settings there is the option to allow the pagination window to be shown directly when loading the metadataeditor.
The standard option is to have the pagination window reduced.

In my workflow the first klick I do is to close the metadata window, since I start with the pagination of my works and I don't need the metadata window.
But I guess this depends on the way you are working. If you use the metadataeditor to enhance the metadata, you probably don't need the pagination, so you would work with the standard option.

Is it possible to create a little more divers choosing option for the windows in the user settings? Not only to choose between metadata or pagination, maybe three options?
In my head I had the vision to clone the option which are chosen for the Galery?

[BartChris]

I think issue #5986 is about discontinous structures and out of the scope of the current issue.

"paginate pages in selected structure (#5986) - this should probably be implemented as a way to select all pages of a structure element via a new context menu option and then apply a pagination to the selected pages"

The feature has no issue yet, if i am not mistaken.

[SonjaGellert]

@BartChris
Yes, you're right. I haven't checked the issues linked. Issue #5986 isn't the same idea as proposed in my discussion thread.

But maybe it is an important feature for others users, but wasn't discussed at the bar camp.

I like the idea since I can picture it to be relevant for others.
At the moment we aren't working with this kind of objects, but I know we have a lot botanical works, where the copper prints are bound as one block in the end. Every graphic has a chapter where it's linked to, but at the moment you are not able to link chapter and graphic together since they are split in the work itself. It sound interesting to link it together somehow, so that they are at least fused when a user is downloading the capter.

Should we still keep it in the bundle? Or asked differently, is it possible to implement it?
Is this anyone who find this helpful for their workflow/projects?

[BartChris]

I like the idea since I can picture it to be relevant for others. At the moment we aren't working with this kind of objects, but I know we have a lot botanical works, where the copper prints are bound as one block in the end. Every graphic has a chapter where it's linked to, but at the moment you are not able to link chapter and graphic together since they are split in the work itself. It sound interesting to link it together somehow, so that they are at least fused when a user is downloading the capter.

Should we still keep it in the bundle? Or asked differently, is it possible to implement it? Is this anyone who find this helpful for their workflow/projects?

I think we cannot keep this in the bundle as it describes a use case which is not generally covered by the current metadata editor which relies on a continuous ordering of pages.
I already discussed this here:
#5457 (comment)

To quote myself.
"The 'combined' structure tree (which is used by the majority of users) does implicitely implement a strict hierarchical view of a document. One cannot e.g. associate page 250 with the first structural element, without changing the physical order of pages. So Kitodo 3 has implemented restrictions on how freely structures can be associated to pages."

In order to fully implement something like you suggested we would have to implement a variant of the editor where this is possible. So i would regard this "out of scope" with regard to the pagination editor.

[BartChris]

I added the new sub issue: #6458 and removed #5986

Description above needs to be adapted @solth

[solth]

Description above needs to be adapted @solth

done (I hope)