Very cool! thank you so much! Would you mind if I create a evg_opensrf.inc file and move the definitions into it? That would help me get a better view of the drupal hooks without being overwelmed by the EG ASI right off the bat.
I would also like to volunteer to work on the naming of the containing folder, and module functions such that they all match the module name a little closer. Do I understand that your Drupal link is the actor.usr.id == drupal.users.uid? Is that correct? Is there any danger of this link being broken from the Evergreen side beyond Drupal's control? For instance, in the case where the EG user is deleted/blocked via the staff client in Evergreen what is the Drupal experience? Thanks, Steve Wills P.S. Should this discussion be moved off General list? -----Original Message----- From: Bob Wicksall [mailto:bwicks...@pls-net.org] Sent: Monday, March 26, 2012 10:17 AM To: 'Evergreen Discussion Group' Subject: Re: [OPEN-ILS-GENERAL] ***SPAM*** Re: To Create a PHP client for OpenSRF and Evergreen None of my modules are on Drupal.org. It's a combination of incomplete modules and a lack of time. You can get them here: http://www.pls-net.org/projectsBob WicksallSystems AdministratorPioneer Library System2557 State Rt. 21Canandaigua, New York 14424Voice: (585) 394-8260Fax: (585) 394-1935----- Original Message -----> From: "Justin Hopkins" > To: "Evergreen Discussion Group" > Sent: Sunday, March 25, 2012 12:03:58 PM> Subject: Re: [OPEN-ILS-GENERAL] ***SPAM*** Re: To Create a PHP client for OpenSRF and Evergreen> > Good work Bob! I'd love to meet up at the conference and talk more> about this. I can't find your code on Drupal.org - is it available> for> download anywhere?> > Regards,> Justin Hopkins> Coordinator, IT & Web Services> MOBIUS Consortium Office> c: 573-808-2309> > --sent from a mobile device--> > On Mar 24, 2012, at 9:22 PM, Bob Wicksall > wrote:> > > I'd be interested in a PHP-EG group and I'll be at the conference.> >> > I've built 3 Drupal modules that interface with Evergreen. I have> > a basic OpenSRF module that communicates with Evergreen, an> > authentication module and a catalog module. The opensrf and> > authentication modules are pretty clean but the catalog module is> > a big wad of code right now.> >> > I've got some working fieldmapper code that can map the fields as> > well as create objects that are required by some requests. I'm> > pulling the fieldmapper structures directly over opensrf and> > caching them locally.> >> > You can see it in action here:> >> > http://www.e5i5o.com/catalog> >> > Mobile theme (android and iOS) here:> >> > http://mobile.e5i5o.com/catalog> >> > The site is a little sluggish sometimes because it's on a home> > server connecting to a slow Evergreen test server.> >> >> > Bob Wicksall> > Systems Administrator> >> > Pioneer Library System> > 2557 State Rt. 21> > Canandaigua, New York 14424> >> >> > ----- Original Message -----> >> From: "Steve Wills" > >> To: "Evergreen Discussion Group"> >> > >> Sent: Saturday, March 24, 2012 6:12:49 PM> >> Subject: [OPEN-ILS-GENERAL] ***SPAM*** Re: To Create a PHP client> >> for OpenSRF and Evergreen> >>> >>> >> 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.bu...@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" < vrnd...@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> >>>
