cbeer++
wickr++

:-D

On Thu, May 11, 2017 at 3:45 PM, Jason Bengtson <[log in to unmask]>
wrote:

> Thank you very much! This is terrific!
>
> Best regards,
>
> *Jason Bengtson*
>
>
> *http://www.jasonbengtson.com/ <http://www.jasonbengtson.com/>*
>
> On Thu, May 11, 2017 at 3:36 PM, Cynthia Ng <[log in to unmask]> wrote:
>
> > All I can do is second that. Thank you _so_ very much for your (read
> > everyone who contributed) hard work on this!
> >
> > -Arty
> >
> > -----Original Message-----
> > From: Code for Libraries [mailto:[log in to unmask]] On Behalf Of
> > Bess Sadler
> > Sent: Thursday, May 11, 2017 9:44 AM
> > To: [log in to unmask]
> > Subject: Re: [CODE4LIB] jobs.code4lib.org relaunched
> >
> > Hooray!! This board is such a great service to the community. Thank you,
> > Chris.
> >
> > Bess
> >
> > > On May 11, 2017, at 11:02 AM, Chris Beer <[log in to unmask]> wrote:
> > >
> > > Hi all,
> > >
> > > Yesterday (with help from Ryan Wick) I relaunched a brand new,
> > completely rewritten https://jobs.code4lib.org <
> https://jobs.code4lib.org/>
> > with the full job posting history from shortimer and job postings to this
> > list. As before, messages to CODE4LIB-L are aggregated and presented in
> the
> > application (after a quick moderator review).
> > >
> > > In this first iteration, I tried to capture the essential features of
> > the application, which means there’s plenty of opportunity for
> > improvements. The code is available at https://github.com/code4lib/
> > job_board <https://github.com/code4lib/job_board>, and I’d like to call
> > out a couple tickets that may be good starting places for new
> contributors:
> > >
> > > - Include the job title and employer in (https://github.com/code4lib/
> > job_board/issues/28 <https://github.com/code4lib/job_board/issues/28>)
> > > - Send new job notifications to the code4lib slack #jobs channel (
> > https://github.com/code4lib/job_board/issues/30 <
> > https://github.com/code4lib/job_board/issues/30>)
> > >
> > > And some operations tasks:
> > > - Add application monitoring (https://github.com/code4lib/
> > job_board/issues/25 <https://github.com/code4lib/job_board/issues/25>)
> > > - Implement continuous deployment (https://github.com/code4lib/
> > job_board/issues/32 <https://github.com/code4lib/job_board/issues/32>)
> > >
> > > There are also some more data-driven research tasks:
> > >
> > > - Automated tag extraction (https://github.com/code4lib/
> > job_board/issues/8 <https://github.com/code4lib/job_board/issues/8>)
> > > - Job location geocoding and display (https://github.com/code4lib/
> > job_board/issues/4 <https://github.com/code4lib/job_board/issues/4>)
> > > - Better job searching tools (https://github.com/code4lib/
> > job_board/issues/7 <https://github.com/code4lib/job_board/issues/7>)
> > >
> > > If you have questions, comments, or want to get involved, I’d strongly
> > encourage discussion using github issues on the project, and I’m cbeer in
> > the code4lib IRC + slack channels.
> > >
> > > Thanks,
> > > Chris
> > >
> > >
> > >> On Oct 18, 2016, at 1:51 PM, Ed Summers <[log in to unmask]> wrote:
> > >>
> > >> Hi everyone,
> > >>
> > >> If you have used jobs.code4lib.org in the past you may have noticed
> > that job posting has not really been functional for the past few weeks.
> The
> > root cause of this was the eventual shutdown of Google's Freebase API,
> > which the application relied on heavily for tagging employers, locations
> > and subjects. You can read more about it in this issue ticket if you are
> > interested:
> > >>
> > >> https://github.com/code4lib/shortimer/issues/38
> > >>
> > >> Unfortunately I don't have the bandwidth to refactor the code at this
> > point. Before the shutdown of the Freebase API I was actually finding it
> > difficult to moderate the many new jobs that would show up via RSS. In
> > theory this could've been done by any logged in user, but I was often the
> > only person doing it. I'm not complaining--I was the one who set it up to
> > to work this way. I also have been paying $20/month to host it, which
> isn't
> > a lot -- but hey, it adds up.
> > >>
> > >> So .... this is all to say, on November 1st I am planning on creating
> a
> > static version of the site, and dumping the data as JSON, which I will
> put
> > up on Internet Archive for anyone else wanting to create a similar
> service.
> > The code will continue to live up at GitHub [1].
> > >>
> > >> I apologize if this rubs anyone the wrong way, but it is super to see
> > people still posting jobs to the email list as they always have.
> > Applications age like fish, data ages wine -- or so they say...
> > >>
> > >> //Ed
> > >>
> > >> [1] https://github.com/code4lib/shortimer
> >
>