Serials: allow non-numeric input for combined issues in alt. serials control view

Bug #888791 reported by Lebbeous Fogle-Weekley
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Evergreen
Status tracked in Main
2.0
Fix Released
Undecided
Unassigned
2.1
Fix Released
Undecided
Unassigned
2.2
Fix Released
Undecided
Unassigned
Main
Fix Released
Low
Unassigned

Bug Description

This is for master, and I think it can be considered a bugfix and backported to 2.1.

    Serials: allow freer input in holding code mini-wizard

    In the Subscription Details interface of the Alternate Serials Control
    View, under the Issuance tab, if you create a new issuance you can
    now enter things like "01/02" in (say) the month field to denote a combined
    January/February issue. All those fields are now free-form, whereas some of
    them used to be numeric only.

    Also, avoid an occasional issue where an error message about
    dijit.form.DateTextBox not being a constructor would appear in the
    JavaScript console. The problem was in a race condition among some
    co-dependent JavaScript files that were all being loaded at the same
    time.

http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/senator/serials-holding-non-numeric

Tags: pullrequest
Changed in evergreen:
milestone: 2.1.1 → 2.2.0
milestone: 2.2.0 → 2.1.1
Revision history for this message
Dan Wells (dbw2) wrote :

Hello Lebbeous,

In testing using the "01/02" value, I get the following error:

"A valid holding code cannot be produced with any blank fields."

It looks like we need to also remove the isNaN() check in HoldingCode.js. If you can verify and push, I'll sign off.

Thank you,
Dan

Revision history for this message
Lebbeous Fogle-Weekley (lebbeous) wrote :

Dan,

You're right. I've changed that to a triple-equals test against "", and force-pushed a commit to the same branch.

Thanks!

Lebbeous

Revision history for this message
Dan Wells (dbw2) wrote :

Tested and committed back through rel_2_0 (I'd consider it a straight bugfix). Thank you, Lebbeous.

Changed in evergreen:
status: New → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.