You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After the migration of serial publications (hierarchy migration), the created processes for the toplevel-processes, as for example: periodical, multivolume, ... cannot be opened in the metadata editor. The following error message occurs:
Editing metadaten of process 435,649 locked, metadata file belongs to process 370007!Editing metadaten of process 435,649 locked, metadata file belongs to process 370007!
The first number is the ID of the toplevel-process, the second number is the ID of one of its subordinate processes.
Solution
It should be possible to open the toplevel-processes in the metadata editor.
Additionally, the first ID could be depicted without comma 435,649 -> 435649.
The reason for the error message seems to be that:
In the mets.xml file of the toplevel-process, the METS-element <mets:metsDocumentID> contains the Kitodo-ID of one of the subordinate processes.
It is not clear, why the incorrect Kitodo-ID is entered in the metadata file. In the file system, the folder of the process is named correctly. Reasons could be:
The migration tool does not enter the correct Kitodo-ID
The ID is entered correctly, but is overwritten in a following workflow step
The XSLT, which adds the Kitodo-ID enters the wrong ID in the mets.xml file
Problem
After the migration of serial publications (hierarchy migration), the created processes for the toplevel-processes, as for example: periodical, multivolume, ... cannot be opened in the metadata editor. The following error message occurs:
Editing metadaten of process 435,649 locked, metadata file belongs to process 370007!Editing metadaten of process 435,649 locked, metadata file belongs to process 370007!
The first number is the ID of the toplevel-process, the second number is the ID of one of its subordinate processes.
Solution
It should be possible to open the toplevel-processes in the metadata editor.
Additionally, the first ID could be depicted without comma
435,649
->435649
.See also: #3307, #4267, #4268, #4269, #4271
Example
The text was updated successfully, but these errors were encountered: