evergreen:tags/rel_2_2_alpha3

Last commit made on 2012-03-12
Get this branch:
git clone -b tags/rel_2_2_alpha3 https://git.launchpad.net/evergreen

Branch merges

Branch information

Name:
tags/rel_2_2_alpha3
Repository:
lp:evergreen

Recent commits

c34882b... by Thomas Berezansky

Bumping version numbers and adding Changelog

Signed-off-by: Thomas Berezansky <email address hidden>

3b14fa6... by Thomas Berezansky

Updated upgrade script for 2.1-2.2

Prepping for alpha3

Signed-off-by: Thomas Berezansky <email address hidden>

5f33256... by Thomas Berezansky

Copy Location Search Groups Upgrade Script Version

Signed-off-by: Thomas Berezansky <email address hidden>

e6eb405... by Dan Scott

Add styles to org selector for loc groups

Looks like user agents don't let us do a lot with styling OPTION
elements (text colour, background colour) but this gives sites that want
to further distinguish copy groups from libraries in the org selector
something to work with.

Signed-off-by: Dan Scott <email address hidden>

9ff41d4... by Bill Erickson

Copy Location Groups : sort to top option

Adds a 'top' flag to copy_location_groups which, when enabled, will
cause the location group to sort above the child org units in the org
unit selector in the tpac.

Signed-off-by: Bill Erickson <email address hidden>
Signed-off-by: Dan Scott <email address hidden>

8286863... by Bill Erickson

TPac: detail page distinct copy/holdings display depth

This adds a new CGI param "copy_depth" which the record detail page uses
to determine which copies to display in the copy grid and what serials
holdings data to show.

The goal is to separate search depth from copy display depth for 2
main reasons:

1. When present, the search ou is set by the "locg" parameter (org +
copy location group). The "Show" links in the record detail page use
"loc" to determine the copy location org (and subsequently the depth),
which is ignored in the presence of "locg". In other words, we need
a different way to communicate which range of copies to display.

2. Separating copy depth and search depth allows us to display
search location-related summary information while at the same time
displaying a broader set of copy information. For example, searching
BR1, we can see copy summary info for BR1, SYS1, and CONS even when
explicitly viewing copy information for CONS. In other words, viewing a
broader set of copies for a record does not change the search/context
org unit, it only extends the set of copies to display.

Signed-off-by: Bill Erickson <email address hidden>
Signed-off-by: Dan Scott <email address hidden>

01e0058... by Bill Erickson

Copy Location Search Groups : admin UI improvements

Two improvements to the location group list.

1. Replace x / checkmark glyphs with clearer Visible / Not Visible
labels. Thanks for the suggestions, Lebbeous.

2. Vertically align the edit actions block and the drag grips so the
actions are always in the same place.

Signed-off-by: Bill Erickson <email address hidden>
Signed-off-by: Dan Scott <email address hidden>

08b79d6... by Bill Erickson

Copy Location Search Groups : Release Notes

Signed-off-by: Bill Erickson <email address hidden>
Signed-off-by: Lebbeous Fogle-Weekley <email address hidden>
Signed-off-by: Dan Scott <email address hidden>

ddc8c42... by Bill Erickson

Copy Location Search Groups : Admin UI

Added admin UI for managing copy location groups. It allows the user to
create/edit/delete groups and add copy locations to the groups.

The UI can be found under Admin -> Local System Administration -> Copy
Location Groups.

Signed-off-by: Bill Erickson <email address hidden>
Signed-off-by: Dan Scott <email address hidden>

32458ad... by Bill Erickson

Copy Location Search Groups : TPac org unit selector

Adds support for viewing and searching on copy location groups in the
tpac. Groups appear within the org unit selector, when the selector is
used in a search context. Groups display below the owning org unit
similar to a child org unit. Groups are displayed for all org units
that meet the following criteria: search org unit, physical location,
patron home org unit, plus ancestors and descendents of each.

To support this, TPac gets a new "locg" CGI parameter, which contains
the org unit and copy location group. It takes the form
org_id:group_id. The TPac mod_perl code will extract this value and
popuplate the search_ou accordingly. For consistency, we also use
ctx.search_ou instead of directly checking CGI.param('loc') within the
template environment.

This also includes a rewrite of the org_selector.tt2 template. It
changes it from a recursive routine to a depth-first while loop. I did
this mainly because the recursive approach was suffering from global
variable clobbering in the template environment. In theory, this new
approach should be faster as well.

Signed-off-by: Bill Erickson <email address hidden>
Signed-off-by: Dan Scott <email address hidden>