Skip to content

Latest commit

 

History

History
88 lines (61 loc) · 2.69 KB

changelog.rst

File metadata and controls

88 lines (61 loc) · 2.69 KB

Changelog

Overview

Here we summarize the key features and changes for each FAIR Data Point release. For details including bugfixes and minor changes, see detailed-changelog.

1.9.0

  • Publishing and sharing SHACL shapes between FDPs
  • Metadata children pagination
  • Generating OpenAPI based on resource definitions
  • Several dependencies updates including Spring Boot 2.4.5

1.8.0

  • Added Admin UI to FDP Index with possibility to trigger metadata retrieval, change settings, or delete entry
  • Several bug fixes and dependencies updated (including Java 15)

1.7.0

  • Including FDP Index functionality into FAIR Data Point with harvesting metadata
  • Metadata search including RDF types
  • Possibility to change profile and password for current user

1.6.0

  • API keys for making integrations with FDP easier
  • State "draft" for created metadata

1.5.0

  • Support for editable resource definitions
  • Possibility to specify custom storage in OpenRefine using frontend

1.4.0

  • Ping service for call home functionality
  • Suggesting prefixes for namespaces

1.3.0

  • Introduced DASH and dynamic SHACL shapes
  • Audit log in OpenRefine extension to keep track of actions performed

1.2.0

  • Option to customize metamodel (metadata layers)
  • Possibility to delete and create metadata entities

1.1.0

  • New monitoring and configuration for client application
  • Several further improvements in terms of technical debt
  • Enhanced connecting to FDP from OpenRefine extension and update to OpenRefine 3.3

1.0.0

  • User management, enhanced security, and ACL
  • Huge refactoring and upgrades of previously accumulated features and technical debt
  • Separate project for FAIR Data Point Client (frontend application using FDP API)
  • New OpenRefine Metadata Extension as a replacement for the deprecated FAIRifier

Detailed changelog

Each of components developed has its own Changelog based on Keep a Changelog, and our projects adhere to Semantic Versioning. It is recommended to use matching versions of all components.