Re: [OPEN-ILS-GENERAL] Amending example consortium
Dan Scott dan@... writes: Have you confirmed that the branch names, etc, were actually changed by checking the database? Stranger and stranger. Checking the table showed the following. evergreen=# select id, shortname, name from actor.org_unit; id | shortname | name +---+--- 8 | SL1 | Example Sub-library 1 9 | BM1 | Example Bookmobile 1 3 | SYS2 | Saltwell Street 5 | BR2 | Back Study 6 | BR3 | Ruth's 7 | BR4 | Kitchen 4 | BR1 | Home Library 2 | SYS1 | Ovett 1 | CONS | JH Consortium (9 rows) The names shown above are the long names I have set, but the short names are the originals (that is, I changed these and none of the 'shortname' changes are reflected in the table). Even more oddly, the changed long names visible in the table are not shown under 'Organizational Units' in the staff client, which appears to load correctly but still shows the original short names with the long names of 'Example Branch 1', 'Example Branch 2' etc. Any thoughts on this?
Re: [OPEN-ILS-GENERAL] Amending example consortium
Jason Stephenson jstephenson@... writes: Any thoughts on this? Quit the staff client. Run autogen.sh -u on the server. Login again with the staff client. I should share the SQL that I used to setup our organizational units during our migration. It's probably on paste.lisp.org somewhere. Thanks, but I'd already tried the above. I added the names shown in my post above a few days ago and the server has been restarted and autogen run a few times since then. I tried again just to make sure (autogen.sh -u followed by a restart of Apache). I didn't see any errors but, when I logged into the client, everything was exactly the same as shown above. I re-checked the table and my new long names are in there, but not showing in the client.
Re: [OPEN-ILS-GENERAL] Amending example consortium
Dan Scott dan@... writes: ... http://evergreen-ils.org/documentation/install/README_2_1_1.html linked from the Downloads page, under Starting Evergreen, says to just use autogen.sh -u. The script automatically figures out where the configuration file lives these days. Thanks. I think I went to the full command with -c when I first noticed that the changes weren't being saved, or weren't showing. Have you confirmed that the branch names, etc, were actually changed by checking the database? No, but I will now - your SQL statements will certainly be useful. I guess what you're saying is that changes I make in the client should go into the appropriate database table immediately, and that autogen simply passes a change notification to other parts of the system. If it turns out that the changes aren't appearing in the table, I'll try editing it directly - although that would suggest that there might still be other problems with my system.
Re: [OPEN-ILS-GENERAL] Amending example consortium
John Hudson gadgetfan.john@... wrote: Any thoughts about why the following is happening? With Evergreen 2.1.0 and staff client 2.1, I'm trying to rename the branches in the example consortium. I make the changes in the client, click SAVE, then go to the server and type the following (from the documentation for 1.6 - this doesn't seem to be in 2.1 docs at all): /openils/bin/autogen.sh -c /openils/conf/opensrf_core.xml -u This shows the following: /openils/bin/autogen.sh: illegal option -- c ... I then run /etc/init.d/apache2 restart as root and the server restarts but, when I go back into Evergreen, all my changes have reverted to the defaults. Can no-one help me on this? I did find something that might describe the problem at http://list.georgialibraries.org/pipermail/open-ils-commits/2011- October/015316.html but, from my minimal knowledge of Perl, the fix there looked as if it had some missing closing brackets. I wasn't sure exactly what I was meant to type, or even if Configure.pm becomes an executable script... I'd be grateful for any clarification as I'm stuck with the example branches at the moment. Thanks.
Re: [OPEN-ILS-GENERAL] Amending example consortium
On Wed, Nov 30, 2011 at 07:38:56PM +, John Hudson wrote: John Hudson gadgetfan.john@... wrote: Any thoughts about why the following is happening? With Evergreen 2.1.0 and staff client 2.1, I'm trying to rename the branches in the example consortium. I make the changes in the client, click SAVE, then go to the server and type the following (from the documentation for 1.6 - this doesn't seem to be in 2.1 docs at all): /openils/bin/autogen.sh -c /openils/conf/opensrf_core.xml -u This shows the following: /openils/bin/autogen.sh: illegal option -- c ... I then run /etc/init.d/apache2 restart as root and the server restarts but, when I go back into Evergreen, all my changes have reverted to the defaults. Can no-one help me on this? I did find something that might describe the problem at http://list.georgialibraries.org/pipermail/open-ils-commits/2011- October/015316.html but, from my minimal knowledge of Perl, the fix there looked as if it had some missing closing brackets. I wasn't sure exactly what I was meant to type, or even if Configure.pm becomes an executable script... http://evergreen-ils.org/documentation/install/README_2_1_1.html linked from the Downloads page, under Starting Evergreen, says to just use autogen.sh -u. The script automatically figures out where the configuration file lives these days. I'd be grateful for any clarification as I'm stuck with the example branches at the moment. Have you confirmed that the branch names, etc, were actually changed by checking the database? -- This will show you what you currently have SELECT id, shortname, name FROM actor.org_unit; And you can change the shortnames / long names via regular SQL: -- This will change the data for BR1 to NEWNAME / My long new name UPDATE actor.org_unit SET shortname = 'NEWNAME', name = 'My long new name' WHERE shortname = 'BR1';
