Laces Data Platform v12.0#
Release date: Oct 1, 2023
Since the previous release the following changes have been implemented.
Styling#
We've been working on updating the Laces Data Platform in recent months! Our developers have put in a lot of effort to create a fresh and user-friendly design that maintains all the familiar features in their usual locations. We hope you'll find the changes pleasant, and we'd love to hear your thoughts and feedback!
JSON-LD#
Users are now able to also upload their JSON-LD files onto the LDP. JSON-LD is based on JSON, a widely adopted data interchange format. This means JSON-LD is familiar to developers who already work with JSON and can easily be integrated into existing systems. By supporting JSON-LD we are trying to lower the barrier of using the Data Platform.
Viewing files#
Now, when Users upload files, they will be displayed as thumbnail images alongside their filenames, providing a visual preview for quick identification. Additionally, for image files, the actual image will be rendered as the thumbnail. We've also made these thumbnails and filenames clickable, allowing you to open them in the details pane for a closer look. Furthermore, accessing the details pane for a file has been made even more straightforward – you can now directly reach it through a URL. These improvements aim to make file navigation and exploration more intuitive than before.
Asynchronous publications#
Users can initiate dataset uploads in the background while adding new publications. This means you can initiate the upload process and continue with your tasks without any interruption. Once the upload is complete, a notification pop-up will provide you with the upload status, and you'll find your dataset visible in the publications pane. This enhancement is designed to optimize your experience and make managing datasets and publications even more efficient.
Consolidation of Object Types#
The Swagger model is streamlined by consolidating redundant types such as Repository, RepositoryView, RepositoryPartial, RepositoryPage and Groups, Publications, Files. This optimization simplifies the API, enhancing clarity and usability. This change also facilitated the creation of a cleaner and more efficient API client.
Uniformity in Path Fields#
The updated API guarantees consistent and easily interpretable paths in the path fields. This improvement eliminates the confusion caused by inconsistent inclusion of parent segments, resulting in smoother experience for data location, navigation and management.
Simplified Group Path Retrieval#
The enhanced API streamlines the process of retrieving the Group's path, affording users a more convenient and efficient means of obtaining the accurate path. Currently, determining the accurate route of a Group necessitated manually navigating through the parent structure and piecing together segments.
Enhanced File Version Identification#
The API has been upgraded with enhancements that simplify the process of recognizing the correct versioned file among multiple responses. This enhances data management and version control capabilities.
Improved User Identification#
The update to the API ensures that the createdBy and modifiedBy fields now display user names instead of internal IDs, offering better context and enhancing the user experience during interactions with the API.
Enhanced API Documentation#
API documentation is enhanced, offering more comprehensive and lucid explanations for the functionality and usage of each endpoint in its metadata descriptions.
Alignment of Definitions and Responses#
There were instances where the definitions within the API did not match the actual responses it produced. To rectify this, steps were taken to align the API definitions more accurately with the returned data. This has led to a reduction in discrepancies, resulting in enhanced reliability and consistency of the API.