export_OAI_ORE.cached output differences
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
I've just reproduced this possibly unimportant behavior in a fresh installation of 5.5.
On dataset publish, Dataverse exports metadata to export_format.cached files in the dataset's files.dir directory.
If one then calls reExportAll, Dataverse overwrites these files, but export_OAI_ORE.cached now contains slightly different contents from its first version:
- In the pair of files which called this to my attention, some elements (Author, Citation Depositor, Subject) have identical values but are presented in a different order. This may not matter.
- the
schema:dateModifiedchanges from2021-07-30 18:42:50.867toFri Jul 30 18:42:50 UTC 2021
Small differences, absolutely, but they may point to other differences in the code generating exported dataset metadata.
If this really doesn't matter, feel free to close the issue.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing dataset publication followed by reExportAll in a fresh Dataverse 5.5 installation, then compare the resulting export_format.cached files, especially export_OAI_ORE.cached. Trace the metadata export path responsible for element ordering and schema:dateModified formatting; done means determining whether the differences are unintended and making repeated exports consistent, or documenting why they are acceptable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, data
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100