Saving Edits in custom schema

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Saving Edits in custom schema

sammeek
Hi List,

I have implemented a schema in GeoNetwork that is mostly working. However
when I try to save the edits in the visual editor I get a 400 bad request.

I have compared the POST with an ISO 19139 POST request to save and I notice
that in my schema, the date field element is prefixed with _X<element
number> and then <gco:date>....

In the ISO 19139 schema, there is no _X prefix and there is no <gco:date>
element, there is just the raw data. I understand the the _X prefix is put
in to stop an XML error with the editor (i.e. it attempts to create an
element with a number as a name, which is not allowed). Am I right in
thinking that the _X and <gco:date> is stripped out somewhere? If so, where
is this in the code please?

Thanks



--
Sent from: http://osgeo-org.1560.x6.nabble.com/GeoNetwork-users-f3860293.html


_______________________________________________
GeoNetwork-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/geonetwork-users
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork
Reply | Threaded
Open this post in threaded view
|

Re: Saving Edits in custom schema

sammeek
Hello,

Is there an answer on this yet? I just need to know where in the code the
request is constructed to the GeoNetwork API when I press the Save button in
the interface. It looks as though the request be being constructed
incorrectly.

Sam



--
Sent from: http://osgeo-org.1560.x6.nabble.com/GeoNetwork-users-f3860293.html


_______________________________________________
GeoNetwork-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/geonetwork-users
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork