Opened 6 years ago

Closed 6 years ago

#368 closed enhancement (fixed)

Make GeoNetwork auto-changing your metadata optional

Reported by: heikki Owned by: heikki
Priority: minor Milestone: v2.7.0
Component: General Version: v2.6.0
Keywords: Cc:


Some people have complained about update-fixed-info, that it makes changes changes to their metadata.

We can makes this operation optional, where Admin users might switch it off in the System config page.

If the default option is to run it, there will be effectively no change unless Admins opt for it.

Attachments (1)

368.patch (2.5 KB) - added by fxp 6 years ago.

Download all attachments as: .zip

Change History (10)

comment:1 Changed 6 years ago by heikki

Owner: changed from geonetwork-devel@… to heikki

comment:2 Changed 6 years ago by heikki

committed to trunk

comment:3 Changed 6 years ago by heikki

Resolution: fixed
Status: newclosed

committed to 2.6.x

comment:4 Changed 6 years ago by heikki

Milestone: v2.7.0v2.6.2

comment:5 Changed 6 years ago by fxp

Resolution: fixed
Status: closedreopened

1) This option is not used as DataManager use "system/autofixing/enabled" and settings is "system/autofixing/enable".

2) If you turn this on, create a record and you'll get an extra root element (in XML view) :

<?xml version="1.0" encoding="UTF-8"?>
	<gmd:MD_Metadata xmlns:gts="" xmlns:xsi="" xmlns:gml="" xmlns:gco="" xmlns:gmd="">

and then extra root element on each save action.

3) "CharacterString must have content or parent's nilReason attribute must be legitimate." ISO rule could then only be solved by fix in XML view.

4) dateStamp will never change.

5) " cvc-complex-type.4: Attribute 'id' must appear on element 'gml:Polygon'. (Element: gml:Polygon with parent element: gmd:polygon)" could then only be solved by fix in XML view.

6) Upload document will not work anymore.

7) Multilingual metadata does not work because Id are not created for other languages.

Maybe user should be aware of all these consequences !

comment:6 Changed 6 years ago by heikki

ok, I'll take a look.

seems (1) and (2) and maybe (6) are bugs. The rest is just the effect of not having GeoNetwork making automatic changes to metadata without user intervention.

It's clear that the GeoNetwork editor (except the XML editor) are not OK to be used with this, for reasons like you mention; I think the complainers probably used another means of creating or obtaining metadata, and they want to have it in GeoNetwork unchanged.

We could add some warning when people disable auto-changing, that it is not recommended if they intend to use the GN editor for anything, what do you think ?

Changed 6 years ago by fxp

Attachment: 368.patch added

comment:7 Changed 6 years ago by fxp

Patch for 1 & 2.

For (6), upload works but URL is not created according to configuration. Empty URL and no file to download even if upload is ok.

comment:8 Changed 6 years ago by heikki

thanks ! I've committed your patch to 2.6.x and trunk.

What about warning when people disable autofixing ? Display an otherwise hidden div next to it in the sysconfig page, with the text "It is recommended you do not use the GeoNetwork default or advanced editor when auto-changing is disabled", or something like that ?

comment:9 Changed 6 years ago by fxp

Milestone: v2.6.3v2.7.0
Resolution: fixed
Status: reopenedclosed

Add info in documentation r7493.

Note: See TracTickets for help on using tickets.