4.0 Migration artifact: the auto-generated DRAFTS in CFA collection need to be removed from deposits
sbarbosadataverse opened this issue · comments
At CfA, a depositor has a draft that was created during the migration from (4.0 likely) and never published, for obvious reasons. Look under the versions tab:
https://dataverse.harvard.edu/dataset.xhtml?persistentId=doi:10.7910/DVN/23099
In speaking with @landreev
Dataverse v4); so it could have been something that had to be done when we migrated from DVN3.
The draft was last updated in June 2015 - right after the migration.
Although, this part in the file descriptions: [metadata has been automatically re-extracted from this file after Dataverse upgrade to v.4.0] - maybe that’s all it is, all that extra metadata is what Dataverse 4 automatically extracted from their FITS files after we migrated to Dataverse 4?
@scolapasta If anyone else within the team can possibly remember anything about this, that would be Gustavo.
The Draft was not created by the author and this issue is likely to impact any dataset that was migrated for this purpose (and other purposes?)
I don't recall the particular details of why this text was added, it does look like it did also add extra metadata to the dataset metadata.
Regardless we could search for drafts which have files in their metadata with the text:
[metadata has been automatically re-extracted from this file after Dataverse upgrade to v.4.0]
and then delete those. Or at least inventory them.