Bug 2683

Summary: Supplemental issues cannot be planned for in serials module.
Product: Koha Reporter: Chris Cormack <chris>
Component: SerialsAssignee: Bugs List <koha-bugs>
Status: NEW --- QA Contact:
Severity: enhancement    
Priority: P3    
Version: Main   
Hardware: PC   
OS: All   
GIT URL: Change sponsored?: ---
Patch complexity: --- Documentation contact:
Documentation submission: Text to go in the release notes:
Version(s) released in:
Circulation function:

Description Chris Cormack 2010-05-21 00:54:39 UTC


---- Reported by rch@liblime.com 2008-10-15 16:58:41 ----

Additional serial issues that fall outside the capacity of Koha's planning code can only be received ex post facto.  One should be able to add to a pattern a supplement prior to receiving.  

This enhancement involves two pieces:  
(1)  allowing 'receipt' of a supplement without receiving / editing another serial issue ( current interface only offers 'supplement' with edit of another serial issue record );
(2)  adding a new serial status ( something along the lines of 'anticipated', i.e. /expected/, but without the special meaning of 'expected' in terms of Koha's prediction routines ).  The issue would otherwise be handled as a late or missing issue, except not be included in claims functions.



--- Bug imported by chris@bigballofwax.co.nz 2010-05-21 00:54 UTC  ---

This bug was previously known as _bug_ 2683 at http://bugs.koha.org/cgi-bin/bugzilla3/show_bug.cgi?id=2683

Actual time not defined. Setting to 0.0
The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here: chris@bigballofwax.co.nz.
   Previous reporter was rch@liblime.com.

Comment 1 Paul Poulain 2011-08-02 13:05:41 UTC
still relevant for point (2) you can just set late/arrived/missing/claimed, not "expected"

The point (1) is no more relevant : you can create a serial in recieve without recieving a regular one
Comment 2 Katrin Fischer 2012-02-19 12:56:52 UTC
On current master you can create a supplement without receiving it or changing the date of other issues. The only problem I see is that you still can't select it to be 'Expected'.
Comment 3 Paul Poulain 2016-06-04 08:53:40 UTC
The issue described is still valid in 16.05