-
Notifications
You must be signed in to change notification settings - Fork 63
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: toplevel-processes without properties #4271
Comments
Just guessing: this new top level hierarchy processes are created in an other way at hierarchy migration then normal top level hierarchy processes by import. So this information needed for properties are not existing and can not be added on migration. Question still remain: from where should this property data come? Maybe even this properties are not needed any more and should be removed - see comments in #3482 . |
Maybe it is then not a bug. |
In version 3, properties are considered eliminated. They still exist internally because they are used in the Switzerland project, so they could not be removed yet. However, they should be removed as far as possible. Instead, the corresponding metadata should be displayed or changed here. See #3156 and #3335 |
I close the issue, because it turned out that the initial declared bug is not a bug. |
Problem
After the migration of serial publications (hierarchy migration), the created processes for the toplevel-processes, as for example: periodical, multivolume, ... have no properties (template properties, workpiece properties, ...).
The processes of PeriodicalVolume and Monograph have these properties after the migration.
Solution
The toplevel-processes should have properties after the migration, like the other processes.
See also: #4267, #4268, #4269, #4270
The text was updated successfully, but these errors were encountered: