Lots of crosschecking. Accept files from command line or STDIN.
Had to break out the logic in EDI to accommodate non-retrieved input.
Remote retrieval now avoids pulling a file if the same file was
previously retrieved and successfully processed. If it bombed out,
then we get it again (on the hopes it might have been fixed).
Also better test_client behavior on edi2json failure.
Overhaul ORDRSP processing based on new Business::EDI capabilities
Lots of error checking
Fetch updates for xpath_value and a B&T data hack
ORDRSP is forced only b/c the DB requires it. We can't accurately
know the message type until the translator deals with it (or we
build our own fault-prone sniffer). But for now all we expect from
vendors in ORDRSP, so we can force temporarily.
* updated bibliographic tooltips; now current as of LC MARC21 Bibliographic
Update 11, including the RDA tags. Along the way, enhanced the bib tooltips to:
* include definitions for embedded holdings tags (84X, 853-855, 863-868, 876-878)
* expand dropdown for nonfiling indicator values
* added tooltip files for authority records and MFHDs
* taught MARC editor how to choose the correct tooltip file
Caveat: if you localize the authority and MFHD tooltips for a locale other than
en-US, you must edit marcedit.js, either to take your translation into account
or to make it smarter about checking for available translations of the tooltips.
additional issuance holds supporting code; in this case, hold_to_mvr func which is used by the uber hold details method; commit also includes a small speed tweak for fetching details for copy holds (1 less cstore call)
Integrate authority browse and creation support into the MARC editor
This commit changes the contextual authority menu to be based on
the authority browse interface; this should result in better
matching behavior. The browse axis (author, subject, title, topic)
is based on the context tag.
The browse interface has enabled the contextual menu to grow
"Next page" / "Previous page" menu items to enable cataloguers
to wade through long lists of similar authority entries.
The browse interface has also grown a "Create new authority record"
menu with two submenu items.
* "Create immediately" takes the field in context and creates a new authority
record based on that field, with matching indicators and subfields.
* "Create and edit..." displays the MARCXML for the authority record in
a MARC editor window before saving the record to the database.
TODO: Make the "Create..." contextual options add the $0 linking subfield
to the newly controlled field.
TODO: Address some of the flaky UI behaviour, such as having to right-click
three times on an authority-controllable field to display the authority menu.
fix retrieval of cat.default_classification_scheme
Fixes bug where the cat.default_classification_scheme OU
setting was effectively ignored in bib call # display
in bib overlay and list of default call numbers during volume
creation.
method for generating a set of compressed holdings statements for a bib with optional location and depth scoping, type filtering and item status filtering
we need to move permissions around for a Great Renumbering, but i18n is not protected by fkeys. this provides infratructure for maintaining i18n values that already exist in a db, and an example usage on permission.perm_list
The custom file need only contain the properties that you wish to change.
The xul <messagecatalog id="commonStrings" src="/xul/server/locale/<!--#echo var='locale'-->/common.properties" /> will attempt to parse both common.properties and common_custom.properties
senator [Sun, 12 Sep 2010 19:03:01 +0000 (19:03 +0000)]
Serials: dojo/autogrid-based scaffolding for building serials objects
Accessible from the staff client OPAC browser's "Actions for this Record" menu
as "Alternate Serial Control", these minimalist interfaces should support a
workflow by which the user can create a subscription and its related parts
(distributions, streams, etc), and get things going in a quick and dirty way
while the existing Serial Control View continues to develop.
Some notable differences in orientation between this and the existing
interface work include:
- The disuse of call numbers on distributions, instead favoring call number
application to items by issuance at receive time (i.e., all copies of
the Sep 2010 issue of Popular Mechanics share a call number rather than
all copies of Popular Mechanics, any issue, at a given library sharing a
call number).
- Lack of attention to binding (although the batch receive interface will
treat each item as a single bound unit, for barcoding, or will avoid
creating units altogether if you don't want to barcode your serials).
If this doesn't sound like the way you would do serials, I'd definitely
recommend sticking with Serials Control View and ignoring these interfaces.
Dan Wells' interface work promises broader functionality in the long run.
senator [Sun, 12 Sep 2010 00:12:26 +0000 (00:12 +0000)]
Serials: support predicting issuances until a specified end date
Previously you could specify a number of issues, or possibly a final holding,
but if you haven't created the final holding yet, but you know when the
subscription ends, this can be useful.
add "type" (siss.holding_type) and "status" (sitem.status) filters; renaming the method to be explicit about the fact that it is for issuances with received (sitem.date_received IS NOT NULL) items /only/
senator [Fri, 10 Sep 2010 22:24:44 +0000 (22:24 +0000)]
Add "refresh grid" buttons to some consistently glitchy autogrids.
This is obviously not an ideal solution, but if the user sees these grids
and it's clear that not all the rows that should appear are rendering, they
at least have a button to click to deal with it. There are probably other
places where this could be applied.
'use parent' consistently throughout OfflineStore.pm
If we're going to use "use parent" instead of "use base" when creating
the child instance of Class::DBI 3.01 that is OpenILS::Utils::OfflineStore,
we might as well be consistent when declaring its own children.
In list.fm_columns, allow us to dictate the data object used for rendering (the row.my object fed into list.append) for all columns via the '*' column definition. Also, wire up mailing and billing address columns into Patron Search
Give the ability to duplicate column definitions by prefixing their id's. Allow the specification of alternate row objects and datafields to render from. The idea is to let us do such things as list address columns for a patron twice, once for the billing address and again for the mailing address.
move Patron Search over to fm_columns instead of patron.util.columns (the former makes use of fm_IDL.xml and can automagically make use of new fields, etc.). Also give fm_columns the ability to hide virtual fields from the column picker
the method behind patron.util.retrieve_fleshed_au_via_id can take a fields parameter for which fields to flesh, so let's expose that, and flesh some patron data being sent to receipt templates while we're here. End-goal is to expose address information in patron searches without sending too much data over the wire
Enable Class::DBI::Frozen::301 use for offline transaction management
Most modern systems will install Class::DBI::Frozen::301 to avoid
conflicts with incompatible Class::DBI packages. We need to teach
offline.pl how to use Class::DBI::Frozen::301 if it is available.
Note that we're using "use parent" instead of "use base" per the
recommendation of "perldoc base"; accordingly, we're adding the
system prerequisite for the parent pragma.
Remove the previously deprecated CGI interfaces for configuring the Evergreen system
The CGI interfaces have not been maintained; the interfaces available through
the Admin -> Server Administration menu in the staff client are the recommended
method for setting up new libraries in the organizational hierarchy,
permissions, copy statuses, and circulation rules.
Note that an adjustment to eg_vhost.conf is recommended to point to the
offline.pl script, which is the only remaining CGI script in use; this
should avoid conflicting Apache definitions for the /cgi-bin/ alias.
senator [Fri, 10 Sep 2010 02:15:06 +0000 (02:15 +0000)]
Booking: stop the "new resource type" dialog from executing a naughty query
The dialog will no longer offer a field for selecting a bibliographic record,
but then again you wouldn't need it. Bibliographically-based resource types
can be set up through a context menu option in the staff OPAC browser, whereas
this interface is only suited to non-bib-based resource types, like meeting
rooms, laptops, etc.
put these buttons under the sway of Dojo so that they don't get triggered when pressing enter in random fields in the patron editor form. I have no idea why this works :)
senator [Thu, 9 Sep 2010 21:28:20 +0000 (21:28 +0000)]
Improve on 17547 to support a default value for /creating/ new objects while
letting the current value of an object pass through to the overriding widget
when /editing/.
Styling tweaks to brief bib summary bar. More tooltips, and expose record id and bib call number (from the first available defined in the appropriate asset.call_number_class entry)