Hi all, testing OpenLayers CSW format I'm facing an issue on FGDC demo
data we have after setup.
It looks like FGDC extract-uuid always return an empty UUID.
I would suggest to add the following to CSW output mapping in order to
always have a UUID in CSW response.
Hi all, testing OpenLayers CSW format I’m facing an issue on FGDC demo
data we have after setup.
It looks like FGDC extract-uuid always return an empty UUID.
I would suggest to add the following to CSW output mapping in order to
always have a UUID in CSW response.
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what’s new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
Hi all, testing OpenLayers CSW format I'm facing an issue on FGDC demo
data we have after setup.
It looks like FGDC extract-uuid always return an empty UUID.
I would suggest to add the following to CSW output mapping in order to
always have a UUID in CSW response.
Yes, it does. The use of the cat_id attribute is an unofficial
extension of the FGDC schema/DTD, but widely (although not universally)
used within the FGDC community to hold a unique catalog identifier.
If I read the code correctly, this is used in generating the CSW
response and creates a new identifier if there is not one present in the
FGDC record. That's the right way for it to work.
I haven't had a chance to look at the relevant record ingest code, but
is there also something equivalent in there? That is, to parse the
identifier from cat_id if it's present, and to generate a new identifier
if it's not? That might be useful for internal purposes.
--
Archie
-- Archie Warnock warnock@anonymised.com
-- A/WWW Enterprises www.awcubed.com
-- As a matter of fact, I _do_ speak for my employer.