OPeNDAP Documentation - User contributions [en]

Hyrax Customization user manual

2010-07-15T21:37:35Z

Rduncan: /* Image Files */

= Web page customization =

Hyrax can be easily customized to fit the end users needs. The public "face" of Hyrax can be easily modified to match an organizations look and feel. Almost all of the web pages can be completely customized by the site administrator by editing a combination of HTML, Image, and CSS files.

== Where to make the changes ==

All of the default versions of the HTML, Image, and CSS files come bundled with Hyrax in the ''$CATALINA_HOME/webapps/opendap/docs'' directory. $CATALINA_HOME is the directory that you installed tomcat in. If you did the default install of tomcat, your $CATALINA_HOME will be "/usr/local/apache-tomcat-6.x.x".

CD to you $CATALINA_HOME directory (again default would look like (on Linux machine): cd /usr/local/apache-tomcat-6.x.x) (The -6.x.x is the version number of tomcat you are running, ex. if you are running tomcat 6.0.24 then it would be just that.)

Make a new directory $CATALINA_HOME/content/opendap/docs/. (This would be: mkdir content, cd content, mkdir opendap ...)

Copy (do not move) the files in $CATALINA_HOME/webapps/opendap/docs to $CATALINA_HOME/content/opendap/docs by using:
cp -r $CATALINA_HOME/webapps/opendap/docs/ $CATALINA_HOME/content/opendap/docs/

;Warning: ''Do NOT remove files from this new directory (Or the old one for that matter). Each file, in its location, is required by Hyrax. You can make changes to the files but you should not rename or remove them.''

'''The rest of these instructions are written with the assumption that a copy of the ''docs'' directory has been made as described above.'''

== What to change ==

=== HTML Files ===
The HTML files provide the static content of a Hyrax server.
{|
|File
|      
|Location
|      
|Description
|-
| '''index.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| The documentation web page for the top level of Hyrax. As shipped it contains a description of Hyrax and links to documentation and funders. The contents.html pages (aka the OPeNDAP directories) links to this document. 
|-
| '''error400.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| Contains the default error page that Hyrax will return when the client request generates a '''Bad Request''' error (Associated with an HTML status of 400) 
|-
| '''error403.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| Contains the default error page that Hyrax will return when the client request generates a '''Forbidden''' error. (Associated with an HTML status of 403) 
|-
| '''error404.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| Contains the default error page that Hyrax will return when the client request generates a '''Not Found''' error. (Associated with an HTML status of 404) 
|-
| '''error500.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| Contains the default error page that Hyrax will return when the client request generates an '''Internal Server Error'''. (Associated with an HTML status of 500) 
|-
| '''error501.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| Contains the default error page that Hyrax will return when the client request generates an '''Not Implemented'''. (Associated with an HTML status of 501) 
|-
| '''error502.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| Contains the default error page that Hyrax will return when the client request generates an '''Bad Gateway'''. (Associated with an HTML status of 502) 
|-
|}
=== CSS Files ===

{|
|File
|      
|Location
|      
|Description
|-
| '''contents.css'''
|
| ''$CATALINA_HOME/content/opendap/docs/css''
|
| The contents.css style sheet provides the default colors and fonts used in the Hyrax site. It is referenced by all of the HTML and XSL files to coordinate the visual aspects of the site. 
|-
| '''thredds.css'''
|
| ''$CATALINA_HOME/content/opendap/docs/css''
|
| The thredds.css style sheet provides the default colors and fonts used by the THREDDS component of Hyrax. 
|-
|}
=== Image Files ===

There are a number of image files shipped with Hyrax. Simply replacing key image files will allow you to customize the icons and logos associated with the Hyrax server.
{|
|File
|      
|Location
|      
|Description
|-
| '''logo.gif'''
|
| ''$CATALINA_HOME/content/opendap/docs/images''
|
| Main Logo for the directory view (produced by contents.css and contents.xsl)
|-
| '''favicon.ico'''
|
| ''$CATALINA_HOME/content/opendap/docs/images''
|
| The cute little icon preceding the URL in the address bar of your browser. To be used this file needs to be installed into Tomcat:cp -r $CATALINA_HOME/webapps/opendap/docs/images/favicon.ico to $CATALINA_HOME/webapps/ROOT/ (OR this is where you can pick another image of your choosing and place in this directory.)
|-
| '''BadDapRequest.gif, BadGateway.png, favicon.ico, folder.png, forbidden.png, largeEarth.jpg, logo.gif, nasa-logo.jpg, noaa-logo.jpg, nsf-logo.png, smallEarth.jpg, sml-folder.png, superman.jpg'''
|
| ''$CATALINA_HOME/content/opendap/docs/images''
|
| These files are referenced by the default collection of web content files (described above) that ship with Hyrax.
|}

Hyrax Customization user manual

2010-07-15T21:36:05Z

Rduncan: /* Image Files */

= Web page customization =

Hyrax can be easily customized to fit the end users needs. The public "face" of Hyrax can be easily modified to match an organizations look and feel. Almost all of the web pages can be completely customized by the site administrator by editing a combination of HTML, Image, and CSS files.

== Where to make the changes ==

All of the default versions of the HTML, Image, and CSS files come bundled with Hyrax in the ''$CATALINA_HOME/webapps/opendap/docs'' directory. $CATALINA_HOME is the directory that you installed tomcat in. If you did the default install of tomcat, your $CATALINA_HOME will be "/usr/local/apache-tomcat-6.x.x".

CD to you $CATALINA_HOME directory (again default would look like (on Linux machine): cd /usr/local/apache-tomcat-6.x.x) (The -6.x.x is the version number of tomcat you are running, ex. if you are running tomcat 6.0.24 then it would be just that.)

Make a new directory $CATALINA_HOME/content/opendap/docs/. (This would be: mkdir content, cd content, mkdir opendap ...)

Copy (do not move) the files in $CATALINA_HOME/webapps/opendap/docs to $CATALINA_HOME/content/opendap/docs by using:
cp -r $CATALINA_HOME/webapps/opendap/docs/ $CATALINA_HOME/content/opendap/docs/

;Warning: ''Do NOT remove files from this new directory (Or the old one for that matter). Each file, in its location, is required by Hyrax. You can make changes to the files but you should not rename or remove them.''

'''The rest of these instructions are written with the assumption that a copy of the ''docs'' directory has been made as described above.'''

== What to change ==

=== HTML Files ===
The HTML files provide the static content of a Hyrax server.
{|
|File
|      
|Location
|      
|Description
|-
| '''index.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| The documentation web page for the top level of Hyrax. As shipped it contains a description of Hyrax and links to documentation and funders. The contents.html pages (aka the OPeNDAP directories) links to this document. 
|-
| '''error400.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| Contains the default error page that Hyrax will return when the client request generates a '''Bad Request''' error (Associated with an HTML status of 400) 
|-
| '''error403.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| Contains the default error page that Hyrax will return when the client request generates a '''Forbidden''' error. (Associated with an HTML status of 403) 
|-
| '''error404.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| Contains the default error page that Hyrax will return when the client request generates a '''Not Found''' error. (Associated with an HTML status of 404) 
|-
| '''error500.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| Contains the default error page that Hyrax will return when the client request generates an '''Internal Server Error'''. (Associated with an HTML status of 500) 
|-
| '''error501.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| Contains the default error page that Hyrax will return when the client request generates an '''Not Implemented'''. (Associated with an HTML status of 501) 
|-
| '''error502.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| Contains the default error page that Hyrax will return when the client request generates an '''Bad Gateway'''. (Associated with an HTML status of 502) 
|-
|}
=== CSS Files ===

{|
|File
|      
|Location
|      
|Description
|-
| '''contents.css'''
|
| ''$CATALINA_HOME/content/opendap/docs/css''
|
| The contents.css style sheet provides the default colors and fonts used in the Hyrax site. It is referenced by all of the HTML and XSL files to coordinate the visual aspects of the site. 
|-
| '''thredds.css'''
|
| ''$CATALINA_HOME/content/opendap/docs/css''
|
| The thredds.css style sheet provides the default colors and fonts used by the THREDDS component of Hyrax. 
|-
|}
=== Image Files ===

There are a number of image files shipped with Hyrax. Simply replacing key image files will allow you to customize the icons and logos associated with the Hyrax server.
{|
|File
|      
|Location
|      
|Description
|-
| '''logo.gif'''
|
| ''$CATALINA_HOME/content/opendap/docs/images''
|
| Main Logo for the directory view (produced by contents.css and contents.xsl)
|-
| '''favicon.ico'''
|
| ''$CATALINA_HOME/content/opendap/docs/images''
|
| The cute little icon preceding the URL in the address bar of your browser. To be used this file needs to be installed into Tomcat:

| cp -r $CATALINA_HOME/webapps/opendap/docs/images/favicon.ico to $CATALINA_HOME/webapps/ROOT/ (OR this is where you can pick another image of your choosing and place in this directory.)
|-
| '''BadDapRequest.gif, BadGateway.png, favicon.ico, folder.png, forbidden.png, largeEarth.jpg, logo.gif, nasa-logo.jpg, noaa-logo.jpg, nsf-logo.png, smallEarth.jpg, sml-folder.png, superman.jpg'''
|
| ''$CATALINA_HOME/content/opendap/docs/images''
|
| These files are referenced by the default collection of web content files (described above) that ship with Hyrax.
|}

Hyrax Customization user manual

2010-07-15T21:35:08Z

Rduncan: /* Image Files */

= Web page customization =

Hyrax can be easily customized to fit the end users needs. The public "face" of Hyrax can be easily modified to match an organizations look and feel. Almost all of the web pages can be completely customized by the site administrator by editing a combination of HTML, Image, and CSS files.

== Where to make the changes ==

All of the default versions of the HTML, Image, and CSS files come bundled with Hyrax in the ''$CATALINA_HOME/webapps/opendap/docs'' directory. $CATALINA_HOME is the directory that you installed tomcat in. If you did the default install of tomcat, your $CATALINA_HOME will be "/usr/local/apache-tomcat-6.x.x".

CD to you $CATALINA_HOME directory (again default would look like (on Linux machine): cd /usr/local/apache-tomcat-6.x.x) (The -6.x.x is the version number of tomcat you are running, ex. if you are running tomcat 6.0.24 then it would be just that.)

Make a new directory $CATALINA_HOME/content/opendap/docs/. (This would be: mkdir content, cd content, mkdir opendap ...)

Copy (do not move) the files in $CATALINA_HOME/webapps/opendap/docs to $CATALINA_HOME/content/opendap/docs by using:
cp -r $CATALINA_HOME/webapps/opendap/docs/ $CATALINA_HOME/content/opendap/docs/

;Warning: ''Do NOT remove files from this new directory (Or the old one for that matter). Each file, in its location, is required by Hyrax. You can make changes to the files but you should not rename or remove them.''

'''The rest of these instructions are written with the assumption that a copy of the ''docs'' directory has been made as described above.'''

== What to change ==

=== HTML Files ===
The HTML files provide the static content of a Hyrax server.
{|
|File
|      
|Location
|      
|Description
|-
| '''index.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| The documentation web page for the top level of Hyrax. As shipped it contains a description of Hyrax and links to documentation and funders. The contents.html pages (aka the OPeNDAP directories) links to this document. 
|-
| '''error400.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| Contains the default error page that Hyrax will return when the client request generates a '''Bad Request''' error (Associated with an HTML status of 400) 
|-
| '''error403.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| Contains the default error page that Hyrax will return when the client request generates a '''Forbidden''' error. (Associated with an HTML status of 403) 
|-
| '''error404.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| Contains the default error page that Hyrax will return when the client request generates a '''Not Found''' error. (Associated with an HTML status of 404) 
|-
| '''error500.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| Contains the default error page that Hyrax will return when the client request generates an '''Internal Server Error'''. (Associated with an HTML status of 500) 
|-
| '''error501.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| Contains the default error page that Hyrax will return when the client request generates an '''Not Implemented'''. (Associated with an HTML status of 501) 
|-
| '''error502.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| Contains the default error page that Hyrax will return when the client request generates an '''Bad Gateway'''. (Associated with an HTML status of 502) 
|-
|}
=== CSS Files ===

{|
|File
|      
|Location
|      
|Description
|-
| '''contents.css'''
|
| ''$CATALINA_HOME/content/opendap/docs/css''
|
| The contents.css style sheet provides the default colors and fonts used in the Hyrax site. It is referenced by all of the HTML and XSL files to coordinate the visual aspects of the site. 
|-
| '''thredds.css'''
|
| ''$CATALINA_HOME/content/opendap/docs/css''
|
| The thredds.css style sheet provides the default colors and fonts used by the THREDDS component of Hyrax. 
|-
|}
=== Image Files ===

There are a number of image files shipped with Hyrax. Simply replacing key image files will allow you to customize the icons and logos associated with the Hyrax server.
{|
|File
|      
|Location
|      
|Description
|-
| '''logo.gif'''
|
| ''$CATALINA_HOME/content/opendap/docs/images''
|
| Main Logo for the directory view (produced by contents.css and contents.xsl)
|-
| '''favicon.ico'''
|
| ''$CATALINA_HOME/content/opendap/docs/images''
|
| The cute little icon preceding the URL in the address bar of your browser. To be used this file needs to be installed into Tomcat:
cp -r $CATALINA_HOME/webapps/opendap/docs/images/favicon.ico to $CATALINA_HOME/webapps/ROOT/ (OR this is where you can pick another image of your choosing and place in this directory.)
|-
| '''BadDapRequest.gif, BadGateway.png, favicon.ico, folder.png, forbidden.png, largeEarth.jpg, logo.gif, nasa-logo.jpg, noaa-logo.jpg, nsf-logo.png, smallEarth.jpg, sml-folder.png, superman.jpg'''
|
| ''$CATALINA_HOME/content/opendap/docs/images''
|
| These files are referenced by the default collection of web content files (described above) that ship with Hyrax.
|}

Hyrax Customization user manual

2010-07-15T21:33:09Z

Rduncan: /* Image Files */

= Web page customization =

Hyrax can be easily customized to fit the end users needs. The public "face" of Hyrax can be easily modified to match an organizations look and feel. Almost all of the web pages can be completely customized by the site administrator by editing a combination of HTML, Image, and CSS files.

== Where to make the changes ==

All of the default versions of the HTML, Image, and CSS files come bundled with Hyrax in the ''$CATALINA_HOME/webapps/opendap/docs'' directory. $CATALINA_HOME is the directory that you installed tomcat in. If you did the default install of tomcat, your $CATALINA_HOME will be "/usr/local/apache-tomcat-6.x.x".

CD to you $CATALINA_HOME directory (again default would look like (on Linux machine): cd /usr/local/apache-tomcat-6.x.x) (The -6.x.x is the version number of tomcat you are running, ex. if you are running tomcat 6.0.24 then it would be just that.)

Make a new directory $CATALINA_HOME/content/opendap/docs/. (This would be: mkdir content, cd content, mkdir opendap ...)

Copy (do not move) the files in $CATALINA_HOME/webapps/opendap/docs to $CATALINA_HOME/content/opendap/docs by using:
cp -r $CATALINA_HOME/webapps/opendap/docs/ $CATALINA_HOME/content/opendap/docs/

;Warning: ''Do NOT remove files from this new directory (Or the old one for that matter). Each file, in its location, is required by Hyrax. You can make changes to the files but you should not rename or remove them.''

'''The rest of these instructions are written with the assumption that a copy of the ''docs'' directory has been made as described above.'''

== What to change ==

=== HTML Files ===
The HTML files provide the static content of a Hyrax server.
{|
|File
|      
|Location
|      
|Description
|-
| '''index.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| The documentation web page for the top level of Hyrax. As shipped it contains a description of Hyrax and links to documentation and funders. The contents.html pages (aka the OPeNDAP directories) links to this document. 
|-
| '''error400.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| Contains the default error page that Hyrax will return when the client request generates a '''Bad Request''' error (Associated with an HTML status of 400) 
|-
| '''error403.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| Contains the default error page that Hyrax will return when the client request generates a '''Forbidden''' error. (Associated with an HTML status of 403) 
|-
| '''error404.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| Contains the default error page that Hyrax will return when the client request generates a '''Not Found''' error. (Associated with an HTML status of 404) 
|-
| '''error500.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| Contains the default error page that Hyrax will return when the client request generates an '''Internal Server Error'''. (Associated with an HTML status of 500) 
|-
| '''error501.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| Contains the default error page that Hyrax will return when the client request generates an '''Not Implemented'''. (Associated with an HTML status of 501) 
|-
| '''error502.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| Contains the default error page that Hyrax will return when the client request generates an '''Bad Gateway'''. (Associated with an HTML status of 502) 
|-
|}
=== CSS Files ===

{|
|File
|      
|Location
|      
|Description
|-
| '''contents.css'''
|
| ''$CATALINA_HOME/content/opendap/docs/css''
|
| The contents.css style sheet provides the default colors and fonts used in the Hyrax site. It is referenced by all of the HTML and XSL files to coordinate the visual aspects of the site. 
|-
| '''thredds.css'''
|
| ''$CATALINA_HOME/content/opendap/docs/css''
|
| The thredds.css style sheet provides the default colors and fonts used by the THREDDS component of Hyrax. 
|-
|}
=== Image Files ===

There are a number of image files shipped with Hyrax. Simply replacing key image files will allow you to customize the icons and logos associated with the Hyrax server.
{|
|File
|      
|Location
|      
|Description
|-
| '''logo.gif'''
|
| ''$CATALINA_HOME/content/opendap/docs/images''
|
| Main Logo for the directory view (produced by contents.css and contents.xsl)
|-
| '''favicon.ico'''
|
| ''$CATALINA_HOME/content/opendap/docs/images''
|
| The cute little icon preceding the URL in the address bar of your browser. To be used this file needs to be installed into Tomcat:
| cp -r $CATALINA_HOME/webapps/opendap/docs/images/favicon.ico to $CATALINA_HOME/webapps/ROOT/ (OR this is where you can pick another image of your choosing and place in this directory.)
|-
| '''BadDapRequest.gif, BadGateway.png, favicon.ico, folder.png, forbidden.png, largeEarth.jpg, logo.gif, nasa-logo.jpg, noaa-logo.jpg, nsf-logo.png, smallEarth.jpg, sml-folder.png, superman.jpg'''
|
| ''$CATALINA_HOME/content/opendap/docs/images''
|
| These files are referenced by the default collection of web content files (described above) that ship with Hyrax.
|}

Hyrax Customization user manual

2010-07-15T21:30:54Z

Rduncan: /* Image Files */

= Web page customization =

Hyrax can be easily customized to fit the end users needs. The public "face" of Hyrax can be easily modified to match an organizations look and feel. Almost all of the web pages can be completely customized by the site administrator by editing a combination of HTML, Image, and CSS files.

== Where to make the changes ==

All of the default versions of the HTML, Image, and CSS files come bundled with Hyrax in the ''$CATALINA_HOME/webapps/opendap/docs'' directory. $CATALINA_HOME is the directory that you installed tomcat in. If you did the default install of tomcat, your $CATALINA_HOME will be "/usr/local/apache-tomcat-6.x.x".

CD to you $CATALINA_HOME directory (again default would look like (on Linux machine): cd /usr/local/apache-tomcat-6.x.x) (The -6.x.x is the version number of tomcat you are running, ex. if you are running tomcat 6.0.24 then it would be just that.)

Make a new directory $CATALINA_HOME/content/opendap/docs/. (This would be: mkdir content, cd content, mkdir opendap ...)

Copy (do not move) the files in $CATALINA_HOME/webapps/opendap/docs to $CATALINA_HOME/content/opendap/docs by using:
cp -r $CATALINA_HOME/webapps/opendap/docs/ $CATALINA_HOME/content/opendap/docs/

;Warning: ''Do NOT remove files from this new directory (Or the old one for that matter). Each file, in its location, is required by Hyrax. You can make changes to the files but you should not rename or remove them.''

'''The rest of these instructions are written with the assumption that a copy of the ''docs'' directory has been made as described above.'''

== What to change ==

=== HTML Files ===
The HTML files provide the static content of a Hyrax server.
{|
|File
|      
|Location
|      
|Description
|-
| '''index.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| The documentation web page for the top level of Hyrax. As shipped it contains a description of Hyrax and links to documentation and funders. The contents.html pages (aka the OPeNDAP directories) links to this document. 
|-
| '''error400.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| Contains the default error page that Hyrax will return when the client request generates a '''Bad Request''' error (Associated with an HTML status of 400) 
|-
| '''error403.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| Contains the default error page that Hyrax will return when the client request generates a '''Forbidden''' error. (Associated with an HTML status of 403) 
|-
| '''error404.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| Contains the default error page that Hyrax will return when the client request generates a '''Not Found''' error. (Associated with an HTML status of 404) 
|-
| '''error500.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| Contains the default error page that Hyrax will return when the client request generates an '''Internal Server Error'''. (Associated with an HTML status of 500) 
|-
| '''error501.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| Contains the default error page that Hyrax will return when the client request generates an '''Not Implemented'''. (Associated with an HTML status of 501) 
|-
| '''error502.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| Contains the default error page that Hyrax will return when the client request generates an '''Bad Gateway'''. (Associated with an HTML status of 502) 
|-
|}
=== CSS Files ===

{|
|File
|      
|Location
|      
|Description
|-
| '''contents.css'''
|
| ''$CATALINA_HOME/content/opendap/docs/css''
|
| The contents.css style sheet provides the default colors and fonts used in the Hyrax site. It is referenced by all of the HTML and XSL files to coordinate the visual aspects of the site. 
|-
| '''thredds.css'''
|
| ''$CATALINA_HOME/content/opendap/docs/css''
|
| The thredds.css style sheet provides the default colors and fonts used by the THREDDS component of Hyrax. 
|-
|}
=== Image Files ===

There are a number of image files shipped with Hyrax. Simply replacing key image files will allow you to customize the icons and logos associated with the Hyrax server.
{|
|File
|      
|Location
|      
|Description
|-
| '''logo.gif'''
|
| ''$CATALINA_HOME/content/opendap/docs/images''
|
| Main Logo for the directory view (produced by contents.css and contents.xsl)
|-
| '''favicon.ico'''
|
| ''$CATALINA_HOME/content/opendap/docs/images''
|
| The cute little icon preceding the URL in the address bar of your browser. To be used this file needs to be installed into Tomcat:
cp -r $CATALINA_HOME/webapps/opendap/docs/images/favicon.ico to $CATALINA_HOME/webapps/ROOT/ (OR this is where you can pick another image of your choosing and place in this directory.)

[http://docs.opendap.org/index.php/Hyrax_-_Installation_Instructions#Miscellaneous as described here]
|-
| '''BadDapRequest.gif, BadGateway.png, favicon.ico, folder.png, forbidden.png, largeEarth.jpg, logo.gif, nasa-logo.jpg, noaa-logo.jpg, nsf-logo.png, smallEarth.jpg, sml-folder.png, superman.jpg'''
|
| ''$CATALINA_HOME/content/opendap/docs/images''
|
| These files are referenced by the default collection of web content files (described above) that ship with Hyrax.
|}

Hyrax Customization user manual

2010-07-15T20:44:33Z

Rduncan: /* Web page customization */

= Web page customization =

Hyrax can be easily customized to fit the end users needs. The public "face" of Hyrax can be easily modified to match an organizations look and feel. Almost all of the web pages can be completely customized by the site administrator by editing a combination of HTML, Image, and CSS files.

== Where to make the changes ==

All of the default versions of the HTML, Image, and CSS files come bundled with Hyrax in the ''$CATALINA_HOME/webapps/opendap/docs'' directory. $CATALINA_HOME is the directory that you installed tomcat in. If you did the default install of tomcat, your $CATALINA_HOME will be "/usr/local/apache-tomcat-6.x.x".

CD to you $CATALINA_HOME directory (again default would look like (on Linux machine): cd /usr/local/apache-tomcat-6.x.x) (The -6.x.x is the version number of tomcat you are running, ex. if you are running tomcat 6.0.24 then it would be just that.)

Make a new directory $CATALINA_HOME/content/opendap/docs/. (This would be: mkdir content, cd content, mkdir opendap ...)

Copy (do not move) the files in $CATALINA_HOME/webapps/opendap/docs to $CATALINA_HOME/content/opendap/docs by using:
cp -r $CATALINA_HOME/webapps/opendap/docs/ $CATALINA_HOME/content/opendap/docs/

;Warning: ''Do NOT remove files from this new directory (Or the old one for that matter). Each file, in its location, is required by Hyrax. You can make changes to the files but you should not rename or remove them.''

'''The rest of these instructions are written with the assumption that a copy of the ''docs'' directory has been made as described above.'''

== What to change ==

=== HTML Files ===
The HTML files provide the static content of a Hyrax server.
{|
|File
|      
|Location
|      
|Description
|-
| '''index.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| The documentation web page for the top level of Hyrax. As shipped it contains a description of Hyrax and links to documentation and funders. The contents.html pages (aka the OPeNDAP directories) links to this document. 
|-
| '''error400.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| Contains the default error page that Hyrax will return when the client request generates a '''Bad Request''' error (Associated with an HTML status of 400) 
|-
| '''error403.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| Contains the default error page that Hyrax will return when the client request generates a '''Forbidden''' error. (Associated with an HTML status of 403) 
|-
| '''error404.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| Contains the default error page that Hyrax will return when the client request generates a '''Not Found''' error. (Associated with an HTML status of 404) 
|-
| '''error500.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| Contains the default error page that Hyrax will return when the client request generates an '''Internal Server Error'''. (Associated with an HTML status of 500) 
|-
| '''error501.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| Contains the default error page that Hyrax will return when the client request generates an '''Not Implemented'''. (Associated with an HTML status of 501) 
|-
| '''error502.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| Contains the default error page that Hyrax will return when the client request generates an '''Bad Gateway'''. (Associated with an HTML status of 502) 
|-
|}
=== CSS Files ===

{|
|File
|      
|Location
|      
|Description
|-
| '''contents.css'''
|
| ''$CATALINA_HOME/content/opendap/docs/css''
|
| The contents.css style sheet provides the default colors and fonts used in the Hyrax site. It is referenced by all of the HTML and XSL files to coordinate the visual aspects of the site. 
|-
| '''thredds.css'''
|
| ''$CATALINA_HOME/content/opendap/docs/css''
|
| The thredds.css style sheet provides the default colors and fonts used by the THREDDS component of Hyrax. 
|-
|}
=== Image Files ===

There are a number of image files shipped with Hyrax. Simply replacing key image files will allow you to customize the icons and logos associated with the Hyrax server.
{|
|File
|      
|Location
|      
|Description
|-
| '''logo.gif'''
|
| ''$CATALINA_HOME/content/opendap/docs/images''
|
| Main Logo for the directory view (produced by contents.css and contents.xsl)
|-
| '''favicon.ico'''
|
| ''$CATALINA_HOME/content/opendap/docs/images''
|
| The cute little icon by preceding the URL in the address bar of your browser. To be used this file needs to be installed into Tomcat [http://docs.opendap.org/index.php/Hyrax_-_Installation_Instructions#Miscellaneous as described here]
|-
| '''BadDapRequest.gif, BadGateway.png, favicon.ico, folder.png, forbidden.png, largeEarth.jpg, logo.gif, nasa-logo.jpg, noaa-logo.jpg, nsf-logo.png, smallEarth.jpg, sml-folder.png, superman.jpg'''
|
| ''$CATALINA_HOME/content/opendap/docs/images''
|
| These files are referenced by the default collection of web content files (described above) that ship with Hyrax.
|}

Hyrax Customization user manual

2010-07-15T20:12:24Z

Rduncan: /* Web page customization */

= Web page customization =

Hyrax can be easily customized to fit the end users needs. The public "face" of Hyrax can be easily modified to match an organizations look and feel. Almost all of the web pages can be completely customized by the site administrator by editing a combination of HTML, Image, and CSS files.

== Where to make the changes ==

All of the default versions of the HTML, Image, and CSS files come bundled with Hyrax in the ''$CATALINA_HOME/webapps/opendap/docs'' directory. $CATALINA_HOME is the directory that you installed tomcat in. If you did the default install of tomcat, your $CATALINA_HOME will be "/usr/local/apache-tomcat-6.x.x".

Copy (do not move) the files in $CATALINA_HOME/webapps/opendap/docs to $CATALINA_HOME/content/opendap/docs by using (on Linux machine):
cp -r /usr/local/apache-tomcat-6.x.x/webapps/opendap/docs/ /usr/local/apache-tomcat-6.x.x/content/opendap/docs/
(The /usr/local/apache-tomcat-6.x.x IS your $CATALINA_HOME and the .x.x after the 6 is the version number of tomcat you have installed)

However, if the ''docs'' directory is copied (preserving its structure) to ''$CATALINA_HOME/content/opendap/'' (creating the directory ''$CATALINA_HOME/content/opendap/docs''), then Hyrax will serve the files from the new location.

;Warning: ''Do NOT remove files from this new directory (Or the old one for that matter). Each file, in its location, is required by Hyrax. You can make changes to the files but you should not rename or remove them.''

Nothing inside the ''$CATALINA_HOME/content'' directory is (automatically) changed when installing new versions of Hyrax.

'''The rest of these instructions are written with the assumption that a copy of the ''docs'' directory has been made as described above.'''

== What to change ==

=== HTML Files ===
The HTML files provide the static content of a Hyrax server.
{|
|File
|      
|Location
|      
|Description
|-
| '''index.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| The documentation web page for the top level of Hyrax. As shipped it contains a description of Hyrax and links to documentation and funders. The contents.html pages (aka the OPeNDAP directories) links to this document. 
|-
| '''error400.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| Contains the default error page that Hyrax will return when the client request generates a '''Bad Request''' error (Associated with an HTML status of 400) 
|-
| '''error403.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| Contains the default error page that Hyrax will return when the client request generates a '''Forbidden''' error. (Associated with an HTML status of 403) 
|-
| '''error404.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| Contains the default error page that Hyrax will return when the client request generates a '''Not Found''' error. (Associated with an HTML status of 404) 
|-
| '''error500.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| Contains the default error page that Hyrax will return when the client request generates an '''Internal Server Error'''. (Associated with an HTML status of 500) 
|-
| '''error501.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| Contains the default error page that Hyrax will return when the client request generates an '''Not Implemented'''. (Associated with an HTML status of 501) 
|-
| '''error502.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| Contains the default error page that Hyrax will return when the client request generates an '''Bad Gateway'''. (Associated with an HTML status of 502) 
|-
|}
=== CSS Files ===

{|
|File
|      
|Location
|      
|Description
|-
| '''contents.css'''
|
| ''$CATALINA_HOME/content/opendap/docs/css''
|
| The contents.css style sheet provides the default colors and fonts used in the Hyrax site. It is referenced by all of the HTML and XSL files to coordinate the visual aspects of the site. 
|-
| '''thredds.css'''
|
| ''$CATALINA_HOME/content/opendap/docs/css''
|
| The thredds.css style sheet provides the default colors and fonts used by the THREDDS component of Hyrax. 
|-
|}
=== Image Files ===

There are a number of image files shipped with Hyrax. Simply replacing key image files will allow you to customize the icons and logos associated with the Hyrax server.
{|
|File
|      
|Location
|      
|Description
|-
| '''logo.gif'''
|
| ''$CATALINA_HOME/content/opendap/docs/images''
|
| Main Logo for the directory view (produced by contents.css and contents.xsl)
|-
| '''favicon.ico'''
|
| ''$CATALINA_HOME/content/opendap/docs/images''
|
| The cute little icon by preceding the URL in the address bar of your browser. To be used this file needs to be installed into Tomcat [http://docs.opendap.org/index.php/Hyrax_-_Installation_Instructions#Miscellaneous as described here]
|-
| '''BadDapRequest.gif, BadGateway.png, favicon.ico, folder.png, forbidden.png, largeEarth.jpg, logo.gif, nasa-logo.jpg, noaa-logo.jpg, nsf-logo.png, smallEarth.jpg, sml-folder.png, superman.jpg'''
|
| ''$CATALINA_HOME/content/opendap/docs/images''
|
| These files are referenced by the default collection of web content files (described above) that ship with Hyrax.
|}

Hyrax Customization user manual

2010-07-15T19:22:52Z

Rduncan: /* Web page customization */

= Web page customization =

Hyrax can be easily customized to fit the end users needs. The public "face" of Hyrax can be easily modified to match an organizations look and feel. Almost all of the web pages can be completely customized by the site administrator by editing a combination of HTML, Image, and CSS files.

== Where to make the changes ==

All of the default versions of the HTML, Image, and CSS files come bundled with Hyrax in the ''$CATALINA_HOME/webapps/opendap/docs'' directory. $CATALINA_HOME is the directory that you installed tomcat in. If you did the default install of tomcat, your $CATALINA_HOME will be "/usr/local/apache-tomcat-6.x.x". You can make changes there, but installing new versions of the OLFS software will overwrite your modifications.

However, if the ''docs'' directory is copied (preserving its structure) to ''$CATALINA_HOME/content/opendap/'' (creating the directory ''$CATALINA_HOME/content/opendap/docs''), then Hyrax will serve the files from the new location.

;Warning: ''Do NOT remove files from this new directory (Or the old one for that matter). Each file, in its location, is required by Hyrax. You can make changes to the files but you should not rename or remove them.''

Nothing inside the ''$CATALINA_HOME/content'' directory is (automatically) changed when installing new versions of Hyrax.

'''The rest of these instructions are written with the assumption that a copy of the ''docs'' directory has been made as described above.'''

== What to change ==

=== HTML Files ===
The HTML files provide the static content of a Hyrax server.
{|
|File
|      
|Location
|      
|Description
|-
| '''index.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| The documentation web page for the top level of Hyrax. As shipped it contains a description of Hyrax and links to documentation and funders. The contents.html pages (aka the OPeNDAP directories) links to this document. 
|-
| '''error400.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| Contains the default error page that Hyrax will return when the client request generates a '''Bad Request''' error (Associated with an HTML status of 400) 
|-
| '''error403.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| Contains the default error page that Hyrax will return when the client request generates a '''Forbidden''' error. (Associated with an HTML status of 403) 
|-
| '''error404.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| Contains the default error page that Hyrax will return when the client request generates a '''Not Found''' error. (Associated with an HTML status of 404) 
|-
| '''error500.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| Contains the default error page that Hyrax will return when the client request generates an '''Internal Server Error'''. (Associated with an HTML status of 500) 
|-
| '''error501.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| Contains the default error page that Hyrax will return when the client request generates an '''Not Implemented'''. (Associated with an HTML status of 501) 
|-
| '''error502.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| Contains the default error page that Hyrax will return when the client request generates an '''Bad Gateway'''. (Associated with an HTML status of 502) 
|-
|}
=== CSS Files ===

{|
|File
|      
|Location
|      
|Description
|-
| '''contents.css'''
|
| ''$CATALINA_HOME/content/opendap/docs/css''
|
| The contents.css style sheet provides the default colors and fonts used in the Hyrax site. It is referenced by all of the HTML and XSL files to coordinate the visual aspects of the site. 
|-
| '''thredds.css'''
|
| ''$CATALINA_HOME/content/opendap/docs/css''
|
| The thredds.css style sheet provides the default colors and fonts used by the THREDDS component of Hyrax. 
|-
|}
=== Image Files ===

There are a number of image files shipped with Hyrax. Simply replacing key image files will allow you to customize the icons and logos associated with the Hyrax server.
{|
|File
|      
|Location
|      
|Description
|-
| '''logo.gif'''
|
| ''$CATALINA_HOME/content/opendap/docs/images''
|
| Main Logo for the directory view (produced by contents.css and contents.xsl)
|-
| '''favicon.ico'''
|
| ''$CATALINA_HOME/content/opendap/docs/images''
|
| The cute little icon by preceding the URL in the address bar of your browser. To be used this file needs to be installed into Tomcat [http://docs.opendap.org/index.php/Hyrax_-_Installation_Instructions#Miscellaneous as described here]
|-
| '''BadDapRequest.gif, BadGateway.png, favicon.ico, folder.png, forbidden.png, largeEarth.jpg, logo.gif, nasa-logo.jpg, noaa-logo.jpg, nsf-logo.png, smallEarth.jpg, sml-folder.png, superman.jpg'''
|
| ''$CATALINA_HOME/content/opendap/docs/images''
|
| These files are referenced by the default collection of web content files (described above) that ship with Hyrax.
|}

Hyrax Customization user manual

2010-07-15T16:57:57Z

Rduncan: /* Web page customization */

= Web page customization =

Hyrax's public "face" is the web pages that are produced by servlets running in the Tomcat servlet engine. Almost all of these pages can be completely customized by the site administrator by editing a combination of HTML, XSLT, and CSS files.

== Where to make the changes ==

All of the default versions of the HTML, XSLT, and CSS files come bundled with Hyrax in the ''$CATALINA_HOME/webapps/opendap/docs'' directory. You can make changes there, but installing new versions of the OLFS software will overwrite your modifications.

However, if the ''docs'' directory is copied (preserving its structure) to ''$CATALINA_HOME/content/opendap/'' (creating the directory ''$CATALINA_HOME/content/opendap/docs''), then Hyrax will serve the files from the new location.

;Warning: ''Do NOT remove files from this new directory (Or the old one for that matter). Each file, in its location, is required by Hyrax. You can make changes to the files but you should not rename or remove them.''

Nothing inside the ''$CATALINA_HOME/content'' directory is (automatically) changed when installing new versions of Hyrax.

'''The rest of these instructions are written with the assumption that a copy of the ''docs'' directory has been made as described above.'''

== What to change ==

=== HTML Files ===
The HTML files provide the static content of a Hyrax server.
{|
|File
|      
|Location
|      
|Description
|-
| '''index.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| The documentation web page for the top level of Hyrax. As shipped it contains a description of Hyrax and links to documentation and funders. The contents.html pages (aka the OPeNDAP directories) links to this document. 
|-
| '''error400.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| Contains the default error page that Hyrax will return when the client request generates a '''Bad Request''' error (Associated with an HTML status of 400) 
|-
| '''error403.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| Contains the default error page that Hyrax will return when the client request generates a '''Forbidden''' error. (Associated with an HTML status of 403) 
|-
| '''error404.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| Contains the default error page that Hyrax will return when the client request generates a '''Not Found''' error. (Associated with an HTML status of 404) 
|-
| '''error500.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| Contains the default error page that Hyrax will return when the client request generates an '''Internal Server Error'''. (Associated with an HTML status of 500) 
|-
| '''error501.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| Contains the default error page that Hyrax will return when the client request generates an '''Not Implemented'''. (Associated with an HTML status of 501) 
|-
| '''error502.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| Contains the default error page that Hyrax will return when the client request generates an '''Bad Gateway'''. (Associated with an HTML status of 502) 
|-
|}
=== CSS Files ===

{|
|File
|      
|Location
|      
|Description
|-
| '''contents.css'''
|
| ''$CATALINA_HOME/content/opendap/docs/css''
|
| The contents.css style sheet provides the default colors and fonts used in the Hyrax site. It is referenced by all of the HTML and XSL files to coordinate the visual aspects of the site. 
|-
| '''thredds.css'''
|
| ''$CATALINA_HOME/content/opendap/docs/css''
|
| The thredds.css style sheet provides the default colors and fonts used by the THREDDS component of Hyrax. 
|-
|}
=== Image Files ===

There are a number of image files shipped with Hyrax. Simply replacing key image files will allow you to customize the icons and logos associated with the Hyrax server.
{|
|File
|      
|Location
|      
|Description
|-
| '''logo.gif'''
|
| ''$CATALINA_HOME/content/opendap/docs/images''
|
| Main Logo for the directory view (produced by contents.css and contents.xsl)
|-
| '''favicon.ico'''
|
| ''$CATALINA_HOME/content/opendap/docs/images''
|
| The cute little icon by preceding the URL in the address bar of your browser. To be used this file needs to be installed into Tomcat [http://docs.opendap.org/index.php/Hyrax_-_Installation_Instructions#Miscellaneous as described here]
|-
| '''BadDapRequest.gif, BadGateway.png, favicon.ico, folder.png, forbidden.png, largeEarth.jpg, logo.gif, nasa-logo.jpg, noaa-logo.jpg, nsf-logo.png, smallEarth.jpg, sml-folder.png, superman.jpg'''
|
| ''$CATALINA_HOME/content/opendap/docs/images''
|
| These files are referenced by the default collection of web content files (described above) that ship with Hyrax.
|}

Hyrax Customization user manual

2010-07-15T16:57:01Z

Rduncan: /* Web page customization */

Hyrax Customization user manual

2010-07-15T16:50:10Z

Rduncan: /* HTML Files */

Hyrax Customization user manual

2010-07-15T16:35:13Z

Rduncan: New page: = Web page customization = Hyrax's public "face" is the web pages that are produced by servlets running in the Tomcat servlet engine. Almost all of these pages can be completely customiz...

Development

2010-07-15T16:35:03Z

Rduncan: /* Current Development */

==Current Development==
* [[Hyrax Development]] This page contains several designs, both completed and ongoing, for parts of Hyrax. They include the NCML handler, DAP4 implementation, THREDDS XSLT implementation, The BES XML interface, NetCDF File Response, ...
* [[IOOS Gateway]]
* [[DAP3/4]]
* [[DAP 4.0 Design]]
* [[WCS]]
* [[NC-DAP]]
* [[REAP Cataloging and Searching]]
* [[AMQP Support in Hyrax]]
* [[libdap refactor]]
* [[HowTo: Adding to the Dataset List]]
* [[Dataset List]]
* [[Javascript Data Request Form]]
* [[Hyrax Customization user manual]]

==Project Ideas==
* [[Server side processing]] Some of these ideas could be part of DAP4, some could be additional services Hyrax performs.
* [[Image Service]]
* [[Hyrax Admin Interface]]
* [[Relational Database Handler | RDH]]
* [[GeoDAP]]
* [[THREDDS Catalog Metadata]]
* [[DAP Capabilities]]
* OGC Web Services Framework
** [[Sensor Observation Service]]
* [[Google Summer of Code 2010 Ideas]]
*[[Hyrax Metadata Management]]
*[[ASCII Data DDX]]

==Completed Projects==
* [[NetCDF Translation]]
* [[CheapStix]]

[[Category:Development|Development]]

Hyrax - Customizing Hyrax

2010-07-15T16:31:18Z

Rduncan: /* HTML Files */

There are several ways in which Hyrax can be customized:
* Web interface look and feel can be changed, as can the pages served.
* Custom DispatchHandlers for the OLFS
* Custom RequestHandlers for the BES.
 
 

= Web page customization =

Hyrax's public "face" is the web pages that are produced by servlets running in the Tomcat servlet engine. Almost all of these pages can be completely customized by the site administrator by editing a combination of HTML, XSLT, and CSS files.

== Where to make the changes ==

All of the default versions of the HTML, XSLT, and CSS files come bundled with Hyrax in the ''$CATALINA_HOME/webapps/opendap/docs'' directory. You can make changes there, but installing new versions of the OLFS software will overwrite your modifications.

However, if the ''docs'' directory is copied (preserving its structure) to ''$CATALINA_HOME/content/opendap/'' (creating the directory ''$CATALINA_HOME/content/opendap/docs''), then Hyrax will serve the files from the new location.

;Warning: ''Do NOT remove files from this new directory (Or the old one for that matter). Each file, in its location, is required by Hyrax. You can make changes to the files but you should not rename or remove them.''

Nothing inside the ''$CATALINA_HOME/content'' directory is (automatically) changed when installing new versions of Hyrax.

'''The rest of these instructions are written with the assumption that a copy of the ''docs'' directory has been made as described above.'''

== What to change ==

=== HTML Files ===
The HTML files provide the static content of a Hyrax server.
{|
|File
|      
|Location
|      
|Description
|-
| '''index.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| The documentation web page for the top level of Hyrax. As shipped it contains a description of Hyrax and links to documentation and funders. The contents.html pages (aka the OPeNDAP directories) links to this document. 
|-
| '''error400.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| Contains the default error page that Hyrax will return when the client request generates a '''Bad Request''' error (Associated with an HTML status of 400) 
|-
| '''error403.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| Contains the default error page that Hyrax will return when the client request generates a '''Forbidden''' error. (Associated with an HTML status of 403) 
|-
| '''error404.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| Contains the default error page that Hyrax will return when the client request generates a '''Not Found''' error. (Associated with an HTML status of 404) 
|-
| '''error500.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| Contains the default error page that Hyrax will return when the client request generates an '''Internal Server Error'''. (Associated with an HTML status of 500) 
|-
| '''error501.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| Contains the default error page that Hyrax will return when the client request generates an '''Not Implemented'''. (Associated with an HTML status of 501) 
|-
| '''error502.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| Contains the default error page that Hyrax will return when the client request generates an '''Bad Gateway'''. (Associated with an HTML status of 502) 
|-
|}
 
 

=== CSS Files ===

{|
|File
|      
|Location
|      
|Description
|-
| '''contents.css'''
|
| ''$CATALINA_HOME/content/opendap/docs/css''
|
| The contents.css style sheet provides the default colors and fonts used in the Hyrax site. It is referenced by all of the HTML and XSL files to coordinate the visual aspects of the site. 
|-
| '''thredds.css'''
|
| ''$CATALINA_HOME/content/opendap/docs/css''
|
| The thredds.css style sheet provides the default colors and fonts used by the THREDDS component of Hyrax. 
|-
|}
 
 

=== Image Files ===

There are a number of image files shipped with Hyrax. Simply replacing key image files will allow you to customize the icons and logos associated with the Hyrax server.
{|
|File
|      
|Location
|      
|Description
|-
| '''logo.gif'''
|
| ''$CATALINA_HOME/content/opendap/docs/images''
|
| Main Logo for the directory view (produced by contents.css and contents.xsl)
|-
| '''favicon.ico'''
|
| ''$CATALINA_HOME/content/opendap/docs/images''
|
| The cute little icon by preceding the URL in the address bar of your browser. To be used this file needs to be installed into Tomcat [http://docs.opendap.org/index.php/Hyrax_-_Installation_Instructions#Miscellaneous as described here]
|-
| '''BadDapRequest.gif, BadGateway.png, favicon.ico, folder.png, forbidden.png, largeEarth.jpg, logo.gif, nasa-logo.jpg, noaa-logo.jpg, nsf-logo.png, smallEarth.jpg, sml-folder.png, superman.jpg'''
|
| ''$CATALINA_HOME/content/opendap/docs/images''
|
| These files are referenced by the default collection of web content files (described above) that ship with Hyrax.
|}

 
 

=== XSL Transform Files ===

These files are used to transform XML documents used by Hyrax. Some transforms operate on source XML from internal documents such as BES responses. Other transforms change things like THREDDS catalogs into HTML for browsers.

''All of these XSLT files are software, and should be treated as such. They are intimately tied to the functions of Hyrax. The likelihood that you can change these files and not break Hyrax is fairly low.''

Current Operational XSLT

{|
|File
|      
|Location
|      
|Description
|-
| '''catalog.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| The catalog.xsl file contains the XSLT transformation that is used to transform BES showCatalog responses into THREDDS catalogs.
|-
| '''contents.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| The contents.xsl file contains the XSLT transformation that is used to build the [http://docs.opendap.org/index.php/ServerDispatchOperations#OPeNDAP_Directory_Response OPeNDAP Directory Response] (''see [http://docs.opendap.org/images/6/6e/DirectoryView.png img]'') 
|-
| '''dap_3.2_ddxToRdfTriples.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| ''Experimental'' - This XSLT is used to produce an RDF representation of a DAP 3.2 DDX.
|-
| '''dataset.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| This transform is used to in conjunction with the opendap.threddsHandler code to produce HTML pages of THREDDS catalog dataset element details.
|-
| '''error400.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| The error400.xsl contains the XSLT transformation that is used to build the web page that is returned when the server generates a Bad Request (400) HTTP status code. If for some reason this page cannot be generated then the HTML version (''$CATALINA_HOME/content/opendap/docs/error400.html'') will be sent. 
|-
|-
| '''error500.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| The error400.xsl contains the XSLT transformation that is used to build the web page that is returned when the server generates a Internal Server Error (500) HTTP status code. If for some reason this page cannot be generated then the HTML version (''$CATALINA_HOME/content/opendap/docs/error500.html'') will be sent. 
|-
| '''thredds.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| This transform is used to in conjunction with the opendap.threddsHandler code to produce HTML pages of THREDDS catalog details.
|-
| '''version.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| This transform is used to provide a single location for the Hyrax version number shown in the public interface.
|-
|}
 

Experimental XSLT

 
{|
|File
|      
|Location
|      
|Description
|-
| '''dapAttributePromoter.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| ''Experimental'' - This XSLT file can be used to promote DAP Attributes whose names contain a namespace prefix to XML elements of the same name os the Attribute. ''Not currently in use.''
|-
| '''dapAttributesToXml.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| ''Experimental'' - This XSLT file might be used to promote DAP Attributes encoded with special XML attributes to represent any XML to the XML the Attribute was encoded to represent. ''Not currently in use.''
|-
| '''dap_2.0_ddxToRdfTriples.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| ''Experimental'' - This XSLT can be used to produce an RDF representation of a DAP2 DDX. ''Not currently in use.''
|-
| '''dap_3.3_ddxToRdfTriples.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| ''Experimental'' - This XSLT can be used to produce an RDF representation of a DAP 3.3 DDX. ''Not currently in use.''
|-
| '''namespaceFilter.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| ''Experimental'' - This XSLT can be used to filter documents so that only elements in a particular namespace are returned. ''Not currently in use.''
|-
| '''wcs_coveragePage.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| ''Experimental'' - This XSLT is used by the prototype CEOP WCS gateway client to produce an HTML page with coverage details. ''Not currently in use.''
|-
| '''wcs_coveragesList.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| ''Experimental'' - This XSLT is used by the prototype CEOP WCS gateway client to produce an HTML page with a list of available coverages. ''Not currently in use.''
|-
| '''xmlToDapAttributes.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| ''Experimental'' - This XSLT can be used to covert any XML content into a set of specially encoded DAP Attributes. The resulting Attribute elements have XML ''type'' attributes that are not currently recognized by any OPeNDAP software. ''Not currently in use.''
|-
|}
 
 

= Software Customization =
== OLFS Customization ==
[http://www.opendap.org/support/bom_sdw/SDW_2r0_OLFSExtensions.ppt Power Point Presentation From the 2007 Software Development Workshop hosted by the Australian Bureau of Meteorology.]
 
 

== BES Customization ==
[http://www.opendap.org/support/bom_sdw/SDW_4r0_BESExtensibility.ppt Power Point Presentation From the 2007 Software Development Workshop hosted by the Australian Bureau of Meteorology.]

Hyrax - Customizing Hyrax

2010-07-15T16:30:33Z

Rduncan: /* HTML Files */

There are several ways in which Hyrax can be customized:
* Web interface look and feel can be changed, as can the pages served.
* Custom DispatchHandlers for the OLFS
* Custom RequestHandlers for the BES.
 
 

= Web page customization =

Hyrax's public "face" is the web pages that are produced by servlets running in the Tomcat servlet engine. Almost all of these pages can be completely customized by the site administrator by editing a combination of HTML, XSLT, and CSS files.

== Where to make the changes ==

All of the default versions of the HTML, XSLT, and CSS files come bundled with Hyrax in the ''$CATALINA_HOME/webapps/opendap/docs'' directory. You can make changes there, but installing new versions of the OLFS software will overwrite your modifications.

However, if the ''docs'' directory is copied (preserving its structure) to ''$CATALINA_HOME/content/opendap/'' (creating the directory ''$CATALINA_HOME/content/opendap/docs''), then Hyrax will serve the files from the new location.

;Warning: ''Do NOT remove files from this new directory (Or the old one for that matter). Each file, in its location, is required by Hyrax. You can make changes to the files but you should not rename or remove them.''

Nothing inside the ''$CATALINA_HOME/content'' directory is (automatically) changed when installing new versions of Hyrax.

'''The rest of these instructions are written with the assumption that a copy of the ''docs'' directory has been made as described above.'''

== What to change ==

=== HTML Files ===
The HTML files provide the static content of a Hyrax server.
{|
|File
|      
|Location
|      
|Description
|-
| '''index.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| The documentation web page for the top level of Hyrax. As shipped it contains a description of Hyrax and links to documentation and funders. The contents.html pages (aka the OPeNDAP directories) links to this document. 
|-
| '''error400.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| Contains the default error page that Hyrax will return when the client request generates a '''Bad Request''' error (Associated with an HTML status of 400) 
|-
| '''error403.html'''
|
| ''$CATALINA_HOME/content/opendap/docs''
|
| Contains the default error page that Hyrax will return when the client request generates a '''Forbidden''' error. (Associated with an HTML status of 403) 
|-
| '''error404.html'''
|
| ''$CATALINA_HOME/content/docs''
|
| Contains the default error page that Hyrax will return when the client request generates a '''Not Found''' error. (Associated with an HTML status of 404) 
|-
| '''error500.html'''
|
| ''$CATALINA_HOME/content/docs''
|
| Contains the default error page that Hyrax will return when the client request generates an '''Internal Server Error'''. (Associated with an HTML status of 500) 
|-
| '''error501.html'''
|
| ''$CATALINA_HOME/content/docs''
|
| Contains the default error page that Hyrax will return when the client request generates an '''Not Implemented'''. (Associated with an HTML status of 501) 
|-
| '''error502.html'''
|
| ''$CATALINA_HOME/content/docs''
|
| Contains the default error page that Hyrax will return when the client request generates an '''Bad Gateway'''. (Associated with an HTML status of 502) 
|-
|}
 
 

=== CSS Files ===

{|
|File
|      
|Location
|      
|Description
|-
| '''contents.css'''
|
| ''$CATALINA_HOME/content/opendap/docs/css''
|
| The contents.css style sheet provides the default colors and fonts used in the Hyrax site. It is referenced by all of the HTML and XSL files to coordinate the visual aspects of the site. 
|-
| '''thredds.css'''
|
| ''$CATALINA_HOME/content/opendap/docs/css''
|
| The thredds.css style sheet provides the default colors and fonts used by the THREDDS component of Hyrax. 
|-
|}
 
 

=== Image Files ===

There are a number of image files shipped with Hyrax. Simply replacing key image files will allow you to customize the icons and logos associated with the Hyrax server.
{|
|File
|      
|Location
|      
|Description
|-
| '''logo.gif'''
|
| ''$CATALINA_HOME/content/opendap/docs/images''
|
| Main Logo for the directory view (produced by contents.css and contents.xsl)
|-
| '''favicon.ico'''
|
| ''$CATALINA_HOME/content/opendap/docs/images''
|
| The cute little icon by preceding the URL in the address bar of your browser. To be used this file needs to be installed into Tomcat [http://docs.opendap.org/index.php/Hyrax_-_Installation_Instructions#Miscellaneous as described here]
|-
| '''BadDapRequest.gif, BadGateway.png, favicon.ico, folder.png, forbidden.png, largeEarth.jpg, logo.gif, nasa-logo.jpg, noaa-logo.jpg, nsf-logo.png, smallEarth.jpg, sml-folder.png, superman.jpg'''
|
| ''$CATALINA_HOME/content/opendap/docs/images''
|
| These files are referenced by the default collection of web content files (described above) that ship with Hyrax.
|}

 
 

=== XSL Transform Files ===

These files are used to transform XML documents used by Hyrax. Some transforms operate on source XML from internal documents such as BES responses. Other transforms change things like THREDDS catalogs into HTML for browsers.

''All of these XSLT files are software, and should be treated as such. They are intimately tied to the functions of Hyrax. The likelihood that you can change these files and not break Hyrax is fairly low.''

Current Operational XSLT

{|
|File
|      
|Location
|      
|Description
|-
| '''catalog.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| The catalog.xsl file contains the XSLT transformation that is used to transform BES showCatalog responses into THREDDS catalogs.
|-
| '''contents.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| The contents.xsl file contains the XSLT transformation that is used to build the [http://docs.opendap.org/index.php/ServerDispatchOperations#OPeNDAP_Directory_Response OPeNDAP Directory Response] (''see [http://docs.opendap.org/images/6/6e/DirectoryView.png img]'') 
|-
| '''dap_3.2_ddxToRdfTriples.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| ''Experimental'' - This XSLT is used to produce an RDF representation of a DAP 3.2 DDX.
|-
| '''dataset.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| This transform is used to in conjunction with the opendap.threddsHandler code to produce HTML pages of THREDDS catalog dataset element details.
|-
| '''error400.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| The error400.xsl contains the XSLT transformation that is used to build the web page that is returned when the server generates a Bad Request (400) HTTP status code. If for some reason this page cannot be generated then the HTML version (''$CATALINA_HOME/content/opendap/docs/error400.html'') will be sent. 
|-
|-
| '''error500.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| The error400.xsl contains the XSLT transformation that is used to build the web page that is returned when the server generates a Internal Server Error (500) HTTP status code. If for some reason this page cannot be generated then the HTML version (''$CATALINA_HOME/content/opendap/docs/error500.html'') will be sent. 
|-
| '''thredds.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| This transform is used to in conjunction with the opendap.threddsHandler code to produce HTML pages of THREDDS catalog details.
|-
| '''version.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| This transform is used to provide a single location for the Hyrax version number shown in the public interface.
|-
|}
 

Experimental XSLT

 
{|
|File
|      
|Location
|      
|Description
|-
| '''dapAttributePromoter.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| ''Experimental'' - This XSLT file can be used to promote DAP Attributes whose names contain a namespace prefix to XML elements of the same name os the Attribute. ''Not currently in use.''
|-
| '''dapAttributesToXml.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| ''Experimental'' - This XSLT file might be used to promote DAP Attributes encoded with special XML attributes to represent any XML to the XML the Attribute was encoded to represent. ''Not currently in use.''
|-
| '''dap_2.0_ddxToRdfTriples.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| ''Experimental'' - This XSLT can be used to produce an RDF representation of a DAP2 DDX. ''Not currently in use.''
|-
| '''dap_3.3_ddxToRdfTriples.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| ''Experimental'' - This XSLT can be used to produce an RDF representation of a DAP 3.3 DDX. ''Not currently in use.''
|-
| '''namespaceFilter.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| ''Experimental'' - This XSLT can be used to filter documents so that only elements in a particular namespace are returned. ''Not currently in use.''
|-
| '''wcs_coveragePage.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| ''Experimental'' - This XSLT is used by the prototype CEOP WCS gateway client to produce an HTML page with coverage details. ''Not currently in use.''
|-
| '''wcs_coveragesList.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| ''Experimental'' - This XSLT is used by the prototype CEOP WCS gateway client to produce an HTML page with a list of available coverages. ''Not currently in use.''
|-
| '''xmlToDapAttributes.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| ''Experimental'' - This XSLT can be used to covert any XML content into a set of specially encoded DAP Attributes. The resulting Attribute elements have XML ''type'' attributes that are not currently recognized by any OPeNDAP software. ''Not currently in use.''
|-
|}
 
 

= Software Customization =
== OLFS Customization ==
[http://www.opendap.org/support/bom_sdw/SDW_2r0_OLFSExtensions.ppt Power Point Presentation From the 2007 Software Development Workshop hosted by the Australian Bureau of Meteorology.]
 
 

== BES Customization ==
[http://www.opendap.org/support/bom_sdw/SDW_4r0_BESExtensibility.ppt Power Point Presentation From the 2007 Software Development Workshop hosted by the Australian Bureau of Meteorology.]

Hyrax - Customizing Hyrax

2010-07-15T16:29:59Z

Rduncan: /* CSS Files */

There are several ways in which Hyrax can be customized:
* Web interface look and feel can be changed, as can the pages served.
* Custom DispatchHandlers for the OLFS
* Custom RequestHandlers for the BES.
 
 

= Web page customization =

Hyrax's public "face" is the web pages that are produced by servlets running in the Tomcat servlet engine. Almost all of these pages can be completely customized by the site administrator by editing a combination of HTML, XSLT, and CSS files.

== Where to make the changes ==

All of the default versions of the HTML, XSLT, and CSS files come bundled with Hyrax in the ''$CATALINA_HOME/webapps/opendap/docs'' directory. You can make changes there, but installing new versions of the OLFS software will overwrite your modifications.

However, if the ''docs'' directory is copied (preserving its structure) to ''$CATALINA_HOME/content/opendap/'' (creating the directory ''$CATALINA_HOME/content/opendap/docs''), then Hyrax will serve the files from the new location.

;Warning: ''Do NOT remove files from this new directory (Or the old one for that matter). Each file, in its location, is required by Hyrax. You can make changes to the files but you should not rename or remove them.''

Nothing inside the ''$CATALINA_HOME/content'' directory is (automatically) changed when installing new versions of Hyrax.

'''The rest of these instructions are written with the assumption that a copy of the ''docs'' directory has been made as described above.'''

== What to change ==

=== HTML Files ===
The HTML files provide the static content of a Hyrax server.
{|
|File
|      
|Location
|      
|Description
|-
| '''index.html'''
|
| ''$CATALINA_HOME/content/docs''
|
| The documentation web page for the top level of Hyrax. As shipped it contains a description of Hyrax and links to documentation and funders. The contents.html pages (aka the OPeNDAP directories) links to this document. 
|-
| '''error400.html'''
|
| ''$CATALINA_HOME/content/docs''
|
| Contains the default error page that Hyrax will return when the client request generates a '''Bad Request''' error (Associated with an HTML status of 400) 
|-
| '''error403.html'''
|
| ''$CATALINA_HOME/content/docs''
|
| Contains the default error page that Hyrax will return when the client request generates a '''Forbidden''' error. (Associated with an HTML status of 403) 
|-
| '''error404.html'''
|
| ''$CATALINA_HOME/content/docs''
|
| Contains the default error page that Hyrax will return when the client request generates a '''Not Found''' error. (Associated with an HTML status of 404) 
|-
| '''error500.html'''
|
| ''$CATALINA_HOME/content/docs''
|
| Contains the default error page that Hyrax will return when the client request generates an '''Internal Server Error'''. (Associated with an HTML status of 500) 
|-
| '''error501.html'''
|
| ''$CATALINA_HOME/content/docs''
|
| Contains the default error page that Hyrax will return when the client request generates an '''Not Implemented'''. (Associated with an HTML status of 501) 
|-
| '''error502.html'''
|
| ''$CATALINA_HOME/content/docs''
|
| Contains the default error page that Hyrax will return when the client request generates an '''Bad Gateway'''. (Associated with an HTML status of 502) 
|-
|}
 
 

=== CSS Files ===

{|
|File
|      
|Location
|      
|Description
|-
| '''contents.css'''
|
| ''$CATALINA_HOME/content/opendap/docs/css''
|
| The contents.css style sheet provides the default colors and fonts used in the Hyrax site. It is referenced by all of the HTML and XSL files to coordinate the visual aspects of the site. 
|-
| '''thredds.css'''
|
| ''$CATALINA_HOME/content/opendap/docs/css''
|
| The thredds.css style sheet provides the default colors and fonts used by the THREDDS component of Hyrax. 
|-
|}
 
 

=== Image Files ===

There are a number of image files shipped with Hyrax. Simply replacing key image files will allow you to customize the icons and logos associated with the Hyrax server.
{|
|File
|      
|Location
|      
|Description
|-
| '''logo.gif'''
|
| ''$CATALINA_HOME/content/opendap/docs/images''
|
| Main Logo for the directory view (produced by contents.css and contents.xsl)
|-
| '''favicon.ico'''
|
| ''$CATALINA_HOME/content/opendap/docs/images''
|
| The cute little icon by preceding the URL in the address bar of your browser. To be used this file needs to be installed into Tomcat [http://docs.opendap.org/index.php/Hyrax_-_Installation_Instructions#Miscellaneous as described here]
|-
| '''BadDapRequest.gif, BadGateway.png, favicon.ico, folder.png, forbidden.png, largeEarth.jpg, logo.gif, nasa-logo.jpg, noaa-logo.jpg, nsf-logo.png, smallEarth.jpg, sml-folder.png, superman.jpg'''
|
| ''$CATALINA_HOME/content/opendap/docs/images''
|
| These files are referenced by the default collection of web content files (described above) that ship with Hyrax.
|}

 
 

=== XSL Transform Files ===

These files are used to transform XML documents used by Hyrax. Some transforms operate on source XML from internal documents such as BES responses. Other transforms change things like THREDDS catalogs into HTML for browsers.

''All of these XSLT files are software, and should be treated as such. They are intimately tied to the functions of Hyrax. The likelihood that you can change these files and not break Hyrax is fairly low.''

Current Operational XSLT

{|
|File
|      
|Location
|      
|Description
|-
| '''catalog.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| The catalog.xsl file contains the XSLT transformation that is used to transform BES showCatalog responses into THREDDS catalogs.
|-
| '''contents.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| The contents.xsl file contains the XSLT transformation that is used to build the [http://docs.opendap.org/index.php/ServerDispatchOperations#OPeNDAP_Directory_Response OPeNDAP Directory Response] (''see [http://docs.opendap.org/images/6/6e/DirectoryView.png img]'') 
|-
| '''dap_3.2_ddxToRdfTriples.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| ''Experimental'' - This XSLT is used to produce an RDF representation of a DAP 3.2 DDX.
|-
| '''dataset.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| This transform is used to in conjunction with the opendap.threddsHandler code to produce HTML pages of THREDDS catalog dataset element details.
|-
| '''error400.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| The error400.xsl contains the XSLT transformation that is used to build the web page that is returned when the server generates a Bad Request (400) HTTP status code. If for some reason this page cannot be generated then the HTML version (''$CATALINA_HOME/content/opendap/docs/error400.html'') will be sent. 
|-
|-
| '''error500.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| The error400.xsl contains the XSLT transformation that is used to build the web page that is returned when the server generates a Internal Server Error (500) HTTP status code. If for some reason this page cannot be generated then the HTML version (''$CATALINA_HOME/content/opendap/docs/error500.html'') will be sent. 
|-
| '''thredds.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| This transform is used to in conjunction with the opendap.threddsHandler code to produce HTML pages of THREDDS catalog details.
|-
| '''version.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| This transform is used to provide a single location for the Hyrax version number shown in the public interface.
|-
|}
 

Experimental XSLT

 
{|
|File
|      
|Location
|      
|Description
|-
| '''dapAttributePromoter.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| ''Experimental'' - This XSLT file can be used to promote DAP Attributes whose names contain a namespace prefix to XML elements of the same name os the Attribute. ''Not currently in use.''
|-
| '''dapAttributesToXml.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| ''Experimental'' - This XSLT file might be used to promote DAP Attributes encoded with special XML attributes to represent any XML to the XML the Attribute was encoded to represent. ''Not currently in use.''
|-
| '''dap_2.0_ddxToRdfTriples.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| ''Experimental'' - This XSLT can be used to produce an RDF representation of a DAP2 DDX. ''Not currently in use.''
|-
| '''dap_3.3_ddxToRdfTriples.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| ''Experimental'' - This XSLT can be used to produce an RDF representation of a DAP 3.3 DDX. ''Not currently in use.''
|-
| '''namespaceFilter.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| ''Experimental'' - This XSLT can be used to filter documents so that only elements in a particular namespace are returned. ''Not currently in use.''
|-
| '''wcs_coveragePage.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| ''Experimental'' - This XSLT is used by the prototype CEOP WCS gateway client to produce an HTML page with coverage details. ''Not currently in use.''
|-
| '''wcs_coveragesList.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| ''Experimental'' - This XSLT is used by the prototype CEOP WCS gateway client to produce an HTML page with a list of available coverages. ''Not currently in use.''
|-
| '''xmlToDapAttributes.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| ''Experimental'' - This XSLT can be used to covert any XML content into a set of specially encoded DAP Attributes. The resulting Attribute elements have XML ''type'' attributes that are not currently recognized by any OPeNDAP software. ''Not currently in use.''
|-
|}
 
 

= Software Customization =
== OLFS Customization ==
[http://www.opendap.org/support/bom_sdw/SDW_2r0_OLFSExtensions.ppt Power Point Presentation From the 2007 Software Development Workshop hosted by the Australian Bureau of Meteorology.]
 
 

== BES Customization ==
[http://www.opendap.org/support/bom_sdw/SDW_4r0_BESExtensibility.ppt Power Point Presentation From the 2007 Software Development Workshop hosted by the Australian Bureau of Meteorology.]

Hyrax - Customizing Hyrax

2010-07-15T16:29:40Z

Rduncan: /* Image Files */

There are several ways in which Hyrax can be customized:
* Web interface look and feel can be changed, as can the pages served.
* Custom DispatchHandlers for the OLFS
* Custom RequestHandlers for the BES.
 
 

= Web page customization =

Hyrax's public "face" is the web pages that are produced by servlets running in the Tomcat servlet engine. Almost all of these pages can be completely customized by the site administrator by editing a combination of HTML, XSLT, and CSS files.

== Where to make the changes ==

All of the default versions of the HTML, XSLT, and CSS files come bundled with Hyrax in the ''$CATALINA_HOME/webapps/opendap/docs'' directory. You can make changes there, but installing new versions of the OLFS software will overwrite your modifications.

However, if the ''docs'' directory is copied (preserving its structure) to ''$CATALINA_HOME/content/opendap/'' (creating the directory ''$CATALINA_HOME/content/opendap/docs''), then Hyrax will serve the files from the new location.

;Warning: ''Do NOT remove files from this new directory (Or the old one for that matter). Each file, in its location, is required by Hyrax. You can make changes to the files but you should not rename or remove them.''

Nothing inside the ''$CATALINA_HOME/content'' directory is (automatically) changed when installing new versions of Hyrax.

'''The rest of these instructions are written with the assumption that a copy of the ''docs'' directory has been made as described above.'''

== What to change ==

=== HTML Files ===
The HTML files provide the static content of a Hyrax server.
{|
|File
|      
|Location
|      
|Description
|-
| '''index.html'''
|
| ''$CATALINA_HOME/content/docs''
|
| The documentation web page for the top level of Hyrax. As shipped it contains a description of Hyrax and links to documentation and funders. The contents.html pages (aka the OPeNDAP directories) links to this document. 
|-
| '''error400.html'''
|
| ''$CATALINA_HOME/content/docs''
|
| Contains the default error page that Hyrax will return when the client request generates a '''Bad Request''' error (Associated with an HTML status of 400) 
|-
| '''error403.html'''
|
| ''$CATALINA_HOME/content/docs''
|
| Contains the default error page that Hyrax will return when the client request generates a '''Forbidden''' error. (Associated with an HTML status of 403) 
|-
| '''error404.html'''
|
| ''$CATALINA_HOME/content/docs''
|
| Contains the default error page that Hyrax will return when the client request generates a '''Not Found''' error. (Associated with an HTML status of 404) 
|-
| '''error500.html'''
|
| ''$CATALINA_HOME/content/docs''
|
| Contains the default error page that Hyrax will return when the client request generates an '''Internal Server Error'''. (Associated with an HTML status of 500) 
|-
| '''error501.html'''
|
| ''$CATALINA_HOME/content/docs''
|
| Contains the default error page that Hyrax will return when the client request generates an '''Not Implemented'''. (Associated with an HTML status of 501) 
|-
| '''error502.html'''
|
| ''$CATALINA_HOME/content/docs''
|
| Contains the default error page that Hyrax will return when the client request generates an '''Bad Gateway'''. (Associated with an HTML status of 502) 
|-
|}
 
 

=== CSS Files ===

{|
|File
|      
|Location
|      
|Description
|-
| '''contents.css'''
|
| ''$CATALINA_HOME/content/docs/css''
|
| The contents.css style sheet provides the default colors and fonts used in the Hyrax site. It is referenced by all of the HTML and XSL files to coordinate the visual aspects of the site. 
|-
| '''thredds.css'''
|
| ''$CATALINA_HOME/content/docs/css''
|
| The thredds.css style sheet provides the default colors and fonts used by the THREDDS component of Hyrax. 
|-
|}
 
 
=== Image Files ===

There are a number of image files shipped with Hyrax. Simply replacing key image files will allow you to customize the icons and logos associated with the Hyrax server.
{|
|File
|      
|Location
|      
|Description
|-
| '''logo.gif'''
|
| ''$CATALINA_HOME/content/opendap/docs/images''
|
| Main Logo for the directory view (produced by contents.css and contents.xsl)
|-
| '''favicon.ico'''
|
| ''$CATALINA_HOME/content/opendap/docs/images''
|
| The cute little icon by preceding the URL in the address bar of your browser. To be used this file needs to be installed into Tomcat [http://docs.opendap.org/index.php/Hyrax_-_Installation_Instructions#Miscellaneous as described here]
|-
| '''BadDapRequest.gif, BadGateway.png, favicon.ico, folder.png, forbidden.png, largeEarth.jpg, logo.gif, nasa-logo.jpg, noaa-logo.jpg, nsf-logo.png, smallEarth.jpg, sml-folder.png, superman.jpg'''
|
| ''$CATALINA_HOME/content/opendap/docs/images''
|
| These files are referenced by the default collection of web content files (described above) that ship with Hyrax.
|}

 
 

=== XSL Transform Files ===

These files are used to transform XML documents used by Hyrax. Some transforms operate on source XML from internal documents such as BES responses. Other transforms change things like THREDDS catalogs into HTML for browsers.

''All of these XSLT files are software, and should be treated as such. They are intimately tied to the functions of Hyrax. The likelihood that you can change these files and not break Hyrax is fairly low.''

Current Operational XSLT

{|
|File
|      
|Location
|      
|Description
|-
| '''catalog.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| The catalog.xsl file contains the XSLT transformation that is used to transform BES showCatalog responses into THREDDS catalogs.
|-
| '''contents.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| The contents.xsl file contains the XSLT transformation that is used to build the [http://docs.opendap.org/index.php/ServerDispatchOperations#OPeNDAP_Directory_Response OPeNDAP Directory Response] (''see [http://docs.opendap.org/images/6/6e/DirectoryView.png img]'') 
|-
| '''dap_3.2_ddxToRdfTriples.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| ''Experimental'' - This XSLT is used to produce an RDF representation of a DAP 3.2 DDX.
|-
| '''dataset.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| This transform is used to in conjunction with the opendap.threddsHandler code to produce HTML pages of THREDDS catalog dataset element details.
|-
| '''error400.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| The error400.xsl contains the XSLT transformation that is used to build the web page that is returned when the server generates a Bad Request (400) HTTP status code. If for some reason this page cannot be generated then the HTML version (''$CATALINA_HOME/content/opendap/docs/error400.html'') will be sent. 
|-
|-
| '''error500.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| The error400.xsl contains the XSLT transformation that is used to build the web page that is returned when the server generates a Internal Server Error (500) HTTP status code. If for some reason this page cannot be generated then the HTML version (''$CATALINA_HOME/content/opendap/docs/error500.html'') will be sent. 
|-
| '''thredds.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| This transform is used to in conjunction with the opendap.threddsHandler code to produce HTML pages of THREDDS catalog details.
|-
| '''version.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| This transform is used to provide a single location for the Hyrax version number shown in the public interface.
|-
|}
 

Experimental XSLT

 
{|
|File
|      
|Location
|      
|Description
|-
| '''dapAttributePromoter.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| ''Experimental'' - This XSLT file can be used to promote DAP Attributes whose names contain a namespace prefix to XML elements of the same name os the Attribute. ''Not currently in use.''
|-
| '''dapAttributesToXml.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| ''Experimental'' - This XSLT file might be used to promote DAP Attributes encoded with special XML attributes to represent any XML to the XML the Attribute was encoded to represent. ''Not currently in use.''
|-
| '''dap_2.0_ddxToRdfTriples.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| ''Experimental'' - This XSLT can be used to produce an RDF representation of a DAP2 DDX. ''Not currently in use.''
|-
| '''dap_3.3_ddxToRdfTriples.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| ''Experimental'' - This XSLT can be used to produce an RDF representation of a DAP 3.3 DDX. ''Not currently in use.''
|-
| '''namespaceFilter.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| ''Experimental'' - This XSLT can be used to filter documents so that only elements in a particular namespace are returned. ''Not currently in use.''
|-
| '''wcs_coveragePage.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| ''Experimental'' - This XSLT is used by the prototype CEOP WCS gateway client to produce an HTML page with coverage details. ''Not currently in use.''
|-
| '''wcs_coveragesList.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| ''Experimental'' - This XSLT is used by the prototype CEOP WCS gateway client to produce an HTML page with a list of available coverages. ''Not currently in use.''
|-
| '''xmlToDapAttributes.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| ''Experimental'' - This XSLT can be used to covert any XML content into a set of specially encoded DAP Attributes. The resulting Attribute elements have XML ''type'' attributes that are not currently recognized by any OPeNDAP software. ''Not currently in use.''
|-
|}
 
 

= Software Customization =
== OLFS Customization ==
[http://www.opendap.org/support/bom_sdw/SDW_2r0_OLFSExtensions.ppt Power Point Presentation From the 2007 Software Development Workshop hosted by the Australian Bureau of Meteorology.]
 
 

== BES Customization ==
[http://www.opendap.org/support/bom_sdw/SDW_4r0_BESExtensibility.ppt Power Point Presentation From the 2007 Software Development Workshop hosted by the Australian Bureau of Meteorology.]

Hyrax - Customizing Hyrax

2010-07-15T16:28:11Z

Rduncan: /* XSL Transform Files */

There are several ways in which Hyrax can be customized:
* Web interface look and feel can be changed, as can the pages served.
* Custom DispatchHandlers for the OLFS
* Custom RequestHandlers for the BES.
 
 

= Web page customization =

Hyrax's public "face" is the web pages that are produced by servlets running in the Tomcat servlet engine. Almost all of these pages can be completely customized by the site administrator by editing a combination of HTML, XSLT, and CSS files.

== Where to make the changes ==

All of the default versions of the HTML, XSLT, and CSS files come bundled with Hyrax in the ''$CATALINA_HOME/webapps/opendap/docs'' directory. You can make changes there, but installing new versions of the OLFS software will overwrite your modifications.

However, if the ''docs'' directory is copied (preserving its structure) to ''$CATALINA_HOME/content/opendap/'' (creating the directory ''$CATALINA_HOME/content/opendap/docs''), then Hyrax will serve the files from the new location.

;Warning: ''Do NOT remove files from this new directory (Or the old one for that matter). Each file, in its location, is required by Hyrax. You can make changes to the files but you should not rename or remove them.''

Nothing inside the ''$CATALINA_HOME/content'' directory is (automatically) changed when installing new versions of Hyrax.

'''The rest of these instructions are written with the assumption that a copy of the ''docs'' directory has been made as described above.'''

== What to change ==

=== HTML Files ===
The HTML files provide the static content of a Hyrax server.
{|
|File
|      
|Location
|      
|Description
|-
| '''index.html'''
|
| ''$CATALINA_HOME/content/docs''
|
| The documentation web page for the top level of Hyrax. As shipped it contains a description of Hyrax and links to documentation and funders. The contents.html pages (aka the OPeNDAP directories) links to this document. 
|-
| '''error400.html'''
|
| ''$CATALINA_HOME/content/docs''
|
| Contains the default error page that Hyrax will return when the client request generates a '''Bad Request''' error (Associated with an HTML status of 400) 
|-
| '''error403.html'''
|
| ''$CATALINA_HOME/content/docs''
|
| Contains the default error page that Hyrax will return when the client request generates a '''Forbidden''' error. (Associated with an HTML status of 403) 
|-
| '''error404.html'''
|
| ''$CATALINA_HOME/content/docs''
|
| Contains the default error page that Hyrax will return when the client request generates a '''Not Found''' error. (Associated with an HTML status of 404) 
|-
| '''error500.html'''
|
| ''$CATALINA_HOME/content/docs''
|
| Contains the default error page that Hyrax will return when the client request generates an '''Internal Server Error'''. (Associated with an HTML status of 500) 
|-
| '''error501.html'''
|
| ''$CATALINA_HOME/content/docs''
|
| Contains the default error page that Hyrax will return when the client request generates an '''Not Implemented'''. (Associated with an HTML status of 501) 
|-
| '''error502.html'''
|
| ''$CATALINA_HOME/content/docs''
|
| Contains the default error page that Hyrax will return when the client request generates an '''Bad Gateway'''. (Associated with an HTML status of 502) 
|-
|}
 
 

=== CSS Files ===

{|
|File
|      
|Location
|      
|Description
|-
| '''contents.css'''
|
| ''$CATALINA_HOME/content/docs/css''
|
| The contents.css style sheet provides the default colors and fonts used in the Hyrax site. It is referenced by all of the HTML and XSL files to coordinate the visual aspects of the site. 
|-
| '''thredds.css'''
|
| ''$CATALINA_HOME/content/docs/css''
|
| The thredds.css style sheet provides the default colors and fonts used by the THREDDS component of Hyrax. 
|-
|}
 
 
=== Image Files ===

There are a number of image files shipped with Hyrax. Simply replacing key image files will allow you to customize the icons and logos associated with the Hyrax server.
{|
|File
|      
|Location
|      
|Description
|-
| '''logo.gif'''
|
| ''$CATALINA_HOME/content/docs/images''
|
| Main Logo for the directory view (produced by contents.css and contents.xsl)
|-
| '''favicon.ico'''
|
| ''$CATALINA_HOME/content/docs/images''
|
| The cute little icon by preceding the URL in the address bar of your browser. To be used this file needs to be installed into Tomcat [http://docs.opendap.org/index.php/Hyrax_-_Installation_Instructions#Miscellaneous as described here]
|-
| '''BadDapRequest.gif, BadGateway.png, favicon.ico, folder.png, forbidden.png, largeEarth.jpg, logo.gif, nasa-logo.jpg, noaa-logo.jpg, nsf-logo.png, smallEarth.jpg, sml-folder.png, superman.jpg'''
|
| ''$CATALINA_HOME/content/docs/images''
|
| These files are referenced by the default collection of web content files (described above) that ship with Hyrax.
|}

 
 

=== XSL Transform Files ===

These files are used to transform XML documents used by Hyrax. Some transforms operate on source XML from internal documents such as BES responses. Other transforms change things like THREDDS catalogs into HTML for browsers.

''All of these XSLT files are software, and should be treated as such. They are intimately tied to the functions of Hyrax. The likelihood that you can change these files and not break Hyrax is fairly low.''

Current Operational XSLT

{|
|File
|      
|Location
|      
|Description
|-
| '''catalog.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| The catalog.xsl file contains the XSLT transformation that is used to transform BES showCatalog responses into THREDDS catalogs.
|-
| '''contents.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| The contents.xsl file contains the XSLT transformation that is used to build the [http://docs.opendap.org/index.php/ServerDispatchOperations#OPeNDAP_Directory_Response OPeNDAP Directory Response] (''see [http://docs.opendap.org/images/6/6e/DirectoryView.png img]'') 
|-
| '''dap_3.2_ddxToRdfTriples.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| ''Experimental'' - This XSLT is used to produce an RDF representation of a DAP 3.2 DDX.
|-
| '''dataset.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| This transform is used to in conjunction with the opendap.threddsHandler code to produce HTML pages of THREDDS catalog dataset element details.
|-
| '''error400.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| The error400.xsl contains the XSLT transformation that is used to build the web page that is returned when the server generates a Bad Request (400) HTTP status code. If for some reason this page cannot be generated then the HTML version (''$CATALINA_HOME/content/opendap/docs/error400.html'') will be sent. 
|-
|-
| '''error500.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| The error400.xsl contains the XSLT transformation that is used to build the web page that is returned when the server generates a Internal Server Error (500) HTTP status code. If for some reason this page cannot be generated then the HTML version (''$CATALINA_HOME/content/opendap/docs/error500.html'') will be sent. 
|-
| '''thredds.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| This transform is used to in conjunction with the opendap.threddsHandler code to produce HTML pages of THREDDS catalog details.
|-
| '''version.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| This transform is used to provide a single location for the Hyrax version number shown in the public interface.
|-
|}
 

Experimental XSLT

 
{|
|File
|      
|Location
|      
|Description
|-
| '''dapAttributePromoter.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| ''Experimental'' - This XSLT file can be used to promote DAP Attributes whose names contain a namespace prefix to XML elements of the same name os the Attribute. ''Not currently in use.''
|-
| '''dapAttributesToXml.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| ''Experimental'' - This XSLT file might be used to promote DAP Attributes encoded with special XML attributes to represent any XML to the XML the Attribute was encoded to represent. ''Not currently in use.''
|-
| '''dap_2.0_ddxToRdfTriples.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| ''Experimental'' - This XSLT can be used to produce an RDF representation of a DAP2 DDX. ''Not currently in use.''
|-
| '''dap_3.3_ddxToRdfTriples.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| ''Experimental'' - This XSLT can be used to produce an RDF representation of a DAP 3.3 DDX. ''Not currently in use.''
|-
| '''namespaceFilter.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| ''Experimental'' - This XSLT can be used to filter documents so that only elements in a particular namespace are returned. ''Not currently in use.''
|-
| '''wcs_coveragePage.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| ''Experimental'' - This XSLT is used by the prototype CEOP WCS gateway client to produce an HTML page with coverage details. ''Not currently in use.''
|-
| '''wcs_coveragesList.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| ''Experimental'' - This XSLT is used by the prototype CEOP WCS gateway client to produce an HTML page with a list of available coverages. ''Not currently in use.''
|-
| '''xmlToDapAttributes.xsl'''
|
| ''$CATALINA_HOME/content/opendap/docs/xsl''
|
| ''Experimental'' - This XSLT can be used to covert any XML content into a set of specially encoded DAP Attributes. The resulting Attribute elements have XML ''type'' attributes that are not currently recognized by any OPeNDAP software. ''Not currently in use.''
|-
|}
 
 

= Software Customization =
== OLFS Customization ==
[http://www.opendap.org/support/bom_sdw/SDW_2r0_OLFSExtensions.ppt Power Point Presentation From the 2007 Software Development Workshop hosted by the Australian Bureau of Meteorology.]
 
 

== BES Customization ==
[http://www.opendap.org/support/bom_sdw/SDW_4r0_BESExtensibility.ppt Power Point Presentation From the 2007 Software Development Workshop hosted by the Australian Bureau of Meteorology.]

Google Summer of Code 2010 Ideas

2010-03-29T16:02:58Z

Rduncan:

=OPeNDAP Google Summer of Code 2010=

[[Image:GSoC 2010 300x267px.jpg|right]]
OPeNDAP would like to welcome all the SoC students for the 2010 iteration of the SoC program! On this page you'll find information about project ideas we have along with information to help you apply to work on our software. The projects range from web site implementation to complex problems in data systems. Several of the projects listed are focused on adding new features to our data server. However, we also have a set of client tools and GUI-based applications that would provide an ample basis for summer projects. If you don't see anything below in the [[#Ideas]] section don't let that stop you from starting a conversation with one of the mentors listed below ([[#Mentors]]) because you may have an idea, talent or skill that is the spark of a great project. Don't hesitate to email us!

We would like to stress that while the ideas included here can be the basis of your project, you can also propose something completely different - maybe you've used our software and wish it included a particular feature.

Before submitting an application to GSoC with OPeNDAP as your mentoring organization, make sure you read our [[Google Summer of Code FAQ|GSoC FAQ]], which provides some pointers on how to write a successful application.

Once you are ready to submit an application, remember that you must do so '''before April 9th''' through the [http://socghop.appspot.com/ GSoC webapp]. A more complete [http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/timeline timeline] is available for the whole project period.

= Ideas =

* [[Development of improved Hyrax User Interfaces]]: Browsers, JavaScript
* [[Extending support for Matlab]]: C; Matlab a plus
* [[KML responses for Hyrax]]: C++
* [[GeoTIFF responses for Hyrax]]: C++
* [[New Features for Hyrax]]: C++
* [[Web Site Design]]: Drupal, mediawiki, ...

= Mentors =

* James Gallagher (jgallagher at opendap.org): The Hyrax data server, Matlab and IDL clients, C, C++, Java
* Patrick West (westp at rpi.edu): The Hyrax data server, C, C++, Java, Apache Modules, Semantic Web, OWL (Web Ontology Language), RDFS, some Java
* Nathan Potter (ndp at opendap.org): The Hyrax data server, OLFS, Java-OPeNDAP, Java
* Rikki McQueary (rmcqueary at opendap.org): The IDL client, OC library, C
* More names will appear soon...

[[Category:Google Summer of Code]]