Host ISO xsl files on GitHub?

[srstsavage]

@amilan17 When dealing with IOOS registry/catalog/metadata issues, we often need to understand how upstream documents (SOS/WMS capabilities, ncML, etc) are being transformed to ISO by the XSL files. It would be very helpful if these files were hosted on GitHub so that they could be easily referenced and others could make patches and pull requests to fix problems. Being able to easily reference the XSL documents would help demystify the harvesting process, and hosting in GitHub would provide benefits like in-browser syntax highlighting, search, and easy cloning to local machines.

I'm assuming that these documents are not already available in a public repository. If they are, can that repo be mentioned in the README?

If for some reason it's not possible to host these files in a repo, can the deployment URL be mentioned in the README?

http://www.ngdc.noaa.gov/metadata/published/views/

[amilan17]

This is an excellent suggestion. I'd like to have a centrally located github for ALL of NOAA XSLs. I don't mind, in the meantime posting copies to the registry.... However, I'm a little concerned that the ioos copy might become out-of-date with my locally subversioned copies.

Anna ~~~~~~~ Anna.Milan@noaa.gov, 303-497-5099 NOAA/NESDIS/NGDC

http://www.ngdc.noaa.gov/metadata/emma ~~~~~~~

On Tue, Oct 28, 2014 at 3:34 PM, Shane StClair notifications@github.com wrote:

@amilan17 https://github.com/amilan17 When dealing with IOOS registry/catalog/metadata issues, we often need to understand how upstream documents (SOS/WMS capabilities, ncML, etc) are being transformed to ISO by the XSL files. It would be very helpful if these files were hosted on GitHub so that they could be easily referenced and others could make patches and pull requests to fix problems. Being able to easily reference the XSL documents would help demystify the harvesting process, and hosting in GitHub would provide benefits like in-browser syntax highlighting, search, and easy cloning to local machines.

I'm assuming that these documents are not already available in a public repository. If they are, can that repo be mentioned in the README?

If for some reason it's not possible to host these files in a repo, can the deployment URL be mentioned in the README?

http://www.ngdc.noaa.gov/metadata/published/views/

— Reply to this email directly or view it on GitHub https://github.com/ioos/registry/issues/62.

[duncombe]

Anna,

Can you transition your SVN repos to git? Syncing with github/ioos will then be easy. If you need to keep subversion, there are ways to keep the git repo in sync with the subversion one ( http://git-scm.com/book/en/v1/Git-and-Other-Systems-Git-and-Subversion). Scanning the text, it looks like moving changes in the other direction may require a little work, but it sounds as though you expect your workflow will be only from svn to git.

Chris

On Tue, Oct 28, 2014 at 5:59 PM, Anna Milan notifications@github.com wrote:

This is an excellent suggestion. I'd like to have a centrally located github for ALL of NOAA XSLs. I don't mind, in the meantime posting copies to the registry.... However, I'm a little concerned that the ioos copy might become out-of-date with my locally subversioned copies.

Anna ~~~~~~~ Anna.Milan@noaa.gov, 303-497-5099 NOAA/NESDIS/NGDC

http://www.ngdc.noaa.gov/metadata/emma ~~~~~~~

On Tue, Oct 28, 2014 at 3:34 PM, Shane StClair notifications@github.com wrote:

@amilan17 https://github.com/amilan17 When dealing with IOOS registry/catalog/metadata issues, we often need to understand how upstream documents (SOS/WMS capabilities, ncML, etc) are being transformed to ISO by the XSL files. It would be very helpful if these files were hosted on GitHub so that they could be easily referenced and others could make patches and pull requests to fix problems. Being able to easily reference the XSL documents would help demystify the harvesting process, and hosting in GitHub would provide benefits like in-browser syntax highlighting, search, and easy cloning to local machines.

I'm assuming that these documents are not already available in a public repository. If they are, can that repo be mentioned in the README?

If for some reason it's not possible to host these files in a repo, can the deployment URL be mentioned in the README?

http://www.ngdc.noaa.gov/metadata/published/views/

— Reply to this email directly or view it on GitHub https://github.com/ioos/registry/issues/62.

— Reply to this email directly or view it on GitHub https://github.com/ioos/registry/issues/62#issuecomment-60839250.

Dr. Christopher M. Duncombe Rae c deirdre.byrne@noaa.gov hristopher.duncombe.rae@noaa.gov Oceanographer / Data Scientist IOOS/NOAA, Suite 1225, 1100 Wayne Avenue, Silver Spring, MD 20910, USA Tel: +1-301-427-2450 Fax: +1-301-427-2073

[srstsavage]

I agree that it wouldn't be a good idea to try to manually keep SVN and GitHub repos synced. As Chris mentioned, there are a number of ways to automatically sync them, but may not be worth pursuing if you're planning to eventually move to git anyway.

In the meantime, is anyone opposed to linking to the deployment URL (or more appropriate URL if one exists) in the README?

http://www.ngdc.noaa.gov/metadata/published/views/

[amilan17]

@shane-axiom @duncombe For the time being, I've added links to the XSLs in use for transforming to ISO in the registry overview... https://github.com/ioos/registry#transformation-files

[amilan17]

@duncombe @shane-axiom https://github.com/ioos/metadataTransformations https://github.com/Unidata/threddsIso/tree/master/src/main/resources/xsl/nciso

[tomkralidis]

:+1: awesome!