[Yazlist] Is it possible to have an additional parameter in simpleserver SRU request?

Mike Taylor mike at indexdata.com
Wed Jul 13 12:03:05 UTC 2016


Extension parameter names must begin with "x-". Compare
http://z3950.indexdata.com:210/gils?version=1.1&operation=searchRetrieve&x-pquery=mineral&startRecord=1&maximumRecords=5&foo=bar
with
http://z3950.indexdata.com:210/gils?version=1.1&operation=searchRetrieve&x-pquery=mineral&startRecord=1&maximumRecords=5&x-foo=bar

-- Mike.


On 13 July 2016 at 11:27, Michael Lackhoff <lackhoff at zbmed.de> wrote:
> Am 13.07.2016 um 12:17 schrieb Mike Taylor:
>
>> What error message?
>
> I tried it with "testparam" as the additional parameter:
>
> http://myserver:210/mydb?version=1.1&operation=searchRetrieve&query=dc.title=cancer&maximumRecords=5&recordSchema=marcxml&testparam=xxxx
>
> result:
>
> <zs:searchRetrieveResponse>
>   <zs:version>1.1</zs:version>
>   <zs:diagnostics>
>     <diag:diagnostic>
>       <diag:uri>info:srw/diagnostic/1/8</diag:uri>
>       <diag:details>testparam</diag:details>
>       <diag:message>Unsupported parameter</diag:message>
>     </diag:diagnostic>
>   </zs:diagnostics>
> </zs:searchRetrieveResponse>
>
>> On 13 July 2016 at 11:16, Michael Lackhoff <lackhoff at zbmed.de> wrote:
>>> Am 13.07.2016 um 11:35 schrieb Mike Taylor:
>>>
>>>> Have your search and scan handler functions look at $args->{EXTRA_ARGS}.
>>>
>>> But I get an error message when I add an extra param to the SRU-URL. How
>>> do I pass the EXTRA_ARG?
>>>
>>> -Michael
>>>
>>>> -- Mike.
>>>>
>>>>
>>>> On 13 July 2016 at 10:22, Michael Lackhoff <lackhoff at zbmed.de> wrote:
>>>>> Hello,
>>>>>
>>>>> I have a requirement to process queries with Simpleserver that consist
>>>>> of two parts: (1) the end-user query and (2) a filter that is used for
>>>>> authorization (a long list of journal-ids).
>>>>> It would be helpful if I could pass the filter as a seperate parameter
>>>>> to the backend, not as part of the query.
>>>>> Is there an easy way to allow/define such an addtional parameter (like
>>>>> "&fq=...") for the SRU-Interface of Simpleserver or do I have to parse
>>>>> the query and do the separation manually?
>>>>>
>>>>> A naive test resulted in an error message but perhaps it is possible to
>>>>> configure the additional parameter somewhere?
>>>>>
>>>>> Related question: Since the ID-list is quite long. What is the maximum
>>>>> length of an SRU request in Simpleserver? Does it support post-requests?
>>>>>
>>>>> -Michael
>>>>>
>>>>> _______________________________________________
>>>>> Yazlist mailing list
>>>>> Yazlist at lists.indexdata.dk
>>>>> http://lists.indexdata.dk/mailman/listinfo/yazlist
>>>>
>>>> _______________________________________________
>>>> Yazlist mailing list
>>>> Yazlist at lists.indexdata.dk
>>>> http://lists.indexdata.dk/mailman/listinfo/yazlist
>>>>
>>>
>>>
>>> _______________________________________________
>>> Yazlist mailing list
>>> Yazlist at lists.indexdata.dk
>>> http://lists.indexdata.dk/mailman/listinfo/yazlist
>>
>> _______________________________________________
>> Yazlist mailing list
>> Yazlist at lists.indexdata.dk
>> http://lists.indexdata.dk/mailman/listinfo/yazlist
>>
>
>
> _______________________________________________
> Yazlist mailing list
> Yazlist at lists.indexdata.dk
> http://lists.indexdata.dk/mailman/listinfo/yazlist



More information about the Yazlist mailing list