Web and Mobile Portal Application Developer

Full Time
New York
Posted 7 months ago

We are looking to have a vendor help us build a multimedia web and mobile portal application.  Our requirements are:

  • Responsive interface design built on W3C standards for access through mobile devices (e.g. smartphones and tablets) and desktop computers with web access. File uploading capability and end-user functionality available in desktop and mobile environment.
  • Browser-based public access for searching and downloading approved content without the need for user accounts or other restrictions
  • Ability to accept submissions from the public for consideration
  • Ability to archive assets for internal viewing only as well as the ability to display assets publicly
  • Support for rich media assets including photos, music, videos, animations, podcasts and other multimedia content
  • Accommodates multiple user roles including admin, approver, uploader, and end user.
  • Solution must be hosted on-premise and compatible to run in VMWare Virtualization environment and run on Windows Server 2012 R2 Operating System.
  • Solution is open to indexing by search engines
  • Capable of full integration with Drupal and Sharepoint allowing complete data exchange between environments

For power users, administrators and content managers, application supports multi-factor authentication, Personal Identity Verification (PIV) card credentials, and can directly connect to Active Directory servers using LDAP protocol

  • Allows multi-level access configuration for administration based upon group, role, or device (e.g. power user, and end user roles). This role based user administration

Deliverables:

A. Admin interface and functions
  • Full admin functionality within a mobile environment either through an Apple iOS compatible browser or Apple iOS (i.e. iPhone or iPad) compatible app
  • Defined roles for users (e.g. “admin,” “approver,” “uploader”) with specific capabilities for each user role
  • Ability to provide workflow status tracking and notify proper users of outstanding tasks, for instance, to email approver of files awaiting approval
  • Ability to stage uploaded assets pending publication by the approver
  • Ability to create custom metadata fields and other identified file properties (such as filesize) as a precondition of file upload
  • Facilitates meta-tagging by providing drop down lists, auto-fill selections, etc.
  • Ability to embed commonly used metadata (e.g., photographer name) within image files upon download such that it is readable in commonly used photo editing software
  • Preserve embedded metadata on file upload and incorporate that metadata into the file record
  • Ability to make custom metadata available to search function
  • Supports batch uploading and meta-tagging
  • Ability to require supporting documents (e.g. caption files, copyright forms) on file upload for relevant files
  • Ability to link copyright release, likeness release, or other relevant documents and information (e.g. rights) to a specified asset
  • Ability to divide content into distinct collections or accounts, each with its own defined management process (e.g. specific uploaders, approvers, etc.). Collection size is limited only by total number of files in system
  • Ability to create groups of collections, for instance, to group field office collections into a regional collection
  • Provides usage analytics for individual assets or defined collections or groups of assets, including information about how, when, and where an asset was published/used
  • Allows administrators to monitor system use such as successful logins, access levels, timestamps, and records updated
  • Ability to retain, retrieve, and link previous versions of relevant files to provide an historical record, e.g. current and previous versions of a document file
  • Ability to identify duplicate files including the analysis of closeness of pixel data forimages
  • Ability to backup and restore media assets and metadata
  • Ability to export assets and metadata according to specified metadata, file properties, etc.
  • Ability to provide a designated outside end-user access to view a file and associated metadata that has been uploaded into the system but not yet added to the public collection (i.e., is still in the approval queue)
B. End-user interface and functions
  • Browser-based, mobile-friendly interface built on broadly accepted web standards
  • “Smart” search that allows for common misspellings, singular/plural noun forms, admingenerated synonyms, and promoted content.
  • Thumbnail preview of images/assets and associated metadata
  • Watermarking or other clear notice of copyrighted content
  • Access to full copyright restrictions and allowances, where applicable
  • Ability to download a given image rendered by the system in a specific resolution selected from a set of options (e.g. 800×600, 1200×800, original size)
  • Persistent user-friendly URLs for assets and search results
  • Ability to generate persistent shortened URLs for sharing media files
  • Preservation of embedded metadata upon download of files
  • Ability to select and share single or multiple images
C. Integration with other systems
  • Drupal

○ Integration between Drupal and the DAM allowing full access to all files and associated metadata and the ability to pass information between the two systems

  • SharePoint

○ Integration between Drupal and the DAM allowing full access to all files and associated metadata and the ability to pass information between the two systems

  • Flickr

○ Able to integrate with Flickr for manual, scheduled, and batch upload/download of images and associated metadata

  • Adobe Creative Cloud

○ Ability to receive and preserve XMP image metadata embedded into images using Photoshop and uploaded into/downloaded from DAM

  • Robust APIs to be utilized in other unspecified systems
  • Web Browsers

○ IE 11 (Microsoft Edge), Google Chrome (current stable release), Mozilla Firefox (current stable release), and Safari (current stable release)

○ DAM interface screens written to comply with W3C standards for broad browser support

  • ContentDM

○ Able to import media assets and metadata that are exported from Content DM in XML or CAB formats

○ The above is a one time requirement to export legacy images into the DAM solution procured through this solicitation

  • National Archives Records Management (NARA)

○ Ability to export records in accordance with National Archives Records Management (NARA) transfer guidance: https://www.archives.gov/recordsmgmt/ policy/transfer-guidance.html

  • Open Archives Initiative Protocol for Metadata Harvesting (OAI-PMH)

○ Ability to export records in accordance with Open Archives Initiative Protocol for Metadata Harvesting (OAI-PMH) implementation guidelines: https://www.openarchives.org/OAI/2.0/guidelines.htm

  • WorldCat

○ Integration with WorldShare for harvesting of records and making them searchable in WorldCat, allowing full access to all files and associated metadata

D. Architectural Requirements
  • The anticipated number of concurrent administrators is 12 or fewer. The anticipated number of users (uploaders and approvers) is 100 or less.

Quote Requirements:

Contractors can submit fixed price or hourly quotes for this work.  In order to be considered, your quote MUST contain a proposed solution AND a detailed architectural diagram showing how you would design the system.  The selection criteria for picking a vendor is based primarily on the quality of the proposed solution and architectural approach with price being a secondary factor.  In addition to vendors and companies, we would also consider working with single contractors that are either technical program/project managers or architects that can design this system.  All bidders, including single contractors, must provide a detailed proposed technical solution and architectural diagrams.

Job Features

Job CategoryWeb and Mobile Portal

Apply Online

A valid email address is required.
A valid phone number is required.