Hi Byron,
This is great work and better vocabulary support in the Geonetwork editor is something that
we at RAN-Metoc had wanted for a while but we didn't have the expertise/time/money
to do. We mostly use the Marine Community Profile of ISO19139 and keyword support
in Geonetwork editor is limited to only 1 vocabulary i.e the NASA Global Change Master
Directory (GCMD) science keywords.
We would like to be able to choose keywords off other thesauri
e.g CF standard names or BODC parameter codes P021 and have the
following features:
- 'plugin' whichever keyword lists we needed as part of geonetwork configuration
- allow entry (configurable by vocab. list) of <gmx:anchor> instead of <gco:characterString> as
per Francois Prunayre's proposal (see http://trac.osgeo.org/geonetwork/ticket/691). Advantage of gmx:anchor is
that the xlink:href attribute may reference to web service URL - (RDF file) which defines the keyword or near matches.
- support both local ISO CT codelist catalogues and RDF file lists.
- Geonetwork administrator is able to edit/cut down size of thesaurus (some e.g BODC P021 are far too large for what you need) to a few typical terms we would encounter
- In editor ability to choose from 1 or more thesauri in describing a dataset.
- auto. generate the thesaurus citation according to the list chosen.
- enter own keyword (free text) when lists don't suit
The above features are a lot of work!
Anyway if I get time (and that's a big IF -:)) I will try out your
metadata-iso19139.anzlic-edit.xsl and figure out how out I might adapt that to
ISO19139-MCP.
Regards,
Andrew
----- Original Message ----- From: "ByronCinNZ" <cochranes4@anonymised.com>
To: <geonetwork-devel@lists.sourceforge.net>
Sent: Friday, December 02, 2011 11:17 AM
Subject: Re: [GeoNetwork-devel] Thesauri and keywords in template records
I have made some good progress on these issues (keywords and thesauri).
Working with the xsl file /metadata-iso19139.anzlic-edit.xsl/ (we are using
the anzlic profile for this project), I was able to make modifications that
provide much of what I was looking for. But with a little more work (which I
am not sure I can justify the time for at the moment) I could make this a
more general improvement that would ease the handling of keywords and
thesauri in iso19139 based metadata.My concept and approach is this. When a user clicks on the binocular icon to
add a set of keyword to a metadata record and ties these keywords to a
thesauri, the keywords added in that block should be restricted to the
vocabularies provided by that thesaurus. If a user wants to add keywords for
a particular theme that is not in that thesaurus or in a different
thesaurus, they add another keyword block. If they want to add free text
keywords, they add a block that does not include a thesaurus.This is what the result looks like in the widgets gui:
http://osgeo-org.1803224.n2.nabble.com/file/n7052859/GN-Keyword-Thesaurus.pngTo improve the display and limit users to use thesaurus values, I changed
the input of the keyword value to hidden. The current value appears in the
dropdown.The code values available come from the referenced thesaurus. To do this I
use the the xml service /geonetwork/srv/en/xml.search.keywords?/ against the
referenced library.
http://osgeo-org.1803224.n2.nabble.com/file/n7052859/GN-Keyword-Thesaurus2.pngWhile this implementation suits my current needs, I think I would like to
make it more universal. It currently works only in the ANZLIC profile and
the linkage is currently hard coded to /Discipline/ keywords (like the
ANZLIC-Themes keywords are hardcoded to /Theme/ keywords). To improve on
this I would extract the value from the Thesaurus metadata for that keyword
block.I have attached my modified version of metadata-iso19139.anzlic-edit.xsl if
anyone is interested.Cheers,
Byron Cochrane
LISAsoft
http://osgeo-org.1803224.n2.nabble.com/file/n7052859/metadata-iso19139.anzlic-edit.xsl
metadata-iso19139.anzlic-edit.xsl--
View this message in context: http://osgeo-org.1803224.n2.nabble.com/Thesauri-and-keywords-in-template-records-tp7041495p7052859.html
Sent from the GeoNetwork developer mailing list archive at Nabble.com.------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork
