Summary: | Permanent withdrawn function | ||
---|---|---|---|
Product: | Koha | Reporter: | Josef Moravec <josef.moravec> |
Component: | Cataloging | Assignee: | Josef Moravec <josef.moravec> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | black23, m.de.rooy |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
GIT URL: | Change sponsored?: | Sponsored | |
Patch complexity: | --- | Documentation contact: | |
Documentation submission: | Text to go in the release notes: | ||
Version(s) released in: | Circulation function: |
Description
Josef Moravec
2015-07-23 13:21:26 UTC
Hi Josef, can you explain a bit more how you need this to work and how to understand a permanent withdrawn in difference to deleting items? Currently we have the option to set items withdrawn and to delete them (or do both...). I just created a report for a library that will probably work that way to list all items bought in a year and all items withdrawn. Coudl the itemnumber serve your purpose as a unique identifier for the item? Hello Katrin, thank you for your response/question. Our librarian act want as to have to two lists of books for inventory purposes. The first one is the list of newly bought books of course. The second one is the list of withdrawn, but the law says also the form of this list. One of them is withdrawn number, which has to be raised one by one as the items are withdrawing from catalogue. But we can't just set the status to withdrawn and then (after some time) delete it. We need the items to stay in catalogue "forever". |