Hi List,
Is there any documentation yet on what would need to be done or changed to convert a metadata profile from one that works with Geonetwork 2.10 to one that works with Geonetwork 3?
I have seen http://www.geonetwork-opensource.org/manuals/trunk/eng/users/customizing-application/implementing-a-schema-plugin.html but that seems to assume you’re starting from scratch.
For what it’s worth, there are still a lot of sections in that document that are marked as TODO.
My assumption is that I’d need to adjust or create the layer and formatter xsl/xml but that other elements would be cross-compatible, is that correct?
Thanks
Jo
···
Jo Cook
t:+44 7930 524 155/twitter:@archaeogeek
Hi,
Unfortunately I haven’t documented the schemas I migrated and I don’t know of anyone who did. But most of the files are the same, maybe just on a different location. What I usually do is just copy the folder and start moving files and adjusting where GeoNetwork complains, having iso19139 as a guide.
For example, now GeoNetwork uses the layout/config-editor.xml to build the editor instead of the xsl views. Also the index file is located on index-fields/default.xsl. Placing and completing right this two files is half the work.
On the other hand, the formatter folder is completely new and builds the metadata views. You can probably start by copying one of the already existing folders (like the one on iso19139) and then adapt it to your schema.
Hope this helps!
María.
···
On Mon, May 16, 2016 at 12:43 PM, Jo Cook <jocook@anonymised.com> wrote:
Hi List,
Is there any documentation yet on what would need to be done or changed to convert a metadata profile from one that works with Geonetwork 2.10 to one that works with Geonetwork 3?
I have seen http://www.geonetwork-opensource.org/manuals/trunk/eng/users/customizing-application/implementing-a-schema-plugin.html but that seems to assume you’re starting from scratch.
For what it’s worth, there are still a lot of sections in that document that are marked as TODO.
My assumption is that I’d need to adjust or create the layer and formatter xsl/xml but that other elements would be cross-compatible, is that correct?
Thanks
Jo
–
Jo Cook
t:+44 7930 524 155/twitter:@archaeogeek
–
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.
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
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