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:

Re: Job: PBCore Cataloging Tool Development Contractor at WGBH Educational Foundation

From:

Rebecca Fraimow <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Mon, 28 Aug 2017 17:07:27 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (1 lines)

Hi all,

As an FYI, we  are extending the deadline to send us an RFP for the PBCore Cataloging Tool Development. We will now be accepting proposals through September 6th.

Thanks!

Best,
Rebecca Fraimow, WGBH

On 8/7/17, 9:37 PM, "Code for Libraries on behalf of Code4Lib Jobs" <[log in to unmask] on behalf of [log in to unmask]> wrote:

    PBCore Cataloging Tool Development RFP
    
    WGBH Educational Foundation
    
    August 1, 2017
    
    I. Project Overview
    
    WGBH is seeking a qualified developer or development team (“the Contractor”) to create a Ruby-based web application tool for the American Archive of Public Broadcasting’s PBCore Development and Training Project. 
    
    The goal of the National Endowment for the Humanities-funded PBCore Development and Training Project is to develop tools, methodologies, workflows and training to enhance and extend the adoption of the Public Broadcasting Metadata Dictionary (“PBCore”), a metadata schema for the management of audio and audiovisual collections.
    
    PBCore can be used as:
    
    A guideline for cataloging or describing audiovisual content (as a content standard)
    A model for building custom databases/applications
    A guideline for identifying a set of vocabularies for fields describing av assets
    A data model for a configurable collection management system (Omeka, Collective Access, etc.)
    A guideline for creating inventory spreadsheets
    An exchange (import or export) mechanism between applications 
    
    PBCore records can easily be shared, allowing information about media assets and collections to be exchanged between organizations and media systems.
    
    Public Broadcasting in the United States developed PBCore so producers and local stations can better share, manage and preserve the media they produce. Because it is so useful in describing media assets, a growing number of film archives and media organizations outside of public broadcasting have adopted PBCore to manage their audiovisual assets and collections. PBCore is used by the American Archive of Public Broadcasting as an exchange format and data model for metadata about public broadcasting collections.
    
    As part of the NEH project, WGBH seeks to create an open-source graphical user interface (“GUI”) cataloging tool. We envision the tool as a simple GUI built in Ruby. The tool will have a function that allows for creation, editing, import and export of PBCoreXML 2.1 documents (and CSVs formatted in accordance with a PBCore data model), which are then stored externally to the app. The tool will also allow for search and discovery of the stored XML documents. The tool should be easy to implement and use by novice and experienced PBCore users.
    
    II. Project Activities
    
    a. Process overview
    
    i.               WGBH will provide contractor with background materials and preliminary requirements for the app development, including information about the metadata structure of PBCore, existing PBCore tools, and the prototype Filemaker-based tool.
    
    ii.              Contractor will create a work plan and more detailed proposal for the product based on the background materials.
    
    iii.            The work plan and detailed proposal will be discussed and approved in a meeting with WGBH staff, launching a six-month development phase.
    
    iv.            Over the course of the development phase, contractor will perform weekly code review with WGBH in-house developers to assure that WGBH development staff are comfortable and familiar with the tool.
    
    v.              Contractor will hold bi-weekly update meetings with WGBH project staff to demo development and discuss direction of the project. 
    
    vi.            After the six-month development phase, WGBH staff will demo tool with Test User group for review and feedback.
    
    vii.           WGBH will share feedback with contractor and jointly determine a proposal for a further three months of development based on user feedback and feasibility.
    
    viii.         After the second development phase, all code and documentation will be turned over to WGBH for release under an MIT Open Source license.  
    
    b. Project Requirements/Desired Features
    
    Required:
    
    User can easily install the tool.
    User can easily create a new PBCore XML document.
    User can add any PBCore XML attribute or element that is allowed to an existing document.
    User can see definitions of each element incorporated into the tool.
    User can see options for elements or attributes to add to an existing document.
    User can import pre-existing batch or single PBCore XML.
    User can export batch or single PBCore XML.
    User can import PBCore-compliant CSV.
    User can export PBCore-compliant CSV.
    User can view created XML documents.
    User can conduct a keyword search across fields in XML documents.
    User can perform a complex search based on values of two elements or more.
    User can edit pre-existing records.
    User can see PBCore controlled vocabularies as drop-down options for elements and attributes.
    User is notified when PBCore document is invalid.
    User can batch add a value in a specific element or attribute to all records in a found set.
    
    III. Proposed Timeline 
    
    We expect preliminary planning to be completed by October 15th, 2017, though this timeline may be extended depending on the length of the hiring process for the contractor. The primary development phase should be completed by March 30th, 2018. User testing will be conducted in April 2018, and the final product should be delivered by July 2018.
    
    IV. Application Process
    
    When selecting an developer or development team for this project, we will be evaluating candidates on the following criteria:
    
    Required experience
    
    Previous experience creating applications in Ruby or similar programming language
    Familiarity with XML creation and editing 
    
    Preferred experience
    
    Experience with XML-based metadata standards such as PBCore, Dublin Core, VRA Core
    Experience in developing applications for cultural heritage organizations
    
    Proposals should consist of a letter of interest, not to exceed 4 pages, including contact information, summary of qualifications, a fairly detailed quote of time, workscope, and a fixed price quote.
    
    Eligibility for the contract is restricted to U.S. citizens or people with valid visas. Activities may be performed remotely.
    
    Proposals should be submitted by August 30th to Rebecca Fraimow at [log in to unmask] Finalists will be notified of their status by September 15th.
    
    
    ----
    Brought to you by code4lib jobs: https://jobs.code4lib.org/jobs/27747-pbcore-cataloging-tool-development-contractor
    

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

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