Is your feature request related to a problem? Please describe.
A process is created for an object. Now it turns out that a single object is too complex in one process (it has over 2000 images) and that slows down processing. Afterwards, you know that it would have been wiser to create the object as a hierarchical process, with a child generation of the highest structural level contained within it. But if you now recreate the process, as parent and children, everything that was structured and metadata recorded, you have to re-enter everything. That is no longer possible.
Describe the solution you'd like
A singular process is automatically split into a parent process with child processes from the first structural level. The idea is to make this a copy aside to the existing process. The original process is renamed ..._orig. The parent process does not get a workflow, the child processes get the copy workflow of the original. The names for the child process be the parent’s name with ..._divisonName appended, with a count, if there are several of them. Comments are copied to the parent, correction comments are converted to normal comments, since there are no tasks to link to in the parent process. The media files must be distributed: They go to all children if they are structured in the child, if they are structured into several children, they must be duplicated. Media that is not yet structured or on the logical root element is copied to the parent process.
Example:
Original process is: Shelf_3C [42]
After work done:
Shelf_3C_orig [42] (the original process)
Shelf_3C [192] (the parent process)
Shelf_3C_envelope [193] (the children)
Shelf_3C_box-1 [194] ( − " − )
Shelf_3C_box-2 [195] ( − " − )
Shelf_3C_box-3 [196] ( − " − )
Shelf_3C_cardfile-1 [197] ( − " − )
Shelf_3C_box-4 [198] ( − " − )
Shelf_3C_cardfile-2 [199] ( − " − )
Shelf_3C_box-5 [200] ( − " − )
…
Describe alternatives you've considered
Doing this manually is too much work.
Is your feature request related to a problem? Please describe. A process is created for an object. Now it turns out that a single object is too complex in one process (it has over 2000 images) and that slows down processing. Afterwards, you know that it would have been wiser to create the object as a hierarchical process, with a child generation of the highest structural level contained within it. But if you now recreate the process, as parent and children, everything that was structured and metadata recorded, you have to re-enter everything. That is no longer possible.
Describe the solution you'd like A singular process is automatically split into a parent process with child processes from the first structural level. The idea is to make this a copy aside to the existing process. The original process is renamed
..._orig
. The parent process does not get a workflow, the child processes get the copy workflow of the original. The names for the child process be the parent’s name with..._divisonName
appended, with a count, if there are several of them. Comments are copied to the parent, correction comments are converted to normal comments, since there are no tasks to link to in the parent process. The media files must be distributed: They go to all children if they are structured in the child, if they are structured into several children, they must be duplicated. Media that is not yet structured or on the logical root element is copied to the parent process.Example:
Original process is:
Shelf_3C
[42]After work done:
Shelf_3C_orig
[42] (the original process)Shelf_3C
[192] (the parent process)Shelf_3C_envelope
[193] (the children)Shelf_3C_box-1
[194] ( − " − )Shelf_3C_box-2
[195] ( − " − )Shelf_3C_box-3
[196] ( − " − )Shelf_3C_cardfile-1
[197] ( − " − )Shelf_3C_box-4
[198] ( − " − )Shelf_3C_cardfile-2
[199] ( − " − )Shelf_3C_box-5
[200] ( − " − )Describe alternatives you've considered Doing this manually is too much work.