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  July 2014

CODE4LIB July 2014

Subject:

Job: Contract Programmer, Repository Registry at Orbis Cascade Alliance

From:

[log in to unmask]

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Tue, 22 Jul 2014 18:09:53 -0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (158 lines)

Contract Programmer, Repository Registry
Orbis Cascade Alliance
Eugene

The Orbis Cascade Alliance seeks a qualified programmer to perform the
following work by 2014 September 30 through a Personal Services Contract with
the Alliance.

  
**Description of Overall Project**  
The Archive Engine West grant began 2011 October 1 as the Cross-Search and
Context Utility and was scheduled to conclude on 2013 December 31. Although
the aims of the Archive Engine West grant have largely been fulfilled, there
is a strong a need to better integrate into the Alliance's Strategic Agenda.
Thus, the extension project addresses infrastructure, digital content
metadata, preparing to potentially become a DPLA Service Hub, and integration
with the Orbis Cascade Alliance's Strategic Agenda and new organizational
structure. The grant extension concludes of 2014 December 31.

  
**Scope of Work**  
Create a sustainable infrastructure for repository records used by AEW and
NWDA's EAD infrastructure. To be completed by 2014 September 30 based on
existing specifications (see below).

  
**Qualifications**  
Skilled at modern web programming standards and UI design. Experienced in
ASP.NET and the C# language. Knowledge of the Windows Internet Information
Server as a platform for ASP-based interfaces. Demonstrated knowledge of XML
as well as digital library metadata standards and systems.

  
Demonstrated record of trustworthiness and completing projects on time and at
or under budget through contacts with past clients.

Evidence of adequate liability insurance.

  
**Compensation**  
Negotiated

  
Application: Due by close of business August 1, 2014 to Jodi Allison-Bunnell,
[log in to unmask]

  
Letter of application that includes a not to exceed price for the project

Portfolio of projects completed

Three client references


**Specifications**  
Objective: Create a sustainable infrastructure for repository records used by
AEW and NWDA's EAD infrastructure.

  
Timeline: To be completed by 2014 September 30.

  
Repository records storage and management is a new module
for the NWDA utility site, a password-protected site accessible only to
members at https://nwda.orbiscascade.org/tools/Login.aspx. The members
currently use the tools linked to this site to validate and upload their
Encoded Archival Description (EAD)-based finding aid documents to the NWDA
back-end database. After the work described here is
completed, NWDA members should be able to log into the utility site and edit
their repository records as well, then have that information be displayed for
all their finding aids on the NWDA site, http://nwda.orbiscascade.org.

  
Repository records are currently encoded via embedded XML elements into each
XML-based EAD document hosted on the NWDA site. Keeping this information
complete and up to date for each individual document is a maintenance issue
that limits the usefulness and accuracy of the metadata. The aim of this
project is to move from this approach to a more flexible and easily maintained
one that produces better user outcomes. Once the repository
records are in a central registry, the XSLT stylesheet for rendering the EAD
documents to HTML will reference the registry records
instead of the encoded information in the EADs.

  
The production utility site is hosted on a dedicated hardware server running
the Windows Server 2008 R2 Standard operating system. The
web server is Microsoft IIS 7 and the site software is written in Microsoft C#
and ASP.NET. Perl, PHP, Python, Javascript, and SQLite are
used as back-end scripts and support for some functions and can be used for
this project as well, if desired. The original development
environment was and continued support has been done with
Visual Studio 2010 Professional.

  
The source code for the utility site will be provided to the developer for
installation on an appropriate local server available to them, with the
expectation that the code for the repository registry will be developed
against this and then returned for integration into the production code
base. Documentation, both external to and within source
code, will be provided by the developer.

  
Repository records should contain the following fields:

• Name of repository with parent institution (e.g. Heritage Resources, Western
Washington University)

• Email

• URL of repository

• Phone number

• Fax number

• Complete mailing address: address, city, state, ZIP

• Narrative for planning an in-person research visit OR URL to website that
provides this information

• Narrative that provides an overview of collection and collection strengths
OR URL to website that provides this information

• Narrative that describes how researchers request copies OR URL to website
that provides this information

• Institutional logo

  
The data listed above has already been collected from NWDA members.

  
The repository records should be constructed such that they can be referenced
by XSLT stylesheets for display as the following EAD fields:

• Name of repository:

• Email, URL, phone, fax, address:  , each on separate

• Narratives: Display under each repository's name under "contact us" section
of website

  
The responsibility of the developer hired for this project will be to
implement the registry record user interface for data entry and the back-end
storage platform for the records. The NWDA database
administrator will take responsibility for the XSLT and finding aid retrieval
code modifications needed to use the repository records during finding aid
retrieval.

  
A non-propriety, open source solution should be used as the back-end storage
platform for the registry, if possible



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

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

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