I'm trying to implement custom code lists in a custom schema. I have
created the codelist file in loc/end/codelists.xml and used a combination
of the new elements' codelists and existing iso 19139 elements that I want
to override. Is there another file I need to edit to assign the codelists
as drop downs? I believe that this is still marked *todo* on the
instructions on the website.
There's no override feature for the translations files. You need to add all
the values for the codelist in your schema, the metadata editor should use
the values from your schema by default.
In case doesn't find a codelist in your schema I think defaults to iso19139
(but not 100% sure), but if the codelist is defined in your schema all the
values for the codelist are taken from there.
Regards,
Jose García
On Tue, Aug 28, 2018 at 3:11 PM Sam Meek <sam.meek@anonymised.com> wrote:
Dear List (Jose?)
I'm trying to implement custom code lists in a custom schema. I have
created the codelist file in loc/end/codelists.xml and used a combination
of the new elements' codelists and existing iso 19139 elements that I want
to override. Is there another file I need to edit to assign the codelists
as drop downs? I believe that this is still marked *todo* on the
instructions on the website.
I did solve it and I did it by using the codelists.xml file in loc/eng/
folder.
I ended up matching on an attribute of the elements in the XML metadata
document that refers to the codelst. For example:
<element codeList="www.mycodelistNameSpace"
codeListValue="myCodeListValue">myCodeListValueLabel</element>
but I used the full codelist namepace in the loc/eng/codelists.xml file to
look up to, does this make sense?
Sam
On Tue, 19 Feb 2019, 18:03 tatau <tarcisio.saraujo@anonymised.com wrote:
Hello Jose,
I used the generator-geonetwork-metadata-schema, but the generated schema
consumes the iso19139 codelist.
On Wed, Feb 20, 2019 at 9:58 AM Sam Meek <sam.meek@anonymised.com> wrote:
Hi
I did solve it and I did it by using the codelists.xml file in loc/eng/
folder.
I ended up matching on an attribute of the elements in the XML metadata
document that refers to the codelst. For example:
<element codeList="www.mycodelistNameSpace"
codeListValue="myCodeListValue">myCodeListValueLabel</element>
but I used the full codelist namepace in the loc/eng/codelists.xml file to
look up to, does this make sense?
Sam
On Tue, 19 Feb 2019, 18:03 tatau <tarcisio.saraujo@anonymised.com wrote: