Re: [OPEN-ILS-DEV] Fwd: errors while running autoget.sh -c
On Fri, Aug 03, 2012 at 10:20:11AM -0400, Ben Shum wrote: Forwarded from where it was wrongly send to the catalogers list, this is a Fedora installation issue. Original Message Subject: [Evergreen-catalogers] errors while running autoget.sh -c Date: Fri, 3 Aug 2012 02:46:34 -0700 (PDT) From: Net Wolf netwolf...@yahoo.com Reply-To: Net Wolf netwolf...@yahoo.com, Evergreen Community Catalogers evergreen-catalog...@list.evergreen-ils.org To: evergreen-catalog...@list.evergreen-ils.org evergreen-catalog...@list.evergreen-ils.org Hi, I am getting the following errors while running autogen.sh -c after a fresh installation of opensrf and evergreen. [opensrf@siddharth opensrf-2.1.0]$ autogen.sh -u Updating Evergreen organization tree and IDL Updating fieldmapper Empty filename at /usr/local/share/perl5/OpenILS/Utils/Fieldmapper.pm line 208. This suggests that you might be using the opensrf.xml file from OpenSRF rather than from Evergreen - and if that's the case, then nothing else will work. Check for an IDL section in the file and a pointer to the right location of fm_IDL.xml. snip Also, I had to install UUID::Tiny, MARC::Record::XML, SRU::Request and maybe a few more that I don't remember using perl -MCPAN. I also installed postgresql-plperl. All the above are not a part of the installation dependencies mentioned in the documentation. A lot of these problems were fixed after the 2.2.0 release, so see the upcoming 2.2.1 release, or just grab the latest Makefile.install directly in git at http://git.evergreen-ils.org/?p=Evergreen.git;a=blob;f=Open-ILS/src/extras/Makefile.install Long story short: I've packaged some of the dependencies for Fedora 17, in an effort to ease the install process on Fedora. MARC::File::XML is unfortunately still waiting approval (mostly my lack of prompting the reviewer) so that needs to be pulled from CPAN still, but I've added that to the FEDORA_CPAN list in the prereq installer. Note that these packages have _not_ been backported to Fedora 16, so we're effectively supporting only the latest stable version of Fedora at this point. Many thanks for giving Evergreen a go on Fedora! I'm a little lonely out here, but I've been running Fedora as my primary environment for years now; it's really helpful having some feedback to catch what I've overlooked. One other thing I should note is that when you get to the point of running Apache, you will need to disable SELinux via setenforce 0 due to our weird run as opensrf with a webroot in a weird location issue. Some day we'll fix that...
[OPEN-ILS-DEV] RELEASE TEAM: Evergreen 2.3.beta1 uploaded
Hi All, Evergreen 2.3.beta1 files are uploaded. Web team, I've made no changes to website repository or the site itself. Let me know if anything is missing. Server: http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.3.beta1.tar.gz http://evergreen-ils.org/downloads/previews/Evergreen-ILS-2.3.beta1.tar.gz.md5 Windows staff client: http://evergreen-ils.org/downloads/previews/evergreen-setup-2.3.beta1.exe http://evergreen-ils.org/downloads/previews/evergreen-setup-2.3.beta1.exe.md5 Not-Windows Staff client files: http://evergreen-ils.org/downloads/previews/evergreen-client-2.3.beta1.tar.bz2 http://evergreen-ils.org/downloads/previews/evergreen-client-2.3.beta1.tar.bz2.md5 Install instructions: http://evergreen-ils.org/documentation/install/README_2_3.html Release notes in progress: http://evergreen-ils.org/documentation/release/RELEASE_NOTES_2_3.html -b -- Bill Erickson | Senior Software Developer | Equinox Software, Inc. / Your Library's Guide to Open Source | phone: 877-OPEN-ILS (673-6457) | email: erick...@esilibrary.com | web: http://esilibrary.com
Re: [OPEN-ILS-DEV] Hold prioritizing for branches within a system
Hi Mike, Oh that's quite interesting. I had forgotten about that blog post, but now in reviewing it, it does sound like it could potentially solve the situation I'm describing. How far along are the plans to port features from Fulfillment to Evergreen? Maybe something that we could help to test in the future. -- Ben On 07/30/2012 01:17 PM, Mike Rylander wrote: On Mon, Jul 30, 2012 at 12:32 PM, Ben Shum bs...@biblio.org wrote: Hi folks, So here's a situation. A library system has multiple branches, and each owns their own copies/patrons. Library A owns a copy of an item and Library B does not. But patrons from both A and B place holds against the material. Because of how holds target / opportunistically capture, the patrons at Library A receive the item first while the item continues to circulate in and out of Library A, while the patrons at Library B never get their holds fulfilled. It would be preferred that Library A's copy be used to fill holds for both Library A and B's patrons in the order the hold was placed regardless of pickup location. While we understand that having additional copies for each branch could solve the issue, it may not be possible for the library to purchase and assign copies to each branch. Instead, they're hoping that it is possible to re-prioritize holds within their system to follow a stricter first-in, first-out (FIFO) policy. However, the concern has been made as to how FIFO might adversely alter how the library system shares material with the rest of the consortium. Does anyone have any suggestions about other solutions or are we looking at some sort of development to change how holds target within different groups? The Custom Best-hold Selection Order part of http://blog.esilibrary.com/2012/04/16/sharing-code-is-caring/ would handle that, if I understand correctly what it is you want to do. -- Benjamin Shum Open Source Software Coordinator Bibliomation, Inc. 32 Crest Road Middlebury, CT 06762 203-577-4070, ext. 113
[OPEN-ILS-DEV] Adding ONIX support and Evergreen acquisitions
Hello everyone, I need to rapidly patch Evergreen to accept ONIX product selection files from vendors as part of EDI. For the short term, the ONIX file will be translated into MARC21slim XML and processed with Vandelay. I may have to extend it to work with non-EDIFACT messages as well. At this point I have two questions. Is anyone already working on this? Also, I am looking at Open-ILS/src/perlmods/lib/OpenILS/Application/Acq/EDI.pm and got curious. I would like to follow the EDI file naming conventions FTP FILENAMING STANDARD – Issue 4 from EDItEUR / BISG / BIC. This would simplify a lot of things. Before I dive into it, though, has anyone noticed whether vendors actually follow this convention? Thanks for any answers you have, Paul -- -- Paul Waak -- Just as most issues are seldom black or white, so are most good solutions seldom black or white. Beware of the solution that requires one side to be totally the loser and the other side to be totally the winner. The reason there are two sides to begin with usually is because neither side has all the facts. Therefore, when the wise mediator effects a compromise, he is not acting from political motivation. Rather, he is acting from a deep sense of respect for the whole truth. -- Stephen R. Schwambach
