This is an incremental software release that adds several improvements across the board. The API is backwards compatible with v1.8.
For the detailed list of updates in this release, see the list of addressed issues since v1.8.
If you are currently using Nexus Delta from 1.8.x, please visit the migration instructions for the necessary steps to successfully upgrade.
Those three links are returned in the response of operations related to the different resources. Until 1.9, they were curied/shortened according to the base and the API mappings defined in the project configuration.
This caused consistency problems, as whenever the base or the API mapping was changing, those shortened links were not valid anymore:
- All data in views displaying metadata (which include those links) had to be indexed again ;
- The change also had to be propagated to other external systems ;
- The resources, including download links to files, had to be patched
Therefore, since 1.9,
outgoing links are not shortened anymore, allowing them to remain stable in time even if the project configuration changes.
Multiple resources can now be retrieved within a single call with the multi-fetch operation.
Until 1.9, operations about resources resulted in writes in the primary store and indexing in the knowledge graph. However, users may also want first to experiment/refine/polish/validate a resource and schema and only create/update the resource when they are happy with it.
It is now forbidden for JSON payloads to contain fields beginning with underscore (_). This can be disabled by setting
lenient; however, it is not recommended as the specification of this data in payloads can have unexpected consequences to both the data and the user interface.
Listings by types can now be controlled with the
typeOperator query parameter. Possible values are
and, which will match any and all types, respectively.
It is now possible to aggregate resources by
This feature is also available on files, resolvers, schemas, storages, and views.
When creating/updating a resource, Nexus Delta now keeps track of the remote contexts that have been resolved during the operation.
The schema of a resource can now be changed:
- When performing a resource update, it is possible to specify a new schema.
- A dedicated endpoint to only change the schema without providing any payload is available.
Create and update operations on resources now accept an optional tag, allowing the resulting resource to be tagged in the same call.
During update and refresh operations, if no change is detected, no new revision will be created and the last existing revision will be returned.
This was introduced to prevent users from creating a large number of revisions for resources when no change is actually introduced.
Previously deprecated resources can now be undeprecated.
Previously deprecated projects can now be undeprecated.
Indexing errors can now be listed and filtered for a given view.
To improve indexing performance, the types defined in the FilterByType pipe, Sparql View payload, or the Composite View source payload are filtered in PostgreSQL rather than in Nexus Delta. This avoids querying for data just to discard it straight away.
The different requests to Elasticsearch are now compressed by default allowing to reduce the I/Os especially during indexing.
New features enhance the performance of indexing of composite views, as well as authentication changes for views which incorporate projects on remote Delta instances.
Construct queries to the intermediate space can now be batched.
A diff is performed when a composite view is updated, and only the necessary spaces are reindexed.
For example, if a source is added/updated/removed, all the spaces (intermediate space and projection spaces) get reindexed. However, if a projection is added/updated/removed, now only the space related to this projection is reindexed, which reduces the number of operations and consequently speed up the indexing.
Preserving the intermediate space also reduces the fragmentation of the Blazegraph journal.
Rather than storing an auth token in the composite view, it is now expected to specify an authentication method in the Delta configuration.
This field was never used, so as there is no plan for it, it has now been removed.
The Elasticsearch mapping of an Elasticsearch View can be retrieved.
Files can be added to an archive using a
Annotated source is now available as an output format when creating an archive.
Creating an archive now requires only the
resources/read permission instead of
Tarball archives are no longer supported due to unnecessary restrictions. ZIP is now the only allowed format and clients should send
application/zip in the
Accept header when creating archives.
Previously, it was only possible to deprecate organizations at a specific revision. Now, organizations containing no projects can be deleted by specifying a prune parameter:
Previously deprecated organizations can now be undeprecated.
Storages can no longer be created with credentials that would get stored:
- For S3 storages, this would be
- For remote storages, this means
These should instead be defined in the Delta configuration.
Previously deprecated files can now be undeprecated.
The automatic detection of the media type can now be customized at the Delta level.
NB: The media type provided by the user still prevails over automatic detection.
Create and update operations on files accept now an optional tag allowing to tag the resulting file in the same call.
The Elasticsearch views behind Graph analytics can now be queried using the
Remote contexts used during the JSON-LD resolution for a resource are now indexed in the Graph analytics views and can be found via the search endpoint
It is now possible to perform ID resolution by providing only the identifier of a resource.
It is now possible to query whether the currently logged-in user has specific permission in a specific context.
The 1.9 release of Nexus Fusion focuses on enhancing user interaction, resource management, and overall application efficiency. This update introduces new features and key improvements across various sections of the application.
- Global User Interface Improvements:
- Improved header menu behavior while scrolling.
- Enhanced uniformity in UI elements.
- Built beta version of data explorer.
- Multi-type filter selection in the “My Data” section.
- New filtering and navigation features.
- Fullscreen mode for Graph Flow.
- Navigation has been improved with back and forward buttons.
- Resource Management and Display:
- Display of resources missing paths and containing specific values.
- Clearer resource counts and enhanced popover information.
- Introduction of Data Cart logic.
- Improved ACL checks and permissions retrieval.
- ID resolution in resource viewer/editor.
- ID resolution via the URL input of the browser.
- Code Editor Enhancements:
- URL copying feature in Code Editor.
- Typo corrections and layout adjustments.
- Tagging resources and splitting resource history.
- Advanced search and filter capabilities.
- New resource tagging features.
- Enhanced error handling and feedback mechanisms.
- Bulk request resources from the backend to reduce the number of network requests.
The Nexus storage app also benefits from the changes in automatic file detection.
This callback has been replaced by a local validation of the token.
For more information about the Forge, please refer to the documentation.