Does anyone have experience modifying the Thredds-to-ISO19119.xsl stylesheet to better harvest Services metadata? It is very minimal and isn't pulling in the right metadata so if someone else has already created a better xsl would you share it with me?
Another issue seems to be that it is not recognizing the UUID that GeoNetwork is generating and is creating a text-based UUID which is not unique so I am only getting one service record (e.g. wms) for the catalog -- Craig Jones states that there is a bug in the harvester java code that uses the netCDF java library UUID regardless of what GN sets. This also means that if I have changed the way the ISO Metadata UUID is generated - the child/parent records don't match.
Has anyone fixed that with a patch I could run or found a solution to this?
Kathy
<../../../../tdekker/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/Content.Outlook/8B0OUOWO/www.limno.com>
Hi,
I make a follow-up on this topic from Oct. 2014 as I'm in the same process.
I want to harvest a TDS server (http://tds.webservice-energy.org) from my
GeoNetwork platform GN (V 2.11.0) and generate ISO 19139 metadata record in
our catalog (http://geocatalog.webservice-energy.org).
The harvest work and provide a very good metadata record from the TDS XML
metadata file.
I choose the following option for harvesting:
<http://osgeo-org.1560.x6.nabble.com/file/n5247732/Capture_d’écran_2016-01-25_à_16.png>
As a results I get metadata records like this:
http://geocatalog.webservice-energy.org/geonetwork/srv/eng/metadata.show?id=5417&currTab=simple
from the original resources from this:
http://tds.webservice-energy.org/thredds/catalog/waves/catalog.html?dataset=waves/wave_power_maps.nc
I also have the pb. that Kathy mention about the UUID. In my case the UUID
takes the form of "waves-wave_power_maps.nc" that is the path and the name
of the file.
I have also some non crucial little "glitch" such as the "Individual name"
of the "Distributor" sub-field that I've not been able to make correspond
from the TDS XML file.
I also have some duplication of the "Transfer Options" links that I don't
explain ?
For me the only IMPORTANT missing feature is that I would have expect to
have "at least" into the ISO metadata record the WMS and WCS links to be
available as they are available operation in my TDS document (see link
above).
My question are as follow:
- Is they any option I missed to an able such WMS WCS links to be
automatically generated at harvest time ?
- If no, does any possible change in the harvest template could solve this
pb ?
- Does anyone already implement such feature ?
- Does the new 3.x versions implement such feature ?
Thanks for reading and possible clues on this topic ?
Lionel
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/Thredds-to-ISO19119-harvesting-tp5166904p5247732.html
Sent from the GeoNetwork users mailing list archive at Nabble.com.
