Comments on: Reality dreams (for Libraries) http://peterbrantley.com/reality-dreams-for-libraries-213 Peter Brantley's thoughts and speculations Wed, 22 Sep 2010 00:21:40 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Peter Keane http://peterbrantley.com/reality-dreams-for-libraries-213/comment-page-1#comment-85 Peter Keane Sat, 02 Jan 2010 03:40:32 +0000 http://peterbrantley.com/?p=213#comment-85 I've put together way more than 140 characters worth of thoughts in a blog post: http://blogs.law.harvard.edu/pkeane/2010/01/01/what-is-datas-killer-app/ I’ve put together way more than 140 characters worth of thoughts in a blog post: http://blogs.law.harvard.edu/pkeane/2010/01/01/what-is-datas-killer-app/

]]> By: peebsley http://peterbrantley.com/reality-dreams-for-libraries-213/comment-page-1#comment-81 peebsley Tue, 29 Dec 2009 23:08:29 +0000 http://peterbrantley.com/?p=213#comment-81 Jonathan, I hate airports (mostly, at least domestic ones). This was too vague in retrospect (my apologies), and I just read through a brief dialogue about this with Dorothea Salo and Peter Keane in twitter. It is my feeling that "data systems" includes data systems support writ large - thus including repositories - but with an emphasis on data infrastructures that make data available for re/use and re/publication. I think existing repository systems are probably marginally desirable, but not conducive to significant out-bound use, and converting them into vehicles for digital objects that enable their enrichment and additive enhancement are necessary for them to generate traffic and value. More in mind are working with science datasets and descriptive metadata catalogues to assist in application of these data to other domains and applications, either via simulations, mining, enrichment, or public access. Jonathan, I hate airports (mostly, at least domestic ones). This was too vague in retrospect (my apologies), and I just read through a brief dialogue about this with Dorothea Salo and Peter Keane in twitter. It is my feeling that “data systems” includes data systems support writ large – thus including repositories – but with an emphasis on data infrastructures that make data available for re/use and re/publication. I think existing repository systems are probably marginally desirable, but not conducive to significant out-bound use, and converting them into vehicles for digital objects that enable their enrichment and additive enhancement are necessary for them to generate traffic and value.

More in mind are working with science datasets and descriptive metadata catalogues to assist in application of these data to other domains and applications, either via simulations, mining, enrichment, or public access.

]]> By: Jonathan Rochkind http://peterbrantley.com/reality-dreams-for-libraries-213/comment-page-1#comment-80 Jonathan Rochkind Tue, 29 Dec 2009 20:29:55 +0000 http://peterbrantley.com/?p=213#comment-80 Nice essay, welcome to our airport. Can you explain more what you mean by "Data systems support"? You talk a lot about the challenges of this and such, but I'm not sure I understand exactly what tasks or functions or services you believe fall under this domain. Is developing and maintaining some sort of "institutional repository" a "data systems support" task? Maintaining access to licensed e-books? Digitizing print collections and providing access to such? Nice essay, welcome to our airport.

Can you explain more what you mean by “Data systems support”? You talk a lot about the challenges of this and such, but I’m not sure I understand exactly what tasks or functions or services you believe fall under this domain. Is developing and maintaining some sort of “institutional repository” a “data systems support” task? Maintaining access to licensed e-books? Digitizing print collections and providing access to such?

]]>