[Koha-bugs] [Bug 23616] New: Private repeatable note field needed in Serials Subscription Record

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

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23616

            Bug ID: 23616
           Summary: Private repeatable note field needed in Serials
                    Subscription Record
 Change sponsored?: ---
           Product: Koha
           Version: 18.11
          Hardware: All
                OS: All
            Status: NEW
          Severity: enhancement
          Priority: P5 - low
         Component: Serials
          Assignee: koha-bugs at lists.koha-community.org
          Reporter: niamh.walker-headon at it-tallaght.ie
        QA Contact: testopia at bugs.koha-community.org
                CC: colin.campbell at ptfs-europe.com

It is useful to have a record of emails and dates of correspondence in the note
field of a journal record in KOHA serials subscriptions. We want to keep this
type of note for staff view only while still having the option of a public note
also. 

Staff need to see at a glance what and when action is taken when a claim is
escalated. When a missing journal eventually arrives and is marked arrived?, 

Currently, the notes in the note field must be deleted, as they will show on
the OPAC. So the record of what happened is lost in KOHA serials. It would be
useful to have a  repeatable private note field as well as the public one. See:
Electrical Times:
https://librarysearch.it-tallaght.ie//cgi-bin/koha/opac-detail.pl?biblionumber=25354
? On this record, See the note for July 2018. It is far easier to see what is
happening when the notes are in KOHA serials than stored elsewhere. 


Serials - Record: Serials administrators need a repeatable private note field,
for administration of the subscription and claiming processes. This field would
be attached to the subscription field and would not display on the opac.
Serials therefore needs two note fields in subscriptions.  One for public
display and a separate repeatable one for non-public display only. This change
would also mean that we can change the status of an issue to “missing (not
received)” and be able to explain this status further, such as “not published”
or “combined with December issue” in the public note, while still being able to
use the non public note for recording details in relation to correspondence and
actions relating to claiming the missing issue.



These notes are kept to observe patterns in failure to supply, issues with
delivery, non-publication etc., so that staff know who was contacted when
regarding issues about issues. Processing of serials claims would be more
accurate and efficient.  This simple change would allow the serials workflow to
stay within the serials module making it more streamlined and efficient.Staff
feel that this data does not belong on the marc record.
Loss of information re business relationship and contractual efficiency with
supplier. We currently use this note field to record any
problems/correspondence in relation to subscriptions. It enables us to spot
patterns in non-supply.  

On arrival of an issue we must then delete the notes from this field or they
will show to the public.  The history of correspondence/problems will now be
lost.  These notes can be useful for tracking ongoing/previous problems. 
Having to ensure that notes are deleted before displaying publicly allows for
possible human error.

As far as I can see, this is not the same issue as bues 11492 and 23416, but
related

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