[GeoNetwork-devel] Help with schema-suggestions.xml

Hi,

I’m working with schema-suggestions.xml to limit the available options when editing a record. This is working fine up to a point, but I’ve reached a point where I am seeing unexpected behaviour.

The two elements I am trying to work with are described here https://www.agi.org.uk/agi-groups/standards-committee/uk-gemini/40-gemini/1062-gemini-datasets-and-data-series#25 and here https://www.agi.org.uk/agi-groups/standards-committee/uk-gemini/40-gemini/1062-gemini-datasets-and-data-series#26.

They both fall within gmd:resourceConstraints\gmd:MD_LegalConstraints blocks, but the guidelines state that they must be in separate gmd:resourceConstraints blocks.

I’m using the following in schema-suggestions.xml (adapted from ISO19139):

However the behaviour I see is that the button to add a new gmd:resourceConstraints block expands immediately to show empty gmd:accessConstraints, gmd:useConstraints elements (plus gmd:otherConstraints, which is behaving correctly), whereas the behaviour I want is a further option to choose from either gmd:accessConstraints or gmd:useConstraints, in the same way that gmd:otherConstraints offers the choice of either anchor or text.

Is this because gmd:resourceConstraints only contains one option? How can I work around this?

Thanks

Jo

Jo Cook
t:+44 7930 524 155/twitter:@archaeogeek
Please note that currently I do not work on Friday afternoons. For urgent responses at that time, please visit support.astuntechnology.com or phone our office on 01372 744009

Sign up to our mailing list for updates on news, products, conferences, events and training

Astun Technology Ltd, The Coach House, 17 West Street, Epsom, Surrey, KT18 7RL, UK
t:+44 1372 744 009 w: astuntechnology.com twitter:@astuntech

iShare - enterprise geographic intelligence platform
GeoServer, PostGIS and QGIS training
Helpdesk and customer portal

Company registration no. 5410695. Registered in England and Wales. Registered office: 120 Manor Green Road, Epsom, Surrey, KT19 8LN VAT no. 864201149.

Hi Jo

See feedback inline.

Regards,
Jose García

Hi,

I’m working with schema-suggestions.xml to limit the available options when editing a record. This is working fine up to a point, but I’ve reached a point where I am seeing unexpected behaviour.

The two elements I am trying to work with are described here https://www.agi.org.uk/agi-groups/standards-committee/uk-gemini/40-gemini/1062-gemini-datasets-and-data-series#25 and here https://www.agi.org.uk/agi-groups/standards-committee/uk-gemini/40-gemini/1062-gemini-datasets-and-data-series#26.

They both fall within gmd:resourceConstraints\gmd:MD_LegalConstraints blocks, but the guidelines state that they must be in separate gmd:resourceConstraints blocks.

I’m using the following in schema-suggestions.xml (adapted from ISO19139):

However the behaviour I see is that the button to add a new gmd:resourceConstraints block expands immediately to show empty gmd:accessConstraints, gmd:useConstraints elements (plus gmd:otherConstraints, which is behaving correctly), whereas the behaviour I want is a further option to choose from either gmd:accessConstraints or gmd:useConstraints, in the same way that gmd:otherConstraints offers the choice of either anchor or text.

That’s not really possible with schema-suggestions, in gmd:otherConstraints works for gmx:Anchor/gco:CharacterString as gmx:Anchor is a replacement for gco:CharacterString.

But for gmd:accessConstraints and gmd:useConstraints are different elements inside gmd:MD_LegalConstraints

gmd:useLimitation [0…]
gmd:accessConstraints [0…
]
gmd:useConstraints [0…]
gmd:otherConstraints [0…
]

So both are suggested from the previous configuration, you can’t decide to have with the suggestions mechanism in these cases a selection.

Is this because gmd:resourceConstraints only contains one option? How can I work around this?

There’re other alternatives to accomplish this kind of stuff, customizing the metadata view for gmd:resourceConstraints

I’ll send you some work done in other similar profiles to deal with the resource constraints in the scope of INSPIRE, I hope can work for GEMINI 2.3 schema also as requirements look similar.

···

Vriendelijke groeten / Kind regards,

Jose García


Veenderweg 13
6721 WD Bennekom
The Netherlands
T: +31 (0)318 416664

Please consider the environment before printing this email.