[OPEN-ILS-GENERAL] 2012 EG Conference satisfaction
Thank you to attendees of the 2012 Evergreen International Conference who filled out the Conference Satisfaction Survey. Your feedback is appreciated and is very important in continuing to grow and develop the annual conference. If you have not yet filled out the survey, please do so here: https://www.surveymonkey.com/s/2012EGConferenceSurvey Vendors please fill out the survey here: https://www.surveymonkey.com/s/2012EGVendorSurvey Thank you in advance for your feedback! ___ Shauna Borger Evergreen Indiana Coordinator Indiana State Library 140 North Senate Avenue Indianapolis, IN 46204 317-234-6536 sbor...@library.in.govmailto:sbor...@library.in.gov http://evergreen2012.org/
[OPEN-ILS-GENERAL] Links for examples of Regular Expressions in the Marc Batch Editor?
Hi all, Anyone have any good examples or documentation on the Regular Expressions function in the Marc Batch Editor? I've got the camel book, but something just isn't clicking when I'm building my terms. Thanks in advance for any thoughts, hints or cheats! Tony *** Tony Bandy to...@ohionet.org OHIONET 1500 West Lane Ave. Columbus, OH 43221-3975 1-800-686-8975 x19
[OPEN-ILS-GENERAL] Holds Shelf Macro
Good afternoon all, We're running 2.0.7, and we've been having some issues with the holds slips. I've set up a receipt template that includes the %shelf_expire_time% macro, which should be displaying when the item can be pulled off the holds shelf. However, when the slip is printed, all we get is %shelf_expire_time% instead of the date/time. Are we using the wrong macro, or is anyone else having (or has had) this problem? Thanks, Rebecca Rebecca Larocque, BA (Hons), MLIS Head of Information Services North Bay Public Library 271 Worthington St. E, North Bay ON P1B 1H1 Phone: (705) 474-4830 x2821 Fax: (705) 495-4010 http://www.cityofnorthbay.ca/library
Re: [OPEN-ILS-GENERAL] Holds Shelf Macro
I don't think that macro exists in 2.0. I believe I added it in time for 2.1, though it needs a date formatter in the mix as well. Thomas Berezansky Merrimack Valley Library Consortium Quoting Rebecca Larocque rebecca.laroc...@cityofnorthbay.ca: Good afternoon all, We're running 2.0.7, and we've been having some issues with the holds slips. I've set up a receipt template that includes the %shelf_expire_time% macro, which should be displaying when the item can be pulled off the holds shelf. However, when the slip is printed, all we get is %shelf_expire_time% instead of the date/time. Are we using the wrong macro, or is anyone else having (or has had) this problem? Thanks, Rebecca Rebecca Larocque, BA (Hons), MLIS Head of Information Services North Bay Public Library 271 Worthington St. E, North Bay ON P1B 1H1 Phone: (705) 474-4830 x2821 Fax: (705) 495-4010 http://www.cityofnorthbay.ca/library
[OPEN-ILS-GENERAL] ***SPAM*** Re: Here we grow again! Link checker functionality in Evergreen
On Fri, May 11, 2012 at 02:55:42PM -0400, Suzannah Lipscomb wrote: Equinox Software, Inc. is excited to announce the development of link checker functionality in Evergreen. Uh-oh! Evergreen currently has no built-in mechanism for verifying the validity of URLs stored in MARC records. The ability to verify URLs will be of particular benefit to locations with large electronic resource collections. The requirements for this project are being developed in partnership with NRCan Library and Statistics Canada Library. The technical specifications for this project will be shared with the Evergreen Community once they are ready. Equinox developers estimate that coding will be completed no later than the end of the third quarter of 2012. As someone who has had to deal with poorly written link checkers and the havoc they wreak, I sincerely hope that one of the requirements will be *politeness* -- specifically, a throttling mechanism that keeps the link checker from hammering away at a server that happens to serve a large number of resources linked to from an Evergreen catalog. (This is actually quite simple in most cases: just shuffle the list of URLs that you check, and don't check too fast. If you have 860,400 links in a catalog you can check ten per second and still finish in 24 hours, but you'd better make sure that those ten per second aren't all requested from the same server!) And -- though it's not clear if this is what's intended or not -- *please* let's not develop an *integrated* link checker for Evergreen at all. A link checker is properly a separate special-purpose tool with a simple, well-defined interface that allows it to be used by any number of applications; it shouldn't be all tangled up in an ILS. There might even be a perfectly good link checker that fits the bill now -- I don't know, as I haven't looked into the matter very closely. OK, I'll get down off my soap box now. :-) Paul. -- Paul Hoffman p...@flo.org Systems Librarian Fenway Libraries Online c/o Wentworth Institute of Technology 550 Huntington Ave. Boston, MA 02115 (617) 445-2914 (617) 442-2384 (FLO main number)
Re: [OPEN-ILS-GENERAL] Holds Shelf Macro
There is a bug listed for this macro in 2.1 and I just verified it did not work in 2.1 also. Here is the bug report: https://bugs.launchpad.net/evergreen/+bug/994606 Lynn Floyd lfl...@andersonlibrary.org Anderson County Library 864-260-4500 x181 http://www.andersonlibrary.org http://www.andersonlibrary.org/ From: open-ils-general-boun...@list.georgialibraries.org [mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Rebecca Larocque Sent: Friday, May 11, 2012 3:59 PM To: 'open-ils-general@list.georgialibraries.org' Subject: [OPEN-ILS-GENERAL] Holds Shelf Macro Good afternoon all, We're running 2.0.7, and we've been having some issues with the holds slips. I've set up a receipt template that includes the %shelf_expire_time% macro, which should be displaying when the item can be pulled off the holds shelf. However, when the slip is printed, all we get is %shelf_expire_time% instead of the date/time. Are we using the wrong macro, or is anyone else having (or has had) this problem? Thanks, Rebecca Rebecca Larocque, BA (Hons), MLIS Head of Information Services North Bay Public Library 271 Worthington St. E, North Bay ON P1B 1H1 Phone: (705) 474-4830 x2821 Fax: (705) 495-4010 http://www.cityofnorthbay.ca/library
Re: [OPEN-ILS-GENERAL] Holds Shelf Macro
Ah. It's listed as one of the macros, which was why we've been trying to use it. Is there another similar macro in 2.0 we could use instead? Rebecca Rebecca Larocque, BA (Hons), MLIS Head of Information Services North Bay Public Library 271 Worthington St. E, North Bay ON P1B 1H1 Phone: (705) 474-4830 x2821 Fax: (705) 495-4010 http://www.cityofnorthbay.ca/library -Original Message- From: open-ils-general-boun...@list.georgialibraries.org [mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Thomas Berezansky Sent: Friday, May 11, 2012 4:08 PM To: Evergreen Discussion Group Subject: Re: [OPEN-ILS-GENERAL] Holds Shelf Macro I don't think that macro exists in 2.0. I believe I added it in time for 2.1, though it needs a date formatter in the mix as well. Thomas Berezansky Merrimack Valley Library Consortium Quoting Rebecca Larocque rebecca.laroc...@cityofnorthbay.ca: Good afternoon all, We're running 2.0.7, and we've been having some issues with the holds slips. I've set up a receipt template that includes the %shelf_expire_time% macro, which should be displaying when the item can be pulled off the holds shelf. However, when the slip is printed, all we get is %shelf_expire_time% instead of the date/time. Are we using the wrong macro, or is anyone else having (or has had) this problem? Thanks, Rebecca Rebecca Larocque, BA (Hons), MLIS Head of Information Services North Bay Public Library 271 Worthington St. E, North Bay ON P1B 1H1 Phone: (705) 474-4830 x2821 Fax: (705) 495-4010 http://www.cityofnorthbay.ca/library
Re: [OPEN-ILS-GENERAL] Here we grow again! Link checker functionality in Evergreen
*please* let's not develop an *integrated* link checker for Evergreen at all Disagree -- there's no reason why link checker code couldn't be developed to be used (or easily adapted) to service both general purpose roles as well as integrated Staff Client functionality. What do you do for libraries who don't have direct server or easy database access? How else can cataloguers be empowered to service link errors, especially as we move towards increasing digital collections? Advantages of integration could include, for example, exposing batch editing and more effective reporting, etc. I won't argue the point right now but integration needn't be incompatible with dis-integration, say encouraging the ability to generalize the service or allowing alternate solutions to the problem. There is currently some sys admin oriented link checker code out there already for Evergreen that could be adapted (and improved) for general purpose usage (esp. for any database generated link listings, etc.) For some basic working code, see our earlier submissions here: http://markmail.org/message/v4cyszy33sgocqab and here: http://markmail.org/message/kgbpzgg25cm6fqcs (with maybe some additional enhancements from Liam's work to be submitted by us later). But a good point to reinforce - it's a good design goal to ensure that any core link checker code be adaptable for more arbitrary purposes. Thanks for the feedback! George George Duimovich NRCan Library / Bibliothèque de RNCan -Original Message- From: open-ils-general-boun...@list.georgialibraries.org [mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Paul Hoffman Sent: May 11, 2012 15:14 To: open-ils-general@list.georgialibraries.org; open-ils-...@list.georgialibraries.org Subject: [OPEN-ILS-GENERAL] ***SPAM*** Re: Here we grow again! Link checker functionality in Evergreen On Fri, May 11, 2012 at 02:55:42PM -0400, Suzannah Lipscomb wrote: Equinox Software, Inc. is excited to announce the development of link checker functionality in Evergreen. Uh-oh! Evergreen currently has no built-in mechanism for verifying the validity of URLs stored in MARC records. The ability to verify URLs will be of particular benefit to locations with large electronic resource collections. The requirements for this project are being developed in partnership with NRCan Library and Statistics Canada Library. The technical specifications for this project will be shared with the Evergreen Community once they are ready. Equinox developers estimate that coding will be completed no later than the end of the third quarter of 2012. As someone who has had to deal with poorly written link checkers and the havoc they wreak, I sincerely hope that one of the requirements will be *politeness* -- specifically, a throttling mechanism that keeps the link checker from hammering away at a server that happens to serve a large number of resources linked to from an Evergreen catalog. (This is actually quite simple in most cases: just shuffle the list of URLs that you check, and don't check too fast. If you have 860,400 links in a catalog you can check ten per second and still finish in 24 hours, but you'd better make sure that those ten per second aren't all requested from the same server!) And -- though it's not clear if this is what's intended or not -- *please* let's not develop an *integrated* link checker for Evergreen at all. A link checker is properly a separate special-purpose tool with a simple, well-defined interface that allows it to be used by any number of applications; it shouldn't be all tangled up in an ILS. There might even be a perfectly good link checker that fits the bill now -- I don't know, as I haven't looked into the matter very closely. OK, I'll get down off my soap box now. :-) Paul. -- Paul Hoffman p...@flo.org Systems Librarian Fenway Libraries Online c/o Wentworth Institute of Technology 550 Huntington Ave. Boston, MA 02115 (617) 445-2914 (617) 442-2384 (FLO main number)
Re: [OPEN-ILS-GENERAL] Here we grow again! Link checker functionality in Evergreen
Paul, Thanks also for your suggestion re: politeness. That's something our current linkchecker doesn't specifically address, except by coincidence (we currently don't sort the targeted URLs to be checked by domain). George George Duimovich NRCan Library / Bibliothèque de RNCan -Original Message- From: open-ils-general-boun...@list.georgialibraries.org [mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Paul Hoffman Sent: May 11, 2012 15:14 To: open-ils-general@list.georgialibraries.org; open-ils-...@list.georgialibraries.org Subject: [OPEN-ILS-GENERAL] ***SPAM*** Re: Here we grow again! Link checker functionality in Evergreen On Fri, May 11, 2012 at 02:55:42PM -0400, Suzannah Lipscomb wrote: Equinox Software, Inc. is excited to announce the development of link checker functionality in Evergreen. Uh-oh! Evergreen currently has no built-in mechanism for verifying the validity of URLs stored in MARC records. The ability to verify URLs will be of particular benefit to locations with large electronic resource collections. The requirements for this project are being developed in partnership with NRCan Library and Statistics Canada Library. The technical specifications for this project will be shared with the Evergreen Community once they are ready. Equinox developers estimate that coding will be completed no later than the end of the third quarter of 2012. As someone who has had to deal with poorly written link checkers and the havoc they wreak, I sincerely hope that one of the requirements will be *politeness* -- specifically, a throttling mechanism that keeps the link checker from hammering away at a server that happens to serve a large number of resources linked to from an Evergreen catalog. (This is actually quite simple in most cases: just shuffle the list of URLs that you check, and don't check too fast. If you have 860,400 links in a catalog you can check ten per second and still finish in 24 hours, but you'd better make sure that those ten per second aren't all requested from the same server!) And -- though it's not clear if this is what's intended or not -- *please* let's not develop an *integrated* link checker for Evergreen at all. A link checker is properly a separate special-purpose tool with a simple, well-defined interface that allows it to be used by any number of applications; it shouldn't be all tangled up in an ILS. There might even be a perfectly good link checker that fits the bill now -- I don't know, as I haven't looked into the matter very closely. OK, I'll get down off my soap box now. :-) Paul. -- Paul Hoffman p...@flo.org Systems Librarian Fenway Libraries Online c/o Wentworth Institute of Technology 550 Huntington Ave. Boston, MA 02115 (617) 445-2914 (617) 442-2384 (FLO main number)
[OPEN-ILS-GENERAL] Evergreen API
Hi Devs and Community, Has there ever been serious consideration given to developing an Evergreen API? And if not, why not? I'm just wondering if that might be something that we could make happen as a community, perhaps with funds we raise through some clever activity or by selling some groovy merchandise. We've been talking about doing something like that on the Oversight Board although no particular project has been suggested. But, I may suggest developing an Evergreen API unless there's some reason not do. Please advise! =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-= Lori Bowen Ayre // Library Technology Consultant / The Galecia Group Oversight Board Communications Committee / Evergreen (707) 763-6869 // lori.a...@galecia.com Availability: http://tungle.me/lori.ayre lori.a...@galecia.comSpecializing in open source ILS solutions, RFID, filtering, workflow optimization, and materials handling =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Re: [OPEN-ILS-GENERAL] [OPEN-ILS-DEV] Evergreen API
On Fri, May 11, 2012 at 07:18:09PM -0700, Lori Bowen Ayre wrote: Hi Devs and Community, Has there ever been serious consideration given to developing an Evergreen API? And if not, why not? I'm just wondering if that might be something that we could make happen as a community, perhaps with funds we raise through some clever activity or by selling some groovy merchandise. We've been talking about doing something like that on the Oversight Board although no particular project has been suggested. But, I may suggest developing an Evergreen API unless there's some reason not do. Please advise! Maybe you need to define what you mean by API. If you mean a set of methods that you can call to return data or produce results, then I think Evergreen has had that since day one. It would be really hard for us to develop Evergreen without an API. A Google search for Evergreen API returns this as hit #2 for me: http://evergreen-ils.org/blog/?p=46 What we have could certainly use a lot more documentation in many places, but we currently have native bindings for Perl, Python, Java, C, and a Google Summer of Code project to pull together an official PHP binding... all talking to the same API.
