Given:

a) FF is designed to handle web content, and does not provide security for external media types ( like streams, illustrator files, images, etc )

b) FF designed to manage 'current' content, as a archive it begins to get cumbersome

c) An external archive based upon file system storage and verity may be cheaper, quicker, and more scalable.  See Bobby.

d) Despite their desire to 'produce web content' such actions run counter to the FF philosophy, and doing so really means doubling their production effort.  Instead their content should marked up in a XML form or built from HTML-free database structure such that our sites can control the Look-n-Feel with their own style sheets, as could other customers of the SHNS.

e) The SHNS website is, in essence, a commerce site ( users register and pay for content, though this is only barely enforced at present )

Solve:

0) SHNS wants to get out of managing their website

1) SHNS wants to "produce" web content for the other sites

2) SHNS needs to work with large files from outside vendors

3) SHNS wants to get rid of their local archive

4) SHNS needs 'first dibs' on content destined for them

5) SHNS wants to streamline interaction between Scripps entities, including those not in FF

6) SHNS is out-scaling Cumulus, Mail Server and Photo Server

		  

Possible Solution:

i		 The SHNS should maintain a local drop zone for outside customers ( 2, 4 )

ii		The archive should be maintained in Knoxville ( 3, 5, 6, b, c )

iii	  The archive should feed into FF ( 0, 5, a, b, c, e )

iv		The SHNS should have a local content management solution tailored to their needs that will pull from the archive as needed and manage a local cache. ( 3, 4, 6, c )

vi		The SHNS staff should be given CMA access to a new site or to CORE itself, which was the original intent. ( 0, 1, !d )

vii	  The SHNS should be given access to new FF functionality for building packages ( 0, 1, !5, d )

viii	 The SHNS should maintain its own email for ingest of materials from outside sources ( 2, 4 )

ix		FF should be upgraded to enforce registration ( 0, e )

x		 SHNS should upgrade its Email infrstructure ( 2, 4, 6 )

xi		SHNS should upgrade its WAN connectivity ( 3, 4, 5 )

Old notes: ShnsContentFlow