IQSS / IQSS/dataverse

Consider making export time stamps more granular

Open
#8,630 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Feature: Harvesting Feature: Metadata FY27 Priority FY27 Roadmap GREI 3 GREI Year 5 Original size: 10 pm.epic.nih_harvesting_framework
Dominant language
Java
Stars
1.1k
Forks
564
Avg merge
2d 2h
Merged PRs (30d)
29

Description

In the current implementation a dataset entity has a single lastexporttime time stamp. Meaning, it's all-or-nothing, a dataset is considered either exported, or not. Seeing how we now support a dozen different metadata formats, this should probably be made more granular. It happens all the time that it's just one specific format that fails to export. So, for the purposes of, for example, serving OAI sets, it would make more sense to be able to select all the datasets for which the OAI_DC, OAI_DDI etc. formats have been successfully exported - but not necessarily ALL of them.

Similarly, under the current scheme whenever we make some change that affects just one metadata format, we tell the installations that a full reexport of all the formats is required. Which feels like quite a waste.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing how the dataset entity uses the single lastexporttime value and how metadata exports record success. Compare the needs of OAI_DC, OAI_DDI, and other supported formats, then define how format-specific export status should support selection and avoid unnecessary full reexports.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.