* all potential capturable copies are now checked (up to the first
one that is permitted for the request), instead of a small random
subset of them
* don't do redundant permission checks
Apply some fixes that were earlier applied to the base installation script
090.schema.action.sql, but not in an upgrade script.
Also: correct a typo (INTEVAL -> INTERVAL). Hence this upgrade needs to go
to v2.0 as well as to trunk.
M Open-ILS/src/sql/Pg/090.schema.action.sql
M Open-ILS/src/sql/Pg/002.schema.config.sql
A Open-ILS/src/sql/Pg/upgrade/0418.function.action.fix-purge-circ.sql
Forward-port of a patch from Steve Callendar, via James Fournie, via launchpad:
When the patron.password.use_phone is set, new patrons are created with their password set to the last 4 digits of their phone number, HOWEVER, when a patron's password is reset, it does not work properly. Although the little underlined summary shows the proper 4 digits, the password box displays 9-ish digits, and is not the last 4 digits of the password.
The attached patch was created by Steve Callender and is confirmed working on 1.6.0
ORIGINAL CAVEAT: This patch will not work on 2.0 as that has a new user editor, but it would presumably be worthwhile to verify this functionality works in that editor as well.
ED NOTE: Because it is possible to use the old editor -- it still exists -- this patch should be applied. It does what it advertises to do, which is fix the old editor to follow the "use phone number" OU setting.
Drop the never-used column item_count from acq.lineitem.
Drop it also from the associated history table, and rebuild
the function that maintains it. Finally, rebuild the
associated lifecycle view.
Apply to trunk only; this column never existed in 2.0.
The column has already been removed from the base installation
script.
M Open-ILS/src/sql/Pg/002.schema.config.sql
A Open-ILS/src/sql/Pg/upgrade/0417.schema.acq.drop-lineitem-item-count.sql
Dropping and recreating a foreign key constraint for config.metabib_field,
in order to change its name. WHen this foreign key was first introduced,
the upgrade script gave it one name and the base install script gave it
a different name. Here we bring the names into sync.
M Open-ILS/src/sql/Pg/002.schema.config.sql
A Open-ILS/src/sql/Pg/upgrade/0415.schema.rename-field-class-fkey.sql
Remove most annoying UI "feature" of the new authority browse list interface
When I added the new authority browse list interface, I used dojo.xhrGet()
to retrieve records from the authority browse backend - but because I didn't
specify sync:true, when you first right-clicked on a subfield, the function
would return immediately and default to showing the context menu. You would
then need to click two more times to show the authority list.
Now you get it on your first right-click, as it should be.
Browse through 20 authority records at a time in management interface
The default browse list is set to 9 elements, but we have enough vertical
space to make use of more. Perhaps we should check the font size and
viewport height and then adjust accordingly, but that would be Hard.
Remove most UI annoyances from authority management interface
* term input field now gets the focus automatically
* pressing enter in most places submits a new search
* removed the onBlur event as that required users to click a second
time to open the action menu
fix from tsbere to handle case where the print strategy is set to custom/external but the actual command is missing (perhaps due to xulrunner upgrades?)
Holdings Maintenance used to make too many assumptions about what a decent org hierarchy looked like, and had these rules to suppress some of the fetch-render-happy behavior that existed when clicking on org units. We can remove them now, and this allows volumes to render when owned by the top of the org tree
Adding a trigger. Upgrade # 0364 created the trigger function but not
the trigger itself. However the base install script 040.schema.asset.sql
creates both the function and the trigger.
M Open-ILS/src/sql/Pg/002.schema.config.sql
A Open-ILS/src/sql/Pg/upgrade/0414.schema.call-number-upd-ins-trigger.sql
In acq.fund_transfer: drop the NOT NULL constraint from dest_fund and
dest_amount, in order to accommodate deallocations -- where we move
money out of a fund without moving it into another fund.
This change was applied via upgrade script # 0135, but apparently was
never applied to the base installation script.
Forward port r17847: Make query parser a bit more careful when converting convenience classes to search classes
Queries like "Heart disease: a global problem" were getting converted to series searches
due to the trailing "se:" in the search terms. This change ensures that the convenience
class is either at the start of the input or preceded by whitespace.
When enabled, the ingest.assume_inserts_only flag disables
checking several tables for old index data to delete; skipping this
makes a small but noticeable difference when doing an initial bib
ingest with more than one process in parallel.
Note that this flag should not be used when *re*ingesting records
unless you clear the old rows beforehand.
add ingest.metarecord_mapping.skip_on_update internal flag
Enabling this allows bibliographic reingests (for new/changed indexes
or after data changes that don't affect the fingerprint) to be run
in parallel without lock contention on metarecord.metarecord* operations.
Clean up description of ARN in O:A:Cat::Authority now that arn_value is gone
A comment in the create_authority_record_from_bib_field() method stated that
the ARN value needed to be unique across the database; that is no longer true
as of r17722. Fix comment accordingly.
Create and edit... authority record now gets $0 control subfield auto-applied
Following on r17857, when you create an authority record in the flow using
the "Create and edit..." option, a $0 control subfield will automatically
be appended to the target field once "Save Record" is clicked on the authority
record editor pane. Non-savers of the bib record beware! Also subject to
interesting effects of the bib editor tab gets destroyed before the auth
record is created via the Save Record button.
Append the $0 controlling subfield to newly created authorities
Still a work in progress; obviously we need to try and grab a better
institutional code, need to teach the "Create and edit..." option
how to do the same thing, and should augment the "Authority created"
dialog box to tell the user to save the record or lose the changes
they just made.
At some point we need to consider auto-saving records, perhaps immediately
after we provide infinite undo capability to step back through previous
changes.
Thomas Berezansky noticed that the README was using "createdb -t template0",
which isn't a valid option. To avoid case problems and to be more apparent
what these options mean, let's use the verbose parameters.
Change behavior of stat cat display in horizontal patron summary. Stat Cat tab shows all patron.stat_cat_entries. Entries with usr_summary true also get shown in the Patron Info pane, underneath Email
senator [Mon, 20 Sep 2010 07:29:58 +0000 (07:29 +0000)]
Add a miniwizard for serials holding codes in the AutoGrid based interfaces,
sparing the user from needed to input MARC breaker.
TODO:
i18n
Don't assume we always start with 4,1,8,1
auto-populate chronlogy caption fields based on date (this should be easy)
make it work in a tooltipdialog? (or don't, it seems frustrating)
senator [Mon, 20 Sep 2010 05:05:00 +0000 (05:05 +0000)]
Acq: change a FilteringSelect dijit to a regular <select> to avoid a
manifestation of Dojo bug #11062; add more refresh grid buttons to unified
search
"Refresh Grid" buttons are a sad little stopgap measure to address a problem
where some AutoGrids show only some of the rows they're supposed to. Calling
.refresh() on the AutoGrid consitently right the grid. Maybe the problem
is some kind of race condition, and maybe it's related to the use of "get"
and "formatter" attributes for some columns. Or maybe it's something else.
Attempts continue to find the root of the problem and repair it.
Search for humans: AND and OR are more understandable than "&&" and "||"
The operators && and || will not mean much to many people, whereas AND and
OR have common meanings that will aid in understanding the advanced search
interface.
senator [Mon, 20 Sep 2010 00:55:16 +0000 (00:55 +0000)]
Acq: make purchase order and invoice interfaces less annoying
They're really just canned acq searches, but now they don't automatically start
the search and hide the search terms, so you have a chance to adjust what
you're looking for
for large sets of holds, usually around 10 or more, the holds display takes a little too long. instead of collecting them all and sorting them by queue position, slot them into the display table (by queue position) as they arrive
This is a patch that makes the toolbar work with the little jellybean
button on Macs. It's that little lozenge-like button on the top
right of Mac programs that shows/hides the toolbar. With this patch
it will show/hide the toolbar "button bar", making it behave more like
most Mac programs. It shouldn't have any affect on other platforms.
Expose an RSS (Atom, actually) feed in the dynamic OPAC for search results
I doubt most humans really care about RSS feeds, but this will make the
RSS feed icon highlight in Firefox and that should satisfy one of the
"requirements" for a Next Generation OPAC if that's the bar for research
papers these days.
Offer a global flag to cause the testing of hold matrix rules against the receiving user instead of the requestor, and set the initial value to enabled as this seems to be the less surprising value for current users of in-db hold logic
senator [Sat, 18 Sep 2010 00:24:41 +0000 (00:24 +0000)]
Serials batch receive: usability improvements
s/fundamental periodicity/frequency/
Smart copy location batch applicator
Dedup call numbers with same label in batch applicator
Tooltips on the holding lib column to show dist label and stream routing label
change pcrud.apply to pcrud.update, and make use of closures in loop. fixes hanging progress bar and lack of list refresh in Messages interface after modifying or archiving an existing message/penalty
Revert attempt to prevent encoding corruption that was causing encoding corruption
LDR/09 was never showing up as 'a' where it was being tested, and adding the
'a' was preventing a reconversion to UTF8. It somewhat looks like the UTF8
MARCXML input gets converted to MARC8 as part of MARC::Batch's magic, then
gets converted back to UTF8 by MARC::File::XML::as_xml_record(). Seems like
this would mean potential performance / encoding problems but it works, which
is better than what my meddlesome tests were doing.
added option to vandelay rec list import that forces it to respond to the client w/ every record processed, instead of throttled responses. this is useful for small batches where it's necessary to know the outcome of each record