-
Notifications
You must be signed in to change notification settings - Fork 64
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
Capture old spelling variants of metadata options #6017
Comments
For simple meta data field you can replace existing old values with new values with the help of the KitodoScript |
I will check how far this can help me. |
@henning-gerhardt : As far as i know, you are right. Values in metadata groups cannot be adjusted by the Metadata-Scripts. @matthias-ronge : We have corrected the incorrect values in the selection lists manually (choosing the value in the list) and with Metadata-Scripts. But this might not always possible. To all who are migrating the metadata from Kitodo.Production 2 to Kitodo.Production 3: You could try to correct the values via the XSLT-transformation of the metadata. At least, if the variants of incorrect values are known, this could save time for the corrections after the migration. |
Is your feature request related to a problem? Please describe.
In legacy data, there are occasionally metadata values that have changed, for example because they have been standardized. This leads to a problem for selection fields if the metadata editor, when opened, finds a value for the field that no longer exists in the ruleset. An error message appears, but when you click Save, the data is gone. Data loss in particular is a problem. If someone inexperienced comes across such a process and saves it, the recorded data is gone.
Inserting the value into the ruleset is not an option because now only the new value is and should be there.
Describe the solution you'd like
You should also be able to specify the old values in the ruleset, which will then be mapped to the new values when opened. Example (the
<map>
tag):At the moment, a metadata entry
role
=Author
would cause an error message, no value is selected in the display, and after saving the value would be gone. With the additional option, Author would be displayed in the display and saved asrole
=aut
when you click Save.Describe alternatives you've considered
sed
. However, this requires access to the file system, and an instruction that is too generic insed
could also cause changes elsewhere.The text was updated successfully, but these errors were encountered: