[open-science] github breaks data hosting: alternatives?

[Tom Roche]

https://github.com/blog/1302-goodbye-uploads
>>>> December 11, 2012 
...
>>>> * The ability to upload new files via the web site is disabled
>>>>   today.

>>>> * Existing links to previously uploaded files will continue to work
>>>>   for the foreseeable future.

>>>> * Repositories that already have uploads will continue to list their
>>>>   downloads for the next 90 days (tack on /downloads to the end of
>>>>   any repository to see them).

>>>> * The Downloads API [will] be disabled in 90 days.

http://lists.okfn.org/pipermail/open-science/2012-December/001943.html
>>> open-science projects [should] host not only code but its associated
>>> inputs and outputs[.] I found github's Downloads function (and esp
>>> its scriptable Downloads API) convenient for this purpose, e.g., for

>>> https://github.com/TomRoche/GEIA_to_NetCDF

>>> [but now] I'll need to migrate my inputs and outputs, or my projects
>>> entirely. Where to? [Or am I missing something?]

http://lists.okfn.org/pipermail/open-science/2012-December/001945.html
>> You could always commit the data files to a directory in [a github]
>> repository (particularly if they are text files such as netCDF

netCDF can be easily converted to/from text (it's a well-tooled format),
but (unless I'm very mistaken) all netCDF files are binary. They also
tend to be large, which (IIRC) can be problematic for git repos (but
ICBW about that, too).

http://lists.okfn.org/pipermail/open-science/2012-December/001948.html
> [DataONE] is conceptually similar to a LOCKSS model,

someday I hope to know what that means :-)

> The DataONE API is documented, including both the data access and data
> contribution REST interfaces, here:

> http://mule1.dataone.org/ArchitectureDocs-current/apis/MN_APIs.html

> The API should work identically regardless of which DataONE compatible
> repository you use, as we are trying to simplify interoperability among
> these repositories.

sounds good

> In terms of what can be uploaded, that is determined by [each DataONE
> Member Node] -- each node controls who can upload and what they can
> upload. For example, Dryad is participating in DataONE, and they will
> only be allowing data associated with journal papers to be uploaded.

not there yet

>  In contrast, the KNB allows any data to be uploaded that is relevant
>  to science and is legal to redistribute.

I'll give KNB a try: more separately.

thanks, Tom Roche <Tom_Roche at pobox.com>