[openbiblio-dev] Datasets spreadsheet
naomi.lillie at okfn.org
Tue Feb 7 11:32:10 UTC 2012
So to confirm -
I will play around with this spreadsheet and make columns to categorise
what is currently denoted by colours. This can then be used for the
purposes I need if for, ie linking to openbiblio.net and updating with
recent dataset acquisitions.
Someone else (Peter?) will import the data using BibJSON to make it into a
collection - please let me know if you need my task completed before you
can start on this.
On 2 February 2012 18:39, Mark MacGillivray <mark at cottagelabs.com> wrote:
> We can already import from csv. However now that bibjson has nested keys,
> we will just need too add some catches.
> But regardless of whether we do something with this and bibserver, it is
> already a great resource that could be built on as is. And a Google
> spreadsheet can be embedded in a web page too.
> On Feb 2, 2012 6:15 PM, "Peter Murray-Rust" <pm286 at cam.ac.uk> wrote:
>> On Thu, Feb 2, 2012 at 3:44 PM, Jim Pitman <pitman at stat.berkeley.edu>wrote:
>>> > >
>> This is a brilliant piece of work by Ross and deserves wider coverage. I
>> hadn't thought of it before but a BibJSON collection based on the
>> publishers (possibly the journal) would be a brilliant and rapid
>> demonstration both of the value of BibJSON and the sorry state (IMO) of
>> hybrid open access.
>>> This is potentially extremely useful. I suggest should be developed as
>>> an openbiblio resource subject
>>> to emerging standards for maintaining such resources.
>>> > > If you're going to reuse this work (or do something similar), I'd
>>> > > suggest explicitly storing the categories in a column rather than
>>> > > making this information only available via color coding. It's
>>> > > impossible to filter, sort, search, facet, etc on a color.
>>> +1 from me. It is fine to keep this sort of data in a spreadsheet, but
>>> its full content
>>> should be exportable as csv or tsv, from which we can easily convert to
>>> BibJSON and provide some kind of
>>> BibServer display, and reuse for whatever other purposes. I have a
>>> couple of questions:
>>> 1) What is the procedure by which rows in this table can be
>> Hard graft - reading the publisher web sites. They are awful.
>>> 2) What is the relation of this table to the JISC sponsored
>>> http://www.sherpa.ac.uk/romeo/ ?
>>> No formal relationship. Romeo works on journals, whereas hybrids are per
>> article. I don't think they cover it. Also there is much fuzziness about
>> the term "open access". DOAJ I think uses the SPARC label to denore
>>> 3) How to get a machine export of http://www.sherpa.ac.uk/romeo/ to
>>> merge with Ross's data?
>>> Anyone on this list part of the Romeo/Sherpa team? Their email is
>>> romeo at sherpa.ac.uk
>>> May be good to invite them to this list if they are not already on it.
>> I know Bill Hubbard. Let's see what is involved. I can see:
>> * translating Ross-googlespreadsheet to BibJSON. Probably an evening (I
>> assume we can export as CSV).
>> * working out a technology to enhance sherpa by overlaying Ross.bjson
>> over their site. When someone click a journal it could also pop up the
>> hybrid info. That would be very useful indeed
>> * talking to sherpa about it
>> Peter Murray-Rust
>> Reader in Molecular Informatics
>> Unilever Centre, Dep. Of Chemistry
>> University of Cambridge
>> CB2 1EW, UK
>> openbiblio-dev mailing list
>> openbiblio-dev at lists.okfn.org
> openbiblio-dev mailing list
> openbiblio-dev at lists.okfn.org
Foundation Administrator and Community Coordinator (Open Bibliography)
Open Knowledge Foundation
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the openbiblio-dev