[evergreen-outreach] scheduling the virtual conference

[Andrea Buntz Neiman]

Here's my yeses so far, including their original audience level and tracks
(note that I only included primary contact, and not all presenters, though
I do have that info):

Rogan Hamby Making it Rain : How To Talk About Open Source Value Novice
General
Rogan Hamby Herding (Bibliographic) Cats: A Mass Cleanup of Fixed Field
Data Intermediate End User
Lynn Floyd AsciiDoc, let's get started Novice General
Andrea Buntz Neiman But wait! There’s more: New feature highlight for 3.4
and 3.5 Novice General
Andrea Buntz Neiman How to write requirements, or, You can’t always get
what you want, but you can get close Intermediate Management / Leadership
Michele Morgan If This Then That: Action Triggers are More Than Just Notices
Intermediate General
J. Sara Paulk Reports that will help your patrons now Novice End User
Elizabeth McKinney Consortium Leaders Roundtable Roundtable / IG
Terran McCanna OPAC Usability Study Results Novice General
Terran McCanna Batch Creation of Student Cards
Novice
General
Benjamin Murphy Rethinking Patron and Staff Permission Groups in NC Cardinal
Intermediate General
Chris Sharp Understanding Evergreen Reports Preconf
Galen Charlton Making Perl work for you in Evergreen Preconf
Rogan Hamby Working with MARC Records in Perl Preconf
Terran McCanna Evergreen Self-Check Round Table Roundtable / IG
Chris Sharp SysAdmin Interest Group Roundtable / IG
John Rempel Keynote Keynote

On Wed, Apr 8, 2020 at 11:11 AM Andrea Buntz Neiman <
abneiman at equinoxinitiative.org> wrote:

> So, we have 17 presentations so far including the keynote & some interest
> groups (and an 18th if you want to do the SQL one, Rogan). There are 10
> presentations and a handful of interest groups that I'm still awaiting
> yes/no answers from.
>
> I think we'd almost have to go with 3 days, unless we're going to run some
> concurrently. Are we open to the idea of doing tracks or groupings? Like,
> "here's three presentations about reports" or whatever.
>
> On Wed, Apr 8, 2020 at 10:52 AM <rogan.hamby at gmail.com> wrote:
>
>> A quick (and modest) proposal.*
>>
>> Since we should have a pretty good idea soon of the number of programs
>> that people are willing to migrate from the original conference to the
>> virtual one that will give us a good idea of how many days to plan for.
>> Once we have that I think we need to pick possible dates in late May or
>> June and get a poll out as soon as possible. This may affect the proposals
>> potentially. For example, there is one week in June that would make it
>> nearly impossible for me to present.
>>
>> Do we think we're looking at two or three days?  Are we still leaning
>> towards the end of weeks as we have done with the in-person conference?  If
>> so I propose once we decide on 2 or 3 days we grab the Thurs/Fridays or
>> Wed/Thursday/Fridays for the last week of May and all of June and get
>> feedback from presenters about where they would have issues presenting due
>> to other time commitments, perhaps in the form of a poll.  After that poll
>> the wider community once we know the dates that work fo presenters.
>>
>>
>>
>>
>>
>>
>> * With apologies to Jonathan Swift.
>>
>> _______________________________________________
>> evergreen-outreach mailing list
>> evergreen-outreach at list.evergreen-ils.org
>> http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-outreach
>>
>
>
> --
> Andrea Buntz Neiman
> Project Manager for Software Development
> Equinox Open Library Initiative
> abneiman at equinoxinitiative.org
> 1-877-OPEN-ILS (673-6457) x5583
> *www.equinoxinitiative.org <http://www.equinoxinitiative.org>*
>


-- 
Andrea Buntz Neiman
Project Manager for Software Development
Equinox Open Library Initiative
abneiman at equinoxinitiative.org
1-877-OPEN-ILS (673-6457) x5583
*www.equinoxinitiative.org <http://www.equinoxinitiative.org>*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.evergreen-ils.org/pipermail/evergreen-outreach/attachments/20200408/60409681/attachment-0001.html>