Infrastructure

I agree the stylesheets (and everything else) should be in svn, but in my opinion live servers should be referring to locally cached copies of those for performance reasons -- we really don't want to be hitting SVN (or any other external web resource) for every search that is performed on the system. At a minimum it would be undesirable because it would be a single point of failure in the CN system.

This goes back to my original suggestion. use of static file names, so that any D1 application can use it. To summarize:
- use svn as a repository for the style sheets
- have a static location for these style sheets
- use static names for the style sheets (since svn keeps track of the changes, there is no real need to create dynamic names)

Update:

I forgot to mention that we have changed some strategy here, we are currently using the Drupal's iframe to display the header and footer and using local style sheet for the content specific styles.

Dave - you have already implemented the iframe in the Drupal site using the pilotcatalog that is running from the Mercury server (http://public-web.dataone.org/node/4). We can update the cn-dev pilotcatalog version with this change, then it can be used in the D1 Drupal as an iframe.

Please advice.

thanks!

1. Stylesheets should be stored in svn (somewhere under software/cicore/trunk/cn-buildout/dataone-cn-mercury )

2. The stylesheets should be incorporated into the CN deployment, along with the Mercury software as part of the dataone-cn-mercury package.

3. Since Mercury is only provided as a .war, there will need to be some package post-install processing to ensure that the stylesheets end up in the right place and/or Mercury is appropriately configured to use the stylesheets.

It is not clear to me if there is a properties file or perhaps a template that can be updated post-install.