| Summary: | Allow to receive double issues in serials | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Radek Šiman (R-Bit Technology, s.r.o.) <rbit> |
| Component: | Serials | Assignee: | Bugs List <koha-bugs> |
| Status: | NEW --- | QA Contact: | Testopia <testopia> |
| Severity: | enhancement | ||
| Priority: | P5 - low | CC: | black23, colin.campbell, emjhet, josef.moravec |
| Version: | Main | ||
| Hardware: | All | ||
| OS: | All | ||
| GIT URL: | Initiative type: | --- | |
| Sponsorship status: | --- | Comma delimited list of Sponsors: | |
| Crowdfunding goal: | 0 | Patch complexity: | --- |
| Documentation contact: | Documentation submission: | ||
| Text to go in the release notes: | Version(s) released in: | ||
| Circulation function: | |||
|
Description
Radek Šiman (R-Bit Technology, s.r.o.)
2016-11-25 19:53:15 UTC
Hi Radek, the current workflow we recommend for dealing with double issues is: - Receive the serial, set it to expected and change the numbering. Example: Change 5 to be 5/6 - The next issue (6) is predicted - set it's status to 'Deleted' - The next issue is predicted - 7. All good. Does this help? Hi Kathrin, workflow that you mentioned we use. But our librarians call for one step solution like this: - Receive the serial as double, set it to expected and change the numbering. Example: Change 5 to be 5/6 and autmatic delete next issue. It`s just easier way that consume less time. Not really great new feature. Is it acceptable point of view? Mike Hi Mike, of course it is - just wanted to share how you can achieve your goal at the moment. Maybe it could be a checkbox 'delete next' or similar on the issue receive screen. Any progress? |