[OPEN-ILS-DEV] Evergreen 2.2 RC1 fresh install questions

[Lazar, Alexey Vladimirovich]

> We noted several of those "missing" features during our review but did not consider them to be serious deal-breakers against adopting Tpac.  As far as "stable and well tested" though, my opinion is that it should definitely fulfill the intended replacement for the simple catalog.  But I think each Evergreen site will need to evaluate carefully for themselves whether Tpac is good enough to fit their needs now or wait longer before adopting it.


Thanks, Ben, your answer helped inform our discussion.  We decided to go with the new TPAC by default, since that's where things are headed anyway.  We all seemed to agree that the interface and features fulfill the needs at this time.  Since this library is migrating to Evergreen for the first time, we might as well get them started in the right direction, rather then with an option nearing end of life.

Alexey Lazar
PALS
Information System Developer and Integrator
507-389-2907
http://www.mnpals.org/

On May 24, 2012, at 09:03 , Ben Shum wrote:

> For 2.2, the goal was to replace the original slimpac (simple OPAC) with Tpac and it is there now as the simple catalog.  However, there is still ongoing work to further enhance and refine various aspects and add features to Tpac before it will fully replace the JSPac.  The projected time table discussed in previous developer meetings assumed that Tpac would become the default by the next Evergreen release 2.3 with JSPac being removed by the next release after that.
> 
> That said, Bibliomation upgraded to using Tpac as our only catalog in production back in early April.  Overall, patron response has been very positive.  The interface is significantly faster than previous catalogs and has a cleaner look and feel to it.  We have continually worked with other members of the Evergreen Community to test and adjust our Tpac as new bugs are identified and fixed or new development work is ready for testing.
> 
> Some pending features for Tpac (so far) are listed on this wiki page: http://evergreen-ils.org/dokuwiki/doku.php?id=dev:opac:template-toolkit:plan
> 
> We noted several of those "missing" features during our review but did not consider them to be serious deal-breakers against adopting Tpac.  As far as "stable and well tested" though, my opinion is that it should definitely fulfill the intended replacement for the simple catalog.  But I think each Evergreen site will need to evaluate carefully for themselves whether Tpac is good enough to fit their needs now or wait longer before adopting it.
> 
> -- Ben
> 
> On 5/24/2012 9:27 AM, Lazar, Alexey Vladimirovich wrote:
>>> In the Evergreen 2.2 RC1 I just installed, how do I enable TPAC by default?  Would that be a good idea at this point, or is it too early?
>> To clarify my own words, is TPAC stable and tested well enough for a production environment?
>> 
>> Alexey Lazar
>> PALS
>> Information System Developer and Integrator
>> 507-389-2907
>> http://www.mnpals.org/
>> 
>> On May 23, 2012, at 17:04 , Lazar, Alexey Vladimirovich wrote:
>> 
>>> In the Evergreen 2.2 RC1 I just installed, how do I enable TPAC by default?  Would that be a good idea at this point, or is it too early?
>>> 
>>> When the final Evergreen 2.2 comes out, what will be the update path from 2.2 RC1 to 2.2 final?
>>> 
>>> Also, what will be the update path from OpenSRF 2.1 RC1 to 2.1 final?
>>> 
>>> Thanks.
>>> 
>>> Alexey Lazar
>>> PALS
>>> Information System Developer and Integrator
>>> 507-389-2907
>>> http://www.mnpals.org/
>>> 
>> 
> 
> -- 
> Benjamin Shum
> Open Source Software Coordinator
> Bibliomation, Inc.
> 32 Crest Road
> Middlebury, CT 06762
> 203-577-4070, ext. 113
>