Hi Bryon,
First, a caveat - my experience is mostly with GN 3.4, so I might be slightly off base on some of these - but a quick glance appears to indicate the core pieces are still correct.
In my recollection, getting the metadata ‘full’ view working requires changing the plugin’s default java packages (https://github.com/geonetwork/core-geonetwork/tree/3.6.x/schemas/iso19139/src/main/java/org/fao/geonet/schema/iso19139), the config-spring-geonetwork file (https://github.com/geonetwork/core-geonetwork/blob/3.6.x/schemas/iso19139/src/main/resources/config-spring-geonetwork.xml), and the groovy files (https://github.com/geonetwork/core-geonetwork/tree/3.6.x/schemas/iso19139/src/main/plugin/iso19139/formatter/groovy/iso19139).
In the packages, add a declaration for your mcp namespace (and any other custom namespaces), and change any lingering references to gmd namespace elements that were moved to mcp. Also change the package name to reduce confusion. The package name cannot contain any periods, as it has to be a canonical java package name. So you would probably want to use something like 19139_mcp_v1_4 or 19139mcp14 instead.
In the config-spring-geonetwork file change the bean class to point to your new package.
In the groovy files, change references to things that are supposed to be in the mcp namespace (e.g., in Handlers, make sure to change the RootEl). If any of your fields contain custom data ‘types’ beyond the core gco ones, you’ll need to add a new Handler (or modify an existing one) for them. For example, when I was working on a Darwin Core plugin, the fact that Darwin Core text fields don’t use gco:CharacterString to package text led to me adding a new Handler. From a glance at the mcp1.4 schema I don’t think this is the case, but I figured I should warn you anyways.
As to the localization issue - you probably already have your labels.xml file updated? If so, I suspect that updating the java packge info might help here as well. Also check your logs to make sure the language is being detected correctly - usually there’s a warning when a language code can’t be read.
Hope this helps!
Kim
···
From: ByronCinNZ <byron@…1263…>
Sent: 09 May 2019 23:50
To: geonetwork-devel@lists.sourceforge.net
Subject: [GeoNetwork-devel] Migrating the MCP-1.4 plugin to GN3.6
Hi,
We are in the process of updating the MCP-1.4 metadata plugin to work in GN
3.6. We are a long way there but are having a difficult time getting a deep
understanding of how the metadata plugins should be properly structured.
We have the plugin now harvesting, editing and creating metadata in the
19139.mcp-1.4 profile. The remaining major issue is that the “Full”
(advanced) view is not portraying the metadata properly. We want this to
display similar to a standard 19139 record with tabs and such. But it
displays as a flat view and many of the element names are not localised.
Any pointers on how we should proceed?
Cheers,
Byron Cochrane
OpenWork Ltd
Nelson NZ
–
Sent from: http://osgeo-org.1560.x6.nabble.com/GeoNetwork-developer-f3874395.html
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork
