Business Sponsor and Organization

Andrew Odewahn

Feature Description

The Central Content Store provides a destination repository for all transformed content served through the Atlas Reader, SOLR API, or other content distribution related initiatives. 

Key requirements include:

• Storage support for Atlas HTML builds and EPUB.  
• Ability to store hierarchical content (i.e., folders) and not just flat structures.
• We should think about it as a S3/CloudDrive setup, where we can only get the content via HTTP. We need to figure out how this intersects with the API, and who does the caching, etc.

Non-Requirements include:

• Caching.  Caching and other performance related system will be handled at the application layer
• Direct content serving.  Content will not be served directly; it can only be served by a client app running on an attached server.

Success Criteria

To be a success, this project must:

• Store titles (EPUB or Atlas) that generate at 80% of revenue by the summer of 2014
• Store 80% of all HTMLBook or EPUB titles by Q4-2014
• Provide a central content repository that can serve the Full Content Search project
• Provide cost effective storage and bandwith

Maximum Level of Development Effort

Assuming we use AWS, this is a relatively straightforward to set up and will not require any development time.  We’ll need to take the appropriate security roles and settings.

Areas of Impact

Please X all areas of functionality that will need to be changed to incorporate this feature: