Bug 30510: Add Patron reason column to suggestion tables
To test: 1. Make some patron reasons for suggestion via Home > Administration > Authorized values > OPAC_SUG 2. Give those reasons a description. 3. Make several suggestions via staff client and/or OPAC and apply some of the reasons you just made 4. Apply patch 5. Go to Home > Acquistions > Suggestions management 6. Give some of the suggestions some different status (PENDING/REJECTED/ACCEPTED/ect) 7. Make sure on each of the tables you can see the column 'Patron reason' 8. Go to Administration > Table settings and attempt to hide the column. 9. Confirm that the column is properly hidden on the Suggestions management page Signed-off-by: Rhonda Kuiper <rkuiper@roundrocktexas.gov> Signed-off-by: Katrin Fischer <katrin.fischer.83@web.de> Signed-off-by: Fridolin Somers <fridolin.somers@biblibre.com>
This commit is contained in:
parent
350cf44770
commit
fa13ec2e93
|
|
@ -174,6 +174,8 @@ modules:
|
|||
columnname: suggested_by
|
||||
-
|
||||
columnname: suggested_on
|
||||
-
|
||||
columnname: patron_reason
|
||||
-
|
||||
columnname: managed_by
|
||||
-
|
||||
|
|
|
|||
|
|
@ -731,6 +731,7 @@
|
|||
<th class="anti-the">Suggestion</th>
|
||||
<th>Suggested by</th>
|
||||
<th>Suggested on</th>
|
||||
<th>Patron reason</th>
|
||||
<th>Managed by</th>
|
||||
<th>Managed on</th>
|
||||
<th>Last modification by</th>
|
||||
|
|
@ -791,6 +792,7 @@
|
|||
<td data-order="[% suggestions_loo.suggesteddate | html %]">
|
||||
[% IF ( suggestions_loo.suggesteddate ) %][% suggestions_loo.suggesteddate | $KohaDates %][% END %]
|
||||
</td>
|
||||
<td>[% AuthorisedValues.GetByCode( 'OPAC_SUG', suggestions_loo.patronreason ) | html %]</td>
|
||||
<td>
|
||||
<a href="/cgi-bin/koha/members/moremember.pl?borrowernumber=[% suggestions_loo.managedby | uri %]">[% suggestions_loo.surnamemanagedby | html %][% IF ( suggestions_loo.firstnamemanagedby ) %], [% suggestions_loo.firstnamemanagedby | html %][% END %]</a>
|
||||
</td>
|
||||
|
|
|
|||
Loading…
Reference in New Issue