[GeoNetwork-devel] Proposal for vote: VirtualCSW

GeoNetwork GeoNetwork Developer
1

Dear PSC members,

A proposal to add the capability to define custom CSW entry points that applies extra criteria to the CSW requests.

http://trac.osgeo.org/geonetwork/wiki/proposals/VirtualCSW

A patch is attached to the the related issue (http://trac.osgeo.org/geonetwork/ticket/660).

Please vote.

Cheers,
Jose García

2

Dear Jose,
+1 from me.
Cheers,
Jeroen

On 17 nov. 2011, at 22:15, jose garcia wrote:

Dear PSC members,

A proposal to add the capability to define custom CSW entry points that applies extra criteria to the CSW requests.

http://trac.osgeo.org/geonetwork/wiki/proposals/VirtualCSW

A patch is attached to the the related issue (http://trac.osgeo.org/geonetwork/ticket/660).

Please vote.

Cheers,
Jose García

All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@anonymised.comet
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork

3

+1 - adds nice flexibility/adaptability to CSW.

(This should be documented in developers manual and perhaps included in an example of how to add services to your own GeoNetwork overlay via configuration overrides as it would be something I think quite a few sites would want to know how to do and maintain over different releases!).

Cheers and thanks,
Simon
________________________________________
From: jose garcia [josegar74@anonymised.com]
Sent: Friday, 18 November 2011 8:15 AM
To: geonetwork-devel@lists.sourceforge.net
Subject: [GeoNetwork-devel] Proposal for vote: VirtualCSW

Dear PSC members,

A proposal to add the capability to define custom CSW entry points that applies extra criteria to the CSW requests.

http://trac.osgeo.org/geonetwork/wiki/proposals/VirtualCSW

A patch is attached to the the related issue (#660 (Virtual CSW endpoints) – GeoNetwork opensource Developer website).

Please vote.

Cheers,
Jose García

4

2011/11/19 <Simon.Pigot@anonymised.com>:

+1 - adds nice flexibility/adaptability to CSW.

(This should be documented in developers manual

Maybe an advanced configuration chapter in the user configuration ?

and perhaps included in an example of how to add services to your own GeoNetwork overlay via configuration overrides

Here is an example
<overrides xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance&quot;&gt;
  <!-- Add custom CSW service -->
  <file name=".*/WEB-INF/config-csw-servers.xml">
    <addXML xpath="services">
      <service name="csw-inspire">
        <class name=".services.main.CswDispatcher">
          <param name="filter" value="+inspirerelated:on"/>
        </class>
      </service>
    </addXML>
  </file>
  <file name=".*/WEB-INF/user-profiles.xml">
    <addXML xpath="profile[@name='Guest']">
      <allow service="csw-inspire"/>
    </addXML>
  </file>
</overrides>

Cheers

Francois

as it would be something I think quite a few sites would want to know how to do and maintain over different releases!).

Cheers and thanks,
Simon
________________________________________
From: jose garcia [josegar74@anonymised.com]
Sent: Friday, 18 November 2011 8:15 AM
To: geonetwork-devel@lists.sourceforge.net
Subject: [GeoNetwork-devel] Proposal for vote: VirtualCSW

Dear PSC members,

A proposal to add the capability to define custom CSW entry points that applies extra criteria to the CSW requests.

http://trac.osgeo.org/geonetwork/wiki/proposals/VirtualCSW

A patch is attached to the the related issue (http://trac.osgeo.org/geonetwork/ticket/660).

Please vote.

Cheers,
Jose García

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
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

5

Hi Jose and list,

this capability is very nice; however, defining the CSW as "virtual", would
imply that we can create CSW subservices, each one with its own scope, where a
user (and her metadata) cannot "escape" from.
With this proposal, the "scope" concept holds only in the case of a read-only
CSW interface; anyway this concept is not enforced when including also the
transactional part.
Let's say we have a user profile where users can only perform CSW requests to
a given Virtual CSW, and also perform Transactions. If the user inserts a
metadata that does not match the Virtual CSW filter, the metadata will then be
invisible to the user (when only using CSW interface, of course). Maybe it
would be useful to define a XSL stylesheet to process metadata to be inserted
via CSW, to make sure they are consistent with the filter (either by rejecting
the insert request or by modifing the metadata to make it filter-compliant).
Update and delete transaction use cases should be examined as well.

   Ciao,
   Emanuele

Alle 22:15:24 di Thursday 17 November 2011, jose garcia ha scritto:

Dear PSC members,

A proposal to add the capability to define custom CSW entry points that
applies extra criteria to the CSW requests.

http://trac.osgeo.org/geonetwork/wiki/proposals/VirtualCSW

A patch is attached to the the related issue (
http://trac.osgeo.org/geonetwork/ticket/660).

Please vote.

Cheers,
Jose García

6

Hi Emanuele

Thanks for feedback and sorry about delay in response.

You’re right about transaction service, but the check is not easy to do if metadata is not inserted, so can use lucene to query for it (one solution to implement can be insert the record in db, query for it using the filter and remove it if doesn’t fill the filter).

For now, I’ll add in manual about the transaction limitation and can open a issue in trac to manage about transaction improvement if seem ok.

Regards,
Jose García

On Wed, Nov 23, 2011 at 11:09 AM, Emanuele Tajariol <e_tajariol@anonymised.com> wrote:

Hi Jose and list,

this capability is very nice; however, defining the CSW as “virtual”, would
imply that we can create CSW subservices, each one with its own scope, where a
user (and her metadata) cannot “escape” from.
With this proposal, the “scope” concept holds only in the case of a read-only
CSW interface; anyway this concept is not enforced when including also the
transactional part.
Let’s say we have a user profile where users can only perform CSW requests to
a given Virtual CSW, and also perform Transactions. If the user inserts a
metadata that does not match the Virtual CSW filter, the metadata will then be
invisible to the user (when only using CSW interface, of course). Maybe it
would be useful to define a XSL stylesheet to process metadata to be inserted
via CSW, to make sure they are consistent with the filter (either by rejecting
the insert request or by modifing the metadata to make it filter-compliant).
Update and delete transaction use cases should be examined as well.

Ciao,
Emanuele

Alle 22:15:24 di Thursday 17 November 2011, jose garcia ha scritto:

Dear PSC members,

A proposal to add the capability to define custom CSW entry points that
applies extra criteria to the CSW requests.

http://trac.osgeo.org/geonetwork/wiki/proposals/VirtualCSW

A patch is attached to the the related issue (
http://trac.osgeo.org/geonetwork/ticket/660).

Please vote.

Cheers,
Jose García

7

hi Jose,

the main implementation issue seems to be that you would need to check if a metadata would be found by a virtual CSW filter, in order to know whether to accept it or reject it.

I don’t think it is necessary to first store it in the db to do this – you could use a very small in-memory Lucene index that is otherwise the same as our ‘normal’ Lucene index, to add the document to and see if you get it back when querying for it with the Virtual CSW filter.

Kind regards
Heikki Doeleman

On Thu, Dec 1, 2011 at 11:54 AM, jose garcia <josegar74@anonymised.com> wrote:

Hi Emanuele

Thanks for feedback and sorry about delay in response.

You’re right about transaction service, but the check is not easy to do if metadata is not inserted, so can use lucene to query for it (one solution to implement can be insert the record in db, query for it using the filter and remove it if doesn’t fill the filter).

For now, I’ll add in manual about the transaction limitation and can open a issue in trac to manage about transaction improvement if seem ok.

Regards,
Jose García

On Wed, Nov 23, 2011 at 11:09 AM, Emanuele Tajariol <e_tajariol@anonymised.com> wrote:

Hi Jose and list,

this capability is very nice; however, defining the CSW as “virtual”, would
imply that we can create CSW subservices, each one with its own scope, where a
user (and her metadata) cannot “escape” from.
With this proposal, the “scope” concept holds only in the case of a read-only
CSW interface; anyway this concept is not enforced when including also the
transactional part.
Let’s say we have a user profile where users can only perform CSW requests to
a given Virtual CSW, and also perform Transactions. If the user inserts a
metadata that does not match the Virtual CSW filter, the metadata will then be
invisible to the user (when only using CSW interface, of course). Maybe it
would be useful to define a XSL stylesheet to process metadata to be inserted
via CSW, to make sure they are consistent with the filter (either by rejecting
the insert request or by modifing the metadata to make it filter-compliant).
Update and delete transaction use cases should be examined as well.

Ciao,
Emanuele

Alle 22:15:24 di Thursday 17 November 2011, jose garcia ha scritto:

Dear PSC members,

A proposal to add the capability to define custom CSW entry points that
applies extra criteria to the CSW requests.

http://trac.osgeo.org/geonetwork/wiki/proposals/VirtualCSW

A patch is attached to the the related issue (
http://trac.osgeo.org/geonetwork/ticket/660).

Please vote.

Cheers,
Jose García

All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d

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