Skip to content

The creation date overwrites the issue date #757

@Zack-83

Description

@Zack-83

Describe the bug

For an ontology with three dates (creation, modification and publication),

    dcterms:created      "2022-02-22"^^xsd:date ;
    dcterms:modified     "2025-03-10"^^xsd:date ;
    dcterms:issued       "2025-03-10"^^xsd:date ;
dateCreated                = 2022-02-22
dateModified               = 2025-03-10
dateIssued                 = 2025-03-10

the dates are reported wrongly when generating the documentation. In particular the XML and HTML output ignore the publication date and use as modification date the release date of the previous version:

        <terms:created>2022-02-22</terms:created>
        <terms:issued>2022-02-22</terms:issued>
        <terms:modified>2024-09-20</terms:modified>
    <h2>Release: 2022-02-22</h2>

Also the provenance indication is wrong:

prov:wasGeneratedAt "2022-02-22";
<li>The documentation was generated at 2022-02-22</ul>

(mind also the non closing list tag)

To Reproduce

Final result: https://nfdi4ing.pages.rwth-aachen.de/metadata4ing/metadata4ing/develop/index.html

All files: https://git.rwth-aachen.de/search?group_id=20626&nav_source=navbar&page=3&project_id=41538&repository_ref=develop&search=2022-02-22&search_code=true

Expected behavior

The dates should be mapped 1:1.

About the provenance, in our opinion the release date should be reported.

Screenshots

Image

Image

Image

Image

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions