On 18 June 2012 23:17, Alan Millar <[email protected]> wrote: >>In the edit form publisher names, publish places and possibly other > >>fields (including series) are split on semicolons, so for humans that >>should work. For bots using the API, they can simply be added as list >>values. > > > The series field does not appear to do that, at least based on the form. See > for example > http://openlibrary.org/books/OL7418657M/Call_To_Arms > > http://openlibrary.org/books/OL7418657M.json > > It shows a single field with the embedded semicolon.
Hmm, that's too bad. I just tried to resave it (with some extra information, otherwise it wouldn't be saved at all (which is nice!)), but that didn't help. By the way, it was AMillarBot that string-joined the two series and put it in one list item, instead of adding one item for each series. Could you perhaps change that? > > > (I notice the rdf format doesn't show the series or a number of other > things. I presume it is a strictly-defined subset of the data?) Ah, the RDF - the reason I joined this list ;) My first thread [1], and second [2] on this topic have not really led to what I would have liked to see [3] (still open for comments :-)). It's created by a template that reads from the database, so it could include any and all information we like it to. The hybrid HTML/Python template for Edition RDF is at [4]. One would need a suitable RDF property to add to the template so that the semantics of the field are aligned to the definition of the property. For series, we would still need a definition. (In RDF, the "nicest" thing to do is to have a URI to refer to. If there is a URI for a series, that is much clearer than a varying series title. It would need a change in the types schema, though. Same goes for publishers, places, formats, etc.) > > > Is there a schema to examine somewhere, which says which way the series field > should go? Or is this one of those things where the API can make anything an > array/list? http://openlibrary.org/type is the list of types in OL: /type/edition for Editions (which has an array/list field for series), /type/work for Works, etc. As far as I know, there is no explicit description of what contents should go in what field (there is only the type, mostly strings). I would like that. > > - Alan Ben [1] http://www.mail-archive.com/[email protected]/msg00478.html [2] http://www.mail-archive.com/[email protected]/msg00556.html [3] https://github.com/internetarchive/openlibrary/pull/136 [4] https://github.com/internetarchive/openlibrary/blob/master/openlibrary/plugins/openlibrary/templates/type/edition/rdf.html > > _______________________________________________ > Ol-discuss mailing list > [email protected] > http://mail.archive.org/cgi-bin/mailman/listinfo/ol-discuss > To unsubscribe from this mailing list, send email to > [email protected] _______________________________________________ Ol-discuss mailing list [email protected] http://mail.archive.org/cgi-bin/mailman/listinfo/ol-discuss To unsubscribe from this mailing list, send email to [email protected]
