[OPEN-ILS-DEV] Server-side OPAC development project: an introduction

[James Fournie]

Hi Bill,

Just to ask a question probably other people are asking -- could you
elaborate on what the SVF infrastructure is for and how it will work?

Will the new TT OPAC be used in the staff client as well?

~James Fournie
BC SITKA

On Wed, Mar 9, 2011 at 7:06 AM, Bill Erickson <erickson at esilibrary.com> wrote:
>
> Hi all,
> Thanks for the testing and words of encouragement!
> Installing over Evergreen 2.0 requires additional undocumented changes.
>  (From memory, oils_auth.c, Actor.pm, Circ/Holds.pm, Circ/Money.pm, and
> Utils/CStoreEditor.pm, plus service restarts).  For now, you can still do
> basic searching without these changes, but in a week or two, the template
> code will start using the new (recently merged to trunk/2.1) SVF
> infrastructure, which means 2.0 will be unusable as a baseline install.
> For those not accustomed to Git, I added a note in the how-to about keeping
> a local checkout up to date.
> When and how these changes may be merged into Evergreen will require
> community discussion and planning.  Our (Equinox's) goal is to have a
> drop-in replacement for the KCLS skin this summer.  Along the way, for the
> code to be generally usable by the community, it will be necessary to
> extract the KCLS-isms (i.e. break the templates up into chunks that can be
> locally overlayed) from the skin and replace them with reasonable Evergreen
> defaults.  This process is where community input and assistance will be
> needed.  ESI will help queue this up, but we need the community to act as
> the final arbiter of function and style for the default skin.
> -b
>
> On Wed, Mar 9, 2011 at 2:35 AM, Dan Scott <dan at coffeecode.net> wrote:
>>
>> On 8 March 2011 21:15, Ben Shum <bshum at biblio.org> wrote:
>> > For fun I tried those steps outlined with a test box running Squeeze and
>> > Evergreen 2.0.1 and pointing at a copy of our 2.0 database.  Overall the
>> > steps worked quite flawlessly, though I did have to use a slightly
>> > different
>> > path directory for the OpenILS/WWW contents than what was given on the
>> > page.
>> >
>> > For me, I ended up copying that material to
>> > /openils/lib/perl5/OpenILS/WWW
>>
>> The path Bill gave (potentially adjusted for distribution-specific
>> locations of Perl modules) is required for Evergreen 2.1 and up. As of
>> Evergreen 2.1, the Evergreen Perl modules are installed as standard
>> Perl modules, rather than in a non-standard path that requires
>> PERL5LIB path munging.
>>
>> Note that if you upgrade a machine from Evergreen 2.0 to 2.1, you will
>> want to "rm -fr /openils/lib/perl5" to avoid having the old 2.0
>> modules get loaded instead of your shiny new 2.1 modules. For those
>> who made the jump from OpenSRF 1.0 to 1.2 or 1.6, a similar step was
>> required at that time
>
>
>
> --
> Bill Erickson
> | VP, Software Development & Integration
> | Equinox Software, Inc. / Your Library's Guide to Open Source
> | phone: 877-OPEN-ILS (673-6457)
> | email: erickson at esilibrary.com
> | web: http://esilibrary.com
>