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:

Proportional Font

LISTSERV Archives

LISTSERV Archives

CODE4LIB Home

CODE4LIB Home

CODE4LIB  April 2015

CODE4LIB April 2015

Subject:

VIVO Project Seeks a Dynamic, Creative, and Innovative Technical Lead

From:

Violeta Ilik <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Wed, 8 Apr 2015 15:31:29 +0000

Content-Type:

multipart/related

Parts/Attachments:

Parts/Attachments

text/plain (109 lines) , 86845948-48B7-4E6C-A1CD-EFC72BAD8308.png (109 lines)

*** Please excuse cross-posting ***

FOR IMMEDIATE RELEASE

April 8, 2015

Read it online: http://duraspace.org/jobs
Contact: [log in to unmask]<mailto:[log in to unmask]>

VIVO Project Seeks a Dynamic, Creative, and Innovative Technical Lead

Are you ready to join an open source software community that’s transforming the landscape for open scholarship? VIVO’s mission is to provide world-class open source software, standard data ontologies, linked open data, and services to our world-wide member institutions. VIVO is at the forefront of a rapidly emerging infrastructure for integrating and sharing information about researchers and scholars and their activities and outputs so as to promote data sharing, attribution, and teamwork within and across institutions. The outcome is a platform that enables discovery across a distributed network of institutions worldwide.

VIVO seeks a dynamic, creative, and innovative Technical Lead for the project. The VIVO Technical Lead will play a major role in a movement that will shape the future of scholarly discovery and collaboration.  The VIVO Technical Lead is a full-time position. Working collaboratively with the VIVO Project Director, accountable to the VIVO Steering Group, and employed by the non-profit DuraSpace organization, the Technical Lead will enable the VIVO community to accomplish its goals by fulfilling the following responsibilities:

Overview of Responsibilities

The VIVO Technical Lead will be responsible for providing leadership, technical guidance, coordination, and support to the open source community in its work to maintain, enhance, and evolve the VIVO software and ontology, and to integrate community-produced apps and tools.  The Technical Lead will ensure that the VIVO software products fulfill the mission and strategic direction of the project and the needs of community members.  Additionally, the Technical Lead will lead the effort to ensure that VIVO implementation tools and application interfaces are made user-friendly and provide value “out of the box.”

The Technical Lead will foster an inclusive, welcoming, and open team environment, based on a meritocracy of committers, contributors, ontologists, documentation specialists, technical trainers, and other volunteer contributors.  S/he will recruit new members to the team from the larger community of volunteers.  S/he will organize events such as hackathons, training sessions, implementation fests, and the like to provide multiple on-ramps for new contributors.

The Technical Lead will organize development sprints and team meetings that are oriented towards incorporating all the work of the project – core development, apps and tools creation, ontology work, documentation, etc. – into an established release schedule.

S/he will attend VIVO Steering Group, Leadership Group, and Management Team meetings. The Technical Lead, working in partnership with the Project Director, will oversee a process of eliciting and documenting new use cases that will be gathered from the VIVO membership.  The process will include steps for surveying the community on feature priorities and will culminate in a published, evolving roadmap of future work that aligns with the VIVO strategic plan and value proposition.

S/he will coordinate technology activities among the Implementation, Development, Applications and Tools, Ontology, and Community Engagement Working Groups; identify, document, and communicate dependencies between working groups; and identify solutions to enhance cross-working group collaborations. The Technical Lead will provide support to technology Task Forces and will monitor their progress.

S/he will provide oversight and coordination of VIVO architecture work and ensure that VIVO core code, ontology, and applications and tools meet open standards; will work with the community to support ontology improvements, integrate community extensions and deliver applications and tools as tested optional extensions to VIVO; maintain code base infrastructure; and coordinate release management and testing activities.

S/he will work collaboratively with developers and stakeholders to create and maintain a technical roadmap and will collaborate on strategic planning. S/he will develop an understanding of the impact of technical decisions on budgets, timelines, and the sustainability of the VIVO open source project.

The Technical Lead will act as a technology spokesperson for VIVO, speaking and giving presentations at meetings, conferences, and other events.

The VIVO Technical Lead will coordinate project work by:


  *   Facilitating scoping of project efforts, soliciting and approving technology Task Forces, and soliciting community participation;
  *   Tracking the progress of Task Force deliverables within defined scope and time;
  *   Tracking, reporting, and communicating project status, progress, and deliverables among technology teams;
  *   Identifying, addressing, and/or escalating issues that pose risks to the project;
  *   Coordinating user acceptance testing within the community.

The VIVO Technical Lead will provide technical leadership, guidance, and support to VIVO Working Group leads and technology Task Forces in the following areas:


  *   Software engineering;
  *   Performance tuning;
  *   Code refactoring;
  *   Pull requests;
  *   Ontology management;
  *   System architecture;
  *   Test writing;
  *   Continuous integration testing;
  *   Code documentation;
  *   Release management;
  *   Technical discussion on project email ;
  *   Project infrastructure (email lists, blog, vivoweb.org<http://vivoweb.org/> website, IRC, issue tracking, continuous integration, GitHub code repository, SourceForge file repository, VIVO wiki resources).

Skills and Competencies

Required:


  *   Bachelors degree, preferably in computer science, or equivalent work experience;
  *   Minimum of five years technical work experience;
  *   Demonstrated leadership experience within a distributed open source team environment;
  *   Demonstrated success in mentoring, developing, and empowering staff with a collaborative and open approach; successful collaborations within and across organizations;
  *   Positive leadership style and ability to thrive in a fast-paced environment; demonstrated initiative and flexibility;
  *   Familiarity with academic institutions, research programs, and scholarly communication;
  *   Ability to document processes and specifications; use of modern documentation strategies that are coupled to the code and services;
  *   Fluency in the full stack of web-based technologies and architectures;
  *   Experience with current and emerging data architectures and technologies;
  *   Experience with linked-data technologies;
  *   Proficiency with Java and web scripting languages;
  *   Excellent communication skills, both oral and written, including the ability to communicate effectively with a diverse group of technologists, researchers, managers, funders, and peers;
  *   Demonstrated ability to manage expectations and priorities diplomatically among various stakeholders.

Desired:


  *   Past experience with and knowledge of best practices and current trends and issues in the application of technology to libraries, research programs, and academic institutions;
  *   Experience working with a diverse and international community;
  *   Experience in a startup environment;
  *   Knowledge of semantic web and linked data technologies, SPARQL, RDF, OWL, relevant tools and APIs, and experience managing semantically annotated data, triple stores, and/or graph databases.

To Apply:  Send a cover letter and resume to [log in to unmask]<mailto:[log in to unmask]>.  Screening of applications will commence immediately and continue until the position is filled.

DuraSpace is an independent 501(c)(3) not-for-profit organization providing leadership and innovation for open technologies that promote durable, persistent access to digital data. We collaborate with scholarly, scientific, cultural, and technology communities by supporting open source projects and creating services to help ensure that current and future generations have access to our collective digital heritage.

DuraSpace is an affirmative action/equal opportunity employer committed to diversity, equity, and inclusiveness.  We offer a competitive salary and benefits package, a work-from-home lifestyle, and a supportive peer group.  Significant travel is expected.



Violeta Ilik
Head, Digital Systems & Collection Services
Digital Innovations Librarian
Galter Health Sciences Library
Feinberg School of Medicine
Northwestern University Clinical and
Translational Sciences Institute (NUCATS)
303 E. Chicago Ave, 2-212
Chicago, Illinois  60611
office: (312) 503 0421
violeta.ilik at northwestern.edu
www.galter.northwestern.edu<http://www.galter.northwestern.edu/>
http://www.galter.northwestern.edu/staff/Violeta-Ilik
[cid:3B5512FD-0814-4C56-B06D-3223900F6C87]

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

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