Skip to content

v3.0.0
Compare
Choose a tag to compare
@huberrob huberrob released this 13 Oct 12:16
· 428 commits to master since this release
v3.0.0
2731632

This new release allows configuration of metric YAML which also affects how tests are performed. More documentation about this will be published soon in the README.

Some changes of F-UJI's behaviour have to be mentioned:

The role of the YAML metric definition file is more important now. It also allows defining individual scores and maturity levels which are now longer hardcoded.
Metrics and tests which are not listed in the YAML files are not performed/assessed; this allows to switch on/off metrics and tests for community specific metrics to be defined in dedicated yaml files.
F-UJI is now able to use different metrics the REST has now an additional parameter ‘metric_version’ by which the yaml file can be defined (default metrics_v0.5.yaml)
F-UJI > 2.3.0 has more tests implemented which allow to define metrics and tests in specific yaml files which are more compatible with RDA and The Evaluator:

  • FsF-F1-01DD unique identifier of data
  • FsF-F1-02DD persistent identifier of data
  • FsF-F1-01M which will replace FsF-F1-01D unique identifier of metadata
  • FsF-F1-02M which will replace FsF-F1-02D persistent identifier of metadata
  • FsF-F3-02M (metadata include identifier of dataset)
  • FsF-F4-01M-2 which tests if OAI-PMH, SPARQl or CSW is used to offer metadata

F-UJI now is not using the first data object for F3, A1, R1 and R1.3 but the first data object which is accessible (HTTP 200)
Fixed a bug which caused wrong scores for R1 because FsF-R1-01MD-3 was sometimes ignoring matching file sizes and types.
F-UJI now also recognizes resource types for R1 if given as URI e.g. schema.org/Dataset
Fixed a bug due to which in 2.2.5 signposting links to JSON-LD files was incorrectly accepted as valid search engine support mechanism.
Fixed a bug which accepted stringified ‘None’ as entry for file type and size and cause wrong scores for R1
Improved license recognition
Improved JSON-LD handling
F-UJI is truncating very large data files prior to testing which caused R1 test FsF-R1-01MD-3 (Data content matches file type and size specified in metadata) to incorrectly compare expected file size with truncated size. Now F-UJI compares expected size with size given in HTTP header (if given) to perform this test for truncated files.
Prior to version 2.3.0 F-UJI was correctly detecting valid domain agnostic metadata standards in R1.3 (FsF-R1.3-01M-3) but did not assign any score for this. This bug was fixed for F-UJI >=2.3.0
Prior to version 3.0.0 F-UJI was accepting content negotiation in addition to html embedding and microdata as a search engine friendly way to offer metadata in FsF-F4-01M - (Metadata is offered in such a way that it can be retrieved programmatically.) Additionally F-UJI did not verify the metadata standard and content offered via RDFa/microdata. Now, F-UJi is exclusively expecting schema.org, DC or DCAT as search engine friendly metadata formats offered via html embedding and microdata/RDFa. It no longer considers empty RDFa content as it did before.

Assets 2
Loading