[openspending-dev] OpenSpending Source Archive

Fri Dec 21 19:48:45 UTC 2012

Very true but I also imagine that:

a) If there were a crash or outage and lost data it would be nice not
to have to wait a couple of days
b) it's nice to have this browsable archive in its own right

Of course if the data really got very big you are quite right that
glacier might be a better cost/benefit trade-off :-)

rufus

On 21 December 2012 18:31, Vitor Baptista <vitor at vitorbaptista.com> wrote:
> Well, that's the use Friedrich said on his first e-mail, right? The data is
> already available on OpenSpending, it's just if "we need to reload the
> database but the original data has become inaccessible".
>
>
> 2012/12/21 Rufus Pollock <rufus.pollock at okfn.org>
>>
>> I don't think Glacier is really suitable as it can take a few days to
>> get access to your data ;-)
>>
>> Glacier is more for long-term archival storage AFAICT ...
>>
>> Rufus
>>
>> On 21 December 2012 16:42, Vitor Baptista <vitor at vitorbaptista.com> wrote:
>> > Although there's not much data, this sounds like a great use for the new
>> > Amazon Glacier (http://aws.amazon.com/glacier/).
>> >
>> >
>> > 2012/12/21 Rufus Pollock <rufus.pollock at okfn.org>
>> >>
>> >> This is brilliant Friedrich.
>> >>
>> >> One thought: what about s3 (or similar) for permanence (as opposed to
>> >> local disk) - this seems like important resources and having them
>> >> preserved would be good.
>> >>
>> >> Also, some ideas (feel free to shoot down!):
>> >>
>> >> * What about one directory per dataset for consistency.
>> >> * What about adding some datapackage.json style metadata in each
>> >> directory (i volunteer to do this)
>> >> * If on s3 we could still have a nice index page with a small
>> >> index.json file and some js (again i volunteer)
>> >>
>> >> Rufus
>> >>
>> >> On 19 December 2012 13:58, Friedrich Lindenberg
>> >> <friedrich.lindenberg at okfn.org> wrote:
>> >> > Hi all,
>> >> >
>> >> > I've begun collecting all the source data for OpenSpending (all
>> >> > datasets) at
>> >> > http://archive.openspending.org/ to protect us from a situation where
>> >> > we
>> >> > need to reload the database but the original data has become
>> >> > inaccessible.
>> >> > It's also a nice set of CSV just to play with.
>> >> >
>> >> > Have fun,
>> >> >
>> >> >  - Friedrich
>> >> >
>> >> > --
>> >> > Friedrich Lindenberg | OpenSpending & OKFN Labs | @pudo
>> >> > http://openspending.org | http://okfnlabs.org | http://pudo.org
>> >> >
>> >> > _______________________________________________
>> >> > openspending-dev mailing list
>> >> > openspending-dev at lists.okfn.org
>> >> > http://lists.okfn.org/mailman/listinfo/openspending-dev
>> >> > Unsubscribe: http://lists.okfn.org/mailman/options/openspending-dev
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >> Co-Founder, Open Knowledge Foundation
>> >> Promoting Open Knowledge in a Digital Age
>> >> http://www.okfn.org/ - http://blog.okfn.org/
>> >>
>> >> _______________________________________________
>> >> openspending-dev mailing list
>> >> openspending-dev at lists.okfn.org
>> >> http://lists.okfn.org/mailman/listinfo/openspending-dev
>> >> Unsubscribe: http://lists.okfn.org/mailman/options/openspending-dev
>> >
>> >
>>
>>
>>
>> --
>> Co-Founder, Open Knowledge Foundation
>> Promoting Open Knowledge in a Digital Age
>> http://www.okfn.org/ - http://blog.okfn.org/
>
>

-- 
Co-Founder, Open Knowledge Foundation
Promoting Open Knowledge in a Digital Age
http://www.okfn.org/ - http://blog.okfn.org/