Hi Galen, Thank you again. It just so happens that my consortium is SPARK, the very one you used as your example below. They are cool with local variation so we will be able to implement this solution.
Scott -----Original Message----- From: Open-ils-general [mailto:[email protected]] On Behalf Of Galen Charlton Sent: Wednesday, February 11, 2015 10:00 AM To: Evergreen Discussion Group Subject: Re: [OPEN-ILS-GENERAL] TPAC and Due Date Hi Scott, On Wed, Feb 11, 2015 at 8:57 AM, Scott Thomas <[email protected]> wrote: > Thank you for replying. We are in a consortium and other members > may not want to hide the due date. My assumption is that OPAC > templates can be customized for each individual library in a > consortium. Is this assumption correct? I am new to EG and still trying to > figure out how all of this fits together. Yes, it is possible. For example, compare https://ashland.sparkpa.org/eg/opac/home and https://york.sparkpa.org/eg/opac/home That said, various Evergreen consortia have different policies regarding the degree to which member libraries' OPACs are allowed to vary -- for example, some place a high value on providing a consistent experience for all patrons of a resource-sharing group -- so there can be a difference between what is technically possible and what fits within a consortium's policies. Regards, Galen -- Galen Charlton Manager of Implementation Equinox Software, Inc. / The Open Source Experts email: [email protected] direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web: http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org & http://evergreen-ils.org
