This sounds amazing, but how does one find the settings related to a print template (all of ours are workstation settings now) so that one can make them a user setting or an org setting instead?
Benjamin Kalish Forbes Library / 413-587-1012 / bkal...@forbeslibrary.org Support Forbes Library: - Consider giving a gift <http://www.forbeslibrary.org/giving> to Forbes Library - Vote for the Friends of Forbes in the Florence Bank Community Grant Program <https://www.florencebank.com/vote>. - Join the Friends the Forbes today <https://forbeslibrary.org/friends/>! Currently reading: *The Indian Clerk* by David Leavitt Just Finished:* The Tombs of Atuan* by Ursula K. Le Guin For information about accessibility at the library, please see: http://forbeslibrary.org/accessibility/ On Tue, Sep 10, 2019 at 11:57 AM Josh Stompro <stomp...@gsuite.larl.org> wrote: > Morgan, thank you for this info. I totally missed the connection to print > templates when I read that message the first time around, and I don't think > I'm the only one. When Bill posted his message about the server side > processed print templates in April 2019 > <http://libmail.georgialibraries.org/pipermail/open-ils-dev/2019-April/010709.html>, > I commented (along with a few other people) that it would be great to have > a way to centrally manage print templates, not realizing that had been > added 8 months earlier. > > I started a bug report with notes on documenting this behavior in the > print templates section. > https://bugs.launchpad.net/evergreen/+bug/1843454 > > Josh > > On Mon, Sep 9, 2019 at 3:26 PM Morgan, Michele <mmor...@noblenet.org> > wrote: > >> Hi Josh, >> >> Since moving to 3.2 where workstation settings were moved to the server, >> we've been making use of org unit settings to set default print templates. >> Any workstation setting can be turned into an org unit setting as Bill >> Erickson described here: >> >> https://markmail.org/message/hfaogumstphagscy >> >> We have set a number of default print templates at the consortium org >> unit level as consortium defaults, and upon request of a library, have >> copied print templates configured on a given workstation into org unit >> settings for that library so they don't need to be set on each workstation. >> We've left the workstation setting types so that individual workstations >> can override the org unit settings when necessary. >> >> This has been pretty successful, eliminating the need for library staff >> to move them from workstation to workstation on a flash drive. >> >> We've done this for many column settings as well. >> >> Hope this is helpful. >> Michele >> -- >> Michele M. Morgan, Technical Support Analyst >> North of Boston Library Exchange, Danvers Massachusetts >> mmor...@noblenet.org >> >> >> >> On Mon, Sep 9, 2019 at 2:25 PM Josh Stompro <stomp...@gsuite.larl.org> >> wrote: >> >>> Hello, I just want to make sure I have this correct while planning our >>> upgrade to 3.3 >>> >>> If I want to set global printer templates in the staff client in 3.3.3 I >>> can modify the templates at >>> /openils/var/templates/staff/share/print_templates/ >>> or if I have alternate TT2 template locations >>> (/openils/var/templates_shared/) I can update them there. >>> >>> If I need to set per location defaults for the print templates, I'll >>> need to enter data per workstation into actor.workstation_setting. >>> >>> In 3.4 there will be an admin gui for updating the print templates per >>> org unit and locale. >>> https://bugs.launchpad.net/evergreen/+bug/1825851 >>> >>> Thanks >>> -- >>> Josh Stompro - IT Director >>> Lake Agassiz Regional Library >>> Desk: 218-233-3757 Ext 139 >>> Cell: 218-790-2110 >>> >> > > -- > Josh Stompro - IT Director > Lake Agassiz Regional Library > Desk: 218-233-3757 Ext 139 > Cell: 218-790-2110 >