[Koha-bugs] [Bug 1142] New: New List of Serials Bugs Reported from User

[bugzilla-daemon]

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1142

           Summary: New List of Serials Bugs Reported from User
           Product: Koha
           Version: branch 2.2
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Serials
        AssignedTo: address@hidden
        ReportedBy: address@hidden
         QAContact: address@hidden


We have a host of small issues with Serials.

1. Serials is not warning us when we have a duplicate barcode, nor is it
denying us when we save the record. It simply checks the issue in, but does not
add the item to our record.

2. When we use the Manual Issue portion of Serials, it is not saving the
barcode information etc. to our record. Once again, it simply checks the issue
in, but doesn't update our record.

3. Serials is not adding a date to our record showing when the issue was added
to our collection. Normally when we catalog, it is one of the blanks and we
click on it to enter today's date. Can this be added to the serials portion of
Koha?

4. Listing the last five issues is causing problems. Koha not only saves the
current issue in the "received issues" box below, but it saves the last five
issues, each time we add a new issue. Kira and I both find having the last five
issues listed there to be confusing; we would rather have the serials portion
set up the old way, just listing the next issue.

5. We have found several serials out on our shelves that when we double check,
they are not checked in Koha anymore. Kira is certain they were checked in, the
issue has the barcode and everything on it. As far as we can determine, at this
point, there is not any certain date that Koha was doing this, it seems to be
random throughout the collection of serials. We are looking for "late issues"
right now and this is how we caught them.




------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.