Hi Jose et al
I have made great strides thanks to your guidance 
! Thank you very much indeed.
I now need to understand a bit more about how to make complex items available in the user interface.
For example - I have added a schema called mim. This – basically – comprises two lists – “inputs” and “outputs”. Each list contains 0 or more elements “input” or “output” – and each of those derive from a base “ioType” element type (so they are identical except for the element name).
Sorry to throw it at you but here's the new schema. What I would like to see on the web page when I create some metadata is – in the contentInfo section – a subsection called “Inputs” with a subsection for each input; and a subsection called “Outputs” with a subsection for each output.
I have modified the labels.xml accordingly (I think). However all I currently see are the fields for a single ioType and no text or sections for Inputs or Outputs.
So the question is – basically – how do I get a template built so that geonetwork will display sections as per the xml structure here and allow the user to add and remove inputs and outputs to their little heart’s desires? Very much appreciate any help you can offer – as I say, couldn’t have got this far without you :-}
<contentInfo>
<mim:modelInstance>
<mim:inputs>
<mim:input>
<mim:featureType>Feature type</mim:featureType>
<mim:position>Position</mim:position>
<mim:parameter>Parameter</mim:parameter>
<mim:timeRange>timeRange</mim:timeRange>
<mim:timeStepType>timesteptype</mim:timeStepType>
<mim:maximumTimestep>Maximum timestep</mim:maximumTimestep>
<mim:minimumTimestep>Minimum timestep</mim:minimumTimestep>
</mim:input>
</mim:inputs>
<mim:outputs>
<mim:output>
<mim:featureType>Feature type</mim:featureType>
<mim:position>Position</mim:position>
<mim:parameter>Parameter</mim:parameter>
<mim:timeRange>timeRange</mim:timeRange>
<mim:timeStepType>timesteptype</mim:timeStepType>
<mim:maximumTimestep>Maximum timestep</mim:maximumTimestep>
<mim:minimumTimestep>Minimum timestep</mim:minimumTimestep>
</mim:output>
</mim:outputs>
</mim:modelInstance>
</contentInfo>
<?xml version="1.0" encoding="utf-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:gmd="http://www.isotc211.org/2005/gmd" xmlns:gco="http://www.isotc211.org/2005/gco" xmlns:gml="http://www.opengis.net/gml" xmlns:mim="http://www.hrwallingford.co.uk/mim/1.0" targetNamespace="http://www.hrwallingford.co.uk/mim/1.0" elementFormDefault="qualified" version="1.0">
<!-- =========================================================================== -->
<xs:import namespace="http://www.isotc211.org/2005/gmd" schemaLocation="../../../iso19139/schema/gmd/gmd.xsd"/>
<xs:import namespace="http://www.isotc211.org/2005/gco" schemaLocation="../../../iso19139/schema/gco/gco.xsd"/>
<xs:import namespace="http://www.opengis.net/gml" schemaLocation="../../../iso19139/schema/gml/gml.xsd"/>
<!-- =========================================================================== -->
<!-- =========================================================================== -->
<xs:element name="modelInstance" type="mim:modelInstanceType"/>
<xs:element name="inputs" type="mim:inputListType"/>
<xs:element name="outputs" type="mim:outputListType"/>
<xs:element name="input" type="mim:ioType"/>
<xs:element name="output" type="mim:ioType"/>
<!-- =========================================================================== -->
<!-- =========================================================================== -->
<xs:complexType name="modelInstanceType">
<xs:annotation>
<xs:documentation>Data specific to a model instance</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element ref="mim:inputs" minOccurs="1" maxOccurs="1"/>
<xs:element ref="mim:outputs" minOccurs="1" maxOccurs="1"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="inputListType">
<xs:annotation>
<xs:documentation>A list of inputs for a model instance</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element ref="mim:input" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="outputListType">
<xs:annotation>
<xs:documentation>A list of outputs for a model instance</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="gmd:AbstractMD_ContentInformation_Type">
<xs:sequence>
<xs:element ref="mim:output" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="inputType">
<xs:annotation>
<xs:documentation>An input for a model instance</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="mim:ioType"/>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="outputType">
<xs:annotation>
<xs:documentation>An output for a model instance</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="mim:ioType"/>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="ioType">
<xs:annotation>
<xs:documentation>Base type for both input and output for a model instance</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element name="description" type="gco:CharacterString_PropertyType"/>
<xs:element name="featureType" type="gco:CharacterString_PropertyType"/>
<xs:element name="position" type="gco:CharacterString_PropertyType"/>
<xs:element name="parameter" type="gco:CharacterString_PropertyType"/>
<xs:element name="timeRange" type="gco:CharacterString_PropertyType"/>
<xs:element name="timeStepType" type="gco:CharacterString_PropertyType"/>
<xs:element name="maximumTimestep" type="gco:CharacterString_PropertyType"/>
<xs:element name="minimumTimestep" type="gco:CharacterString_PropertyType"/>
</xs:sequence>
</xs:complexType>
<!-- =========================================================================== -->
</xs:schema>
From: Jose Garcia [mailto:jose.garcia@…444…]
Sent: Friday, April 25, 2014 3:13 PM
To: Paul Cleverley
Subject: Re: [GeoNetwork-users] Schema plugin and profile
Hi Paul
Not there as the xyz it's only an schema template. If you have a model.xsd should be referenced there.
See for example: https://github.com/geonetwork/schema-plugins/blob/master/iso19139.napm/schema.xsd#L11
<xs:import namespace="http://www.geoconnections.org/nap/napMetadataTools/napXsd/napm" schemaLocation="schema/napm/napm.xsd"/>
You should change for your model.xsd.
Regards,
Jose GarcĂa
On Fri, Apr 25, 2014 at 4:03 PM, Paul Cleverley <P.Cleverley@...1309...<mailto:P.Cleverley@…1309…>> wrote:
Hi Jose
The xyz schema.xsd looks like this:
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema targetNamespace="http://my/schema/target/namespace" elementFormDefault="qualified"
xmlns:xyz="http://my/schema/target/namespace" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:gmd="http://www.isotc211.org/2005/gmd" xmlns:gmx="http://www.isotc211.org/2005/gmx"
xmlns:srv="http://www.isotc211.org/2005/srv">
<xs:include schemaLocation="schema/xyz.xsd"/>
<xs:import namespace="http://www.isotc211.org/2005/srv" schemaLocation="schema/srv/srv.xsd"/>
</xs:schema>
But there is no schema subdirectory containing xyz.xsd… any ideas if this is missing or not required in a sample?
Cheers
Paul
From: Jose Garcia [mailto:jose.garcia@…444…]
Sent: Friday, April 25, 2014 1:50 PM
To: Paul Cleverley
Cc: geonetwork-users@lists.sourceforge.net<mailto:geonetwork-users@lists.sourceforge.net>
Subject: Re: [GeoNetwork-users] Schema plugin and profile
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.Cleverley@...1309...<mailto:P.Cleverley@…1309…>> 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:jose.garcia@…444…]
Sent: Friday, April 25, 2014 1:34 PM
To: Paul Cleverley
Cc: geonetwork-users@lists.sourceforge.net<mailto:geonetwork-users@lists.sourceforge.net>
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.Cleverley@...1309...<mailto:P.Cleverley@…1309…>> 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.cleverley@...1309...<mailto:p.cleverley@…1309…><mailto:p.cleverley@…1309…>
T: +44 (0)1491 822483<tel:%2B44%20%280%291491%20822483>
<http://www.hrwallingford.com/banner.html>
________________________________
[HR Wallingford Logo]
HR Wallingford
Howbery Park, Wallingford, Oxfordshire OX10 8BA, United Kingdom
T: +44 (0)1491 835381<tel:%2B44%20%280%291491%20835381> F: +44 (0)1491 832233<tel:%2B44%20%280%291491%20832233>
www.hrwallingford.com<http://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
GeoNetwork-users@lists.sourceforge.net<mailto:GeoNetwork-users@lists.sourceforge.net>
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/>
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/MZbqvYs5QwJvpeaetUwhCQ==> 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/> for details.
_________________________
Jose GarcĂa
GeoCat bv
Veenderweg 13
6721 WD Bennekom
The Netherlands
http://GeoCat.net/>
________________________________
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/> for details.
_________________________
Jose GarcĂa
GeoCat bv
Veenderweg 13
6721 WD Bennekom
The Netherlands
http://GeoCat.net/>
________________________________
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
________________________________
