tag:blogger.com,1999:blog-63275788210450050262024-02-19T21:31:43.957-05:00Dyrcona's Evergreen BlogWhat I am doing with EvergreenJason Stephensonhttp://www.blogger.com/profile/10445821536426911454noreply@blogger.comBlogger19125tag:blogger.com,1999:blog-6327578821045005026.post-57322451854094352222017-05-22T15:21:00.001-04:002022-03-20T18:34:12.628-04:00NCIPServer and OpenSRF 2.5+Thanks to Jason Boyer of Indiana Evergreen, it was brought to my attention that if you use the recommended Apache configuration with NCIPServer, Evergreen, and OpenSRF version 2.5.0 or later, NCIPServer crashes whenever you access its URL with the following error message:<br />
<br />
Warning caught during route execution: Use of uninitialized value in scalar assignment at /usr/local/share/perl/5.22.1/OpenSRF/DomainObject/oilsMessage.pm line 246.<br />
<br />
The reasons are a bit arbitrary and technical. The solution, however, is simple. To correct the situation, add the following directive inside the <Location /NCIP/> block in your eg_host.conf:<br />
<br />
<span style="font-family: "courier new" , "courier" , monospace;">PerlSetEnv DANCER_ENVIRONMENT "production"</span><br />
<br />
If you're upgrading to Evergreen 2.12 and OpenSRF 2.5, then you need to add the above to your configuration. Even if you are not planning an upgrade in the near future, adding that line will not hurt anything and it will help when you do eventually upgrade. Really, that directive should have been in the recommended configuration from the start, but was ignored owing to an oversight on my part.<br />
<br />
The README has been updated to include the addition of the above line for configuration of both Apache 2.2 and Apache 2.4.<br />
<br />Jason Stephensonhttp://www.blogger.com/profile/10445821536426911454noreply@blogger.com0tag:blogger.com,1999:blog-6327578821045005026.post-46277499175330347132016-08-05T10:15:00.001-04:002022-03-20T18:33:36.612-04:00NCIPServer: better_abstraction branch merged into masterThe Evergreen ILS driver for the <a href="http://git.evergreen-ils.org/?p=NCIPServer.git;a=summary">NCIPServer</a> software reached a milestone with the merge of the <a href="http://git.evergreen-ils.org/?p=working/NCIPServer.git;a=shortlog;h=refs/heads/user/dyrcona/better_abstraction"><i>better_abstraction</i> working branch</a> into the master NCIPServer repository. (NCIPServer is a <a href="http://www.niso.org/workrooms/ncip">NCIP version 2.02</a> responder for processing ILL transactions.) This merge comes after many months of production use with the <a href="https://commonwealthcatalog.org/">Massachusetts Commonwealth Catalog.</a><br />
<br />
While this merge marks the end of development on the better_abstraction branch, it is not the end of the road for NCIPServer development with Evergreen. For one thing, NCIPServer needs documentation. The README is just a placeholder. Jason Boyer of Indiana is working on improvements to the request item response messages. Also, we've given up on any pretense of compatibility with Koha, so there is code to be deleted and examples to be updated. Finally, it would be nice to have an installation method better than just copying files into place and manually editing the configuration.<br />
<br />
It is recommended that those using the better_abstraction branch in production switch to the master branch of the main repository.<br />
<br />Jason Stephensonhttp://www.blogger.com/profile/10445821536426911454noreply@blogger.com0tag:blogger.com,1999:blog-6327578821045005026.post-55687380909226592562016-07-25T12:36:00.001-04:002022-03-20T18:33:12.734-04:00Parameters Spreadsheet Utility Updated <br />
Coincident with <a href="http://evergreen.sigio.com/2016/07/evergreen-utilities-moved-to-github.html">the move to github</a>, the <a href="https://github.com/Dyrcona/evergreen_utilities/blob/master/perl/parameters.pl">parameters.pl program</a> in my <a href="https://github.com/Dyrcona/evergreen_utilities">Evergreen utilities suite</a> received a code update. It now lists all of the fields from the circulation and hold matrix matchpoint tables. Prior to this update, it only output those fields used by MVLC. This change makes the script more useful to other Evergreen sites.Jason Stephensonhttp://www.blogger.com/profile/10445821536426911454noreply@blogger.com0tag:blogger.com,1999:blog-6327578821045005026.post-82024101551226115612016-07-09T15:24:00.003-04:002022-03-20T18:32:58.799-04:00Evergreen Utilities Moved to githubI have made a clone of my Evergreen ILS Perl and SQL utilities on github. The new location is <a href="https://github.com/Dyrcona/evergreen_utilities">https://github.com/Dyrcona/evergreen_utilities</a>. If you have been using these utilities, you may want to change your remotes to the new location.<br />
<br />
I can't say how long the repository will be available at the <a href="http://git.mvlcstaff.org/?p=jason/evergreen_utilities.git;a=summary">old location</a>, but as far as I know there are no plans to take it down any time soon.<br />
<br />
I will have another post ready shortly that explains a recent update to the utility that builds a spreadsheet of your circulation and holds parameters.Jason Stephensonhttp://www.blogger.com/profile/10445821536426911454noreply@blogger.com0tag:blogger.com,1999:blog-6327578821045005026.post-83873661793660451662016-04-01T20:46:00.001-04:002022-03-20T18:32:24.873-04:00JSONPrefs has a new homeIf you have been using my JSONPrefs Perl module in your scripts, you should know that it now has a new home on Github.<br />
<br />
It now resides at <a href="https://github.com/Dyrcona/JSONPrefs">https://github.com/Dyrcona/JSONPrefs</a>.<br />
<br />
It will remain up at the old location, <a href="http://git.mvlcstaff.org/?p=jason/JSONPrefs.git;a=summary">http://git.mvlcstaff.org/?p=jason/JSONPrefs.git;a=summary</a>, for an undetermined amount of time.<br />
<br />
Please note that the history of the master branch was completely rewritten for the new home. Everything was squashed into one commit with all previous history obliterated. Its requirements were also adjusted slightly. It now depends on the <a href="http://search.cpan.org/~makamaka/JSON-2.90/lib/JSON.pm">JSON</a> Perl module and not <a href="http://search.cpan.org/~mlehmann/JSON-XS-3.02/XS.pm">JSON::XS</a>.<br />
<br />
Maybe JSONPrefs will make it to CPAN one day, but I really doubt it. <br />
<br />Jason Stephensonhttp://www.blogger.com/profile/10445821536426911454noreply@blogger.com0tag:blogger.com,1999:blog-6327578821045005026.post-17764774743024297902015-09-18T15:56:00.001-04:002022-03-20T18:32:09.367-04:00Evergreen 2.9.0 Upgrade Script ProblemChris Sharp, of Georgia Pines, detected a problem with the upgrade from Evergreen 2.8.4 to 2.9.0. It would fail because of a table being modified while data was being also being inserted into it.<br />
<br />
This problem has been corrected and a new release uploaded to the public download server: <a href="http://evergreen-ils.org/egdownloads/" target="_blank">http://evergreen-ils.org/egdownloads/</a><br />
<br />
If you have already downloaded Evergreen 2.9.0 from that location and plan to upgrade, you must download it again or the upgrade will fail.<br />
<br />
If you are planning to upgrade using git, the public repositories have been updated, so doing a git pull will get you the fixed upgrade script.<br />
<br />
As the release manager for 2.9, I apologize for any inconvenience this causes.<br />
<br />
<br />
In my defence, this is the largest upgrade script in Evergreen history so far.<br />
Jason Stephensonhttp://www.blogger.com/profile/10445821536426911454noreply@blogger.com0tag:blogger.com,1999:blog-6327578821045005026.post-3004750458141837102015-09-02T18:13:00.001-04:002022-03-20T18:31:27.188-04:00Evergreen 2.9 Release Candidate AvailableThanks to the efforts of dozens of community members, Evergreen 2.9-rc release candidate was released today. Please <a href="http://evergreen-ils.org/egdownloads/">download</a> it and have a go at testing.<br />
<br />
The release candidate contains fixes for the following bugs since the beta release:<br />
<br />
<style type="text/css">p { margin-bottom: 0.08in; text-align: justify; widows: 2; orphans: 2; page-break-before: auto; }</style>
<br />
<div align="left" style="margin-bottom: 0.08in;">
<a href="https://bugs.launchpad.net/evergreen/+bug/1484989">Fines are not calculating until after circulation is closed</a></div>
<div class="yui3-editable_text-content" id="edit-title">
<a href="https://bugs.launchpad.net/evergreen/+bug/1487143"><span class="yui3-editable_text-text ellipsis" id="yui_3_10_3_1_1441231529119_51" style="max-width: 95%;">remove legacy_script_support from sample SIPServer configuration</span></a></div>
<div class="yui3-editable_text-content" id="edit-title">
<a href="https://bugs.launchpad.net/evergreen/+bug/1484281"><span class="yui3-editable_text-text ellipsis" id="yui_3_10_3_1_1441231641463_51" style="max-width: 95%;">authority data may be deleted during propagation with current values of authority.control_set_authority_field</span></a></div>
<div class="yui3-editable_text-content" id="edit-title">
<a href="https://bugs.launchpad.net/evergreen/+bug/1486800"><span class="yui3-editable_text-text ellipsis" id="yui_3_10_3_1_1441231786269_51" style="max-width: 95%;">WARNING for Penalty.pm during make install</span></a></div>
<div class="yui3-editable_text-content" id="edit-title">
<span class="yui3-editable_text-text ellipsis" id="yui_3_10_3_1_1441231786269_51" style="max-width: 95%;">The final release of Evergreen 2.9.0 is scheduled to coincide with the next monthly update releases of the 2.8 and 2.7 Evergreen series in two weeks on Wednesday, September 16, 2015.</span></div>
<div class="yui3-editable_text-content" id="edit-title">
<br /></div>
<div class="yui3-editable_text-content" id="edit-title">
<br /></div>
<div align="left" style="margin-bottom: 0.08in;">
<br /></div>
Jason Stephensonhttp://www.blogger.com/profile/10445821536426911454noreply@blogger.com0tag:blogger.com,1999:blog-6327578821045005026.post-2410492714647593362015-08-21T10:30:00.001-04:002022-03-20T18:30:20.950-04:00A Day Late...: Evergreen 2.9-beta releasedThanks to the efforts of dozens of community members, Evergreen 2.9-beta was released yesterday, August 20, 2015. Please <a href="http://evergreen-ils.org/egdownloads/">download</a> it and have a go at testing.<br />
<br />
New Features in 2.9-beta<br />
<ul>
<li>Caching of compiled OPAC templates for performance.</li>
<li>Support for conditional negative balances.</li>
<li>Disable Google
Analytics in the staff client.</li>
<li>
<style type="text/css">p { margin-bottom: 0.08in; text-align: justify; widows: 2; orphans: 2; page-break-before: </style>Add account expiration date to OPAC My Account area.</li>
<li>More sorting options in OPAC My Account area.</li>
<li>Ability for staff to clear added content cache.</li>
<li>Better progress updates when activating a purchase order in acquisitions.</li>
<li>Ability to assign statistical category entries to items imported through Vandelay.</li>
<li>Support "blanket"
(long-lived, multi-invoice) orders in acquisitions.</li>
<li>Notify patrons via email of pending account expiration. </li>
<li>Add RDA Content Type,
Media Type, and Carrier Type attributes.</li>
<li>MARC tag table service to better teach Evergreen how to use MARC tags.</li>
<li>Teach record attributes
about <a href="http://www.w3.org/2004/02/skos/">SKOS</a> (Simple Knowledge Organization System).</li>
</ul>
Note: The last two on the above list are currently only useful with the web staff client preview but could be useful to other Evergreen components in the future.<br />
<div align="left" style="margin-bottom: 0.08in;">
</div>
<div align="left" style="margin-bottom: 0.08in;">
The web staff client preview was updated with "sprint 2" features, including:</div>
<ul>
<li>MARC Editor</li>
<li>Fixed Field Editor</li>
<li>Flat Text MARC Editor</li>
<li>Embed Vandelay</li>
<li>Batch Edit</li>
<li>URL Verification UI</li>
<li>Manage Authorities UI</li>
<li>Monograph Parts UI </li>
<li>Holdings View</li>
<li>Volume/Copy Editor </li>
<li>Z39.50 Search and Import Interface</li>
<li>Additional Hot Keys for the web staff client</li>
<li>Improve Firefox Compatibility</li>
<li>Add base files for web staff client internationalization/translation.</li>
</ul>
In addition to the removal of scripted circulation and hold rules that was <a href="http://evergreen.sigio.com/2015/07/evergreen-29-rm-update-goodbye-scripted.html">previously announced</a>, more dead code was removed:<br />
<ul>
<li>open-ils.penalty service</li>
<li>legacy self-check interface</li>
<li>last of the code from the JavaScript OPAC</li>
</ul>
One final detail of note, the Acquisitions Administration menu was moved from being a submenu of Server Administration to having its own entry on the Admin menu.Jason Stephensonhttp://www.blogger.com/profile/10445821536426911454noreply@blogger.com0tag:blogger.com,1999:blog-6327578821045005026.post-47024581707082642522015-08-12T15:18:00.001-04:002022-03-20T18:29:40.094-04:00Evergreen 2.9 Upcoming Beta Release ReminderThere will be no alpha release of Evergreen 2.9. With the beta release scheduled to coincide with the monthly maintenance releases next week on Wednesday, August 19, there is little point in doing an alpha release right now.<br />
<br />
This message is also meant to serve as a reminder of the beta release and to encourage everyone to have a look at the bugs targeted for the beta. You can find the list of them here:<br />
<a href="https://www.blogger.com/goog_1136740207"><br /></a>
<a href="https://launchpad.net/evergreen/+milestone/2.9-beta">https://launchpad.net/evergreen/+milestone/2.9-beta</a><br />
<br />
The beta is the cut off point for new features. These are bugs with a "Wishlist" importance in Launchpad, though some of the "Undecided" bugs may fall into that category as well. Any new features not merged by the time the beta is cut will need to wait until the next major release.Jason Stephensonhttp://www.blogger.com/profile/10445821536426911454noreply@blogger.com0tag:blogger.com,1999:blog-6327578821045005026.post-2141668968075926802015-07-30T10:29:00.002-04:002022-03-20T18:29:07.412-04:00Evergreen 2.9-alpha Release PostponedAs release manage for the Evergreen 2.9 release, I decided to postpone yesterday's planned alpha release pending some resolution of two new
Launchpad bugs:<br />
<br />
<a href="https://bugs.launchpad.net/evergreen/+bug/1479107" target="_blank">https://bugs.launchpad.net/evergreen/+bug/1479107</a><br />
<br />
<a href="https://bugs.launchpad.net/evergreen/+bug/1479110" target="_blank">https://bugs.launchpad.net/evergreen/+bug/1479110</a><br />
<br />
Both of these affect the conditional negative balances features, and I
thought it better to wait for some progress on those fronts rather than
releasing something that will change quite a bit in behavior in a few
weeks.<br />
<br />
Furthermore, the release notes for the conditional negative balance
feature have not been rolled out, yet, as those notes also depend upon
what happens with the above two bugs.<br />
Jason Stephensonhttp://www.blogger.com/profile/10445821536426911454noreply@blogger.com0tag:blogger.com,1999:blog-6327578821045005026.post-32020590619002106832015-07-01T10:57:00.001-04:002022-03-20T18:28:31.772-04:00Evergreen 2.9 RM Update: Goodbye Scripted Circ and Hold RulesThis update is to inform everyone that your humble Evergreen 2.9 release manager has pushed Bill Erickson's code branch to remove JavaScript circulation and hold rules in preparation for the 2.9 alpha release later this month. This means that if your site currently uses the JavaScript circulation and hold rules, you must switch to in-database circulation and hold parameters when you upgrade to Evergreen 2.9.<br />
<br />
The plans to eliminate the JavaScript circulation and hold rules have been in the works for some time. It was decided at the <a href="http://evergreen-ils.org/meetings/evergreen/2013/evergreen.2013-03-12-14.04.html">March 12, 2013 Evergreen developers' meeting</a> to deprecate the feature in the upcoming 2.4 release and to tear it out by the 2.6 release. Unfortunately, this announcement did not make it into the release notes for 2.4.<br />
<br />
A <a href="https://bugs.launchpad.net/evergreen/+bug/1312308">Launchpad bug</a> was created in April of 2014 to track progress of this effort, and it was added as a goal to the <a href="http://evergreen-ils.org/dokuwiki/doku.php?id=faqs:evergreen_roadmap:2.7">2.7 release roadmap</a>. Removal of such a large feature takes time, and so the 2.7 and 2.8 releases came and went before the efforts were finally realized earlier this year. In keeping with <a href="http://evergreen-ils.org/dokuwiki/doku.php?id=faqs:evergreen_roadmap:2.9">the goals for the 2.9 release</a>, I have tested and pushed this branch.<br />
<br />
Many thanks go to Bill Erickson and to the others who have worked on this project. The elimination of JavaScript circulation and hold rules also removes several prerequisite modules from the Evergreen installation process. This lightens the load and makes Evergreen easier to install.Jason Stephensonhttp://www.blogger.com/profile/10445821536426911454noreply@blogger.com0tag:blogger.com,1999:blog-6327578821045005026.post-35691822316142159052013-12-05T21:25:00.001-05:002022-03-20T18:27:48.377-04:00Billing Enhancements for Evergreen<p><a href="http://masslnc.cwmars.org/">MassLNC</a> has engaged me to develop <a href="http://www.sigio.com/evergreen/billing2013.html">billing enhancements</a> for Evergreen.</p>
<p>These are just about ready for testing at this point. I would have mentioned this sooner, but I've been otherwise engaged. I did <a href="http://markmail.org/message/rbz6atf7j2zhe2k3">mention it on the mailing lists</a> back in July.</p>
Jason Stephensonhttp://www.blogger.com/profile/10445821536426911454noreply@blogger.com0tag:blogger.com,1999:blog-6327578821045005026.post-63402853986163842222012-07-02T13:56:00.001-04:002022-03-20T18:27:26.205-04:00Coming soon, to a TPAC near you....<a href="http://evergreen.sigio.com/2012/05/ability-to-add-titles-to-permanent-book.html">It</a> is now finished.<br />
<br />
Having received the approval from <a href="http://masslnc.cwmars.org/">MassLNC</a>,<span style="background-color: white;"> the project sponsors, I have pushed a </span><a href="http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/dyrcona/add-to-permanent-bookbag" style="background-color: white;">cleaned up branch</a><span style="background-color: white;"> of the code to the </span><a href="http://git.evergreen-ils.org/?p=working/Evergreen.git;a=summary" style="background-color: white;">Evergreen working repository</a><span style="background-color: white;"> and added a "pullrequest" tag to the </span><a href="https://bugs.launchpad.net/evergreen/+bug/1003409" style="background-color: white;">LaunchPad bug</a><span style="background-color: white;">.These are the first steps in getting something accepted into the official Evergreen code base. With any luck, this will make it into the 2.3.0 final release.</span><br />
<br />
This project was generously funded by <a href="http://masslnc.cwmars.org/">MassLNC</a>.Jason Stephensonhttp://www.blogger.com/profile/10445821536426911454noreply@blogger.com0tag:blogger.com,1999:blog-6327578821045005026.post-42115490274467208142012-06-22T19:29:00.001-04:002022-03-20T18:26:47.463-04:00Almost There<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi-xvjZ429z3UDWihUquICCWhZbF-goqAoACOJMJtLYUFbJ25zli4A0ekfEMdgkUMlDvKj7veHGLuHrea8rs-OsFOOog-KAV-aszCXa19BHkiJ_kW7AR7IwYYT-hEcDD0jmA7jVGXy4b_2E/s1600/menushot1.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="186" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi-xvjZ429z3UDWihUquICCWhZbF-goqAoACOJMJtLYUFbJ25zli4A0ekfEMdgkUMlDvKj7veHGLuHrea8rs-OsFOOog-KAV-aszCXa19BHkiJ_kW7AR7IwYYT-hEcDD0jmA7jVGXy4b_2E/s400/menushot1.png" width="400" /></a></div>
<div class="separator" style="clear: both; text-align: center;">
<br /></div>
<div class="separator" style="clear: both; text-align: justify;">
As the above screenshot shows, I basically have this working. There are a few rough edges to be smoothed over such as redirecting to the search page after adding a record to bookbag and making similar changes on the individual record view, but most of the hard stuff is finished. A couple of currently missing features still need to be implemented.</div>
<div class="separator" style="clear: both; text-align: justify;">
<br /></div>
<div class="separator" style="clear: both; text-align: justify;">
Looks like the work will definitely be finished by the July 1 deadline.</div>
<br />Jason Stephensonhttp://www.blogger.com/profile/10445821536426911454noreply@blogger.com0tag:blogger.com,1999:blog-6327578821045005026.post-55164556952217063232012-06-14T10:13:00.001-04:002022-03-04T21:47:46.361-05:00"He's NOT the Messiah!"This isn't strictly an Evergreen post, though I did the work in the context of my role as the Chief Bug Wrangler for Evergreen/Open-ILS.<br />
<br />
Release days are always busy for me, since one of my tasks is to go through the various milestones leading up to the release and changing all of the "Fix Committed" bug to "Fix Released." In addition, I have to create a new milestone for the next bug fix release and move any remaining bugs to that new milestone. Of these two tasks, the first is generally the most time consuming.<br />
<br />
I have been looking for a way to automate some of this, and last night, I finally hit pay dirt.<br />
<a name='more'></a>
<br />
I had installed the python-launchpadlib from Canonical on my Ubuntu laptop and decided last night to use that to automate the bug closing. I found <a href="http://bazaar.launchpad.net/~lazr-developers/launchpadlib/trunk/view/head:/contrib/close-my-bugs.py">this lovely conrtib script</a> that looked like it would do the job, but after about 45 minutes of fooling around with it, I couldn't get it to work. (For those who care, the <code>lp_project.getMilestone()</code> call at line 66 kept returning an empty value.)<br />
<br />
So, then I decided to try python-launchpadlib-toolkit, which comes with the lovely <code>close-fix-committed-bugs</code> script. I browsed its source code and decided that I really wanted something slightly different, so after a few minutes of tinkering, I came up with this:<br />
<br />
<pre>
#!/usr/bin/python
# Copyright 2010 Bryce Harrington <bryce@canonical.com>
# Copyright 2012 Jason Stephenson <jason@sigio.com>
#
# This program is free software: you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation, either version 3 of the License, or
# (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program. If not, see <http://www.gnu.org/licenses/>.
import sys
import lpltk
if len(sys.argv) < 3:
print 'Usage: %s <project-name> <milestone>...' % sys.argv[0]
sys.exit(1)
project_name = sys.argv[1]
try:
lp = lpltk.LaunchpadService()
project = lp.load_project(project_name)
except:
sys.stderr.write("Could not connect to launchpad\n")
sys.exit(7)
for series in project.series:
for milestone in series.all_milestones:
for mstone_name in sys.argv[2:]:
if milestone.name == mstone_name:
for bugtask in milestone.searchTasks(status = "Fix Committed"):
print "%7s %s-->Fix Released %-40s" %(bugtask.bug.id,
bugtask.status,
bugtask.bug.title)
bugtask.status = "Fix Released"
bugtask.lp_save()
sys.exit()
</pre>
<br />
<div>
I call it <code>close-bugs.py</code>, and it works like a charm for closing bugs. To use it, you simply run it from the command line with the Launchpad Project, Evergreen in our case, as the first argument followed by the milestones whose bugs you want to close:<br />
<br />
<pre>
$ close-bugs.py Evergreen 2.2.0 2.2.0beta2 2.2.0beta1 2.2.0rc1
</pre>
<br />
That's all there is to it!<br />
<br />
Now the milestones don't have to be a millstone hanging 'round my neck! ("And, there was much rejoicing!")<br />
</div>Jason Stephensonhttp://www.blogger.com/profile/10445821536426911454noreply@blogger.com3tag:blogger.com,1999:blog-6327578821045005026.post-61117655319150589672012-06-11T19:02:00.001-04:002022-03-18T07:09:26.938-04:00Some Progress to ShowI can report some progress on the add to permanent book list feature for TPac. There is now actually some code that does something visible in my repository.<br />
<br />
So far, I believe I have worked out how to set a bookbag/list to be a patron's default list. When a logged in patron accesses their lists in TPac for the first time, they will see this:<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiio6o6P5Qh_LobUqAUWLHlzbuf0vRjVQeKlVomMKyehwhkXLQQBfdERI6_wy7Opo_9LQRQeuSid-RSTHwMOQ9wwKh1O0r724bc1WG1xrcH_i38Qiwmixp6XUeHISYtbk1HV6u0WzO_XeXL/s1600/Default+List+Before.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="227" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiio6o6P5Qh_LobUqAUWLHlzbuf0vRjVQeKlVomMKyehwhkXLQQBfdERI6_wy7Opo_9LQRQeuSid-RSTHwMOQ9wwKh1O0r724bc1WG1xrcH_i38Qiwmixp6XUeHISYtbk1HV6u0WzO_XeXL/s400/Default+List+Before.png" width="400" /></a></div>
<div class="separator" style="clear: both; text-align: center;">
<br /></div>
<div class="separator" style="clear: both; text-align: left;">
You can see above that the patron in question, me, has no default list chosen. After clicking the "Make Default List" button next to the "My List" entry, the patron's list screen will look like this:</div>
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjcBooQZhxAJzYmgrqCVgP_vpMW6Vot-lNbtlNYdqUA_E3KFC5Tc0ANR8vZ_mJzZnrZmYmbrrYDqA5JQ2KgutaRJE3EoBOiNYw8eZfZcQTu66_KS33YtXDJ014B1nqGcpeHcoNSQDUwbEfa/s1600/Default+List+After.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="221" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjcBooQZhxAJzYmgrqCVgP_vpMW6Vot-lNbtlNYdqUA_E3KFC5Tc0ANR8vZ_mJzZnrZmYmbrrYDqA5JQ2KgutaRJE3EoBOiNYw8eZfZcQTu66_KS33YtXDJ014B1nqGcpeHcoNSQDUwbEfa/s400/Default+List+After.png" width="400" /></a></div>
<br />
<br />
I know you are probably thinking, "That's it? What has he been doing for the past couple weeks?" "Working on other things," is the answer. I was hoping to get more time to work on this, but other things have come up. It should be done real soon, now, on the order of a week or two depending on how much free time I can steal at home.Jason Stephensonhttp://www.blogger.com/profile/10445821536426911454noreply@blogger.com0tag:blogger.com,1999:blog-6327578821045005026.post-4663811592771735812012-05-20T19:13:00.001-04:002022-03-20T18:24:45.717-04:00For those of you following along at home.Just thought that I'd mention that I started coding the work mentioned in my <a href="http://evergreen.sigio.com/2012/05/ability-to-add-titles-to-permanent-book.html">previous blog post.</a><br />
<br />
I have created a publicly accessible <a href="http://git.mvlcstaff.org/?p=jason/ILS.git;a=shortlog;h=refs/heads/add-to-permanent-bookbag">git branch</a> for those of you following along at home.Jason Stephensonhttp://www.blogger.com/profile/10445821536426911454noreply@blogger.com0tag:blogger.com,1999:blog-6327578821045005026.post-78751213269549562582012-05-16T21:54:00.003-04:002022-03-20T18:24:19.898-04:00Ability to add titles to permanent book lists<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head>
<meta http-equiv="Content-Type" content="application/xhtml+xml; charset=UTF-8" />
<meta name="generator" content="AsciiDoc 8.6.6" />
<title>Ability to add titles to permanent book list</title>
</head>
<body class="article">
<div id="content">
<div id="preamble">
<div class="sectionbody">
<div class="paragraph"><p>I have been hired to work on
<a href="http://masslnc.cwmars.org/node/2439">this</a>.</p></div>
<div class="imageblock">
<div class="content">
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhykQLpHrfuQydnqfK9nRvnkkjC-vpV_8qW53dbEITUXq3OfqYawoDe5C5Hbr456chc4OTMetPx5vtpFGI6k1JTJsALrN5WL623Xc8L97nfYSqpSpi5-oz1jzcxJ2h8fC7UioqIyeYO2sSX/s1600/add_to_my_list.PNG" imageanchor="1" style="margin-left:1em; margin-right:1em"><img border="0" height="213" width="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhykQLpHrfuQydnqfK9nRvnkkjC-vpV_8qW53dbEITUXq3OfqYawoDe5C5Hbr456chc4OTMetPx5vtpFGI6k1JTJsALrN5WL623Xc8L97nfYSqpSpi5-oz1jzcxJ2h8fC7UioqIyeYO2sSX/s400/add_to_my_list.PNG" /></a></div>
</div>
</div>
<div class="paragraph"><p>My proposed implementation basically covered the following:</p></div>
<div class="olist arabic"><ol class="arabic">
<li>
<p>
Add an ou setting to enable the warning when adding to a temporary
list: opac.temporary_list.warn. This will function so that if it is
not set or set to off, then the software behaves as it currently does
for adding to a temporary list.
</p>
</li>
<li>
<p>
Add an actor usr setting for holding the name of a default book
list: opac.my_list.default.
</p>
</li>
<li>
<p>
Add a checkbox on the my list interface to indicate that a certain
list should be the default list for adding titles.
</p>
</li>
<li>
<p>
Modify opac/record and opac/results so that if a patron is logged
in their my lists will populate a drop down with the default list
selected. Clicking on add to my list will add to the list currently
selected in the drop down.
</p>
</li>
<li>
<p>
If a logged in patron does not have a list, then the behavior will
be the same as for a patron who is not logged in.
</p>
</li>
<li>
<p>
If a patron is not logged in, the add to my list will appear the
same as it does currently.
</p>
</li>
<li>
<p>
Clicking on add to my list will check the ou setting mentioned in
above in 1. If that setting is on it will display a warning page to
the patron that the item has been added to a temporary list.
</p>
</li>
<li>
<p>
There will be a checkbox on this warning page so that if it is
checked when the patron dismisses the warning page, a session cookie
will be set to indicate that the patron does not want any more
warnings about the temporary list.
</p>
</li>
<li>
<p>
Logged in users will be able to skip all such warnings via a user
setting: opac.temporary_list.warn.
</p>
</li>
</ol></div>
<div class="paragraph"><p>The above was amended at an impromptu meeting held during the 2012
International Conference in Indianapolis:</p></div>
<div class="ulist"><ul>
<li>
<p>
We selected the attached mock-up as the model.
</p>
</li>
<li>
<p>
We would like some type of border around the dropdown so that it
doesn’t blend into the background (a css class for this element will
allow us to customize this).
</p>
</li>
<li>
<p>
The behavior for non-logged-in users will essentially be the same as
described in [the] proposal.
</p>
</li>
<li>
<p>
For logged-in users, the temporary list will appear first followed
by the patron’s existing lists. The default list will appear at the top.
</p>
</li>
<li>
<p>
There will also be an option to "add to new list" at the bottom of
the dropdown.
</p>
</li>
<li>
<p>
There will be a cap on the number of lists that display here. If a
user owns more lists, there will be a "See All" option that will lead
them to a new page where they can select the right list.
</p>
</li>
<li>
<p>
There will be a separate css class for the "Temporary List" element
and the "Add to New List" element.
</p>
</li>
</ul></div>
<div class="paragraph"><p>So far, I’ve got a working mockup of the menu that uses only CSS.
Since it is CSS, it can easily be styled differently from what you see
in the screen shot above. In fact, my current mockup does a reverse
video effect on the open menu, with white text on a dark green
background.</p></div>
<div class="paragraph"><p>I’ll update my progress as things develop. (Ahem.)</p></div>
</div>
</div>
</div>
</body>
</html>Jason Stephensonhttp://www.blogger.com/profile/10445821536426911454noreply@blogger.com0tag:blogger.com,1999:blog-6327578821045005026.post-82558266455965072092012-05-15T09:04:00.002-04:002022-03-20T18:23:55.365-04:00Evergreen 2.0.11 Release Announcement<div xmlns="http://www.w3.org/1999/xhtml">
<div id="preamble">
<div class="sectionbody">
<div class="paragraph">
<em>From the day late and a dollar short department.</em></div>
<div class="paragraph">
Today, the Evergreen development team released Evergreen 2.0.11, the final bug fix release for the Evergreen 2.0 series. This release includes fixes for over 35 publicly reported bugs as listed here: <a href="https://launchpad.net/evergreen/+milestone/2.0.11">https://launchpad.net/evergreen/+milestone/2.0.11</a></div>
<div class="paragraph">
This announcement ends the community’s general support for the Evergreen 2.0 series. There will be no future 2.0 releases, with the exception of those addressing security issues through August 14 2012. There will be absolutely no community releases of the 2.0 series after that date, so any sites still using the 2.0 series in production are strongly encouraged to upgrade to 2.1 or 2.2 by that date.</div>
<div class="paragraph">
The release is available for download at <a href="http://evergreen-ils.org/downloads">http://evergreen-ils.org/downloads</a></div>
<div class="paragraph">
<em>Note:</em> I’m the Evergreen 2.0 release maintainer. Well, for the 2.0.11 release anyway.</div>
</div>
</div>
</div>Jason Stephensonhttp://www.blogger.com/profile/10445821536426911454noreply@blogger.com0