Thanks Owen,

I conflated github and dropbox in my earlier summary and left out any
reference to dropbox...they do the email requirement...sorry...it was late
and a hurried summary...will look again for that download option on github

thanks again,
dana


On Thu, Jun 13, 2013 at 9:09 AM, Owen Stephens <[log in to unmask]> wrote:

> On 13 Jun 2013, at 02:57, Dana Pearson <[log in to unmask]> wrote:
>
> > quick followup on the thread..
> >
> > github:  I looked at the cooperhewitt collection but don't see a way to
> > download the content...I could copy and paste their content but that may
> > not be the best approach for my files...documentation is thin, seems i
> > would have to provide email addresses for those seeking access...but
> > clearly that is not the case with how the cooperhewitt archive is
> > configured..
> >
> > My primary concern has been to make it as simple a process as possible
> for
> > libraries which have limited technical expertise.
>
> I suspect from what you say that GitHub is not what you want in this case.
> However, I just wanted to clarify that you can download files as a Zip file
> (e.g. for Cooper Hewitt
> https://github.com/cooperhewitt/collection/archive/master.zip), and that
> this link is towards the top left on each screen in GitHub. The repository
> is a public one (which is the default, and only option unless you have a
> paid account on GitHub) and you do not need to provide email addresses or
> anything else to access the files on a public repository
>
> Owen
>



-- 
Dana Pearson
dbpearsonmlis.com