Dan, you're the best. You save my day ;) Thanks a lot. Simon. ==========☺ ♥ ♫ ☺ ♥ ♫ ☺ ♥ ♫ ☺ ♥ ♫ ☺ ========== Hieu Mai (Simon) Systems Developer - PALS A Program of the Minnesota State Colleges and Universities Email: [email protected] ([email protected]) "Every day may not be good… but there’s something good in every day"
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Saturday, February 16, 2013 11:00 AM To: [email protected] Subject: Open-ils-dev Digest, Vol 83, Issue 10 Send Open-ils-dev mailing list submissions to [email protected] To subscribe or unsubscribe via the World Wide Web, visit http://libmail.georgialibraries.org/mailman/listinfo/open-ils-dev or, via email, send a message with subject or body 'help' to [email protected] You can reach the person managing the list at [email protected] When replying, please edit your Subject line so it is more specific than "Re: Contents of Open-ils-dev digest..." Today's Topics: 1. Define the hold pickup location based on the physical location of the workstation (Mai, Hieu Trung) 2. Re: Define the hold pickup location based on the physical location of the workstation (Dan Wells) 3. Minor issues with 0752, 0753, and 0756 (Ben Shum) ---------------------------------------------------------------------- Message: 1 Date: Fri, 15 Feb 2013 22:27:25 +0000 From: "Mai, Hieu Trung" <[email protected]> Subject: [OPEN-ILS-DEV] Define the hold pickup location based on the physical location of the workstation To: "Evergreen Dev mailing list ([email protected])" <[email protected]> Message-ID: <[email protected]> Content-Type: text/plain; charset="utf-8" Hi all, I?m wondering if we have the way to do this? Because our libs want to define the hold pickup location (for patrons that don?t have the default hold pickup location) based on the physical location of the workstation that that staff has been using. For example, the workstation is at Library C (the organization was he/she selected at the 1st time creating his/her profile with the staff client) When he places hold for a patron A, he want the pickup location will be defined as his above physical library (Library C). In this file: /openils/var/template/opac/parts/place_hold.tt2, I think I have to fix the below code: [% l('Pickup location:') %] [%- test = What_Variable_Should_I_Use_Here; INCLUDE build_org_selector name='pickup_lib' id='pickup_lib' value=test can_have_vols_only=1 %] So do we have any variable (something like ctx.default_pickup_lib) that help me to get the physical location of the workstation I am using? Thank you ! Simon. ==========? ? ? ? ? ? ? ? ? ? ? ? ? ========== Hieu Mai (Simon) Systems Developer - PALS A Program of the Minnesota State Colleges and Universities Email: [email protected]<mailto:[email protected]> ([email protected]<mailto:[email protected]>) "Every day may not be good? but there?s something good in every day" -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://libmail.georgialibraries.org/pipermail/open-ils-dev/attachments/20130215/a7a38231/attachment-0001.htm> ------------------------------ Message: 2 Date: Fri, 15 Feb 2013 18:06:37 -0500 From: "Dan Wells" <[email protected]> Subject: Re: [OPEN-ILS-DEV] Define the hold pickup location based on the physical location of the workstation To: "Evergreen Dev mailing list ([email protected])" <[email protected]> Message-ID: <[email protected]> Content-Type: text/plain; charset=UTF-8 Hello Simon, I think ctx.user.ws_ou() is what you are looking for. Dan -- ********************************************************************************* Daniel Wells, Library Programmer Analyst [email protected] Hekman Library at Calvin College 616.526.7133 >>> On 2/15/2013 at 5:27 PM, "Mai, Hieu Trung" <[email protected]> wrote: > Hi all, > I?m wondering if we have the way to do this? > Because our libs want to define the hold pickup location (for patrons that > don?t have the default hold pickup location) based on the physical location > of the workstation that that staff has been using. > For example, the workstation is at Library C (the organization was he/she > selected at the 1st time creating his/her profile with the staff client) > When he places hold for a patron A, he want the pickup location will be > defined as his above physical library (Library C). > In this file: /openils/var/template/opac/parts/place_hold.tt2, I think I > have to fix the below code: > > [% l('Pickup location:') %] > [%- test = What_Variable_Should_I_Use_Here; > INCLUDE build_org_selector name='pickup_lib' id='pickup_lib' > value=test can_have_vols_only=1 %] > > So do we have any variable (something like ctx.default_pickup_lib) that help > me to get the physical location of the workstation I am using? > Thank you ! > Simon. > > ==========? ? ? ? ? ? ? ? ? ? ? ? ? ========== > Hieu Mai (Simon) > Systems Developer - PALS > A Program of the Minnesota State Colleges and Universities > Email: [email protected]<mailto:[email protected]> > ([email protected]<mailto:[email protected]>) > "Every day may not be good? but there?s something good in every day" ------------------------------ Message: 3 Date: Sat, 16 Feb 2013 05:16:56 -0500 From: Ben Shum <[email protected]> Subject: [OPEN-ILS-DEV] Minor issues with 0752, 0753, and 0756 To: Evergreen Development Discussion List <[email protected]> Message-ID: <[email protected]> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Just noting some minor issues as I was worked through upgrading a copy of our production DB with the new upgrade scripts: 0752: evergreen.is_json might be public.is_json on older upgraded databases; creating that as a new function or changing the script to allow for the old naming worked for me. Still not sure how to deal with this issue for us. 0753: encountered following error, easily resolved by adding Rose::URI on our separate DB server (maybe a new dependency we should note in the README for extra modules that need to be installed for separate DB): psql:0753.functions.url_verify.sql:21: ERROR: Can't locate Rose/URI.pm in @INC (@INC contains: /etc/perl /usr/local/lib/perl/5.10.1 /usr/local/share/perl/5.10.1 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.10 /usr/share/perl/5.10 /usr/local/lib/site_perl .) at line 3. 0756: search.staged_fts ? psql:0756.drop.query_parser_fts.sql:6: ERROR: cannot drop type search.search_result because other objects depend on it DETAIL: function search.staged_fts(integer,integer,text,integer[],integer[],text[],text[],text[],text[],text[],text[],text[],text,text,text,text[],text,real,text,boolean,boolean,boolean,integer,integer,integer) depends on type search.search_result HINT: Use DROP ... CASCADE to drop the dependent objects too. This one was fun to track down. It looks like there's an old commit to remove it from the schema back in June 2010 but never an upgrade script to perform the action. See: http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=415e0c40cf8ac0fbba91541f9ddf386d02f01fec Since we were in the middle of the 1.6.0 series in June 2010 and we started Evergreen as a 1.6.0 site, I guess these remnant functions have finally caught up to us. So it looks like we need to remove both search.staged_fts and search.parse_search_args from old Evergreen systems as part of the upgrade action. I'll try wrapping all this up into a branch later this weekend if nobody beats me to it; just wanted to note these issues so that I didn't forget about them. -- Ben -- Benjamin Shum Open Source Software Coordinator Bibliomation, Inc. 32 Crest Road Middlebury, CT 06762 203-577-4070, ext. 113 End of Open-ils-dev Digest, Vol 83, Issue 10 ********************************************
