Skip to content
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

Hierarchy migration: metadata editor cannot be opened for toplevel-processes #4270

Closed
andre-hohmann opened this issue Mar 12, 2021 · 1 comment · Fixed by #4356
Closed

Hierarchy migration: metadata editor cannot be opened for toplevel-processes #4270

andre-hohmann opened this issue Mar 12, 2021 · 1 comment · Fixed by #4356

Comments

@andre-hohmann
Copy link
Collaborator

andre-hohmann commented Mar 12, 2021

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

errormessage_open_metadata

@andre-hohmann
Copy link
Collaborator Author

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:

  1. The migration tool does not enter the correct Kitodo-ID
  2. The ID is entered correctly, but is overwritten in a following workflow step
  3. The XSLT, which adds the Kitodo-ID enters the wrong ID in the mets.xml file

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant