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  August 2017

CODE4LIB August 2017

Subject:

Job: Senior Application Developer at Art Institute of Chicago

From:

Code4Lib Jobs <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Wed, 16 Aug 2017 15:00:48 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (51 lines)

Job ID: 9829

The Art Institute of Chicago is seeking a Senior Application Developer for a full-time, salaried position to support the ongoing development and maintenance of a Digital Asset Management System (DAMS) for the Museum collections.

The Art Institute of Chicago (AIC) is a world-renowned art museum housing one of the largest permanent collections in the United States. It is encyclopedic in nature with strong holdings across all media, all traditions and all ages. The Art Institute is particularly recognized for its extraordinary Impressionist, Modern, Contemporary, Asian and American collections, among other aspects of its holdings. 

The AIC Collections DAMS, named LAKE, was launched in Spring 2017.  LAKE is poised to become the Museum’s central repository for preserving, managing, accessing and publishing millions of digital assets related to the life cycle of all AIC collection items. LAKE will store very diverse kinds of digital assets and will be accessed by staff from over 25 departments with widely different access levels. LAKE is also meant to integrate with several existing applications and data sources as both a data provider and a data consumer.

LAKE is a groundbreaking effort by a major museum to embrace standards-based, community-driven open source software to build its core data repository. It is an exciting and challenging project requiring skilled, forward-thinking individuals with a strong commitment to its core values.

 

DUTIES AND RESPONSIBILITIES:

 

Responsible for developing, maintaining, deploying, testing and documenting software related to LAKE which consists of a serving as the main data store; an based on Hydra; an -based integration framework; triplestore and Solr indexes; a Python ETL framework used to migrate and synchronize data from other systems; and a set of mirror systems (Fedora, Solr, IIIF server) specifically aimed at serving web-published data.
Primarily focused on the Hydra front end and ETL scripts while also providing backup support for the other areas of the LAKE architecture.
Prioritize work according to tickets assigned via a bug tracking system (Redmine), update these tickets as work progresses, and request feedback via the same ticketing system when needed.
Review other developers' code, comment on commits and manage merging of pull requests and branches.
Monitor the health and performance of systems on which LAKE runs, help to configure new systems, upgrade local software packages and apply security patches promptly.Coordinate these activities with the Network Services and systems administration staff.
Provide realistic work estimates, deliver in a timely manner, collaborate with other team members on overlapping areas, and switch between different projects according to priorities.
Dedicate time to researching new technologies and keeping abreast of current tools, best practices and patterns used in relevant technologies as well as in the Digital Humanities fields. Attendance to conferences and other events related to museum and repository technology is expected.
Collaborate and initiate discussion with other team members on issues involving multiple areas of LAKE and other applications as needed.  Interaction with communities supporting upstream projects is also expected – if necessary, participating in interest groups and working groups on topics shared with other institutions.
Maintain good working relationships with the Collections development team, other departments of the museum in order and occasionally with on or off-site contractors to identify and address system requirements.

 

Qualifications

 

Bachelors or Masters degree in a related field is required.

Primary requirements:

Working experience with Ruby on Rails, especially with complex gem stacks; previous experience with Hydra is ideal.
Working experience with Python (3.4 or higher).
Proficiency in Solr (5.5 or higher) query and schema language; SolrCloud administration a plus.
Thorough understanding of the HTTP protocol and REST API patterns.
Previous experience with large and complex data repositories a plus.
Experience with or ability to learn the IIIF protocol, Mirador, Universal Viewer, RDF, semantic stores and SPARQL is ideal.

Experience building functional, intuitive interfaces with HTML, CSS and JS frameworks (JQuery, Bootstrap) preferred.
Experience with configuring Apache httpd, Tomcat, Varnish cache, and other server systems is helpful.

 


----
Brought to you by code4lib jobs: https://jobs.code4lib.org/jobs/27763-senior-application-developer

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

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