Re: [GeoNetwork-users] Schema plugin and profile

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 454-5900

Hi Paul

In step 7) you say “Almost all the other files you can see that delegate to
iso19139” – do you mean I don’t have to have instances of these for my
iso19139.model?

You need to have them in your schema, but can copy from
https://github.com/geonetwork/schema-plugins/blob/master/iso19139.xyz

See for example
https://github.com/geonetwork/schema-plugins/blob/master/iso19139.xyz/index-fields.xsl#L3,
imports the same file from iso19139 schema, but the file
index-fields.xsl should be also in your profile.

I would start the schema based on
https://github.com/geonetwork/schema-plugins/blob/master/iso19139.xyz and
start customising the files I described in the previous mail. All the other
files you can leave untouched.

Regards,
Jose García

On Fri, Apr 25, 2014 at 2:43 PM, Paul Cleverley <
P.C...@hr...> wrote:

>  Jose, thank you very much indeed - that gives me a lot to go on!
>
>
>
> I have managed to fake my iso19139.model schema to the point where the
> whole system doesn’t fall over.  I am currently trying to edit an example
> MEF file to incorporate the new element I have added (ModelFeatureType) so
> I can add it as sample-data.
>
>
>
> In step 7) you say “Almost all the other files you can see that delegate
> to iso19139” – do you mean I don’t have to have instances of these for my
> iso19139.model?
>
>
>
> I don’t know what oasis is or what it is for?
>
>
>
> I don’t know how geonetwork uses schema-ident.xml.
>
>
>
> I don’t know how geonetwork uses codelists (lookup tables yes? – but the
> references to codelists are relative to what?)
>
>
>
> I can’t find an explanation of what geonetwork thinks a “template” is –
> and no idea what the metadata.xsl and metadata-edit.xsl transforms are used
> for or where or when.
>
>
>
> Labels is good!  I will obviously need a new label for my element – I’ll
> call it “Model Feature Type” – but not yet clear on how GN uses the labels
> files (there appear to be lots of files called labels.xml, codelist.xml etc
> all in different directories and it’s not clear how GN merges / separates
> these )
>
>
>
> Thank you so much for your help with this I will endeavour to go through
> each step accordingly!
>
>
>
> Thanks!
>
>
>
> Best wishes
>
> Paul
>
>
>
> *From:* Jose Garcia [mailto:jos...@ge...]
> *Sent:* Friday, April 25, 2014 1:34 PM
> *To:* Paul Cleverley
> *Cc:* geo...@li...
> *Subject:* Re: [GeoNetwork-users] Schema plugin and profile
>
>
>
> Hi Paul
>
>
>
> I have worked recently in some schemas, let me explain how I managed:
>
>
>
> I started the development based on this template project:
> https://github.com/geonetwork/schema-plugins/tree/master/iso19139.xyz
>
>
>
> One of the schemas is
> https://github.com/geonetwork/schema-plugins/tree/master/iso19139.napm ,
> that is iso19139 with customisations in xsd related to cardinality and some
> custom codelist values mostly.
>
>
>
> I did mostly these steps:
>
>  1)  Customise schema-ident.xml with the rules to match metadata to the
> new schema
>
>
>
>
>
> 2) In schema folder copy the iso19139 xsd and custom xsd (see
> https://github.com/geonetwork/schema-plugins/tree/master/iso19139.napm/schema/napm
> )
>
>
>
>
>
> 3) Map custom xsd in oasis-catalog.xml (see
> https://github.com/geonetwork/schema-plugins/blob/master/iso19139.napm/oasis-catalog.xml#L58
> )
>
>
>
>
>
> 4) Customise the codelists (if your schema has new values for iso19139
> codelist or new codelists)
>
>
>
> See
> https://github.com/geonetwork/schema-plugins/blob/master/iso19139.napm/loc/eng/codelists.xml
>
>
>
>
>
> 5) Customise the labels (if your schema requires to replace iso19139
> element labels or add labels for new elements)
>
>
>
> See
> https://github.com/geonetwork/schema-plugins/blob/master/iso19139.napm/loc/eng/labels.xml
>
>
>
>
>
> 6) Customise template names in present/metadata-edit.xsl and
> present/metadata.xsl (I assume you work with 2.8 or 2.10 versions, for
> develop branch changes a bit)
>
>
>
> Take a look for example to
> https://github.com/geonetwork/schema-plugins/blob/master/iso19139.napm/present/metadata-edit.xsl,
> my schema is named iso19139.napm, some templates should have this name in
> the template name (you need to replace with your schema name)
>
>
>
>
>
> 7) Almost all the other files you can see that delegate to iso19139 (see
> for example,
> https://github.com/geonetwork/schema-plugins/blob/master/iso19139.napm/index-fields.xsl
> )
>
>
>
>
>
> Another plugin that can be interesting to check is this one:
> https://github.com/geonetwork/schema-plugins/tree/master/iso19139.naplio-dataset, as adds new elements to iso19139.
>
>
>
>  1) The steps are similar, but present/metadata-edit.xsl and
> present/metadata.xsl require some additional customisation to manage the
> new elements. See
> https://github.com/geonetwork/schema-plugins/blob/master/iso19139.naplio-dataset/present/metadata.xsl#L234
>
>
>
> 2) Also another change is to remove the custom elements from CSW responses
> when requested iso19139 output. See
> https://github.com/geonetwork/schema-plugins/blob/master/iso19139.naplio-dataset/present/csw/iso-full.xsl#L15
>
>
>
>
>
> A bit long mail, but hope can help a bit to clarify the steps. I want to
> update the documentation to improve it with a simple case, but could not
> manage yet, will try to check in coming weeks.
>
>
> Regards,
>
> Jose García
>
>
>
>
>
> On Fri, Apr 25, 2014 at 1:01 PM, Paul Cleverley <
> P.C...@hr...> wrote:
>
> HI
>
> I wonder if anyone could point me at a *simple* example of a "profile"
> with a clear statement about the minimum requirements for adding to - say -
> iso19139?
>
> All I want to do is....:-)
>
> Add a few elements to the iso19139 schema
>
> I don't want to extend or otherwise modify *anything* in the iso19139
> schema except to add a couple of elements - let's call the profile / plugin
>
> iso19139.model
>
> I have a model.xsd file and a schema.xsd file and a schema-ident.xml file
>
> What else is needed?
>
> I find the current documentation confusing I'm afraid - sections which say
> these directories *can* be present which implies they are optional followed
> by some which are mandatory and some which are optional?
>
> Are "converters" XSLT transforms or a servlet or what?  I feel I am
> swimming way out of my depth here and would appreciate some help :)!
>
> Thanks
> Paul
>
>
> Paul Cleverley
> Software Developer, Hydrodynamics & Metocean
>
> E: p.c...@hr...<mailto:p.c...@hr...>
> T: +44 (0)1491 822483
> <http://www.hrwallingford.com/banner.html>
> ________________________________
> [HR Wallingford Logo]
>
> HR Wallingford
> Howbery Park, Wallingford, Oxfordshire OX10 8BA, United Kingdom
> T: +44 (0)1491 835381     F: +44 (0)1491 832233
> www.hrwallingford.com
>
> [HR Wallingford Secondary Logo]
>
> ________________________________
>
> ________________________________
>
> HR Wallingford and its subsidiaries uses faxes and emails for confidential
> and legally privileged business communications. They do not of themselves
> create legal commitments. Disclosure to parties other than addressees
> requires our specific consent. We are not liable for unauthorised
> disclosures nor reliance upon them.
> If you have received this message in error please advise us immediately
> and destroy all copies of it.
>
> HR Wallingford Limited
> Howbery Park, Wallingford, Oxfordshire, OX10 8BA, United Kingdom
> Registered in England No. 02562099
>
> ________________________________
>
> ------------------------------------------------------------------------------
> Start Your Social Network Today - Download eXo Platform
> Build your Enterprise Intranet with eXo Platform Software
> Java Based Open Source Intranet - Social, Extensible, Cloud Ready
> Get Started Now And Turn Your Intranet Into A Collaboration Platform
> http://p.sf.net/sfu/ExoPlatform
> _______________________________________________
> GeoNetwork-users mailing list
> Geo...@li...
> https://lists.sourceforge.net/lists/listinfo/geonetwork-users
> GeoNetwork OpenSource is maintained at
> http://sourceforge.net/projects/geonetwork
>
>
>
>
>
> --
>
> GeoCat Bridge for ArcGIS allows instant publishing of data and metadata on
> GeoServer and GeoNetwork. Visit http://geocat.net for details.
>
> _________________________
>
> Jose García
>
> GeoCat bv
>
> Veenderweg 13
>
> 6721 WD Bennekom
>
> The Netherlands
>
> http://GeoCat.net <http://geocat.net/>
>
>
>
>
>
> This message has been scanned for viruses by MailControl<http://www.mailcontrol.com/>,
> a service from BlackSpider Technology
>
> Click here<https://www.mailcontrol.com/sr/n274HG0AFdHGX2PQPOmvUvmldA89nuwlhZgA2r7PaGotm4jMfTGRzy6Jv+6tRVI65zXWrIMm5qT1JTd!1uc+!w==>to report this email as spam.
>
>
>
> ------------------------------
>
> *HR Wallingford and its subsidiaries* uses faxes and emails for
> confidential and legally privileged business communications. They do not of
> themselves create legal commitments. Disclosure to parties other than
> addressees requires our specific consent. We are not liable for
> unauthorised disclosures nor reliance upon them.
> If you have received this message in error please advise us immediately
> and destroy all copies of it.
>
> HR Wallingford Limited
> Howbery Park, Wallingford, Oxfordshire, OX10 8BA, United Kingdom
> Registered in England No. 02562099
>
> ------------------------------
>
>

-- 

* GeoCat Bridge for ArcGIS allows instant publishing of data and metadata
on GeoServer and GeoNetwork. Visit http://geocat.net
<http://geocat.net/> for details.  _________________________Jose
GarcíaGeoCat bvVeenderweg 13 6721 WD BennekomThe
Netherlandshttp://GeoCat.net <http://geocat.net/> *