[OPEN-ILS-GENERAL] ***SPAM*** Re: To Create a PHP client for OpenSRF and Evergreen

[David Busby]

I guess now is as good as time as any to bring this up; a little
project I've been working on:"Sap".  The goal is to create a PHP
web-ui that allows for catalogue search, placing a hold and/or doing a
checkout.  I've got the system sort of broken into basic MVC pieces.
An osrf http interface and also some oils objects; some even work with
the fieldmapper xml files - hooray!  It's mostly been a project to
help me learn some guts of Evergreen. Sounds like there is more
interest in this than I thought there would be so I'm thinking I
should get these libraries posted on to githug

I'm +1 to the group idea, will post this code and update wiki.

Very eager to here what others think.


--
David Busby
Edoceo, Inc.
http://edoceo.com/
206.282.6500



On Sat, Mar 24, 2012 at 3:12 PM, Steve Wills <swills at beyond-print.com> wrote:
> I hope that an appearance of difficulty interfacing Evergreen to a PHP
> front-end doesn't stop your exploration.   My understanding is that our lack
> of PHP solutions is a direct result of a lack of contributions.  While I
> have not been able to find the time to implement a PHP solution personally,
> I work on a PHP platform of equal complexity and identical underlying
> technologies for the CIO council at CIO.com, full time. I frequently solve
> small Evergreen problems for the Balsam Consortium in Maine using PHP 'one
> offs' and I share David's pain in climbing the Evergreen API learning curve.
>   Between the wiki and the work DIG has done over the past couple of years
> this effort will continue to get easier.
>
> Perhaps the task can be made less daunting by narrowing the scope?   For
> instance, rather than completely replacing the staff client, why not make a
> simple PHP "toolbox" with limited capability?   One could start with
> something like a circ-mod editor that didn't rely on the Ajax for it's
> dynamic table builds.   In general, my biggest complaint with the staff
> client is the way dojo draws and manages the table views in the various
> admin editors.
>
>
> The opportunities to interface with Drupal, Wordpress, VuFind and the like
> are quite exciting.  I am happy to consult with others who are interested in
> bringing their PHP solutions forward into the community?  How about forming
> a PHP-EG group?  Look for me at Evergreen 2012 if you wish to discuss a PHP
> interest group further.
>
> Steve Wills
>
> -----Original Message-----
> From: David Busby [mailto:david.busby at edoceo.com]
> Sent: Saturday, March 24, 2012 05:40 PM
> To: 'Evergreen Discussion Group'
> Subject: Re: [OPEN-ILS-GENERAL] To Create a PHP client for OpenSRF and
> Evergreen
>
> My biggest hurdle with building a PHP based front end (on osrf-translayor)
> has been the object/field  mapping.  And folowjng that was undetstaning the
> 100s of API calls.
>
> I think others would also point to the considerable amount of code that
> needs to be 4created in order to just provide basic auth and search
> functionality.  And access controls as well have been rather difficult.
>
> /djb
> http://edoceo.com
> 206.282.6500
>
> On Mar 24, 2012 4:49 AM, "Virendra Kumar" <vrndrkr at gmail.com> wrote:
>>
>> Hi
>> I am Virendra Kumar. I have some doubts as follows:-
>> Why Evergreen has not been integrated  with popular frameworks such as
>> Drupal and Wordpress, as well as with library-specific applications
>> such as VuFind??
>> what problems you face while integrating Evergreen with frameworks
>> such as Drupal and Wordpress ???
>> could anybody help me to undersatnd what will be basic problem to
>> integrate Evergreen with other Popular frameworks
>> like Drupal and Wordpress ??
>>
>>
>> Thanks,
>> Virendra kumar