Enhancements to the MARC editor concerning fixed fields

[Lebbeous Fogle-Weekley]

For Evergreen master (and hopefully 2.6?)

Here's a branch[0] with code, release notes, and one DB test (no big DB changes were made, just a little thing), to implement two new features.

Feature #1: right-click context menus in the fixed fields part of the staff client's MARC editor, which provide a list of possible values for the given field based on consulting the database[1] with reference to the current record type. You can still type in arbitrary values, of course.

The full set of possible values for some fixed fields is not present in Evergreen stock data, but data to fill in the gaps can be added any time or on a site-by-site basis. For a fixed field that's pretty well covered by stock data, so you can see the feature in action, try "Form".

Feature #2: a wizard for the 007 field (the Physical Characteristics Wizard) to step users through each position, showing the meaning of the current position and the possible values for it, again based on the database. Testing is appreciated on the whole of the code presented, of course, but especially on this feature.

The included release notes should give an idea of how to get to these new features for UI-level testing.

Oh, and major credit to Mike Rylander for helping me grok exactly what is being modeled in the database tables listed in the footnote below, making this implementation possible.

[0] http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/collab/senator/fixed_fields_enhancements_rebase
[1] In the tables config.coded_value_map, config.record_attribute_definition, and config.marc21_physical_characteristic_*_map

[Lebbeous Fogle-Weekley (lebbeous)]

This branch is freshly rebased against master, and has an extra commit to remove some debugging cruft I'd forgotten about. Thanks to Pasi Kallinen for spotting it.

http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/collab/senator/fixed_fields_enhancements_rebase_2

[Dan Wells (dbw2)]

Programmers say: "Why can't people put good data in their records?"
Catalogers say: "Why can't programmers make MARC editing easier?"

At last, a thaw in this persistent cold war begins... with this code!

Well, I like it, anyway. I need to run home to attempt to beat some nasty weather, but I'll be pushing this asap.

[Dan Wells (dbw2)]

Moved the test file to t/regress/ (as discussed) and pushed to master. Thanks, Lebbeous!