lp1012237 HOLD_ITEM_CHECKED_OUT display

Added a definition to the HOLD_ITEM_CHECKED_OUT event in ils_events.xml.
Trying to be generic between the opac and the staff client the message
reads, "The item you have attempted to place on hold is already checked
out to the requestor."

[LFW: I made a tiny spelling change to be consistent with other
appearances in Evergreen of the term "requestor".]

Signed-off-by: Garry Collum <gcollum@gmail.com>
Signed-off-by: Lebbeous Fogle-Weekley <lebbeous@esilibrary.com>
LP1251424 - Fix for submit button when placing holds in staff client

I've moved the initializing of the cur_hold_barcode variable
to within the function rather than floating outside of it.
This seemed to fix an intermittent issue where the submit
button would not become activatable when first going to the
place hold screen via the staff client. To create the hold,
ths user had to cycle through the "Place hold by patron barcode"
option and then back to "Place hold for me" option.

It looked like behind the scenes for certain org units that
variable would not be set and the button will not open until
it at least has something. This causes it to be set on the initial
loading of the screen.

Signed-off-by: Steven Callender <stevecallender@esilibrary.com>
Signed-off-by: Ben Shum <bshum@biblio.org>
Fix untranslatable strings in several dijits:

AutoGrid, EditPane, FlattenerGrid, GridColumnPicker and HoldingCode.

[LFW: One string amended in conflict resolution; commit message edited
to wrap; one line of code moved (this.nls assignment in
GridColumnPicker.js).]

Signed-off-by: Pasi Kallinen <pasi.kallinen@pttk.fi>
Signed-off-by: Lebbeous Fogle-Weekley <lebbeous@esilibrary.com>
Add basic docs for testing with pgTAP

This can be expanded to describe how to create pgTAP tests later. For
now, let's help people actually set up their environment and test.

Signed-off-by: Dan Scott <dscott@laurentian.ca>
Document how to load concerto sample data

We might as well make it as easy as possible for people to use the
sample dataset that we created!

Signed-off-by: Dan Scott <dscott@laurentian.ca>
Docs: Fix leveloffset bug, raise REL NOTES level

We should restrict our use of the asciidoc leveloffset command to the
root.txt file, since it is a global setting and cannot be set relative
to an existing offset.

This commit also raises the Release Notes section to the highest level
in order to prevent the lowest level subsections within it from being
lost. This is in response to asciidoc errors:

    WARNING: RELEASE_NOTES_2_5.txt: line 950: missing section: [sect5]

Signed-off-by: Remington Steed <rjs7@calvin.edu>
Docs: Remove ref to missing included file

This file was moved into the 2.5 release notes. If others believe it
belongs in the main documentation, it can easily be added in again. For
now, we will remove the reference because it only generates an asciidoc
warning.

Signed-off-by: Remington Steed <rjs7@calvin.edu>
LP#1037171 Removed Expert Search paramters from subject links

After performing an Expert Search, if a user visits a record and then
clicks on one of the author, subject, or series search links within that
record, then they are given the results of the Expert Search again
instead of the relevant subject or author search.

This is happening because the Expert Search parameters are retained in
the URLs via the TT2 MACRO mkurl.  In particular, the tag parameter is
used to identify an Expert Search, so if it is present in a URL, than an
Expert Search will be attempted regardless of which other paramaters are
in the URL.

To fix this, I created two varialbes within header.tt2 above the
definition of mkurl.  These variables group common URL paramters for
Expert Searches and General Search parameters together.  These variables
can be used wherever mkurl is used to strip out unneeded search
paramters.

There is a third variable that is already present within many of these
pages named stop_parms.  While I initially tried to modify this
variable, I found that there are some instances where the general search
parameters should be retained while the Expert Search parameters must go.

This commit uses these three variables togehter as input into the third
arugment of the mkurl MACRO.  The third arugment specifies which
paramtes to remove from the previous URL before making a new URL based
on the pervious URL.

I also added the query parameter to the Place Hold's hold_source_page
URL variable.  I did this, so that the query terms would be preserved
once the user is done placing the hold or decides to cancle the placing
of the hold.

As well, I used the new variables to remove Expert Search paramters
from the Advanced Search links on the results and record pages.

Conflicts:

	Open-ILS/src/templates/opac/parts/searchbar.tt2

Signed-off-by: Liam Whalen <whalen.ld@gmail.com>
Signed-off-by: Mike Rylander <mrylander@gmail.com>
LP1093856 fix Fast Item Add with Z39.50 import

The first time I tried this fix I ran afoul of
https://bugs.launchpad.net/evergreen/+bug/787561

But a second attempt worked.  So I didn't kill
two birds with one stone, but this should take
care of 1093856.

Signed-off-by: Jason Etheridge <jason@esilibrary.com>
Signed-off-by: Mike Rylander <mrylander@gmail.com>
Replace erroneous calls to $e->retrieve_authority_record($rec_id).

On lines 153 and 175 of OpenILS::Application::Cat::Authority calls
like the above should be $e->retrieve_authority_record_entry($rec_id).
This branch replaces the two misspelled calls with the proper ones.

Signed-off-by: Jason Stephenson <jstephenson@mvlc.org>
Signed-off-by: Mike Rylander <mrylander@gmail.com>
Enforce one-payment-per-xact-per-call

There is no legitimate reason for a transaction to receive more than
one payment per call to open-ils.circ open-ils.circ.money.payment,
but we have seen the staff client generate such a data structure. This
leads to seemingly duplicate payments, and is bad all around.  So,
we will enforce the restriction by taking only the first payment per
xact in the list of payments.

Signed-off-by: Mike Rylander <mrylander@gmail.com>
Signed-off-by: Bill Erickson <berick@esilibrary.com>
LP#1251774 exit and alert on multiple payments per xact

If more than one payment for a transaction is received, exit the API
call early and return a MULTIPLE_PAYMENTS_FOR_XACT event.

Signed-off-by: Bill Erickson <berick@esilibrary.com>
Signed-off-by: Mike Rylander <mrylander@gmail.com>