Hi Jose: thanks for the info. Trying this via a CSW Transaction (full record) yielded no effect, but scraping the HTML per below. Thanks much for the advice.
..Tom
From: Jose Garcia [mailto:jose.garcia@…444…]
Sent: Thursday, April 25, 2013 15:55
To: Kralidis,Tom [Ontario]
Cc: geonetwork-users@lists.sourceforge.net
Subject: Re: [GeoNetwork-users] metadata version info
Hi
Just checking a bit more about metadata.update, possibly following solution can work, but never tried. The option requires to scrap the HTML code:
If you call first metadata.edit, this service returns the html form of the editor and contains the version field:
<input class="md" type="hidden" name="version" value="1"/>
You can take it and use it for the call you do to metadata.update. This service output is again the metadata editor html form, where should be the previous field with the new value that you can grab for following calls to metadata.update.
Regards,
Jose García
On Thu, Apr 25, 2013 at 9:46 PM, Jose Garcia <jose.garcia@...444...> wrote:
Hi Tom
I'm afraid no good solution to use the metadata.update service. This service is for the metadata editor, due to the counter stuff and can be used in a good way outside of the editor code.
The only options I see are to use either CSW Transaction Update (note that in 2.6.x is not according spec and the service requires the full metadata) or the mef.import service. You can use mef.import to upload the xml file (instead of requiring to create a mef file), if provide the parameter file_type=single.
Regards,
Jose García
On Thu, Apr 25, 2013 at 9:06 PM, Kralidis,Tom [Ontario] <Tom.Kralidis@...43...> wrote:
Using 2.6.4, as part of our metadata management processes we are
programmatically inserting and updating metadata via GN's XML services
API.
Using metadata.update, the version parameter is mandatory. This appears
to be a serial value (i.e. if the current version is 4, then pass 5,
etc.).
We require the current version of the metadata to be able to increment
and pass along the new version as part of metadata updating jobs.
It appears that the 2.8+ XML services API provides more flexible options
(which is great), however we are operationally locked on 2.6.4
currently.
Any advice on how to access this information? Neither xml.search or
xml.metadata.get return this information. Are there any configuration
settings we can use to expose this? We're open to scraping HTML if we
have to.
Thanks
..Tom
------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
_______________________________________________
GeoNetwork-users mailing list
GeoNetwork-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-users
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork
--
GeoCat Bridge for ArcGIS allows instant publishing of data and metadata on GeoServer and GeoNetwork. Visit http://geocat.net for details.
_________________________
Jose García
GeoCat bv
Veenderweg 13
6721 WD Bennekom
The Netherlands
http://GeoCat.net
--
GeoCat Bridge for ArcGIS allows instant publishing of data and metadata on GeoServer and GeoNetwork. Visit http://geocat.net for details.
_________________________
Jose García
GeoCat bv
Veenderweg 13
6721 WD Bennekom
The Netherlands
http://GeoCat.net