Yes, we're an Aleph and Voyager customer, and we use YAZ Proxy also
with Voyager.
I opted on using plain YAZ Proxy with proper configuration instead of
the "built-in" version Aleph provides, which was an older version and
didn't provide e.g. the authorization module that we (unfortunately)
need. I don't have any issues here.
--Ere
Quoting "Ziso, Ya'aqov" <ziso_at_ROWAN.EDU>:
> Ere,
> This may be the first time the issue comes up at this level with
> Aleph. Are YOU an ALEPH or Voyager customer?
> If you are on ALEPH, simply open a support_ticket requesting what
> you need/want.
> Any ALEPH customer can do that (Please!) and keep CODE4LIB up-to-date.
> ./Ya’aqov
>
>
>
>
> On 6/9/10 11:29 AM, "LeVan,Ralph" <levan_at_OCLC.ORG> wrote:
>
>> -----Original Message-----
>> From: Code for Libraries [mailto:CODE4LIB_at_LISTSERV.ND.EDU] On Behalf Of Ere
>> Maijala
>> Sent: Wednesday, June 09, 2010 4:11 AM
>>
>>> it's probably a custom YAZ Proxy. This is as far as I know the default
>>> mapping to Z39.50 (of course it could have been modified locally):
>>
>> Really? I find it hard to believe that the Index Data folks don't
>> know how to
>> make an Explain record.
>>
>> Are you saying that Aleph has no native SRU capability and YAZ is
>> the only SRU
>> access to it?
>>
>> Thanks!
>>
>> Ralph
>
>
--
Ere Maijala (Mr.)
Kansalliskirjasto / The National Library of Finland
Received on Thu Jun 10 2010 - 03:01:58 EDT