Bug 9599 - Printable work slip on receive in acquisitions
Summary: Printable work slip on receive in acquisitions
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Acquisitions (show other bugs)
Version: Main
Hardware: All All
: P1 - high new feature
Assignee: Bugs List
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-12 16:49 UTC by Nicole C. Engard
Modified: 2025-11-11 13:37 UTC (History)
8 users (show)

See Also:
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:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nicole C. Engard 2013-02-12 16:49:28 UTC
It would be nice to have a work slip that can be printed at the time of receipt in acquisitions that can be passed on to the cataloger so that he/she can then finish the processing of the item.  It should include the bib record info and the item info. It could maybe be controlled by notices and slips and show whatever the library wanted.
Comment 1 Sandre Cunha 2017-07-05 16:19:11 UTC
Has anyone looked into the feasibility of doing this? It would really speed up the process, especially for larger libraries.
Comment 2 Katrin Fischer 2017-07-08 18:26:37 UTC
Sandre, curious - can you explain the use case a bit? What would your library print on the slip for which purpose?
Comment 3 Sandre Cunha 2017-07-21 18:33:07 UTC
Replacement cost (some library's may use retail, but we use actual)

Shelving location (sometimes multiple locations)

Notes regarding special cataloguing or processing, e.g. Use a specific Dewey number, (for a set) catalog items as set or catalog separately, discard old edition after cataloging/processing new, add holiday sticker, check out to specific person after cataloging/processing (cannot always accomplish desired outcome by placing a hold on it), etc.

I would assume Notes information would come from the notes field.
Comment 4 Sandre Cunha 2017-07-21 18:35:08 UTC
Replacement cost (some library's may use retail, but we use actual)

Shelving location (sometimes multiple locations)

Notes regarding special cataloguing or processing, e.g. Use a specific Dewey number, (for a set) catalog items as set or catalog separately, discard old edition after cataloging/processing new, add holiday sticker, check out to specific person after cataloging/processing (cannot always accomplish desired outcome by placing a hold on it), No "new" sticker, added copy, replacement, etc.

I would assume Notes information would come from the notes field.
Comment 5 Katrin Fischer 2017-08-04 10:28:53 UTC
Moving out of "in Discussion" - I think it was good to get more information - thx Sandre!
Comment 6 Sandre Cunha 2017-08-04 15:13:05 UTC
Thank you, Karen, for moving it along.
Comment 7 Katrin Fischer 2019-04-27 22:17:31 UTC
Still valid.
Comment 8 Lucas Gass (lukeg) 2023-03-02 17:02:42 UTC
This one is still valid.
Comment 9 Monique 2024-10-03 21:29:43 UTC
This would be a great option. I enter this kind of information on a slip for each ordered item. It would save time and probably easier to read. Definitely have the biblio number on the slip.
Comment 10 Alexander Wagner 2025-11-11 13:37:35 UTC
I worked on this recently as it is required for our internal workflows at the library. My approach (kindly hinted at by @cait ;) uses a report in conjunction with notices and slips.

As in the end I want to call it from the intranet catalog, I know the biblio number of the record displayed. This is fed to a report:

```sql
SELECT biblio.*, biblioitems.*, items.*,
       ExtractValue(biblio_metadata.metadata, '//datafield[@tag="035"]/subfield[@code="a"]') AS nsk,
       ExtractValue(biblio_metadata.metadata, '//datafield[@tag="082"]/subfield[@code="a"]') AS ddc,
       ExtractValue(biblio_metadata.metadata, '//datafield[@tag="083"]/subfield[@code="a"]') AS oddc
FROM items
  LEFT JOIN biblioitems on (items.biblioitemnumber=biblioitems.biblioitemnumber)
  LEFT JOIN biblio on (biblioitems.biblionumber=biblio.biblionumber)
  LEFT JOIN biblio_metadata on (biblio_metadata.biblionumber=biblio.biblionumber)
WHERE biblio.biblionumber IN <<Biblionumber|list>>
```

Then this report is then "run with template" so it displays via some nice slip. The latter consist of a few lines of HTML and CSS, and fills in the required values from the bibliographic record and uses a few form elements like check boxes to mark what has been done already.

If it's "good enough" to call up the report, add the biblio numbers (or scan barcodes with a slightly modified sql) and then click through to `run` and then `run with template`, this can be done with just the stuff that exists in Koha already.

For us I wanted to have a simple menu, from which we can select the form (we actually have more than one of this kind) so I glued it together with a rather simple (and still a bit rough) plugin that hooks up with `intranet_catalog_biblio_enhancements_toolbar_button`. This allows to have a menu right from the catalogue intranet and call up the work slip from there right up to display in the template. (So it's just one click.)