This ensures most of the rest goes without error first
Disable triggers on the table before doing update
This speeds the update up significantly as we don't need to re-calc the
additional column's new data.
Allow new column to be null (at first) with no default
This allows the column to be added *without* re-writing every row. We still
re-write every row with the update, but at least we aren't doing that
*twice* this way.
And add the not null/default to new column and re-enable triggers as our
last action.
Signed-off-by: Thomas Berezansky <email address hidden>
Signed-off-by: Jason Stephenson <email address hidden>
Adds 2 default vandelay merge profiles, in part so users will have some
useful sample data, but also so the community can have some
basic/consistent profiles for documentation purposes.
1. Match-Only Merge
This is a no-op merge. It's only purpose is to allow Vandelay, which
requires a profile of some sort to do anything, to find matching
records. This is useful for importing holdings when the MARC from the
source record is not desired. It will also be useful in the
(forthecoming) Vandelay-driven Acquisitions lineitem linking (LP
pending).
The target/incumbent record is not affected.
2. Full Overlay
Used for overlaying an entire inbound MARC record over its target
record. The target/incumbent record is completely replaced by the
inbound record.
For both, 901c is used because it's automatically updated on the target
record to match the internal ID, regardless of any field
preservation/stripping.
Signed-off-by: Bill Erickson <email address hidden>
Signed-off-by: Mike Rylander <email address hidden>
Vandley sub-pages are currently managed as hidden divs that come into
view when the requested tab is selected. This creates two types of
problems in the interface. The first is that newly created data (e.g. a
new queue) is not available in the UI, because it's not getting
re-fetched from the server when the tab is opened (or added to local
data stores). Second, certain form elements misbehave when the form is
re-rendered without a refresh. Elements, typically checkboxes, will
appear to be selected when they are not. (Or, perhaps they are, and the
method to detect their selection is not sufficient). The simplest
solution to both problems is to simply reload the page....
This patch changes the tabs for Import Records and Inspect Queue so that
they reload the page (focused on the selected tab) instead of just
showing the hidden div. These pages were chosen because they are the
only interfaces that don't automatically refresh their own data and (for
Import Record) have forms that need refreshing.
Additionally, since the user may spend more time loading Vandelay
pages, this also fixes the long-standing annoyance of seeing the
Vandelay UI partially render while waiting for the page to load. Now,
it all remains hidden, except for a brief "Loading..." message.
Signed-off-by: Bill Erickson <email address hidden>
Signed-off-by: Jason Stephenson <email address hidden>
Signed-off-by: Mike Rylander <email address hidden>
Replace the old "Circ Mod Test" limit system with a more flexible system.
In addition to circ modifiers this system supports "Limit Groups" that are
automatically applied (by default) to any circulation checking them. This
can be overidden by setting the "Check Only" flag when linking a Limit
Group to a Limit Set.
Both the limit groups and circ modifiers are linked to "Limit Sets" that
act similarly to rules. Each Set can be attached to 0 or more circulation
matchpoints.
Each Limit set supports a number of items out (0 replaces infinite), depth
in the org tree to start counting at (0 for up to the top, 1 for 1 below,
etc), and a global flag (to check everywhere below the depth point, rather
than just those circulations that happend at ancestors/descendants).
When a Limit Set is linked to a Circulation Matchpoint it can be made
inactive and has a fallthrough flag. When the fallthrough flag is enabled
the Limit Set will be used whenever the matchpoint is involved with making
a decision. When it is disabled the Limit Set will only be used when the
matchpoint is the most specific matchpoint used in making the decision.
Limit Groups management can be found on the server administration menu.
Limit Sets management can be found on the local administration menu.
Limit Set -> Matchpoint linking is done via editing Circulation Policies.
The upgrade script does not remove the old tables in case something goes
wrong with migrating the information contained within them.
Signed-off-by: Thomas Berezansky <email address hidden>
