A minor suggestion of no urgency, but an ncWMS server config file can specify the following metadata attributes, which in addition to being part of the config file will be displayed in the Web Console and I think GetCapabilities requests:
Contact name, organization, telephone, and email
A server title
Abstract
Keywords
url
It might be nice to fill in some of these details, especially as we look at the possibility of software outside PCIC requesting maps from these servers.
Additionally, it would be helpful to me personally as someone who updates ncWMS servers sometimes to have the date a server was configured and the ensemble(s) containing the data files it serves present in the config file and the web console, in either the abstract or title attributes.
Options include:
1) automatically generating these metadata attributes as the configuration file is generated
2) accepting a metadata file, probably YAML (and possibly falling back to option 1 if no file supplied). We could add 2 YAML files to the repository; one for a typical development server and one for a typical production server.
A minor suggestion of no urgency, but an ncWMS server config file can specify the following metadata attributes, which in addition to being part of the config file will be displayed in the Web Console and I think
GetCapabilitiesrequests:It might be nice to fill in some of these details, especially as we look at the possibility of software outside PCIC requesting maps from these servers.
Additionally, it would be helpful to me personally as someone who updates ncWMS servers sometimes to have the date a server was configured and the ensemble(s) containing the data files it serves present in the config file and the web console, in either the
abstractortitleattributes.Options include: 1) automatically generating these metadata attributes as the configuration file is generated 2) accepting a metadata file, probably YAML (and possibly falling back to option 1 if no file supplied). We could add 2 YAML files to the repository; one for a typical development server and one for a typical production server.