[Eg-oversight-board] Call for agenda items - 21.08.14 meeting

[Grace Dunbar]

Thanks for mentioning the vendor listing, Rogan, as I have a piece of
business that serendipitously feeds into that.
The lovely folks in Granville, NC had a very challenging time with an
Evergreen vendor.  The people at Greenville were so upset at the poor
service they feel that they received that they wrote a letter of complaint.
 They delivered that to me, as a member of the EOB, and have asked that we
consider removing this vendor from the vendor listing page.
Please see their letter of complaint, which is attached.

I know that this is a challenging issue.  We don't want to be put in the
position of policing vendors or getting caught in disputes between vendors
and their clients.  However, I also feel some responsibility comes from
even having the vendor page.  The question foremost in my mind is whether
we should be proactive or reactive (or inactive) in this kind of situation.
 In other words, should we change the vendor listing policy to ask for
references from live Evergreen sites who are serviced by that vendor prior
to listing them?  Or should we take on the role of possibly removing a
vendor if it becomes clear they have caused "irreparable" harm to a client.
 'Irreparable harm' being data loss, excessive downtime, or something
fairly serious.  Or do we see our role in the EOB as not being responsible
for ensuring that the community is pointing potential Evergreen sites at
vendors who are capable of doing the work - caveat emptor.

There are, of course, many sides to this issue.  I look forward to the
discussion!
Grace

p.s. In the interest of full disclosure, Granville contracted with Equinox
earlier this year to fix many of their lingering issues.  It was a limited
term consulting contract that is no longer in effect.


On Mon, Aug 18, 2014 at 1:23 PM, Rogan Hamby <rogan.hamby at gmail.com> wrote:

> I wanted to chat about the Evergreen vendor listing.  It's been a year
> since we adopted the current policy and there's been discussion about it a
> couple of times.  I've always said we should wait a year before we
> entertained any discussion of change and it's been that year now.  One
> minor thing that I'd like to do is require that we link to the description
> of Evergreen services on an entry.
>
>
>
>
> On Mon, Aug 18, 2014 at 12:40 PM, Ben Hyman <ben.hyman at bc.libraries.coop>
> wrote:
>
>> Hi all,
>>
>> We have an EOB meeting scheduled for this Thursday, the 21st @ 11 Pacific.
>> Please send any agenda items along, and I'll pull things together by the
>> 20th.
>>
>> All the best
>> Ben
>>
>> Ben Hyman
>> Executive Director | BC Libraries Cooperative
>> ben.hyman at bc.libraries.coop | 1.855.383.5761 ext 1001 | cell:
>> 250.889.2738
>> bc.libraries.coop | Twitter: @BCLibrariesCoop
>> _______________________________________________
>> eg-oversight-board mailing list
>> eg-oversight-board at list.evergreen-ils.org
>> http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/eg-oversight-board
>>
>
>
> _______________________________________________
> eg-oversight-board mailing list
> eg-oversight-board at list.evergreen-ils.org
> http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/eg-oversight-board
>
>


-- 
Grace Dunbar, Vice President
Equinox Software, Inc.  -  The Open Source Experts
gdunbar at esilibrary.com
1-877-OPEN-ILS    www.esilibrary.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.evergreen-ils.org/pipermail/eg-oversight-board/attachments/20140818/8d1f9963/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: approved memo to Evergreen oversite committee.doc
Type: application/msword
Size: 41472 bytes
Desc: not available
URL: <http://list.evergreen-ils.org/pipermail/eg-oversight-board/attachments/20140818/8d1f9963/attachment-0001.doc>