Corrupted dataset (ds001246)

[chrisgorgo]

CHANGES on the latest snapshot (https://openneuro.org/datasets/ds001246/versions/1.0.1/file-display/CHANGES)

1.0.1	2018-09-10

	- Update documentation.

1.0.0	2018-08-24

	- Add 'BIDSVersion' in dataset_description.json.
	- Change 'stim_file' to 'stim_id' in task event files.
	- Update README.

v00005	2018-04-26

	- Replace 'null' with 'n/a' in task event files.
	- Fix column name in task event files ('image_file' --> 'stim_file').
	- Add ORCID for YK.
	- Update README.

v00002	2018-03-04

	- Modify dataset name.
	- Update README.

CHANGES on S3 (http://openneuro.org.s3.amazonaws.com/ds001246/CHANGES) - doesn't match what is on the web UI

6.0.0	2018-XX-XX

	- Add 'BIDSVersion' in dataset_description.json.
	- Update README.

5.0.0	2018-04-26

	- Replace 'null' with 'n/a' in task event files.
	- Fix column name in task event files ('image_file' --> 'stim_file').
	- Add ORCID for YK.
	- Update README.

2.0.0	2018-03-04

	- Modify dataset name.
	- Update README.

1.0.0	2018-03-01

	- Initial release.

This could be just the CHANGES file or affecting other files in the dataset.

[chrisgorgo]

dataset_description.json also seems out of sync in terms of content and the timestamp on S3 precedes the creation of the latest snapshot.

[chrisgorgo]

On GH the changes from the latest snapshot (09/11) seem to be missing: https://github.com/OpenNeuroDatasets/ds001246/blob/master/CHANGES

[nellh]

The export here didn't run. I am looking for logs still to see why. Exporting the missing snapshots should fix it - I'd like to fix up the remotes first so we don't need to redo the export here again with enabling native git-annex S3 versioning on everything.

[nellh]

This is fixed on S3 now, I will close this once I've confirmed it does not affect any other datasets. I believe this may be related to maintenance interrupting the export to S3.

[chrisgorgo]

Awesome - thanks!

…

On Fri, Oct 12, 2018 at 2:06 PM Nell Hardcastle ***@***.***> wrote: This is fixed on S3 now, I will close this once I've confirmed it does not affect any other datasets. I believe this may be related to maintenance interrupting the export to S3. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#947 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAOkpxJflvXjcmTTInt7JYSRMqjHTZ1Eks5ukQRSgaJpZM4XX2BM> .