Support mets:area - added fptr in mets:div are removed with meta data editor saving

[stefanCCS]

If I have a logical structure, e.g like this:

and, the Title element includes a reference to an ALTO area, whick looks like in the METS like this:
(created by 3rd party tool).

                <mets:div ID="..." DMDID="..." TYPE="CHAPTER" ORDER="1" LABEL="Chapter 1">
                    <mets:div ID="..." TYPE="TITLE" ORDER="1"/>
                    <fptr>
                      <area BETYPE="IDREF" FILEID="uuid-7da00287-d7df-417d-be56-7e7f0b88d982" BEGIN="P1_TB00001"/>
                    </fptr>
                </mets:div>

--> This entry is deleted by the meta data editor with saving

Maybe I need something to add for the ruleset?
       <restriction division="Monograph" unspecified="forbidden">
            <permit division="VOLUME"/>
        </restriction>
        <restriction division="VOLUME" unspecified="forbidden">
            <permit division="CHAPTER"/>
            <permit key="LABEL" />
        </restriction>
        <restriction division="CHAPTER" unspecified="forbidden">
            <permit division="TITLE"/>
        <restriction division="TITLE" unspecified="forbidden">
        </restriction>

==> Please clarify!

[matthias-ronge]

Production works internally with an object model. The object model contains all degrees of freedom that can be edited in Production. It is converted to an internal METS XML when it is saved. This internal format has only limited similarities with the METS XML that is written during the export. When loading, the object model is rebuilt from the METS XML. The fact that the object model is saved in a format that is valid METS XML could lead to the assumption that Production is an editor for METS XML. However, this is wrong. Production is an editor for all properties of a workpiece that can be edited in Production. A basic design decision was that Production is the sole editor of the metafiles. That is, Production need not keep anything that it cannot produce. As long as Production does not support <fptr> references in included structural elements, these are ignored during loading and are lost.

Currently, the only way to deal with this is to insert the references in the metafiles only after they have been edited.

[stefanCCS]

Ok, understood. This is a non-existing feature ("to keep things, which are inserted by 3rd party tools").
But anyway, in my point of view this is an important feature, because otherwise Kitodo Production would never by able to support ALTO extensions, created by 3rd party.
@Kathrin-Huber : Please clarify, how to go on ...

[matthias-ronge]

Support for the <mets:area> element tends to be implemented in the future. Views are already used internally for this. At the moment, only views for whole pages can be created (which is implicit and not mapped in METS).

Goal: Add support for <mets:area>

[stefanCCS]

Additional information: This feature is especially needed for Newspapers, which are digitized on Article-Level.

[matthias-ronge]

This feature is especially needed for Newspapers, which are digitized on Article-Level.

Not only. It can be used for any media:

• For page-based media, it can be used for marking up charts and tables on a page of an article
• For media content, it is intended to mark up the individual scenes of a film, or songs on an ongoing phonographic recording