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:

Monospaced Font

LISTSERV Archives

LISTSERV Archives

CODE4LIB Home

CODE4LIB Home

CODE4LIB  August 2019

CODE4LIB August 2019

Subject:

Job: Developer for Archives Public User Interface at Hauser & Wirth Institute

From:

Code4Lib Jobs <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Fri, 30 Aug 2019 16:34:06 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (121 lines)




Request for Proposals

Project Title: Archives Public User Interface and Digital Object Viewer 

Hauser &amp; Wirth Institute requests proposals from developers to build a custom public user interface that extends the capabilities of the ArchivesSpace PUI. 

Purpose and Objectives of the Project

As part of its program to process artists’ archives and make them accessible, the Institute is undertaking a project to develop a public user interface to deliver digitized archival content to the public. As part of its processing of artists’ archives, HWI plans to make an initial 18,000 image files, as well as streaming media, accessible to researchers, and allow for ongoing future access to online content as the HWI program grows. The Institute plans to make the descriptive metadata and the digitized images accessible for use both by researchers familiar with archival finding aids, and by a general audience more familiar with a typical digital library application (e.g., Google Books).

HWI uses the web-based archives information management system ArchivesSpace, hosted by Lyrasis, to describe the collection using standard practices. The Institute digitizes archival materials corresponding primarily to folder-level “archival object” records in ArchivesSpace, and is committed to repurposing this archival metadata as a practical and efficient approach to publishing large amounts of images online for the broader public. Digitized content follows filename conventions that will allow them to be matched to the ArchivesSpace records we create. 

Our expectation is that both experienced scholars who rely on standard finding aids, and a general public more used to a typical “digital library”, may be served by a single public user interface. To achieve this, we are looking for a developer to 1) create an ArchivesSpace plugin that extends the built-in ArchivesSpace public user interface and search index, as well as 2) an ancillary digital object rendering service that can provide an image-viewer (which will be embedded in the public user interface). We will favor proposals that provide a solution that will allow us to store and serve large format image files with minimal maintenance; a hosting plan is not required but will make a proposal stronger.

About Hauser &amp; Wirth Institute 

Hauser &amp; Wirth Institute is a nonprofit, 501(c)(3) private operating foundation dedicated to art historical scholarship and to the preservation and accessibility of artists’ archives.

Under the guidance of its Board of Directors and Advisory Board, the Institute was established to:

build a public study center for artists’ archival materials in New York City and make these resources available for primary document research and digitally online
nurture innovation and substance in art historical research primarily through the funding of fellowships in partnership with academic and archive-based institutions
produce online catalogues raisonnés and print publications that advance the highest academic standards to strengthen the field of art history
initiate programs to inform a public conversation about the obligations and opportunities inherent in archive stewardship

Project Requirements

Customized public user interface for viewing archival data and digital objects. 
The interface must support research by presenting the collection as a structured tree of metadata and inline visual representations ("embedded digital objects") - i.e., as an online "finding aid" allowing researchers to go up and down a hierarchy and view / expand object representations in the context of this intellectual arrangement. This should be achievable through customizations of the ArchivesSpace public user interface, most significantly with the addition of expandable embedded digital object players (see below).User can peruse the entire archival collection using the scrolling idiom and structure of traditional EAD finding aids, as with the current ArchivesSpace public user interface. Scrolling may be replaced with collapsing / expanding navigation - see Smithsonian Archives of American Art site.

The interface should also support browsing by generalists and researchers who are unaccustomed to archival arrangement and primarily interested in viewing digitized material. In other words, the interface should function as a "digital library" of digital objects that can be browsed, searched, and viewed ("play", "rewind", "turn page", etc.). It is expected that the search functionality can be powered by the existing ArchivesSpace Solr index with minimal customization, and that "Digital Objects" would be added to the top-level navigation in the public user interface. A user clicking on "Digital Objects" would see a grid of visual and text search results (thumbnail image, title, etc) and would be able to search / filter these. Customizations to the ArchivesSpace indexer may be required to enable searching on these digital objects using folder and item-level metadata.
Digital object viewer(s) requirements
Digital objects must be viewable inline in the "research view" (1.1) and as individual objects (pages) in the "digital library view" (1.2).
Viewer must support a variety of digital objects: photographs, notebooks, videos.
User can page back and forth between sequential images within a digital object representation of a bound item (e.g., a notebook).
User can use zoom and pan controls to examine individual high resolution images. True zooming will require an image server which can dynamically serve “tiles” of an image at different resolutions as the user pans and zooms. An IIIF-compliant server and client library are recommended.
User can play / stop digital object representations of moving image objects (e.g., video).




Auto-Populating Digital Object RecordsIn addition to developing the public user interface and digital object viewer, the contractor will need to auto-populate digital object records in ArchivesSpace, and auto-link digital objects to archival object records (either folder or item level, depending on the object type and the granularity of description).
Photographs / documents. There will be 1 digital object record for each digitized photograph or document (approx 18,000). A digital object record representing a document may correspond to an item-level node in the intellectual hierarchy, or several may correspond to a single folder. (I.e., some items will be individually cataloged, while most will be cataloged at the less granular "folder" level.)  Both scenarios should be supported. A search in the "digital library" on metadata from a folder-level description should return all the photographs in the folder. In the "finding aid" view, it should be possible to expand or overlay a viewer showing all the photographs in a folder.
Notebooks. There will be 1 digital object record for each digitized notebook (currently approximately 15 notebooks, 800 pages total). A digital object representing a notebook may correspond to a folder or item-level node in the intellectual hierarchy. A notebook should appear as a single item in the digital library view, and as an expandable or modal overlay in the finding aid view.
Video / audio. There will be 1 digital object record for each digitized video or audio file (number of files TBD). As above, the video should be playable from the finding aid view, and should appear as a single object in the library view. 



Ongoing digitizationResponses should include a plan that will allow for future digitization and publication of additional digital objects. At a minimum, project deliverables should include documentation clearly explaining how additional batches of content can be processed into digital objects and digital object records.

User Interface and Graphic Design
Responses should include wireframe sketches showing the basic page layout for the finding aid view with expandable embedded digital objects, for the digital library search results, and for digital objects as stand-alone resources within the digital library view.
Responses including graphic design treatments (color palette, fonts, etc.) are welcome, but separate responses for design and development are expected and acceptable.


Non-functional Requirements
The viewer should be built using open-source tools and software libraries, and a language (e.g., Ruby, Python) and framework (e.g., Ruby on Rails, Django) should be chosen with consideration for breadth of adoption, ease of maintenance, and alignment with best practices and patterns within the cultural heritage community. All things being equal, a framework written in Ruby, Python, Javascript, or PHP would be typical. Given the choice of Ruby and Javascript by ArchivesSpace, these languages ought to be preferred if possible.
The viewer should be easy to deploy on a commercial application hosting service - or, alternatively, embeddable in the ArchivesSpace plugin.


Project management and plan of work
Responses should include a high-level plan of work and project timeline.
Responses should include a project management plan which includes multiple iterations based on client feedback.



Timeline

September 20: Proposals are due

October 4: Developer is selected and notified

October 15: Work begins

December 15: Delivery and demonstration of working code meeting all project requirements

Hard Finish: March 15, 2019 

Instructions

RFP Contact Person: Lisa Darms, Senior Archivist

[log in to unmask]

All inquiries questions should be sent via email to the RFP contact --  no phone calls will be accepted.

The deadline for proposal is 11:00 P.M. Eastern Time on September 20, 2019. Proposals must be submitted electronically to the RFP contact person listed above with a subject line of “RFP – 2019”. Proposals must be Adobe PDF or Microsoft Word documents.

Proposal Requirements

Proposals should include the following

Relevant experience with ArchivesSpace, Solr, and online finding aids.
Wireframes showing 1) collection of digital objects presented as a digital library 2) presentation of a digital object with controls for IIIF image interactivity 3) presentation of digital object inline as part of the finding aid view
Proposed technologies (language, framework, etc.)
Strategy for serving digital objects, esp. tile-based hi-res images. 
Project management plan. 
Work plan and cost.
Itemized list of deliverables.
Separate / optional maintenance plan and cost, including cost of hosting and serving digital objects.
Examples of relevant former projects and/or references from former clients.

Conditions of the Project

Vendor is responsible for the contents of its proposal and for satisfying the requirements set forth in the RFP. The vendor is expected to comply with the true intention of this RFP and shall not take advantage of any errors or omissions in the description of the requested services. The successful vendor and all subcontractors hired by them must comply with all applicable laws. 

Cost of Preparing Proposal 

The cost of developing and submitting the proposal is entirely the responsibility of the vendor, including costs related to preparing and submitting the proposal, negotiating a contract, and other costs associated with the RFP.

Preparation of Proposal

HWI has the right to rely on any information and price quotes provided by vendors. The vendor shall be responsible for any errors in quotes. 


----
Brought to you by code4lib jobs: https://jobs.code4lib.org/jobs/36814-developer-for-archives-public-user-interface

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

March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
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