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


  • Application title and subtitle in config and settings

  • Possibility to configure ping endpoints in config file

  • SHACL preview for metadata schemas

  • (Index) Cleanup of harvested records before next harvesting

  • Add support for sh:order, sh:description, sh:minLength and sh:maxLength, sh:in, sh:group, dash:DateTimePickerEditor, dash:EnumSelectEditor

  • Add groups and order to entity metadata

  • Add form preview to resource definition and metadata schema

  • Add autocomplete widget

  • Add settings for autocomplete

  • Add extra class statement for fields with class

  • Rename search param from q to query

  • Remove hardcoded metadata timestamps

  • Fix search filters with too many values

  • Fix nested NodeShapes in form previews

  • Fix value validation for multiple values


  • Extended search (filters, simple and complex query)

  • Add saved search queries

  • Several dependencies updated


  • Security audit via GitHub Actions (Snyk and CodeQL)

  • Introduced metadata schemas (as replacement of shapes) including versioning and importing

  • Updated RDF4J to 4.0

  • Several dependencies updated


  • Added restriction to URL prefixes of Resource Definitions

  • Upgraded Java JDK from 16 to 17, updated SpringDoc OpenAPI UI and several other dependencies

  • Compliance with FDP-O ontology (fdp-o:FAIRDataPoint)

  • Added form preview to shape edit


  • Settings (metrics and ping) can be adjusted directly from UI

  • Default values can be specified using sh:defaultValue

  • **/expanded endpoint marked as deprecated (may be removed in the following version)

  • Fixed bugs related to resource definition (same child relations, multiple parents)

  • Fixed computing cache on DB migration and reset to defaults and ordering or resource definitions


  • All metadata have dct:conformsTo with profile based on resource definition

  • Resolving labels for RDF resources

  • Registration of standard namespaces in RDF output

  • Resource definitions are now related directly to shapes

  • Fixed metadata with empty keywords and pagination


  • Reset to factory defaults (users, metadata, resource definitions)

  • Improved UX for browsing child metadata

  • Allow to change internal shapes (and delete dataset and distribution)

  • Several dependencies updated (including Java 16)


  • 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


  • 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)


  • 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


  • API keys for making integrations with FDP easier

  • State “draft” for created metadata


  • Support for editable resource definitions

  • Possibility to specify custom storage in OpenRefine using frontend


  • Ping service for call home functionality

  • Suggesting prefixes for namespaces


  • Introduced DASH and dynamic SHACL shapes

  • Audit log in OpenRefine extension to keep track of actions performed


  • Option to customize metamodel (metadata layers)

  • Possibility to delete and create metadata entities


  • 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


  • 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.