adding query syntax to check for existance of a value in a field, especially uri field

[Richard Aroksaar]

It would be useful to be able to restrict searches to citations that have some value in a given field, especially the uri field. This would mimic SQL syntax that tests for NOT NULL values. Specifically it would be useful to focus searches for citations that have harvestable links to web resources, besides the fulltext subset in OL.

[solrize (solrize)]

It may already be possible to do this with existing lucene syntax in a search query. I'll look at the docs and see if I can figure out a way. If not, it can be done by adding a new field to each record at search index time, containing the names of all nonempty field for that record.

Books with uri's actually sounds useful enough that it may be worth adding as a search facet. Any thoughts?

[Richard Aroksaar (richard-aroksaar)]

Thanks for the prompt reply.

One idea that I've had since this morning is that since Open Library
citations seem to become searchable as "Scanned books only" as soon as an
"ocaid" has been added to the citation, it might be possible to mimic that
functionality for the uri field.

 I've experimented with uploading a pdf to the Internet Archive into the
Temp collection, using the IA "Upload" button. I added
the ocaid value supplied by IA to the Open Library citation and now a "Read
online" button displays and this citation shows up in
the "Scanned books only" subset. Here it is:

http://openlibrary.org/b/OL344308M

This case seems a bit buggy when I try to reach the pdf from the OL
citation, perhaps because I chose the IA "Temp" collection for it. I don't
think I made a mistake
when I added the ocaid to the citation.

"Lucene syntax" sounds interesting. I think I should try to learn more
about it.

Richard Aroksaar
NPS Voyager System Administrator
206-220-4252
206-612-2006 (cell)

             solrize
             <email address hidden>
             Sent by: To
             bounces@canonical <email address hidden>
             .com cc

                                                                   Subject
             01/06/2009 01:56 [Bug 314193] Re: adding query
             AM GMT syntax to check for existance of a
                                       value in a field, especially uri
                                       field
             Please respond to
                Bug 314193
             <<email address hidden>
                chpad.net>

It may already be possible to do this with existing lucene syntax in a
search query. I'll look at the docs and see if I can figure out a way.
If not, it can be done by adding a new field to each record at search
index time, containing the names of all nonempty field for that record.

Books with uri's actually sounds useful enough that it may be worth
adding as a search facet. Any thoughts?

--
adding query syntax to check for existance of a value in a field,
especially uri field
https://bugs.launchpad.net/bugs/314193
You received this bug notification because you are a direct subscriber
of the bug.

Status in Open Library: New

Bug description:
It would be useful to be able to restrict searches to citations that have
some value in a given field, especially the uri field. This would mimic SQL
syntax that tests for NOT ...

[George (george-archive)]

Anand - please fold this in to your API work. It's important that our API allow external devs to use any of the ID types we support to query the API.