[Bug 40208] New: ILL requests documentation needed
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40208 Bug ID: 40208 Summary: ILL requests documentation needed Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs@lists.koha-community.org Reporter: hebah@bywatersolutions.com QA Contact: testopia@bugs.koha-community.org CC: aude.charillon@openfifth.co.uk, philip.orr@lmscloud.de The Koha manual spells out the available ILL statuses, but the information is very bare bones. It is not clear which ones are mandatory, which can be skipped if not applicable to a library's workflow, what triggers some of them beyond the obvious like 'checked out,' or even the expected sequence of statuses in the lifetime of a request (is completed before checked out? that's confusing in the manual without explanation). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40208 Aude Charillon <aude.charillon@openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |Needs documenting --- Comment #1 from Aude Charillon <aude.charillon@openfifth.co.uk> --- Thank you for flagging this. If you have content for the case you describe, the Documentation team would be happy to help you format it for submission to the Manual :-) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40208 Esther Melander <esther.melander@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |esther.melander@bywatersolu | |tions.com --- Comment #2 from Esther Melander <esther.melander@bywatersolutions.com> --- When creating a new ILL request, a form appears based on the type selected. Several types, such as book, include a field with the DOI abbreviation. It is not clear what this field label means. The abbreviation should be spelled out and not abbreviated at all. Or the documentation should explain the terminology. It would be nice if there was documentation about the request types and the corresponding forms and the option to add custom fields. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
participants (1)
-
bugzilla-daemon@bugs.koha-community.org