Overview
New major release introducing new commands related to recently introduced functionality for project aliases and configurations in Ontotext Refine.
New
-
Introduced new command for retrieval of project configurations, which is based on the Refine extension. This extension provides a way for the users to export more complete set of configurations for a project so that they can be reused for creation of other projects.
The configurations include the import options for the uploaded dataset and the operations history of the project.
The primary reason for the extension is the usage of this configuration in the CLI transformation pipelines. Therefore the CLI commands will be updated to accept and work this configuration. -
Introduced new command for identifying project by using alias or project id. The command is related to the new functionality introduced in Ontotext Refine 1.2, where the users are able to assign aliases to the projects and afterwards using them as reference.
-
Introduced new command for updating project alias(es). As the command for the project identification, it is related to the new functionality in Ontotext Refine 1.2.
The command can be used to add and/or remove alias(es) from a specific project.
Changes
- Removed old
create
method fromRefineClients
. The method was deprecated and announced for removal in version1.4
. All of the related logic and tests were either updated or removed. - Updates the version of all third party dependencies used by the project. This is done in order to keep the project up-to-date and avoid potential security issues due vulnerabilities in the libraries.
Bug fixes
-
Fixed the error messages for creation of the projects. The expected response code from the operation is usually
302
. When the code is different, the produced error message is rather misleading, then helpful. There are cases when the code is200
and the user receives message for error with status code200
. -
Fixed an issue with the provision of the
options
for the create project command. It is related to the way the arguments are expected and handled in the OpenRefine.
Basically Theoptions
should be provided as query parameters to the request, instead of as part of the request payload.