LISTSERV mailing list manager LISTSERV 16.5

Help for CODE4LIB Archives


CODE4LIB Archives

CODE4LIB Archives


CODE4LIB@LISTS.CLIR.ORG


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Monospaced Font

LISTSERV Archives

LISTSERV Archives

CODE4LIB Home

CODE4LIB Home

CODE4LIB  December 2011

CODE4LIB December 2011

Subject:

Re: Obvious answer to registration limitations

From:

Shaun Ellis <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Thu, 22 Dec 2011 11:52:05 -0500

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (139 lines)

I agree that the discussion should focus on ways of adapting the
conference to serve the expanding community without losing the good
qualities that come from keeping it small. This is the future, so the
community is only going to get bigger.

Perhaps coordinating a different regional meetup every 3 or 4 months is
not a bad idea. This way, there are more options in terms of timing, it
can stay small, and folks at orgs with smaller budgets can justify the
lower travel costs to their managers. Of course, registration would not
be closed to participants outside the region. And yes, streaming should
be a priority [...signs up for video streaming/archiving team].

Presentations for each conference could even be grouped to loosely focus
on certain areas of the domain -- which would draw a concentration of
those interested in certain domain issues/software. One of the main
draws for me to Access this year was the focus on Open Data.

-Shaun


On 12/22/11 11:25 AM, Michael North wrote:
> I have followed this discussion with great interest and have only one comment....."watch out for the slippery slope."
>
> There will be "unintended consequences" whenever you try to ensure a "just" registration system, be it by controlling "randomness" or by "qualifying" the participants. Where do you stop!
>
> In the spirit of collaboration and openness, instead of focusing on how to control the 250 registration slots, we should focus on how to make it available to more people (be it by size increase or by video streaming, etc). True openness and fairness for registration will mean that some people will always not be able to attend, and setting up registration "justice" will not fix that.... approximately 150+ people (and more in the future) will not be able to attend no matter what. And if there is no solution to increasing participation, then so be it. It stays the same size, and registration opens at the advertised time (everyone will know when that is) and close when full. Everyone will know that....and make their plans accordingly.
>
> I think of it like the Oklahoma Land Rush, or getting your plane reservations for Christmas. Some get in, some do not, and each person is responsible only to himself for doing it "in time."
>
> This is from a person who is coming for the first time following two failed attempts to attend in previous years.
> My humble opinion only.
> Michael North
>
>
>
>
> -----Original Message-----
> From: Code for Libraries [mailto:[log in to unmask]] On Behalf Of Reese, Terry
> Sent: Thursday, December 22, 2011 9:46 AM
> To: [log in to unmask]
> Subject: Re: [CODE4LIB] Obvious answer to registration limitations
>
> I find it hard not to laugh a little bit at this ongoing discussion because it is so uniquely part of this community. On the one hand, you have some very creative people that think that they see a problem and want to fix it. On the other, people are spinning their wheels, throwing out the crazies solutions trying to solve a problem that we as the community have created ourselves. It makes me smile because it really does personify both the strengths and weakness of this community. I think people like this group because there certainly isn't a lack of ideas or people willing to spend time and energy on them. When we put that energy towards coding and solving problems in libraries -- good things happen (as well as some crazy things). However, there are those times when it feels like things go off the rails and to me, this is one of them.
>
> The conference is a nice event. It's something I know a lot of us enjoy because it’s a time to get together with colleagues and find out what people are working on. One of the reasons it works is because of its size. It's one of the few conferences where I get the opportunity to meet most of the attendees and get to have significant conversations around some very cool projects. But it's certainly not the only place where this happens.
>
> And with all that said, I can't help but make one suggestion to help add some diversity to the registration process. I've not looked at the list fully to see who is attending, but I think you'd find that some institutions are sending large contingencies to the conference (and I can't toss stones, because Oregon State is one of them). A simple solution would be to limit registrations per institution, much the same way CNI does. My guess is that if registration per institution was capped, at least during the early registration period, you'd find that a much more diverse audience could attend.
>
> --TR
>
> ***************************
> Terry Reese, Associate Professor
> Gray Family Chair for
> Innovative Library Services
> 121 Valley Library
> Corvallis, OR 97331
> tel: 541.737.6384
> ***************************
>
>
>
> -----Original Message-----
> From: Code for Libraries [mailto:[log in to unmask]] On Behalf Of Brett Bonfield
> Sent: Thursday, December 22, 2011 7:27 AM
> To: [log in to unmask]
> Subject: Re: [CODE4LIB] Obvious answer to registration limitations
>
> Seems like a hybrid system might make sense.
>
> Reserve spots for presenters and scholarship winners, and decide on both before registration opens. I'm sure it's difficult to coordinate voting for presenters, and I know from having volunteered on the scholarship committee that it would be difficult to complete that process in time. But I think it would be worth it.
>
> I think it also makes sense to reserve spots for some number of volunteers. I think this would help with continuity, help to preserve the idea that everyone is a participant, reward people who put in considerable time, and also encourage more people to volunteer for the more time-consuming jobs. As with presenters, volunteers would have to pay for registration and their reserved spots would be non-transferable. Code4lib could vote on which volunteer positions guarantee the option to attend the conference.
>
> I think the rest of the open spots could be divided between first-come-first-served and a lottery system (50/50? 60/40?). The people who are sitting at their computers the moment registration opens would still get in, and the people who didn't know that was required -- the newer folks whose participation is necessary for code4lib to stay relevant -- would have a reasonable chance to see, in person, what code4lib is all about.
>
> Brett
>
> Brett Bonfield
> Director
> Collingswood Public Library
>
> On Thu, Dec 22, 2011 at 9:50 AM, Edward M. Corrado<[log in to unmask]> wrote:
>> I disagree about the random registration concept. As long as the time
>> is announced in advance (which was done this year) people should plan
>> accordingly. You didn't need to register the first minute this year. I
>> registered an hour after registration opened and while I was initially
>> on the waiting list, I eventually got a slot. If I ended up getting
>> locked out it would've been my own fault. I could have done what
>> others did and purposely avoided scheduling meetings around that time
>> and rescheduled the one that was but I didn't. Yes, I have bazillions
>> of other things to do and the registration time wasn't convenient for
>> me, but everyone else has bazillions of things to do as well. It would
>> not have been luck that got the people in who registered before me a
>> slot - it would have been a combination of their good planning and my
>> poor planning. Yes good people miss out when registration fills up and
>> maybe the library world suffers, but a random process would still have
>> good people miss out -- including those who would make the effort and
>> adjust there schedules accordingly -- which I think would lead to the
>> library world suffering more.
>>
>> Edward
>>
>> On Wed, Dec 21, 2011 at 8:00 PM, Karen Schneider<[log in to unmask]> wrote:
>>> I was really hoping that our Associate Director for Library
>>> Technology could attend Code4Lib. She did her best, but didn't make
>>> it. She was then pushed hard, early on, to drop her hotel room, which
>>> she did not do (good for her) though I'm guessing she has by now.
>>> We're a 5-person library and it's amazing to have someone with her
>>> expertise (IT tried to steal her before I arrived, but I took her
>>> back), and we wouldn't be what we were without her. I felt I owed her
>>> Code4Lib, but busy with my own distractions I hadn't been on this
>>> list for a long time, and didn't tune in to the fact that
>>> registration for C4L has become so nutzo that either she or her proxy
>>> needed to be sitting on the reg process the very minute it opened,
>>> not a few minutes later. She was probably doing one of the 8
>>> bazillion things she does every long day that help keep us going and differentiate us from all the other teeny-weeny uni libraries out there.
>>>
>>> The library world will be a little less than what it could be because
>>> she's not at Code4Lib.
>>>
>>> My idea: registration should open for two weeks, close, and then
>>> assign spots randomly (and if it's too hard to think how that might
>>> be done, I have a few thousand old catalog cards you can toss in a bucket).
>>>
>>> FYI, I know what zoia is, and I even know WHO the real Zoia is, but
>>> invoking that super-secret-stuff is just icky. Maybe she doesn't need
>>> your super-secret decoder rings anyway. She does want to stretch
>>> herself beyond what we can make possible. We'll keep looking.
>>>
>>> Karen G. Schneider
>>> Director for Library Services
>>> Holy Names University
>>> http://library.hnu.edu

--
Shaun D. Ellis
Digital Library Interface Developer
Firestone Library, Princeton University
voice: 609.258.1698 | [log in to unmask]

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

October 2024
September 2024
August 2024
July 2024
June 2024
May 2024
April 2024
March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003

ATOM RSS1 RSS2



LISTS.CLIR.ORG

CataList Email List Search Powered by the LISTSERV Email List Manager