[OPEN-ILS-GENERAL] Evergreen Community Survey

[Rogan Hamby]

Hi Ben,

We talked about this a little in IRC but I'll go over some of the same
stuff if you don't mind, for the sake of anyone reading along.  :)

You're correct in that the community survey at this point doesn't cover the
entire community.  It excludes independent developers (like Ken Cox working
on the android app), support companies (like ESI) and other types of
entities I'm surely forgetting.  However, it's also our first year.

There was a deliberate intention in it's design to stay as simple as
possible.  While the community is more than the libraries using Evergreen I
don't think it's unfair to say that Evergreen is literally here for them.
In future years we do want to expand the survey both in breadth and depth.
Right now I can't say what those future versions will look like but nothing
so far as been without intent or thought for the future.

We want to learn from this one and we want to get it off the ground.  It
will be the first of an annual survey.  When that time comes for the second
annual survey a challenge will be in trying to keep it concise and direct
enough to encourage as many respondents as we can.  We hope we erred on the
side of ease of access this year for libraries responding to it.

This isn't to say that we won't include other sources of data in our final
products.  Git will give us a great deal of information about development.
We will look at our wonderful documentation community.  We will cast our
eyes everywhere we think to.  I have folders of content that Kathy has been
gathering in that vein to look at when I have some time.  (probably this
weekend)

On Fri, Apr 1, 2016 at 1:09 PM, Ben Shum <ben at evergreener.net> wrote:

> Hi Rogan,
>
> I'm curious what the Evergreen Outreach Committee has discussed
> regarding how this data is to be used.  Given that the linked survey
> appears to be very user focused at the moment, i.e. most if not all
> the questions are geared with the mindset that it applies to library
> institutions or groups who use Evergreen.  But what about the rest of
> the community?
>
> I wonder if it would be helpful to clarify the intent of this survey
> as targeting the Evergreen Community's users?  And whether there would
> be separate surveys or approaches used similarly to gauge (and maybe
> identify) other aspects of our community.  Off the top of my head, I
> would like to see representation in any final picture of our community
> to include also developers, individuals and companies alike, along
> with the various support organizations that participate in Evergreen's
> deployment and ongoing maintenance.  Documentation, translation, etc.?
>
> Just what I was thinking.
>
> Regards,
>
> -- Ben
>
> On Fri, Apr 1, 2016 at 12:13 PM, Rogan Hamby <rhamby at esilibrary.com>
> wrote:
> > The Evergreen Outreach Committee is asking anyone who can to respond to
> the
> > first annual community survey.  If you are a member of a consortium we
> only
> > need one response for the entire consortium.
> >
> > The information is for an annual report that we will present at the
> > conference each year.  Additionally, the information will help us have a
> > better image of the community as a whole.  We will also use it to create
> > materials aimed at creating an accurate picture of our community.
> >
> > We have kept the survey short and simple and should only take a few
> moments.
> > Thank you in advance.
> >
> > The survey can be accessed here:  https://www.surveymonkey.com/r/5MZWBYY
> >
> > --------------------------------------------------------------
> > Rogan R. Hamby, Data and Project Analyst
> > Equinox - Open Your Library
> > rogan at esilibrary.com
> > 1-877-OPEN-ILS | www.esilibrary.com
> >
>



-- 
--------------------------------------------------------------
Rogan R. Hamby, Data and Project Analyst
Equinox - Open Your Library
rogan at esilibrary.com
1-877-OPEN-ILS | www.esilibrary.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://libmail.georgialibraries.org/pipermail/open-ils-general/attachments/20160401/20bfc962/attachment-0001.html>