[GeoNetwork-devel] Custom formatting proposal vote

GeoNetwork GeoNetwork Developer
1

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

2

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 GeoNetwork-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geonetwork-devel GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork

3

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 <john.hockaday@anonymised.com> 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 GeoNetwork-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geonetwork-devel GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork

4

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 [jesse.eichar@anonymised.com]
Sent: Wednesday, 2 May 2012 4:13 PM
To: john.hockaday
Cc: Devel geonetwork-devel@lists.sourceforge.net
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 <john.hockaday@anonymised.com<mailto:john.hockaday@anonymised.com>> 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: CustomFormatting – GeoNetwork opensource Developer website

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 GeoNetwork-devel@lists.sourceforge.net<mailto:GeoNetwork-devel@anonymised.comourceforge.net> geonetwork-devel List Signup and Options GeoNetwork OpenSource is maintained at GeoNetwork - Geographic Metadata Catalog download | SourceForge.net

5

At the moment you don’t know which schemas the sheet can be applied to. There is currently a config file in the formatter bundle which could easily contain a property that can specify the supported schemas. Shall I add that change?

I could probably get that change done today. I would also change the list service to have a parameter where one could specify the schema of interest or a metadata id and the list would get the bundles that work for that schema or metadata.

Jesse

On Wed, May 2, 2012 at 11:24 AM, <Simon.Pigot@anonymised.com> wrote:

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 [jesse.eichar@…189…]
Sent: Wednesday, 2 May 2012 4:13 PM
To: john.hockaday
Cc: Devel geonetwork-devel@lists.sourceforge.net
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 <john.hockaday@anonymised.commailto:[john.hockaday@anonymised.com.](mailto:john.hockaday@anonymised.com)> 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 GeoNetwork-devel@lists.sourceforge.netmailto:[GeoNetwork-devel@anonymised.comet](mailto:GeoNetwork-devel@lists.sourceforge.net) https://lists.sourceforge.net/lists/listinfo/geonetwork-devel GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork

6

Jesse,

From my point of view it is a useful change - however I don't want to add anything extra to your workload before the feature freeze - so I don't think the change has to be committed as part of the proposal - it could be added as a small enhancement later (with a ticket as reminder) if you're busy with other things.

In short, I'm voting +1 for the proposal as is - it seems to me to provide a direct and useful way that sites can plug in their own presentations/formats for metadata records.

Cheers,
Simon
________________________________________
From: Jesse Eichar [jesse.eichar@anonymised.com]
Sent: Wednesday, 2 May 2012 7:33 PM
To: Pigot, Simon (CMAR, Hobart)
Cc: john.hockaday@anonymised.com; geonetwork-devel@lists.sourceforge.net
Subject: Re: [GeoNetwork-devel] Custom formatting proposal vote

At the moment you don't know which schemas the sheet can be applied to. There is currently a config file in the formatter bundle which could easily contain a property that can specify the supported schemas. Shall I add that change?

I could probably get that change done today. I would also change the list service to have a parameter where one could specify the schema of interest or a metadata id and the list would get the bundles that work for that schema or metadata.

Jesse

On Wed, May 2, 2012 at 11:24 AM, <Simon.Pigot@anonymised.com<mailto:Simon.Pigot@…192…>> wrote:
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 [jesse.eichar@anonymised.com<mailto:jesse.eichar@anonymised.com>]
Sent: Wednesday, 2 May 2012 4:13 PM
To: john.hockaday
Cc: Devel geonetwork-devel@lists.sourceforge.net<mailto:geonetwork-devel@anonymised.comsts.sourceforge.net>
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 <john.hockaday@anonymised.com<mailto:john.hockaday@anonymised.com><mailto:john.hockaday@anonymised.com>> 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: CustomFormatting – GeoNetwork opensource Developer website

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 GeoNetwork-devel@lists.sourceforge.net<mailto:GeoNetwork-devel@anonymised.comourceforge.net><mailto:GeoNetwork-devel@lists.sourceforge.net> geonetwork-devel List Signup and Options GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork

7

+1 for me Jesse.

Francois

2012/5/1 Jesse Eichar <jesse.eichar@anonymised.com>:

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
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at
http://sourceforge.net/projects/geonetwork

8

Hi Jesse,

I think you should add that change. The easier it is to apply the XSL
for HTML presentation during the harvesting process of a particular
agency/node the more that function is likely to be used. (Especially by
me. ;--) )

Thanks.

John Hockaday

On Wed, 2012-05-02 at 11:33 +0200, Jesse Eichar wrote:

At the moment you don't know which schemas the sheet can be applied
to. There is currently a config file in the formatter bundle which
could easily contain a property that can specify the supported
schemas. Shall I add that change?

I could probably get that change done today. I would also change the
list service to have a parameter where one could specify the schema of
interest or a metadata id and the list would get the bundles that work
for that schema or metadata.

Jesse

On Wed, May 2, 2012 at 11:24 AM, <Simon.Pigot@anonymised.com> wrote:
        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 [jesse.eichar@anonymised.com]
        Sent: Wednesday, 2 May 2012 4:13 PM
        To: john.hockaday
        Cc: Devel geonetwork-devel@lists.sourceforge.net
        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
        <john.hockaday@anonymised.com<mailto:john.hockaday@anonymised.com>> 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
        GeoNetwork-devel@lists.sourceforge.net<mailto:GeoNetwork-devel@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/geonetwork-devel GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork
        

9

Hi John.

It looked like the proposal passed so I have committed it. Now if you would be so kind and create a ticket for harvesting + formatter I will take that ticket and fix it as soon as I can.

Priorities say I have to do the harvesting scheduling work first though.

Jesse

On Thu, May 3, 2012 at 6:40 AM, john.hockaday <john.hockaday@anonymised.com25…> wrote:

Hi Jesse,

I think you should add that change. The easier it is to apply the XSL
for HTML presentation during the harvesting process of a particular
agency/node the more that function is likely to be used. (Especially by
me. ;–) )

Thanks.

John Hockaday

On Wed, 2012-05-02 at 11:33 +0200, Jesse Eichar wrote:

At the moment you don’t know which schemas the sheet can be applied
to. There is currently a config file in the formatter bundle which
could easily contain a property that can specify the supported
schemas. Shall I add that change?

I could probably get that change done today. I would also change the
list service to have a parameter where one could specify the schema of
interest or a metadata id and the list would get the bundles that work
for that schema or metadata.

Jesse

On Wed, May 2, 2012 at 11:24 AM, Simon.Pigot@anonymised.com wrote:
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 [jesse.eichar@anonymised.com]
Sent: Wednesday, 2 May 2012 4:13 PM
To: john.hockaday
Cc: Devel geonetwork-devel@lists.sourceforge.net
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
<john.hockaday@anonymised.commailto:[john.hockaday@anonymised.com](mailto:john.hockaday@...825...)> 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
GeoNetwork-devel@lists.sourceforge.netmailto:[GeoNetwork-devel@anonymised.comsourceforge.net](mailto:GeoNetwork-devel@lists.sourceforge.net) https://lists.sourceforge.net/lists/listinfo/geonetwork-devel GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork

10

Hi Jesse, it's not exactly the same as formatter but at least using
GeoNetwork harvester, you can apply XSL filter [1] [2] (coming from
the process directory) when harvesting . Maybe this option could be
more generic ...

Cheers

Francois

[1] http://trac.osgeo.org/geonetwork/ticket/645
[2] http://geonetwork-opensource.org/manuals/trunk/eng/users/admin/harvesting/index.html#adding-a-geonetwork-node

2012/5/3 Jesse Eichar <jesse.eichar@anonymised.com>:

Hi John.

It looked like the proposal passed so I have committed it. Now if you would
be so kind and create a ticket for harvesting + formatter I will take that
ticket and fix it as soon as I can.

Priorities say I have to do the harvesting scheduling work first though.

Jesse

On Thu, May 3, 2012 at 6:40 AM, john.hockaday <john.hockaday@anonymised.com>
wrote:

Hi Jesse,

I think you should add that change. The easier it is to apply the XSL
for HTML presentation during the harvesting process of a particular
agency/node the more that function is likely to be used. (Especially by
me. ;--) )

Thanks.

John Hockaday

On Wed, 2012-05-02 at 11:33 +0200, Jesse Eichar wrote:
> At the moment you don't know which schemas the sheet can be applied
> to. There is currently a config file in the formatter bundle which
> could easily contain a property that can specify the supported
> schemas. Shall I add that change?
>
>
> I could probably get that change done today. I would also change the
> list service to have a parameter where one could specify the schema of
> interest or a metadata id and the list would get the bundles that work
> for that schema or metadata.
>
>
> Jesse
>
> On Wed, May 2, 2012 at 11:24 AM, <Simon.Pigot@anonymised.com> wrote:
> 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 [jesse.eichar@anonymised.com]
> Sent: Wednesday, 2 May 2012 4:13 PM
> To: john.hockaday
> Cc: Devel geonetwork-devel@lists.sourceforge.net
> 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
> <john.hockaday@anonymised.com<mailto:john.hockaday@anonymised.com.>>
> 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
>
> GeoNetwork-devel@lists.sourceforge.net<mailto:GeoNetwork-devel@anonymised.comourceforge.net>
> https://lists.sourceforge.net/lists/listinfo/geonetwork-devel GeoNetwork
> OpenSource is maintained at http://sourceforge.net/projects/geonetwork
>
>
>
>

------------------------------------------------------------------------------
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
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at
http://sourceforge.net/projects/geonetwork