An alternative way to do what the script does is to manually use OpenRefine: https://www.oclc.org/developer/news/2018/using-oclc-apis-in-open-refine.en.html
The added value of the script is that no code needs to be written (only XPath's need to be specified in the config) and that the script can run automatically without interacting with a UI.
However, for a better integration of the script into automatic workflows, it would be nice if one could specify a log file (e.g. via --log or --logfile).
Currently there is still a lot of console output. It would be nice if this could be silenced too (e.g. via --quiet or --silent)
An alternative way to do what the script does is to manually use OpenRefine: https://www.oclc.org/developer/news/2018/using-oclc-apis-in-open-refine.en.html
The added value of the script is that no code needs to be written (only XPath's need to be specified in the config) and that the script can run automatically without interacting with a UI.
However, for a better integration of the script into automatic workflows, it would be nice if one could specify a log file (e.g. via
--logor--logfile).Currently there is still a lot of console output. It would be nice if this could be silenced too (e.g. via
--quietor--silent)