Need help to integrate Aleph500
hi community, I'm very new to library systems, maybe I'm posting to the wrong list. BTW, I'm developing an application based on RFID technology. Basically, I need to integrate my client application to Aleph500 for checkout and checkin notifications. May I have some suggestions from this list on how to do that? I know that one possibility is to interface to Aleph SIP2 server extension (used also from 3M RFID systems to notify circulations), but I'd prefer to use a real and open standard, such as NCIP protocol (if possible, is it?). Any suggestion, reference, help will be **very** appreciated. regards, Dariush.
Re: Lint.pm and 250$b
On Tue, Nov 18, 2003 at 02:31:59PM -0600, Bryan Baldus wrote: > When I ran Lint on a file of records, one of the errors I received was "250: > Subfield _b is not allowed." Sorry for the delay. This indeed looks like a bug in MARC::Lint. In case you are curious MARC::Lint's rules are obtained in an interesting way (which was devised by Colin Campbell). In the MARC::Record distribution you'll find a file etc/specs which is a program which reads a particular page that LC publishes, and then writes out an updated version of Lint.pm. This allows the rules to be updated (as LC updates them), by simply. % cd etc/ % GET http://www.loc.gov/marc/bibliographic/ecbdlist.html > file.html % ./specs file.html > Lint.pm Unfortunately, it looks like specs is somehow not getting the 250 $b properly. Which means it's probably not getting others properly as well. I'll look into it. Thanks for taking the time to report it. //Ed
Re: Lint.pm and 250$b
Bryan: On Tue, Nov 18, 2003 at 02:31:59PM -0600, Bryan Baldus wrote: > When I ran Lint on a file of records, one of the errors I received was "250: > Subfield _b is not allowed." The LC doc [1] is meticulously formatted (which is what allows specs to do what it does). Unfortunately the 250 has a slight defect: --Edition, Imprint, etc. Fields 250-270-- 250 - EDITION STATEMENT (NR) Indicators First - Undefined # - Undefined Second - Undefined # - Undefined Subfield Codes $a - Edition statement (NR) $b - Remainder of edition statement(NR) <= HERE $6 - Linkage (NR) $8 - Field link and sequence number (R) Notice how the (NR) following the $b line doesn't have a preceding space like the other equivalent spots? Well, this threw off the regex in specs, and caused the 250 $b to not make it into Lint.pm's rules. Yucky! But it's fixed. Verification before and after with diff show that it was the only data point that had that problem. So **KUDOS** to you for catching it. The fix has been committed to CVS and will go out with the next version of MARC::Record. //Ed [1] http://www.loc.gov/marc/bibliographic/ecbdlist.html
