[Koha-bugs] [Bug 12375] Store serials enumeration data in separate fields

[bugzilla-daemon at bugs.koha-community.org]

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12375

Kyle M Hall <kyle at bywatersolutions.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|Failed QA                   |Signed Off

--- Comment #19 from Kyle M Hall <kyle at bywatersolutions.com> ---
(In reply to Julian Maurice from comment #16)
> If a numbering pattern uses {X}, {X}{Y} or {X}{Y}{Z}, in this order, then
> the updatedatabase works.
> But if I have a numbering pattern that uses only {Z} for example, then the Z
> part will be stored in serialseq_x (and future serials will have the Z part
> in serialseq_z column)
> If my numbering pattern uses only {X} and {Z}, the Z part will be in
> serialseq_y.
> I think this have to be fixed, so failing QA here.

Fixed! The attached qa followup should allow the database update to handle
these situations.

> Also the original serialseq column is not removed. Is it intended ? I think
> we should not keep values in database that can be easily generated on the
> fly.

We need to keep the serialseq column, at least for the time being. Right now
the new columns are for reporting. In the future we can also use them to
improve the sorting of serials. In the long run we may want to deprecate
serialseq, but each library would need to go through all their serials to
verify the sequence values are correct before upgrading ( that is, the values
may have been migrated from a previous ILS and need to be updated ).

-- 
You are receiving this mail because:
You are watching all bug changes.