Bug 11147 - Changes on the “new purchase suggestion” page
Summary: Changes on the “new purchase suggestion” page
Status: CLOSED WONTFIX
Alias: None
Product: Koha
Classification: Unclassified
Component: Acquisitions (show other bugs)
Version: unspecified
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-10-28 13:46 UTC by gbarna
Modified: 2017-12-07 22:15 UTC (History)
1 user (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments
New Purchase Suggestion page (55.18 KB, image/png)
2013-10-28 13:46 UTC, gbarna
Details

Note You need to log in before you can comment on or make changes to this bug.
Description gbarna 2013-10-28 13:46:18 UTC
Created attachment 22468 [details]
New Purchase Suggestion page

One of our library staff person made the following inquiry. Is anybody interested in such changes?

"Would it be possible to change things on the “new purchase suggestion” page in the catalog?  Here’s what it currently looks like below.  Could the “Notes” be changed to “Reason”.  Notes seems a little ambivalent.  Could we change the second sentence at the top to start, “Only the title, author and reason is required,…”   In titles for research, there are titles that are very close if not identical, especially dealing with critiques.  I’m thinking if the reason is pleasure reading I can just process and handle.  If it is for class research, we can refer to the liaison for evaluation."

I have attached the image she submitted to us. 

Thanks,

Geanina King
Comment 1 Katrin Fischer 2015-02-22 09:18:26 UTC
You can define a separate pull down for a reason using the OPAC_SUG authorised value. It would also be possible to use jquery to change the text and labelling of the fields to better suit your needs. The manual has screenshots showing the additional field:
http://manual.koha-community.org/3.18/en/purchasesuggest.html

I think since there is a specific field for the reason, renaming the notes field would get a bit confusing. I think as the needs of the libraries are very different, we probably need to stick with a general text or add options to better customize.