FAIRDataTeam / FAIRDataPoint-client

FAIR Data Point Client application for browsing the metadata and administration.
MIT License
5 stars 8 forks source link

Datatype constraint violation on metadataIssued and metadataModified when editing the repository layer metadata on client `1.17.0` #147

Open kburger opened 6 months ago

kburger commented 6 months ago

Using a fresh deployment of server 1.17.1 and client 1.17.0, when editing the repository layer the following error prevents a user from saving:

[] a sh:ValidationReport;
  sh:conforms false;
  rdf4j:truncated false;
  sh:result [ a sh:ValidationResult;
      sh:focusNode <https://purl.org/fairdatapoint/staging>;
      rsx:shapesGraph rdf4j:SHACLShapeGraph;
      sh:value "Thu Mar 07 2024 09:58:24 GMT+0100 (Central European Standard Time)"^^xsd:dateTime;
      sh:resultPath <https://w3id.org/fdp/fdp-o#metadataIssued>;
      sh:sourceConstraintComponent sh:DatatypeConstraintComponent;
      sh:resultSeverity sh:Violation;
      sh:sourceShape [ a sh:PropertyShape;
          sh:path <https://w3id.org/fdp/fdp-o#metadataIssued>;
          sh:datatype xsd:dateTime
        ]
    ], [ a sh:ValidationResult;
      sh:focusNode <https://purl.org/fairdatapoint/staging>;
      rsx:shapesGraph rdf4j:SHACLShapeGraph;
      sh:value "Thu Mar 07 2024 09:58:24 GMT+0100 (Central European Standard Time)"^^xsd:dateTime;
      sh:resultPath <https://w3id.org/fdp/fdp-o#metadataModified>;
      sh:sourceConstraintComponent sh:DatatypeConstraintComponent;
      sh:resultSeverity sh:Violation;
      sh:sourceShape [ a sh:PropertyShape;
          sh:path <https://w3id.org/fdp/fdp-o#metadataModified>;
          sh:datatype xsd:dateTime
        ]
    ] .

There seems to be an issue with the values provided by the datepicker widget.

markwilkinson commented 3 months ago

This is a REALLY urgent bug, by the way... it's a blocker for EJP!

markwilkinson commented 3 months ago

I backed-down to 1.16.* (client and server) and still have the issue...

markwilkinson commented 3 months ago

I guess the incorrect format is written into GraphDB, so backing down wont solve the problem... :-(

dennisvang commented 1 month ago

possibly related to