Thanks Heikki - appreciate the detailed feedback - I'll include it in the review.
Cheers,
Simon
________________________________________
From: heikki [tropicano@anonymised.com]
Sent: Wednesday, 7 December 2011 7:59 AM
To: Pigot, Simon (CMAR, Hobart)
Cc: geonetwork-users@lists.sourceforge.net; GeoNetwork-devel@anonymised.comrge.net
Subject: Re: [GeoNetwork-users] [GeoNetwork-devel] HELP NEEDED.. additional metadata elements in GN (how to describe them)..
hi Tania, Simon,
if your schema is named iso19139.yourprofilename, then it is assumed in the
code that it is an extension of iso19139, is what I think. This means that
many of the XSLTs just use the templates in the XSLTs in the iso19139
schema present directory, unless you override them. Simon please correct me
if I'm wrong here ..
for example written on page 26 - Creating the extract XSLTs - its written
we must create four xslts, but there is only three examples
(extract-date-modified.xsl, extract-gml.xsl, and extract-uuid.xsl).
You can just copy the same 4 xslts from the iso19139 schema and not modify
them unless that's needed for your profile.
Also there is an example of the eml-gbif schema (p.31) and there was
nothing written about eml-gbif schema before, which got me lost.
Yes, it may be a bit unclear that in the middle of explaining about the mcp
profile, the doc starts referring to other profiles as well. Probably to
illustrate some points that could not be illustrated with the mcp profile.
In any case, like Simon said, check out the schemaprofiles SVN directory,
for several examples including that one.
Some remarks about the documentation from my experience:
(1) if you just create the profile in the /schemas directory with the
intention of having it automatically loaded on startup, you need to include
it too in WEB-INF/schemaplugin-uri-catalog.xml. Don't think this is
documented and took me awhile to discover.
(2) what's not clear to me is what forms of detection you can put in
schema-ident.xml -- don't think all the mechanism is documented, there are
just some examples in the schemaprofiles SVN. For example can I detect a
schema by the simple presence of a particular namespace declaration in the
root element ? And what if several schemas match, how is it decided which
one wins ?
(3) the doc describes first one method of doing it, and then shows another
way of doing it. This is a bit disconcerting if you follow the doc as a
step-by-step guide. Maybe it's better to introduce in the beginning the two
methods with links to them; or just describe only one of them, certainly if
one method is preferred over the other.
If I think of anything else, I'll add to this thread.
Thanks and kind regards,
Heikki Doeleman
On Mon, Dec 5, 2011 at 2:06 PM, <Simon.Pigot@anonymised.com> wrote:
Hi Tania,
The examples in the documentation are based on real schema plugins in the
subversion repository and include references to a couple of different
schemas so that you can get the idea of how to do the steps for profiles of
ISO19115/19139 as well as non ISO schemas like eml-gbif. So if an example
doesn't refer to the schema you were following you should still be able to
find what you need by browsing the schema plugins directory at
GeoNetwork - Geographic Metadata Catalog download | SourceForge.net
That said, the docs are down on my list of things to review before the 2.8
RC process starts as there have been some changes related to the
experimental ExtJS interface etc and so we can still work on clarity as
well - I'll see if I can review them in the next couple of days. Also if
others have comments and things they want to add to the doco then maybe now
is a good time to do this.
Cheers,
Simon
________________________________________
From: Tania Firdausy [tania.puspita@anonymised.com]
Sent: Monday, 5 December 2011 7:58 PM
To: tropicano@anonymised.com
Cc: geonetwork-users@lists.sourceforge.net;
GeoNetwork-devel@lists.sourceforge.net
Subject: Re: [GeoNetwork-devel] HELP NEEDED.. additional metadata elements
in GN (how to describe them)..
Hi Heikki,
Thank you for your response. I tried to follow the schema extension steps
but there were steps which were not clear for me. for example written on
page 26 - Creating the extract XSLTs - its written we must create four
xslts, but there is only three examples (extract-date-modified.xsl,
extract-gml.xsl, and extract-uuid.xsl). Also there is an example of the
eml-gbif schema (p.31) and there was nothing written about eml-gbif schema
before, which got me lost. also the locations of the example files
(labels.xml) were not in the specified directory, etc.. and I tried to
continue..but I didnt succeed.
Maybe do you have a more comprehensive and clear documentation for
extending schemas in GN? it would be very nice if you could share it with
me.
Thank you very much in advance.
Regards,
Tania
On Fri, Dec 2, 2011 at 6:17 PM, heikki <tropicano@anonymised.com<mailto:
tropicano@anonymised.com>> wrote:
hi Tania,
could you be more specific how you were not successful using the schema
extension steps ? What did or did not work ?
Kind regards
Heikki Doeleman
On Fri, Dec 2, 2011 at 6:05 PM, Tania Firdausy <tania.puspita@anonymised.com
<mailto:tania.puspita@anonymised.com>> wrote:
Hi there,
I have been working with geonetwork for a couple of months. My institute
wants to implement a geocatalog service using GN but we have additional
metadata elements which are not yet defined in GN. for example we want to
include metadata which describes the pixel information of the image
(raster). I have been searching the wiki and forum, but seems like the
steps defined there are not that clear (i have been following the schema
extension steps described in GeoNetwork Developer Manual, Release
2.7.0-SNAPSHOT but not successful). It would be nice if you could give me
some clear hints or step by step advice on how to do this. Thank you very
much in advance.
With best regards,
Tania P Firdausy
GIS Software Engineer
------------------------------------------------------------------------------
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.
Best Open Source Mac Front-Ends 2024
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net<mailto:
GeoNetwork-devel@lists.sourceforge.net>
geonetwork-devel List Signup and Options
GeoNetwork OpenSource is maintained at
GeoNetwork - Geographic Metadata Catalog download | SourceForge.net
