Missing online resource protocols

[ianwallen]

It seems like the code is currently hard coded to used the following protocols however they are not in the protocol list (​https://github.com/geonetwork/core-geonetwork/blob/master/web/src/main/webapp/loc/eng/xml/strings.xml#L712)

WWW:LINK-*http--download	iso-19139
WWW:LINK-1.0-http--metadata-URL	MCP
WWW:LINK-*http--downloaddata	MCP

These should be added to the list otherwise what is happening, is that they assigned but when the protocol drop down list is shown - it ends up defaulting to the first item in the list.

See the following thread

​http://osgeo-org.1560.n6.nabble.com/Questions-regarding-online-resource-protocols-inconsistencies-tc5013538.html

[ianwallen]

If someone wants to supply me with the protocol values and the associated text then I can add them to the list.

[ianwallen]

I believe I found the value to be used.

<protocolChoice value="WWW:LINK-1.0-http--download">Web address for download</protocolChoice>

comes from ​https://geonetwork.svn.sourceforge.net/svnroot/geonetwork/sandbox/geocat.ch/trunk/web/geonetwork/loc/eng/xml

<protocolChoice show="y" value="WWW:LINK-1.0-http--metadata-URL">Metadata URL</protocolChoice>
<protocolChoice show="y" value="WWW:LINK-1.0-http--downloaddata">Data for download (URL)</protocolChoice>

Comes from ​https://geonetwork.svn.sourceforge.net/svnroot/geonetwork/sandbox/BlueNetMEST/ANZMEST/web/src/main/webapp/WEB-INF/anzmest-config-overrides.xml

As the MCP file are added based on the anzmest-config-overrides.xml - it seems that if these are added to the current list, it may cause some issues.

Any objection with adding these to the current list?

The reason I believe they should be there is because they are hard coded in the current logic and if they are not added the protocol drop down list defaults to to first item in the list.

If there are objections it is not a problem - a work around would be to create my own config-overrride to include these value.

Any comments?

[ianwallen]

Note: This is related to Ticket #984

[ianwallen]

I now have a better understanding of this list and it seems to be related to not being able to fully separate the xsl from other projects such as anzmest and geocat.

Ticket #984 should help separate the projects better.

So Marking it as invalid for now.