Meta data editor - validation warning

[stefanCCS]

It looks like that the meta data editor includes a validation check (when pressing on button "validation"), which checks, if all(!) logical structure elements are mapped to the physical pages. I would like to ask, if/how this validation can be configured, in the meaning of

• that no validation of this kind is done at all
• or even better, that this validation is done for specific logical structure elements only. Background is the follwing situation. If you have a detailed logical structure, then you will have a lot of elements on the same page. For monograph see the image below, for newspapers imagine 50 or more text blocks on the same page. It simply makes no sense in this meta data editor to see always the same image. The information itself is much better to identify in the according ALTO file.

==> My question/proposal is:

• How to configure, what link from logical structure to physical page is visible/validated?

[stefanCCS]

Idea: Put something in ruleset like: <restriction division="CHAPTER" unspecified="forbidden" validationforpage="true">

[matthias-ronge]

If you have a lot of elements on the same page, then you have to assign the page to all of these elements. (It is sufficient to assign them to all elements of the lowest level, in this case the elements author, title, text, image and caption. The assignment is necessarily inherited automatically upwards.) A link symbol (🔗) is then displayed if a page is assigned to several included structural elements, see screenshot in issue #3751 for an example how this looks.

[stefanCCS]

If I have understood it correctly, idea is to assign the page to all "leafes". In my opinion this is not an practical option. Imagine a newspaper page, structured in articles and each article has textblocks. This would mean I have to assign the page for all textblocks on this newspaper page, which could be a huge number (>50). In our experience, this kind of structuring in METS is not used at all. This is, where ALTO is used. --> This means, I am still in favor for the idea mentioned above, which allows in the ruleset to enable/disable this validation warning.

[matthias-ronge]

You're right.

I don't know this type of structuring in METS either. Assigning a page to several structural elements is actually intended so that, for example, a chapter ends on one page and the next chapter begins on the same page. Structuring similar to ALTO in the metadata editor feels wrong to me, but at this point I have only explained how the validation function is intended.

About using ALTO: Production currently supports the option of defining ALTO as a file group. The ALTO XML files must then be provided in a separate folder with the same name as the images. You cannot make ALTO visible or even change it in the metadata editor. In this case, it would be sufficient to assign all newspaper pages to the issue.

[stefanCCS]

I think we have the same view - assinging the newspaper pages to the issue should be enough. Therefore, I am still would like to have something to avoid the warning mentioned at the beginning.

Concerning ALTO: I think I have understood. ALTO files are supported in the meaning, that they can be provided "somehow" (e.g. 3rd party tool), and will be added to a filegroup, if the according folder in configured. I have tried this out, and it work fine. It is not my expectation, that Kitodo can make the ALTO results itself visible.

The only issue for a good integration is ALTO files, is the topic mentioned here: #3837 (and maybe also #3817).

[matthias-ronge]

assinging the newspaper pages to the issue should be enough.

Then, the correct solution in this case is not to create logical strucure elements below the issue level. If you create them but don’t assign pages to them, they will not show any content in Presentation, which is likely not what you want.

[stefanCCS]

Of course I want to create the logical structure (e.g. ariticles on a newspaper). And, also it is not meaningful to assign pages to all of these items. The usual solution is to put the ALTO fptr in the METS (at least after export). As a workaround we now think of creating intermediate images/pages, which looks like the ALTO block. Just to have something to show in the Meta file editor. Finally, I still think a kind of ruleset extension like already proposed <restriction division="CHAPTER" unspecified="forbidden" validationforpage="true"> is still helpful in general.