Hi Andrea,
Thanks for your reply regarding the use of JavaScript to interface the
content of two HTML select lists.
I now have a further question:
If I look at the full metadata record for the results from a remote search,
GeoNetwork seems to use its own XSL and the XML for the full metadata record
to present the information. We have many Z39350 metadata nodes (remote
sites) that deliver XML, HTML or SUTRS. Many of the custodians of those
nodes would like the presentation of the full metadata record to use their
HTML. This can be done using z3950 by setting the "record syntax" to be
"HTML". The record syntax number is "1.2.840.10003.5.109.3".
Can GeoNetwork be configured to replace the "XML" record syntax of
"1.2.840.10003.5.109.10" to the "HTML" record syntax of
"1.2.840.10003.5.109.3" when viewing the full metadata record from a remote
site?
I'm happy for anyone to answer this question. ;--)
Thanks.
John Hockaday
Geoscience Australia
GPO Box 378
Canberra ACT 2601
(02) 6249 9735
http://www.ga.gov.au/
john.hockaday\@ga.gov.au
Hi John,
geonetwork cannot be configured to automatically switch from XML to HTML
on Z39.50 searches. Now the XML is mandatory because the result is sent
to the presentation pipeline. Furthermore, prior to that the result is XSL
transformed in order to have a common set of properties to display (title,
abstract etc...)
What you request can be done because you have the source code and it
should not be hard: you need to change 1 or 2 java classes and the search-results.xsl
stylesheet. Prior to do that, I suggest you to give a look at geonetwork beta3
because the Z39.50 code has been fixed and changed.
Cheers,
Andrea
Hi Andrea,
Thanks for your reply regarding the use of JavaScript to interface the
content of two HTML select lists.
I now have a further question:
If I look at the full metadata record for the results from a remote search,
GeoNetwork seems to use its own XSL and the XML for the full metadata record
to present the information. We have many Z39350 metadata nodes (remote
sites) that deliver XML, HTML or SUTRS. Many of the custodians of those
nodes would like the presentation of the full metadata record to use their
HTML. This can be done using z3950 by setting the "record syntax" to be
"HTML". The record syntax number is "1.2.840.10003.5.109.3".
Can GeoNetwork be configured to replace the "XML" record syntax of
"1.2.840.10003.5.109.10" to the "HTML" record syntax of
"1.2.840.10003.5.109.3" when viewing the full metadata record from a remote
site?
I'm happy for anyone to answer this question. ;--)
Thanks.
John Hockaday
Geoscience Australia
GPO Box 378
Canberra ACT 2601
(02) 6249 9735
http://www.ga.gov.au/
john.hockaday\@ga.gov.au
John.Hockaday@anonymised.com wrote:
Hi Andrea,
Thanks for your reply regarding the use of JavaScript to interface the
content of two HTML select lists.
I now have a further question:
If I look at the full metadata record for the results from a remote search,
GeoNetwork seems to use its own XSL and the XML for the full metadata record
to present the information. We have many Z39350 metadata nodes (remote
sites) that deliver XML, HTML or SUTRS. Many of the custodians of those
nodes would like the presentation of the full metadata record to use their
HTML. This can be done using z3950 by setting the "record syntax" to be
"HTML". The record syntax number is "1.2.840.10003.5.109.3".
Can GeoNetwork be configured to replace the "XML" record syntax of
"1.2.840.10003.5.109.10" to the "HTML" record syntax of
"1.2.840.10003.5.109.3" when viewing the full metadata record from a remote
site?
I'm happy for anyone to answer this question. ;--)
I'll defer to the developers and people with a better knowledge of Z39.50 on this one but I'd say - yes - though it's not straightforward - geonetwork basically assumes (as you know) that everything is xml and the xml must be given meaning by the appropriate xslt scripts.
We've implemented a workaround which gets both the HTML and XML version of the full record from the Z3950 server - the HTML gets dumped into a file and the filename is supplied as a geonet:html element with the XML version for geonetwork's XSLT scripts to handle. Basically we've set the remote-show.xsl script such that the HTML version in the file is available as a link in the title of the XML version.
I'm sure there are other ways that the filename/HTML content could be handled by the XSLT to generate a desirable interface.
Cheers,
Simon