-
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
Automatic meta data creation (linkage of files) #3817
Comments
It would make sense to me if this happened automatically at the end of a task of type “write images” or after an automatic task. This is not a big change. The function is separate of the metadata editor and only needs to be invoked. |
fine for me ... |
Related: #3333 |
Note that this is meanwhile already possible with a KitodoScript command. (But it will require its own workflow step.) See #4450. Is this sufficient for you? |
@matthias-ronge : Many thanks for this hint: The only question which is open: |
Regarding "Where can I find all available KitodoScript and an explanation, what they do?": The metadata scripts are described in the documentation for Kitodo.Production 3: For the KitodoScript "action:createFolders" i have found no information. |
It creates the subfolders in the process folder, as specified in the folders setting of the project. The subfolders are typically created during process creation. The only use case that I know for this script is after migrating an instance from 2.x to 3.x to create the additional subfolders for thumbnails. |
Tested with 3.2-build 16.09.2020:
In full automatic workflow, it should be possible, to use the Kitodo-SW without going manually into the meta data editor.
Unfortunately, this is not possible as of today, because as with opening meta data editor and saving its data afterwards, the links of the files (e.g. scanned images, thumbnails, etc.) are written to meta.xml.
Expectation from my side would be, if I choose "Automatic Task" in the workflow editor, it should be possible that the SW performs this change of the meta.xml automatically.
==> In my opinion this a very important feature, which is missing!
The text was updated successfully, but these errors were encountered: