On 23/08/2012 6:31 a.m., Chris Holmes wrote: > But CSW in GeoServer should make it easier for GeoNetwork to harvest > information from GeoServers, and to just follow a philosophy of > keeping the metadata close to the data. Yes, this is precisely my interest. There is this complicated problem with metadata - where to keep it. Ideally, you keep it with the data and let likes of geonetwork harvest it. Ditto for geoserver - if its metadata handling mapped better to source and to geonetwork, then keeping things in sync is easily. The problem I have is that geoserver can use all kind of data sources. Geonetwork can harvest from say SDE and from geoserver but how to control the harvester when the same dataset is in arcSDE and also exposed in Geoserver? On the other hand, for some data sources, geoserver lets us build metadata when there is no standard close to the data and no harvester for geonetwork. We have been hacking around with geonetwork harvesters to resolve this. A consistent picture and a way to expose to geonetwork harvesters whether the metadata is created in geoserver or fetched from another source would be good. -- Phil Scadden, Senior Scientist GNS Science Ltd 764 Cumberland St, Private Bag 1930, Dunedin, New Zealand Ph +64 3 4799663, fax +64 3 477 5232
Notice: This email and any attachments are confidential. If received in error please destroy and immediately notify us. Do not copy or disclose the contents. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
