While datastore works, it breaks the extension manager (open DataStore module, close the window; open Extension Manager => instead of "Install" button, "Download" button is displayed and it downloads the extension instead of installing it).

Also, it is clear that there will be no Midas communities (there are many alternative, more open and more popular data repositories) and at some point the Midas server will be retired.

@Slicer/slicer-core What do you think about removing DataStore module, moving data to into a github repository and add links to important data sets (atlas collection, registration case library, maybe a few more nicer data sets) to SampleData module? We could use the existing SlicerTestingData or a new SlicerDataStore github repository.

I like the idea of migrating from midas to github for this.

I'm not sure what you mean by removing the SampleData module - did you mean DataStore? If so, yes.

Yes, sorry I meant removing DataStore module.

removing DataStore

That makes sense.

Also, if there is a strong push to keep similar functionality we could modify the DataStore module and leverage GitHub API to upload asset. That said, I would prefer to avoid the added complexity and associated maintenance cost.

existing SlicerTestingData or a new SlicerDataStore github repository.

That is a tough questions.

Before answering, may be we should define the role of each. Here is an attempt:

• SlicerTestingData: Collection of datasets used for testing Slicer. These datasets may not have any clinical relevance and may be incomplete.

• SlicerDataStore: Collection of datasets that are clinically relevant and anatomically correct

Now for practical reason, we could organize all data under the same repository: SlicerDataStore and have different type of release: testing-data-<hashalgo> and clinical-data-<hashalgo>

https://github.com/Slicer/SlicerDataStore/releases/download/testing-data-<hashalgo>/<hash>
https://github.com/Slicer/SlicerDataStore/releases/download/clinical-data-<hashalgo>/<hash>

I think it would be easier to have two separate repositories, as we would not need to migrate SlicerTestingData, it would allow using the exact same script for managing data (upload scripts, various download scripts implemented in Python and CMake, etc.), and the download URLs would remain simpler (https://github.com/Slicer/SlicerTestingData/releases/download/MD5/nnnn).

would be easier to have two separate repositories

Agree with you.

Then, should we name it SlicerDataStore or SlicerClinicalData or SlicerSampleData or ... ?

I like SlicerSampleData

SlicerDataStore sounds a bit more appropriate to me, as we move DataStore content there, and some data sets, such as atlases and registration case library images, are more than just some "sample" data sets.

The repository for the DataStore module is https://github.com/Slicer/Slicer-DataStore, I will update its README and archive the repository.

In the meantime, I just created a repository called SlicerDataStore (along with README file including a Maintenance and an History section). See https://github.com/Slicer/SlicerDataStore

I will update its README and archive the repository.

README has been updated (addition of History section), and the repository has been archived. see https://github.com/Slicer/Slicer-DataStore

All files from the DataStore collection (see here) are being downloaded. I wrote a small script leveraging pydas to download the file locally along with relevant metadata (contributor, description, number of views and downloads, ...)

Soon I will upload the files as release assets along with the metadata (for historical reference) into https://github.com/Slicer/SlicerDataStore

Once this is completed, I will submit a PR to update the download links in Slicer and remove the DataStore module from Slicer.

Later, we could still revisit and have am updated DataStore module allowing to directly upload MRB as release asset ...

Once this is completed, I will submit a PR to update the download links in Slicer and remove the DataStore module from Slicer.

Since it appears the download links have been updated in 3ae8c31, is the next step to remove the DataStore module?

There are lots of datasets in Data Store that has not been added to SampleData module yet.

As discussed in the past, all datasets have been added here: https://github.com/Slicer/SlicerDataStore/releases

Next step would be generate a static github page to organize them in categories along with relevant metadata stored in the file datastore.json found in the release asset.

@lassoan and I are currently finalizing this

Closing. All datasets have been archived in this project. See https://github.com/Slicer/slicer.kitware.com-midas3-archive#readme