In GeoNode all metadata attributes are stored at least twice - once in the Django database and once in the GeoNetwork backend. I think of the Django database as canonical and at least for demo.geonode.org am pretty nonchalant about wiping out the GeoNetwork metadata storage during upgrades; it can be regenerated from the Django database using the "django-admin.py updatelayers --settings=geonode.settings" command.
So I don't actually have a lot of experience migrating data from one version of GeoNetwork to another. If searching for "migrate" and "upgrade" doesn't produce useful results, perhaps "backup" would be a useful keyword? It turns up this GeoNetwork mailing list thread for me which looks relevant: http://osgeo-org.1803224.n2.nabble.com/Saving-and-restoring-GeoNetwork-td3900790.html <http://osgeo-org.1803224.n2.nabble.com/Saving-and-restoring-GeoNetwork-td3900790.html> -- David Winslow OpenGeo - http://opengeo.org/ On Tue, May 3, 2011 at 4:25 AM, Jude Mwenda <[email protected]> wrote: > Hi, > tried to google on possible ways to upgrade geonetwork. I would like to > change my geonetwork version and wondering how to do so without metadata > loss. > Any pointers on this? > > Regards >
