From: <Sim...@cs...> - 2012-05-02 09:25:03
|
This could be used in harvester protocols that support requesting formats other than xml (eg Z3950 protocol). You could request html and xml - index the content from the xml, then present using the harvested html format. That way the custodian of the metadata could control the presentation and the indexed content of harvested records if an html bundle exists that can produce output for that schema. I suppose that brings me to a question about the formatters proposal (which I like) - I understand that a formatter could handle records from a number of different schemas (this is good) but if I can get a list of formatters available on a GeoNetwork catalog from the metadata.formatter.list service (in order to request that a record/records be formatted with that formatter), how do I know which metadata schemas a particular formatter can be applied to? (I suspect I would just get nothing back from the formatter if the schema was not supported by it but this is a bit indirect). Cheers, Simon ________________________________________ From: Jesse Eichar [jes...@ca...] Sent: Wednesday, 2 May 2012 4:13 PM To: john.hockaday Cc: Devel geo...@li... Subject: Re: [GeoNetwork-devel] Custom formatting proposal vote The way we use it is that the data is all the same format in the database and one can view it using the formatters. Because of that I never looked at the harvesters issue. One thing I was considering is integrate these with the csw output formats. This would allow csw harvesting. I wouldn't imagine it would be too difficult to modify the harvester to harvest using the formatter service instead of or in addition to the service used currently. Jesse On Wed, May 2, 2012 at 1:38 AM, john.hockaday <joh...@ii...<mailto:joh...@ii...>> wrote: Hi Jesse, I quite like the proposal. We harvest metadata from around Australia and New Zealand. Only yesterday a potential node manager stated that he would like to have their own presentation format of their metadata. You proposal seems like it would allow that. However, maybe I missed something but I didn't see anything to indicate that the URL or remote XSL could be applied to the metadata during the harvesting process. Is that already covered by the application of an XSL during the harvesting configuration or will that also need to be added to the harvesting configuration interface? Thanks. John Hockaday On Tue, 2012-05-01 at 17:59 +0200, Jesse Eichar wrote: > Today in the IRC meeting we discussed my new CustomFormatting > proposal: http://trac.osgeo.org/geonetwork/wiki/CustomFormatting > > > So I would like to put it up for vote. We are branching for 2.8 next > week so I would like to commit the feature this week. > > > Jesse > ------------------------------------------------------------------------------ > 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/ > _______________________________________________ GeoNetwork-devel mailing list Geo...@li...<mailto:Geo...@li...> https://lists.sourceforge.net/lists/listinfo/geonetwork-devel GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork |