Usage of datestamp from Record during harvest using oai_dc format

When I setup a client using oai_dc format, the datestamp from Record is used as release time and is display above the citation:

<header>
<identifier>https://doi.org/10.15454/1TPZGG</identifier>
<datestamp>2020-10-08T13:01:11Z</datestamp>
<setSpec>Doi2Pmh</setSpec>
<setSpec>test-dduni</setSpec>
</header>

and result :

I think it is the good behavior because of the definition of datestamp tag: "the date of creation, modification or deletion of the record for the purpose". This is coherent with hosted datasets, this date is used as release time of datasetversion object and so for sorting dataset on display.

But when I harvest an other dataverse with this format, the datestamp is the export date of the record and this date can be updated without a new version of the dataset.

So I have 2 questions:

1- Why can the datestamp be updated without new version of the dataset?
2- Can I modify the code so that the datestamp will be the release time? A full haversting will be necessary for the client to rollback to the release time older than the current record datestamp

Which version of Dataverse are you using?

5.5 or 5.10.1

Any related open or closed issues to this bug report?

The issue names no source files, tests, or entry points. Trace the OAI-DC harvesting path and the handling of record datestamps, then determine whether export-time updates can be separated from dataset release times; done means the intended datestamp behavior is documented and covered by a regression test.