question about dates on dataset on harvester

[Jacek Chudzik]

Hi,

we are working on 6.6 and I've noticed some problem with dataset dates on harvester instance. It seems like it is showing the date of harvesting not the publishing date (and not depsit date).

What is interesting, in harvester facets serach under 'Depist date' datasets are correctly categorized, even though the date on dataset (print screnn attached) is same for most of harvested datasets.

This may mislead users.

...or is there a feature that I'm missing here something wrong in my config?

Thanks for any help

Jacek

[Jacek Chudzik]

I really would like to come back to this problem and get your advice on the subject.

General problem: difference in publication date dataverse instance and on harvester.

Currently we are using Dataverse 6.7.1 version. Metadata are harvested via dataverse_json.

Example of original json:

https://uj.rodbuk.pl/api/datasets/export?exporter=dataverse_json&persistentId=doi%3A10.57903/UJ/LBPCGT

and on harvester:
https://rodbuk.pl/api/datasets/export?exporter=dataverse_json&persistentId=doi%3A10.57903/UJ/LBPCGT

(not using api/search as it is not working - can create separate git issue for that).

Harvester was showing Oct 5, 2025 (date was not in json).

I tried to re-harvest with no luck.

I decided to remove harvesting client and create it once again - which turned out to be a failure as 90% harvested datasets now have the same date (https://rodbuk.pl/dataverse/wb/ - most datasets are on Feb 4, 2026).

Please, help me understand teh problem and find the solution.

Regards

Jacek

[Philip Durbin]

Hi Jacek,

Is this the same problem as the one described at https://github.com/IQSS/dataverse/issues/8693 ?

Thanks,

Phil

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/dataverse-community/2e7b0ebd-5f5e-450f-8e04-1b640d419aden%40googlegroups.com.

--

Philip Durbin
Software Developer for http://dataverse.org
http://www.iq.harvard.edu/people/philip-durbin

[Jacek Chudzik]

Hi Philip!

It's something similar, but a bit different. 

Yesterday, I've even deleted harvesting client for one collection hoping it will help to keep dates in touch, but it fails - now 3/4 of my collection has a random - from my point of view - date in Feb 2026.

Like, there is no Feb 2026 date in json:

https://rodbuk.pl/api/datasets/export?exporter=dataverse_json&persistentId=doi%3A10.57903/UJ/LBPCGT

But it is visible for the end user.

My question is how to make harvester show same date on dataset card as on the original instance, how to fix differences?

I will try to delete both server and client, set them up again and harvest collection one more time.

Regards,

Jacek

[Jacek Chudzik]

PS. Nope. Creating new pair server-client ends up with current date on all datasets on harvester :(

It seems like there is no publicationDate in harvester json.

[Philip Durbin]

Hmm, it sounds like a bug. Please consider opening an issue!

To view this discussion visit https://groups.google.com/d/msgid/dataverse-community/2237bebc-5c1f-4a3d-bead-cc7fab9a4536n%40googlegroups.com.