In a recent Dataverse PR IQSS/dataverse#11439, the API for editing dataset metadata and files was changed to use sourceLastUpdateTime rather than internalVersionNumber to check for stale updates.
Tests against the latest Dataverse unstable image are currently failing because we are still using internalVersionNumber in our testing of updateDataset.
We need to update our use cases to reflect this change.
-
Dataset model: replace internalVersionNumber with lastUpdateTime from getDataset API endpoint.
-
UpdateDataset use case: replace optional param, internalVersionNumber with sourceLastUpdateTime, to validate that the update is not from stale data.
-
File model: add lastUpdateTime from the getFile API endpoint.
-
UpdateFile use case: add optional param sourceLastUpdateTime to validate that the update is not from stale data.
In a recent Dataverse PR IQSS/dataverse#11439, the API for editing dataset metadata and files was changed to use
sourceLastUpdateTimerather thaninternalVersionNumberto check for stale updates.Tests against the latest Dataverse
unstableimage are currently failing because we are still usinginternalVersionNumberin our testing of updateDataset.We need to update our use cases to reflect this change.
Dataset model: replace
internalVersionNumberwithlastUpdateTimefrom getDataset API endpoint.UpdateDataset use case: replace optional param,
internalVersionNumberwithsourceLastUpdateTime, to validate that the update is not from stale data.File model: add
lastUpdateTimefrom the getFile API endpoint.UpdateFile use case: add optional param
sourceLastUpdateTimeto validate that the update is not from stale data.