[CODE4LIB] Job: Library Web Services Assistant at Five Colleges of Ohio

[jobs]

 Library Web Services Assistant
Five Colleges of Ohio
Ohio

The Five Colleges of Ohio (a consortium of liberal arts colleges comprised of
The College of Wooster, Denison University, Kenyon College, Oberlin College,
and Ohio Wesleyan University) is seeking candidates enthusiastic about library
technology to work in collaboration with members of our consortium to support,
enhance, and extend the capabilities of our shared library management system,
discovery tools, and digital scholarship initiatives.

  
Under the supervision of the Associate Director of Consortial Library Systems,
the Library Web Services Assistant provides superb support to library staff
members using the Sierra library management system, loads data for electronic
resources (ebooks, videos, journals) into the consortial catalog, and
contributes to new and ongoing investigations of digital tools for use in our
libraries.

  
This is a part-time position with flexible hours, and offers a unique
opportunity for someone interested in building experience with a variety of
library systems. The pay is $20.00 per hour without benefits. The Assistant's
office could be at Denison, Kenyon, Ohio Wesleyan, or Wooster, but occasional
travel to each of the colleges will be required.

  
**Required Qualifications:**

  * Coursework in computer science, library and information science, or 
equivalent experience
  * Strong attention to detail to ensure data integrity across library systems
  * Strong customer service skills and a demonstrated desire to help solve 
problems
  * Proactive, quick learner, with a strong sense of curiosity and enthusiasm 
for learning new technologies
  * Ability to work independently in a highly collaborative environment
  * Experience managing a website, including working with hosting providers, 
FTP software, and working with files on a web server
  
**Preferred Qualifications:**

  * Bachelor's degree in computer science, information science and technology, 
or related field
  * Experience with an integrated library system (ILS) and library 
bibliographic data
  * Experience with Javascript, PHP, MySQL, and/or HTML/CSS
  
Five Colleges of Ohio employees are hired through Kenyon College, an Equal
Opportunity Employer. It is the college's policy to evaluate qualified
applicants without regard to age, ancestry, disability, national or ethnic
origin, race, religion, sex, sexual orientation, marital status, political
belief or activity, or status as a veteran. We welcome diversity and encourage
applications from women and minority candidates.



Brought to you by code4lib jobs: http://jobs.code4lib.org/job/25035/
To post a new job please visit http://jobs.code4lib.org/

[CODE4LIB] Looking for a Blackmagic Extreme HDMI and analog capture device

[Peter Murray]

All,

We are in need of a Blackmagic Design Intensity Extreme HDMI and Analog Capture 
& Playback Device with a Thunderbolt interface for use at Code4Lib Con.  Do you 
have one we could borrow?  It looks something like this:

  
http://www.amazon.com/Blackmagic-Design-Intensity-Extreme-Playback/dp/B007CYJ4WM

If so, please contact me.


Peter
-- 
Peter Murray
Dev/Ops Lead and Project Manager, Cherry Hill Company
Blogger, Disruptive Library Technology Jester - http://dltj.org/

Re: [CODE4LIB] OregonDigital's BookReader integration (was: Listserv communication)

[Laura Buchholz]

Thanks guys, and thank you Shaun, for following up. This is exactly what I
was hoping to learn.

I have to admit I'm surprised that the "direct-to-page-link" functionality
isn't more common in the newer/inspiring digital collections. It exists in
contentDM (not saying that is reason it should continue to exist), and
seems intuitively useful. We're planning on doing some usability testing
soon, and I'm going to try to get feedback on this feature.

On Tue, Mar 1, 2016 at 7:51 AM, Gum, Josh  wrote:

> Shaun,
>
> Thanks, I’m psyched to be at OSU!
>
> I think you’ve nailed down the process here, and there are a couple
> concepts that I wanted to follow-up on;
>
> 1. “Download document from search results list” : This would be a simple
> enhancement to the rendering of each search result and exposing the
> download link.. The software has access to all of the necessary values
> (document ID, and how to generate a “downloads” link for it) at render
> time, so adding a new link should be trivial.. It seems like it would be a
> good enhancement to me.
>
> 2. “Direct-to-page link” : Generating a link to guide a PDF reader to a
> specific page [1] seems easy, although I’m not sure that every reader would
> work the same. So the missing piece is being able to associate a SOLR hit
> with the page it was found in the PDF.. So, I think you’re right about
> needing to index each page individually in order to facilitate rendering a
> link to a specific page related to the search result hit being rendered on
> the page.
>
> I can’t speak to the history behind implementing the search the way it is
> right now.. But it does seem like both of these concepts would be great
> additions to the next installment of OregonDigital!
>
> [1] http://oregondigital.org/downloads/oregondigital:df66z508t?page=3
>
> ———
> Josh Gum
> Oregon State University Libraries and Press
>
>
>
>
>
> On 2/29/16, 4:13 PM, "Code for Libraries on behalf of Shaun D. Ellis" <
> CODE4LIB@LISTSERV.ND.EDU on behalf of sha...@princeton.edu> wrote:
>
> >Josh,
> >Congrats on the new gig, and thank you for this explanation of
> OregonDigital’s BookReader integration.  I’m sorry I wasn’t more specific
> about this, but I think the original question had less to do with the
> BookReader integration, and more to do with a non-frameworky explanation of
> configuring Solr to return direct links to pages where the keywords appear
> in a “compound” object, such as a book.
> >
> >As the original poster (Laura Buchholz) mentioned, it seems like
> OregonDigital does not provide direct links until after the BookReader is
> loaded.  It’s only then that pins are placed on the “slider nav” to
> indicate where the keyword appears.  So, to answer the original question,
> it seems like all the full-text may be dumped into a single Solr field that
> returns the object in the initial search result, and then upon loading the
> BookReader makes a subsequent query (limited to that one object) retrieve
> the “data payload” in your example to then locate the exact pages where the
> terms appear?  Is that what’s going on there?
> >
> >I suppose if you wanted to return all the page numbers in the original
> search query, you may have to send each page individually to Solr to be
> indexed, and if you have a viewer with conventions for "deep linking" (like
> the BookReader has) you could generate the link for each page and index it
> to provide this functionality.
> >
> >I was curious as folks were posting all the inspiring digital collections
> sites earlier today, so I looked for this pattern but didn’t see it.  Most
> of the apps use the same pattern as OregonDigital (although my testing was
> not particularly thorough, so let me know if I’m wrong, folks!).  On the
> otherhand, you do see the "direct-to-page link" interface with both Amazon
> and Google Books search, which takes you directly to the page from the
> initial search results.
> >
> >So, I’m not sure if this was a conscious design decision on the part of
> library digital collections creators, if the pattern is followed because
> it’s considered a “best practice” or a “convention” in our field, or if it
> was just simpler to implement.
> >
> >Thanks again for the follow up,
> >Shaun
> >
> >> On Feb 26, 2016, at 2:51 PM, Gum, Josh 
> wrote:
> >>
> >> I’m very new (<1 month) to Oregon State University, library technology,
> and Code4Lib. So please bear with me. Also, I’m going to put a disclaimer
> out that I may be missing some of the picture here.. I’m willing to lend a
> hand digging into more details if needed, so please feel free to ask.
> >>
> >> Also.. I’m going to split this part of the discussion into a separate
> thread, so we can address the question regarding the OregonDigital
> BookReader integration. I’ve done some digging this morning, and spoke to a
> colleague who took part in some of the text extraction for PDF assets in
> OregonDigital.. I’m hopeful that these details are enough to help connect
> the dots reg

Re: [CODE4LIB] onboarding developers coming from industry

[Mark V. Sullivan]

> And for all those reasons and more, don't put IT in a back room and leave it
> there, unconnected to the rest of the library and institution.  How library IT
> works with and is integrated into the rest of the library varies from place to
> place, but if the developers and sys admins don't regularly see and work with
> and around students and faculty, they'll be badly disconnected and could 
> develop
> a bunker mentality.

> Aside from being important, in a university, being around the students and
> faculty is really interesting, and it's fun.  It's like being in a little city
>where everyone's studying and thinking, and every year a quarter of the
>population moves out and a new quarter moves in.

>Bill

This.. absolutely this +100.

Mark (formerly of a University settings)

Mark V. Sullivan
Sobek Digital Hosting and Consulting, LLC
mark.v.sulli...@sobekdigital.com
https://sobekdigital.com



From: Code for Libraries  on behalf of William Denton 

Sent: Wednesday, March 2, 2016 11:12 AM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] onboarding developers coming from industry

On 2 March 2016, Jason Casden wrote:

> The advantages that we do have over many of these organizations include the
> opportunity to work directly with the users of your products, the ability to
> be more involved in broader systems analysis work, and the pursuit of a
> mission anchored in education and research.

And for all those reasons and more, don't put IT in a back room and leave it
there, unconnected to the rest of the library and institution.  How library IT
works with and is integrated into the rest of the library varies from place to
place, but if the developers and sys admins don't regularly see and work with
and around students and faculty, they'll be badly disconnected and could develop
a bunker mentality.

Aside from being important, in a university, being around the students and
faculty is really interesting, and it's fun.  It's like being in a little city
where everyone's studying and thinking, and every year a quarter of the
population moves out and a new quarter moves in.

Bill
--
William Denton ↔  Toronto, Canada ↔  https://www.miskatonic.org/

Re: [CODE4LIB] onboarding developers coming from industry

[Alex Gil]

Sign me up for this sentiment too. Even architecturally, we need more
windows.

On Wed, Mar 2, 2016 at 11:43 AM, Mark V. Sullivan <
mark.v.sulli...@sobekdigital.com> wrote:

> > And for all those reasons and more, don't put IT in a back room and
> leave it
> > there, unconnected to the rest of the library and institution.  How
> library IT
> > works with and is integrated into the rest of the library varies from
> place to
> > place, but if the developers and sys admins don't regularly see and work
> with
> > and around students and faculty, they'll be badly disconnected and could
> develop
> > a bunker mentality.
>
> > Aside from being important, in a university, being around the students
> and
> > faculty is really interesting, and it's fun.  It's like being in a
> little city
> >where everyone's studying and thinking, and every year a quarter of the
> >population moves out and a new quarter moves in.
>
> >Bill
>
> This.. absolutely this +100.
>
> Mark (formerly of a University settings)
>
> Mark V. Sullivan
> Sobek Digital Hosting and Consulting, LLC
> mark.v.sulli...@sobekdigital.com
> https://sobekdigital.com
>
>
> 
> From: Code for Libraries  on behalf of William
> Denton 
> Sent: Wednesday, March 2, 2016 11:12 AM
> To: CODE4LIB@LISTSERV.ND.EDU
> Subject: Re: [CODE4LIB] onboarding developers coming from industry
>
> On 2 March 2016, Jason Casden wrote:
>
> > The advantages that we do have over many of these organizations include
> the
> > opportunity to work directly with the users of your products, the
> ability to
> > be more involved in broader systems analysis work, and the pursuit of a
> > mission anchored in education and research.
>
> And for all those reasons and more, don't put IT in a back room and leave
> it
> there, unconnected to the rest of the library and institution.  How
> library IT
> works with and is integrated into the rest of the library varies from
> place to
> place, but if the developers and sys admins don't regularly see and work
> with
> and around students and faculty, they'll be badly disconnected and could
> develop
> a bunker mentality.
>
> Aside from being important, in a university, being around the students and
> faculty is really interesting, and it's fun.  It's like being in a little
> city
> where everyone's studying and thinking, and every year a quarter of the
> population moves out and a new quarter moves in.
>
> Bill
> --
> William Denton ↔  Toronto, Canada ↔  https://www.miskatonic.org/
>

Re: [CODE4LIB] onboarding developers coming from industry

[William Denton]

On 2 March 2016, Jason Casden wrote:

The advantages that we do have over many of these organizations include the 
opportunity to work directly with the users of your products, the ability to 
be more involved in broader systems analysis work, and the pursuit of a 
mission anchored in education and research.


And for all those reasons and more, don't put IT in a back room and leave it 
there, unconnected to the rest of the library and institution.  How library IT 
works with and is integrated into the rest of the library varies from place to 
place, but if the developers and sys admins don't regularly see and work with 
and around students and faculty, they'll be badly disconnected and could develop 
a bunker mentality.


Aside from being important, in a university, being around the students and 
faculty is really interesting, and it's fun.  It's like being in a little city 
where everyone's studying and thinking, and every year a quarter of the 
population moves out and a new quarter moves in.


Bill
--
William Denton ↔  Toronto, Canada ↔  https://www.miskatonic.org/

Re: [CODE4LIB] onboarding developers coming from industry

[Gum, Josh]

+1 to TH5!

I’m also very new to the environment.. And I’m really liking what I see. 
Fifteen years of multi-billion dollar tech industry work makes what I’m seeing 
around library tech and the processes/services involved seem like a piece of 
cake. OTOH, I’m coming from a corporation which was under a huge amount of 
change (painful at times) for almost the entire 15 years I was there… I’m 
certain that someday the twitches that happen when I hear the word “reinvent” 
will stop. :)



Seriously though, the technology in the library is fascinating to me.. I 
thought we just had banks of card catalogs and microfiche! 

#seeyouinphilly
Josh



On 3/2/16, 6:30 AM, "Code for Libraries on behalf of Tom Hutchinson" 
 wrote:

>I just wanted to say thank you for this thread. I recently jumped ship from 
>industry and am still orienting myself. The non-technical aspects are a much 
>bigger change than I anticipated; they are also precisely why I switched.
>
>To be honest I feel like I still don’t even really know what libraries / 
>librarians are yet.
>
>Tom
>(th5)
>
>> On Mar 2, 2016, at 5:52 AM, Keith Gilbertson  wrote:
>> 
>> I also agree very much with what Deborah wrote. I'd come from an
>> IT/software development background, and even after a couple of years in
>> libraries, I hadn't adjusted to library culture. I was frustrated enough to
>> write a paper about it and present at ACRL:
>> 
>> http://vtechworks.lib.vt.edu/handle/10919/23885
>> Mutant Superheroes, Contained Chaos, and Smelly Pets: Library Innovation
>> through Imaginary Anarchy
>> 
>> Reading my paper now, I recognize that I was completely wrong about a few
>> things (meetings aren't always terrible), and the tone seems entitled to me
>> today. But two of the things that I noticed that are considered good about
>> library culture were very stressful to me as a library newbie, and match
>> what Deborah has pointed out:
>> 
>> - Emphasis on collaboration and consensus
>> - Expectation to work on multiple, simultaneous projects
>> 
>> By the way, I've adjusted my attitude somewhat, and we've gotten better at
>> doing IT and software in the library and in our group, so I'm happy in
>> libraries now.
>> 
>> 
>> On Tue, Mar 1, 2016 at 9:39 PM, Fitchett, Deborah <
>> deborah.fitch...@lincoln.ac.nz> wrote:
>> 
>>> I actually feel that the tech side of library things may be less
>>> bewildering to a non-tech person than the *culture*. Things like:
>>> 
>>> * the way any progress happens in University Time
>>> * the way we're dependent on vendors in ways that mean that yes, often our
>>> systems SUCK but we just have to play the hand we're dealt
>>> * the sometimes-fraught relationship between Library IT and University IT
>>> * the customer-focus of the library - including colleagues as customers
>>> * and relatedly, the collaborative nature of so much library work
>>> * depending on where they've come from and how well you're staffed, the
>>> very "bitsy" nature of Library IT, not just in having to know about lots of
>>> things but having to jump from one thing to another at a moment's notice to
>>> troubleshoot instead of being able to get stuck into a project
>>> 

Re: [CODE4LIB] onboarding developers coming from industry

[Jason Casden]

I think that the importance of sharing your passion for library service
should not be overlooked. While universities can be rather bureaucratic,
this may also be true of many of the commercial and governmental
organizations from which these developers are being hired. The advantages
that we do have over many of these organizations include the opportunity to
work directly with the users of your products, the ability to be more
involved in broader systems analysis work, and the pursuit of a mission
anchored in education and research.

Echoing Leah's comments, I think there is great potential to foster a more
rewarding professional experience for developers new to libraries, and
facilitating connections with library users may be a good place to start.

Jason

On Wed, Mar 2, 2016 at 9:58 AM, Leah Root  wrote:

> On Mar 2, 2016, at 9:30 AM, Tom Hutchinson 
> wrote:
>
> > ...To be honest I feel like I still don’t even really know what libraries
> / librarians are yet.
>
>
> > ..  Tom, when you find out, please tell the rest of us.  ;-)  —Eric Lease
> Morgan
>
>
>  this ++
>
> We actually speak the same language - the dialect is a little different.
> Slightly less verbose, but we get it :)
>
>
>
> On Wed, Mar 2, 2016 at 9:33 AM, Eric Lease Morgan  wrote:
>
> > On Mar 2, 2016, at 9:30 AM, Tom Hutchinson 
> > wrote:
> >
> > > ...To be honest I feel like I still don’t even really know what
> > libraries / librarians are yet.
> >
> >
> >   Tom, when you find out, please tell the rest of us.  ;-)  —Eric Lease
> > Morgan
> >
>
>
>
> --
> Leah M Root
> Library Publishing/Web Services Developer
> Milne Library, SUNY Geneseo 
> 1 College Circle, Geneseo, NY 14454
> 585-245-6061 | cell 585-802-4676
> ro...@geneseo.edu
> @RootLeah 
>

[CODE4LIB] No proposals received to host Code4Lib in 2017

[Anna Headley]

Sadly, we have received no proposals to host next year's conference.

Please get in touch if you have been considering hosting code4lib. Members
of this year's committee would be happy to meet with you to give more
information about what it takes to host the conference, and help with any
road bumps you've encountered.

Thanks & best,
Anna


On Tue, Feb 23, 2016 at 9:33 AM, Anna Headley  wrote:

> Dear potential 2017 conference hosts,
>
> I promise this is the last reminder. As always, details are below and
> please let me know if you have any questions.
>
> Thanks for all the work you've done so far!!
>
> Anna
>
>
> On Tue, Feb 9, 2016 at 9:34 AM, Anna Headley  wrote:
>
>> Good morning potential Code4Lib 2017 conference hosts,
>>
>> 3 weeks left!! Still time to get started? If you get to work Right Now.
>>
>> All details below. Looking forward to seeing your proposals! Please let
>> me know if you have any questions.
>>
>> Best,
>> Anna
>>
>>
>>
>> On Tue, Jan 19, 2016 at 12:11 PM, Anna Headley  wrote:
>>
>>> Host Code4Lib 2017 in your city!
>>>
>>> The deadline for proposals is midnight PT Tuesday 1 March 2016.
>>>
>>> To apply please email the Code4Lib Conference Planning list [0] and link
>>> to your proposal on the 2017 Host Proposals wiki page [1]
>>>
>>> The decision will be made by popular vote. Voting will begin on or
>>> around Thursday March 3rd, 2016 and will continue until midnight PT March
>>> 15th, 2016. The results of the vote will be announced Friday March 16th via
>>> listserv.
>>>
>>> Prior to submitting a proposal we recommend reviewing the conference hosting
>>> web page [2] and How To Plan a Code4LibCon on the wiki [3] to learn
>>> more about the kind of venue the community seeks and the responsibilities
>>> involved with hosting the conference.
>>>
>>> Here's a sample of past successful proposals:
>>>
>>>- 2016: http://c4l-phl.github.io/
>>>- 2015: http://osulp.github.io/code4lib-pdx/
>>>- 2014:
>>>
>>> https://docs.google.com/document/d/1amxzn4xs26ILszZek5nIEEfd4qHNfLjp1BAc5CU5YKw/edit
>>>- 2013: http://tigger.uic.edu/~kayiwa/code4lib.html
>>>- 2012: https://sites.google.com/site/code4lib2012seattle/
>>>
>>> Thank you and good luck!!
>>> Anna Headley
>>> On behalf of the 2016 Planning Committee
>>>
>>> [0] code4lib...@googlegroups.com
>>> [1] http://wiki.code4lib.org/2017_Host_Proposals
>>> [2] http://code4lib.org/conference/hosting
>>> [3] http://wiki.code4lib.org/index.php/How_To_Plan_A_Code4LibCon
>>>
>>>
>>>
>>
>

[CODE4LIB] Job: Library Systems Manager at Washington University in St. Louis

[Davis, Shannon]

Recruitment has started for the position of Library Systems Manager at 
Washington University in St. Louis. I will be attending code4lib next week and 
would be happy to talk more with anyone who's interested! Apply at 
https://jobs.wustl.edu by searching for job # 32532.



Job Title

Library Systems Manager, Olin Library - 32532

Job ID

32532










Essential Functions




Under the direction of the Head of Library Technology Services, provides a 
reliable, accurate, responsive, efficient, and secure information systems 
platform for library service delivery.  Manages service delivery at both the 
desktop and server level, ensuring a cohesive technology platform for library 
services. Provides support to strengthen the library's online systems, which 
our patrons rely upon as research infrastructure.

Leads operations for desktop support by providing oversight, leadership, and 
direction in designing, implementing, maintaining, monitoring, and supporting 
the desktop and mobile computing environments available to staff and library 
patrons. Works with a team of staff and students to respond to support requests 
with staff and public computing, troubleshoots and solves hardware and software 
problems, monitors overall system performance, and implements improvements.

Leads operations for server support. Works with a team of systems support staff 
to manage the Libraries' server infrastructure supporting our web applications 
and related services. Develops, documents and implements server administration 
policies and processes. Maintains and troubleshoots hardware, software, and 
network issues. Ensures system integrity, reliability, responsiveness, security 
and compliance with library policies. Maintains a regular backup schedule and 
off-site backup storage.

Develops and implements technology plans to keep existing library services 
operational and to implement new services in collaboration with Libraries staff 
and stakeholders.

Works with Washington University Information Technology and campus technology 
organizations to maximize campus-wide shared technology services.



Required Qualifications




  *   Bachelor's degree in computer science, information systems, or related 
field with a minimum of 3 years of experience in information management in a 
higher-education context, or equivalent experience;
  *   Demonstrated understanding of issues related to university-wide 
information systems and technology
  *   Excellent communication skills and the ability to interact professionally 
with a diverse group of staff.
  *   Familiarity with best practices and procedures for managing library 
technologies within an academic library;
  *   An understanding of the information needs of a research library serving 
students, faculty, community members, and international scholars;
  *   Excellent written and verbal communication skills;
  *   Experience defining technology needs related to library spaces and 
collections.



Preferred Qualifications




  *   Master's degree in information systems
  *   Ability to work productively in teams;
  *   Significant technical and supervisory experience in a hybrid technology 
environment consisting of Windows, Macs, Linux, and mobile systems.

Re: [CODE4LIB] onboarding developers coming from industry

[Leah Root]

On Mar 2, 2016, at 9:30 AM, Tom Hutchinson  wrote:

> ...To be honest I feel like I still don’t even really know what libraries
/ librarians are yet.


> ..  Tom, when you find out, please tell the rest of us.  ;-)  —Eric Lease
Morgan


 this ++

We actually speak the same language - the dialect is a little different.
Slightly less verbose, but we get it :)



On Wed, Mar 2, 2016 at 9:33 AM, Eric Lease Morgan  wrote:

> On Mar 2, 2016, at 9:30 AM, Tom Hutchinson 
> wrote:
>
> > ...To be honest I feel like I still don’t even really know what
> libraries / librarians are yet.
>
>
>   Tom, when you find out, please tell the rest of us.  ;-)  —Eric Lease
> Morgan
>



-- 
Leah M Root
Library Publishing/Web Services Developer
Milne Library, SUNY Geneseo 
1 College Circle, Geneseo, NY 14454
585-245-6061 | cell 585-802-4676
ro...@geneseo.edu
@RootLeah 

Re: [CODE4LIB] onboarding developers coming from industry

[Eric Lease Morgan]

On Mar 2, 2016, at 9:48 AM, LeVan,Ralph  wrote:

> …I've written so much bloat that didn't get used because a librarian was sure 
> the system would fail without it….

I’m ROTFL because just a few minutes ago, while composing an informal essay on 
the history of bibliographic description, I wrote the following sentence:

  The result is library jargon solidified in an obscure
  data structure. Moreover, in an attempt to make the
  surrogates of library collections more meaningful, the
  information of bibliographic description bloats to fill
   ^^
  much more than the traditional three to five catalog
  cards of the past.

levan++

—
ELM

Re: [CODE4LIB] onboarding developers coming from industry

[LeVan,Ralph]

On the culture side: librarians insisting that they know what their patrons 
want.  I've written so much bloat that didn't get used because a librarian was 
sure the system would fail without it.

Ralph

-Original Message-
From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of 
Fitchett, Deborah
Sent: Tuesday, March 01, 2016 9:39 PM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: onboarding developers coming from industry

I actually feel that the tech side of library things may be less bewildering to 
a non-tech person than the *culture*. Things like:

* the way any progress happens in University Time
* the way we're dependent on vendors in ways that mean that yes, often our 
systems SUCK but we just have to play the hand we're dealt
* the sometimes-fraught relationship between Library IT and University IT
* the customer-focus of the library - including colleagues as customers
* and relatedly, the collaborative nature of so much library work
* depending on where they've come from and how well you're staffed, the very 
"bitsy" nature of Library IT, not just in having to know about lots of things 
but having to jump from one thing to another at a moment's notice to 
troubleshoot instead of being able to get stuck into a project

If someone has no experience in libraries and gets thrust into this culture 
from something quite different, then no matter how quickly they pick up the 
tech they risk feeling very adrift in terms of how Things Are Done Around Here 
and jangling with people because each party is trying to interact in very 
different ways.

Or they may be a perfect fit culturally and that's why they've made the move! 
But it's worth keeping a watch to be sure there aren't any "culture shock" 
incidents, or if there are to deal with them before they cause too much stress.

Deborah

-Original Message-
From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Jenn 
Riley
Sent: Saturday, 27 February 2016 9:42 a.m.
To: CODE4LIB@LISTSERV.ND.EDU
Subject: [CODE4LIB] onboarding developers coming from industry

Dear Code4Libbers,

We have a new developer starting soon that’s coming from industry with no 
experience in libraries. We're interested in hearing about any strategies or 
training methods you’ve found successful in introducing developers from other 
areas to the quirkiness of library tech – things like MARC, proxy servers, 
Z39.50, catalogue knowledgebases, e-resources access, etc. Do you have any 
successes or advice to share?

For those of you in academic libraries, we also are interested in strategies 
for getting someone new oriented to the academic environment.

Thanks so much!

Jenn

---
Jenn Riley
Associate Dean, Digital Initiatives | Vice Doyenne, Initiatives numériques

McGill University Library | Bibliothèque Université McGill
3459 McTavish Street | 3459, rue McTavish Montreal, QC, Canada H3A 0C9 | 
Montréal (QC) Canada  H3A 0C9

(514) 398-3642
jenn.ri...@mcgill.ca


P Please consider the environment before you print this email.
"The contents of this e-mail (including any attachments) may be confidential 
and/or subject to copyright. Any unauthorised use, distribution, or copying of 
the contents is expressly prohibited. If you have received this e-mail in 
error, please advise the sender by return e-mail or telephone and then delete 
this e-mail together with all attachments from your system."

Re: [CODE4LIB] onboarding developers coming from industry

[Eric Lease Morgan]

On Mar 2, 2016, at 9:30 AM, Tom Hutchinson  wrote:

> ...To be honest I feel like I still don’t even really know what libraries / 
> librarians are yet.


  Tom, when you find out, please tell the rest of us.  ;-)  —Eric Lease Morgan

Re: [CODE4LIB] onboarding developers coming from industry

[Bethany Seeger]

One of the big shifts for me - a newbie to library science who switched
over from industry late last spring - is just how many people _outside_
the college I interface with, part of that being the open source
community. And I LOVE that aspect of my job, knowing that there¹s a larger
community out there, ready to share information with and support one
another. 

-Bethany

On 3/2/16, 9:21 AM, "Code for Libraries on behalf of Brian Kennison"
 wrote:

>On Mar 1, 2016, at 9:39 PM, Fitchett, Deborah
>mailto:deborah.fitch...@lincoln.ac.nz>>
>wrote:
>
>I actually feel that the tech side of library things may be less
>bewildering to a non-tech person than the *culture*. Things like:
>
>* the way any progress happens in University Time
>* the way we're dependent on vendors in ways that mean that yes, often
>our systems SUCK but we just have to play the hand we're dealt
>* the sometimes-fraught relationship between Library IT and University IT
>* the customer-focus of the library - including colleagues as customers
>* and relatedly, the collaborative nature of so much library work
>* depending on where they've come from and how well you're staffed, the
>very "bitsy" nature of Library IT, not just in having to know about lots
>of things but having to jump from one thing to another at a moment's
>notice to troubleshoot instead of being able to get stuck into a project
>
>If someone has no experience in libraries and gets thrust into this
>culture from something quite different, then no matter how quickly they
>pick up the tech they risk feeling very adrift in terms of how Things Are
>Done Around Here and jangling with people because each party is trying to
>interact in very different ways.
>
>Or they may be a perfect fit culturally and that's why they've made the
>move! But it's worth keeping a watch to be sure there aren't any "culture
>shock" incidents, or if there are to deal with them before they cause too
>much stress.
>
>Deborah
>
>+1

Re: [CODE4LIB] onboarding developers coming from industry

[Tom Hutchinson]

I just wanted to say thank you for this thread. I recently jumped ship from 
industry and am still orienting myself. The non-technical aspects are a much 
bigger change than I anticipated; they are also precisely why I switched.

To be honest I feel like I still don’t even really know what libraries / 
librarians are yet.

Tom
(th5)

> On Mar 2, 2016, at 5:52 AM, Keith Gilbertson  wrote:
> 
> I also agree very much with what Deborah wrote. I'd come from an
> IT/software development background, and even after a couple of years in
> libraries, I hadn't adjusted to library culture. I was frustrated enough to
> write a paper about it and present at ACRL:
> 
> http://vtechworks.lib.vt.edu/handle/10919/23885
> Mutant Superheroes, Contained Chaos, and Smelly Pets: Library Innovation
> through Imaginary Anarchy
> 
> Reading my paper now, I recognize that I was completely wrong about a few
> things (meetings aren't always terrible), and the tone seems entitled to me
> today. But two of the things that I noticed that are considered good about
> library culture were very stressful to me as a library newbie, and match
> what Deborah has pointed out:
> 
> - Emphasis on collaboration and consensus
> - Expectation to work on multiple, simultaneous projects
> 
> By the way, I've adjusted my attitude somewhat, and we've gotten better at
> doing IT and software in the library and in our group, so I'm happy in
> libraries now.
> 
> 
> On Tue, Mar 1, 2016 at 9:39 PM, Fitchett, Deborah <
> deborah.fitch...@lincoln.ac.nz> wrote:
> 
>> I actually feel that the tech side of library things may be less
>> bewildering to a non-tech person than the *culture*. Things like:
>> 
>> * the way any progress happens in University Time
>> * the way we're dependent on vendors in ways that mean that yes, often our
>> systems SUCK but we just have to play the hand we're dealt
>> * the sometimes-fraught relationship between Library IT and University IT
>> * the customer-focus of the library - including colleagues as customers
>> * and relatedly, the collaborative nature of so much library work
>> * depending on where they've come from and how well you're staffed, the
>> very "bitsy" nature of Library IT, not just in having to know about lots of
>> things but having to jump from one thing to another at a moment's notice to
>> troubleshoot instead of being able to get stuck into a project
>> 

Re: [CODE4LIB] onboarding developers coming from industry

[Brian Kennison]

On Mar 1, 2016, at 9:39 PM, Fitchett, Deborah 
mailto:deborah.fitch...@lincoln.ac.nz>> wrote:

I actually feel that the tech side of library things may be less bewildering to 
a non-tech person than the *culture*. Things like:

* the way any progress happens in University Time
* the way we're dependent on vendors in ways that mean that yes, often our 
systems SUCK but we just have to play the hand we're dealt
* the sometimes-fraught relationship between Library IT and University IT
* the customer-focus of the library - including colleagues as customers
* and relatedly, the collaborative nature of so much library work
* depending on where they've come from and how well you're staffed, the very 
"bitsy" nature of Library IT, not just in having to know about lots of things 
but having to jump from one thing to another at a moment's notice to 
troubleshoot instead of being able to get stuck into a project

If someone has no experience in libraries and gets thrust into this culture 
from something quite different, then no matter how quickly they pick up the 
tech they risk feeling very adrift in terms of how Things Are Done Around Here 
and jangling with people because each party is trying to interact in very 
different ways.

Or they may be a perfect fit culturally and that's why they've made the move! 
But it's worth keeping a watch to be sure there aren't any "culture shock" 
incidents, or if there are to deal with them before they cause too much stress.

Deborah

+1

[CODE4LIB] need a registration spot for c4l16?

[Rosalyn Metz]

Hi everyone,

Anyone perchance interested in attending c4l16 next week?  I have a
registration spot I won't be able to use (moving cross country + driving
cross country + starting new job is a full month already).  If you're
interested, let me know and we can work something out.

Rosy

Re: [CODE4LIB] onboarding developers coming from industry

[Leah Root]

I am an IT professional who transferred from a 20 year corporate background
to the Academic Library Universe. I agree with nearly everything that
Deborah and Keith wrote.

My advice to those working with  a 'Library IT newbie person' is this:
Show the Library IT person  how the end user works with your software,
platforms, servers, databases, and other electronic resources.  Let the
Library IT person meet with individual librarians, staff, student workers,
and  faculty as much as possible.That way the Library IT person can
understand the practical applications and workflow of all the systems in
the library, and understand the needs and frustrations of the end users.
We cannot code in a vacuum.

Disclaimer of sorts: I am very grateful to be in an Academic Library
environment.  I will never look back.  When I see that anything I have
programmed or developed: tracks and proves benefits of library resource
usage; allows students to download textbooks freely; allows authors and
professors to publish their work via Creative Commons; allows better access
to knowledge in general - - that outweighs any frustration.



On Wed, Mar 2, 2016 at 5:52 AM, Keith Gilbertson 
wrote:

> I also agree very much with what Deborah wrote. I'd come from an
> IT/software development background, and even after a couple of years in
> libraries, I hadn't adjusted to library culture. I was frustrated enough to
> write a paper about it and present at ACRL:
>
> http://vtechworks.lib.vt.edu/handle/10919/23885
> Mutant Superheroes, Contained Chaos, and Smelly Pets: Library Innovation
> through Imaginary Anarchy
>
> Reading my paper now, I recognize that I was completely wrong about a few
> things (meetings aren't always terrible), and the tone seems entitled to me
> today. But two of the things that I noticed that are considered good about
> library culture were very stressful to me as a library newbie, and match
> what Deborah has pointed out:
>
> - Emphasis on collaboration and consensus
> - Expectation to work on multiple, simultaneous projects
>
> By the way, I've adjusted my attitude somewhat, and we've gotten better at
> doing IT and software in the library and in our group, so I'm happy in
> libraries now.
>
>
> On Tue, Mar 1, 2016 at 9:39 PM, Fitchett, Deborah <
> deborah.fitch...@lincoln.ac.nz> wrote:
>
> > I actually feel that the tech side of library things may be less
> > bewildering to a non-tech person than the *culture*. Things like:
> >
> > * the way any progress happens in University Time
> > * the way we're dependent on vendors in ways that mean that yes, often
> our
> > systems SUCK but we just have to play the hand we're dealt
> > * the sometimes-fraught relationship between Library IT and University IT
> > * the customer-focus of the library - including colleagues as customers
> > * and relatedly, the collaborative nature of so much library work
> > * depending on where they've come from and how well you're staffed, the
> > very "bitsy" nature of Library IT, not just in having to know about lots
> of
> > things but having to jump from one thing to another at a moment's notice
> to
> > troubleshoot instead of being able to get stuck into a project
> >
>



-- 
Leah M Root
Library Publishing/Web Services Developer
Milne Library, SUNY Geneseo 
1 College Circle, Geneseo, NY 14454
585-245-6061 | cell 585-802-4676
ro...@geneseo.edu
@RootLeah 

[CODE4LIB] DCMI Webinar Series: Generic Tools and Methods for SKOS-based Concept Schemes

[DCMI Announce]

***PLEASE EXCUSE THE CROSS-POSTING***

*DCMI/ASIST Joint Webinar Series in partnership with AIMS: Agricultural
Information Management Standards*

SKOS in Two Parts: Generic Tools and Methods for SKOS-based Concept Schemes


*with Joachim Neubert (ZBW Leibniz Information Centre for Economics,
Germany) & Osma Suominen (National Library of Finland)*

**
*:: Dates:* Wednesday, 16 March 2016 &
   Wednesday,  6 April 2016
*:: Time: * 10:00am - 11:15am EDT (UTC 14:00:00)
*:: Registration Information: *
   http://dublincore.org/resources/training/#2016neubert
**

*ABOUT THE WEBINAR SERIES:*

In the past seven years, SKOS has become a widely recognized and used
common interchange format for thesauri, classifications, and other types of
vocabularies. This has opened a huge opportunity for the development of
generic tools and methods that should apply to all vocabularies that can be
expressed in SKOS. While expensive, proprietary or custom-developed
solutions aimed at one particular thesaurus or classification have been
dominant, now more and more open source tools are being created to deal
with various aspects of vocabulary management. In this series of two
webinars with Joachim Neubert (ZBW Leibniz Information Centre for
Economics, Germany) and Osma Suominen (National Library of Finland), we
start on 16 March 2016 with Webinar 1 by examining skos-history, a method
and toolset to nail down changes in a vocabulary. We follow with Webinar 2
on 6 April 2016 focusing on Skosmos, a full-fledged web application for
publishing SKOS vocabularies.


*ABOUT WEBINAR 1 (16 March 2016):*

Change Tracking in Knowledge Organization Systems with skos-history

When a new version of a vocabulary is published, users want to know "What’s
new?" and "What has changed?" Vocabulary managers had differing strategies
to answer these questions—relying on internal logs of the vocabulary
management system or the intellectual collection of changes deemed
relevant. These methods generally are not available to third parties using
a vocabulary, or for example are trying to keep vocabulary mappings up to
date.

Having vocabularies published in SKOS as RDF triples has changed this
situation: Vocabularies can be compared algorithmically, and deltas between
versions can be computed. This data can be loaded into a version store, and
evaluated by SPARQL queries. Therefore, the published versions alone are
sufficient to get the differences.

The webinar will explain how you can create a version store, how
skos-history interlinks versions and deltas, and how queries can get a grip
on added or removed concepts, on changed notations, or on merges and splits
of concepts. We will show how aggregated change information about a concept
scheme can be obtained, and how the complete change history of a single
concept across multiple versions can be traced. Finally, you will learn how
you can adapt skos-history queries to the features of a particular concept
scheme in which you are interested.


*ABOUT WEBINAR 2 (6 April 2016):*

Publishing SKOS Concept Schemes with Skosmos

With more and more thesauri, classifications and other knowledge
organization systems being published as Linked Data using SKOS, the
question arises how best to make them available on the web. While just
publishing the Linked Data triples is possible using a number of RDF
publishing tools, those tools are not very well suited for SKOS data,
because they cannot support term-based searching and lookup.

This webinar presents Skosmos, an open source web-based SKOS vocabulary
browser that uses a SPARQL endpoint as its back-end. It can be used by e.g.
libraries and archives as a publishing platform for controlled vocabularies
such as thesauri, lightweight ontologies, classifications and authority
files. The Finnish national thesaurus and ontology service Finto, operated
by the National Library of Finland, is built using Skosmos.

Skosmos provides a multilingual user interface for browsing and searching
the data and for visualizing concept hierarchies. The user interface has
been developed by analyzing the results of repeated usability tests. All of
the SKOS data is made available as Linked Data. A developer-friendly REST
API is also available providing access for using vocabularies in other
applications such as annotation systems.

We will describe what kind of infrastructure is necessary for Skosmos and
how to set it up for your own SKOS data. We will also present examples
where Skosmos is being used around the world.


*ABOUT THE PRESENTERS:*

*Joachim Neubert* is a scientific software developer at the ZBW Leibniz
Information Centre for Economics (http://www.zbw.eu). He published the STW
Thesaurus for economics (http://zbw.eu/stw) and several other datasets as
Linked Open Data. In 2009, he started the SWIB – Semantic Web for Libraries
conference and serves to date 

Re: [CODE4LIB] onboarding developers coming from industry

[Keith Gilbertson]

I also agree very much with what Deborah wrote. I'd come from an
IT/software development background, and even after a couple of years in
libraries, I hadn't adjusted to library culture. I was frustrated enough to
write a paper about it and present at ACRL:

http://vtechworks.lib.vt.edu/handle/10919/23885
Mutant Superheroes, Contained Chaos, and Smelly Pets: Library Innovation
through Imaginary Anarchy

Reading my paper now, I recognize that I was completely wrong about a few
things (meetings aren't always terrible), and the tone seems entitled to me
today. But two of the things that I noticed that are considered good about
library culture were very stressful to me as a library newbie, and match
what Deborah has pointed out:

- Emphasis on collaboration and consensus
- Expectation to work on multiple, simultaneous projects

By the way, I've adjusted my attitude somewhat, and we've gotten better at
doing IT and software in the library and in our group, so I'm happy in
libraries now.


On Tue, Mar 1, 2016 at 9:39 PM, Fitchett, Deborah <
deborah.fitch...@lincoln.ac.nz> wrote:

> I actually feel that the tech side of library things may be less
> bewildering to a non-tech person than the *culture*. Things like:
>
> * the way any progress happens in University Time
> * the way we're dependent on vendors in ways that mean that yes, often our
> systems SUCK but we just have to play the hand we're dealt
> * the sometimes-fraught relationship between Library IT and University IT
> * the customer-focus of the library - including colleagues as customers
> * and relatedly, the collaborative nature of so much library work
> * depending on where they've come from and how well you're staffed, the
> very "bitsy" nature of Library IT, not just in having to know about lots of
> things but having to jump from one thing to another at a moment's notice to
> troubleshoot instead of being able to get stuck into a project
>