Pitfalls & Warnings Do not specify the source file in evidence: W007, P015

[Anas-Elhounsri]

It only states metadata file in "evidence", although it is mentioned after in "suggestion". It should be consistent with the rest of the report methodology.

{
      "@type": "CheckResult",
      "assessesIndicator": {
        "@id": "https://w3id.org/rsmetacheck/catalog/#W007"
      },
      "process": "Checks if the Identifier field in codemeta.json is empty or completely missing.",
      "status": {
        "@id": "schema:CompletedActionStatus"
      },
      "output": "true",
      "evidence": "W007 detected: metadata files identifier field is empty or missing",
      "suggestion": "Add a valid unique identifier to the identifier field in codemeta.json, such as a DOI or SWHID.",
      "checkId": "eadd68508b98739e202ae308713419a1a8a7c4e54e336282674c7fa694ef9821"
}

[Anas-Elhounsri]

Same thing for P015:

{
      "@type": "CheckResult",
      "assessesIndicator": {
        "@id": "https://w3id.org/rsmetacheck/catalog/#P015"
      },
      "process": "Sends a request to the contIntegration URL in codemeta.json to verify it does not return a 404 Not Found error.",
      "status": {
        "@id": "schema:CompletedActionStatus"
      },
      "output": "true",
      "evidence": "P015 detected: metadata files Continuous integration URL returns unknown: https://jenkins.i3m.upv.es/job/grycap/job/im-client-unit-master/",
      "suggestion": "You need to update the outdated URLs to point to the current CI platform, or remove the property if no active CI is in place. A good practice would be to periodically test all external links, especially those related to CI or build status.",
      "checkId": "9b855e85186c239b47af1800d65f1fe149afae1918c55c56ad2a8cdf70f75baf"
}