[GeoNetwork-devel] CFV: Proposal to add Metadata version history to GeoNetwork

Dear PSC,

A proposal to add metadata history or 'versioning' is available at metadatachanges – GeoNetwork opensource Developer website

Basic summary:

- A user can choose to start 'versioning' on any metadata record or group of metadata records using the 'Actions' menu
- Changes to the metadata record and the properties of the record (privileges, categories, owner, status) are recorded in a subversion repository
- Versions in the subversion repository are stored as XML files, the version history can be viewed using graphical tools such as viewvc-standalone or the command line subversion tools
- This proposal initially provides an audit trail but will also provide the basis for future enhancements that will allow the user to make use of the version history in GeoNetwork

A patch is attached to ticket #726: #726 (Add support for versioning metadata and metadata properties (privileges, categs, status, owner...)) – GeoNetwork opensource Developer website.

Cheers and thanks,
Simon

dear Simon,

one question about this: how does it deal with metadata “snippets” (“directories”), which are separate metadata documents ?

Suppose metadata A has an xlink to a contact info in directory B. To be able to correctly reconstruct a particular revision of A, you must know which was the particular revision of B at that time.

Kind regards,
Heikki Doeleman

On Tue, Jan 10, 2012 at 8:53 AM, Simon.Pigot@anonymised.com wrote:

Dear PSC,

A proposal to add metadata history or ‘versioning’ is available at http://trac.osgeo.org/geonetwork/wiki/metadatachanges

Basic summary:

  • A user can choose to start ‘versioning’ on any metadata record or group of metadata records using the ‘Actions’ menu
  • Changes to the metadata record and the properties of the record (privileges, categories, owner, status) are recorded in a subversion repository
  • Versions in the subversion repository are stored as XML files, the version history can be viewed using graphical tools such as viewvc-standalone or the command line subversion tools
  • This proposal initially provides an audit trail but will also provide the basis for future enhancements that will allow the user to make use of the version history in GeoNetwork

A patch is attached to ticket #726: http://trac.osgeo.org/geonetwork/ticket/726.

Cheers and thanks,
Simon

Write once. Port to many.
Get the SDK and tools to simplify cross-platform app development. Create
new or port existing apps to sell to consumers worldwide. Explore the
Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
http://p.sf.net/sfu/intel-appdev


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

Heikki,

At the moment, the metadata record is versioned with links to fragments (xlinks) resolved, that is, the complete record with all fragments included is versioned. However if one or more of the fragments changes, this would not be captured in the subversion repository until the record or its properties were updated and a new version created in the subversion repo. This approach seemed to be the simplest to me and it could be augmented by creating a new version of a record if a linked fragment it uses is updated (the links a record uses are in the lucene index).

If we were versioning unresolved records in the repository then maybe we could handle situations like you mention below using the svn:externals property to create a connection in the repository to a particular version of a fragment. At the moment I'm more in favour of the versioning resolved records though.

Fragments are not versioned in the current implementation (as far as I recall) but it would be easy to add this and that should be checked/done.

The idea with the current proposal is to get workable base functionality into the next major release and then improve upon it.

Cheers and thanks,
Simon

________________________________________
From: heikki [tropicano@anonymised.com]
Sent: Friday, 13 January 2012 2:29 AM
To: Pigot, Simon (CMAR, Hobart)
Cc: geonetwork-devel@lists.sourceforge.net
Subject: Re: [GeoNetwork-devel] CFV: Proposal to add Metadata version history to GeoNetwork

dear Simon,

one question about this: how does it deal with metadata "snippets" ("directories"), which are separate metadata documents ?

Suppose metadata A has an xlink to a contact info in directory B. To be able to correctly reconstruct a particular revision of A, you must know which was the particular revision of B at that time.

Kind regards,
Heikki Doeleman

On Tue, Jan 10, 2012 at 8:53 AM, <Simon.Pigot@anonymised.com> wrote:
Dear PSC,

A proposal to add metadata history or 'versioning' is available at metadatachanges – GeoNetwork opensource Developer website

Basic summary:

- A user can choose to start 'versioning' on any metadata record or group of metadata records using the 'Actions' menu
- Changes to the metadata record and the properties of the record (privileges, categories, owner, status) are recorded in a subversion repository
- Versions in the subversion repository are stored as XML files, the version history can be viewed using graphical tools such as viewvc-standalone or the command line subversion tools
- This proposal initially provides an audit trail but will also provide the basis for future enhancements that will allow the user to make use of the version history in GeoNetwork

A patch is attached to ticket #726: #726 (Add support for versioning metadata and metadata properties (privileges, categs, status, owner...)) – GeoNetwork opensource Developer website.

Cheers and thanks,
Simon
------------------------------------------------------------------------------
Write once. Port to many.
Get the SDK and tools to simplify cross-platform app development. Create
new or port existing apps to sell to consumers worldwide. Explore the
Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join<http://appdeveloper.intel.com/join&gt;
http://p.sf.net/sfu/intel-appdev
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net<mailto:GeoNetwork-devel@anonymised.comforge.net>
geonetwork-devel List Signup and Options
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork

Hi,

Recently in Geocat.ch I changed the xlinks to have a local:// protocol which essentially calls the local service without an http connection making the xlinks quite a bit quicker to resolve.

Should I propose that to be merged to trunk?

Jesse

On Fri, Jan 13, 2012 at 6:38 AM, Simon.Pigot@anonymised.com wrote:

Heikki,

At the moment, the metadata record is versioned with links to fragments (xlinks) resolved, that is, the complete record with all fragments included is versioned. However if one or more of the fragments changes, this would not be captured in the subversion repository until the record or its properties were updated and a new version created in the subversion repo. This approach seemed to be the simplest to me and it could be augmented by creating a new version of a record if a linked fragment it uses is updated (the links a record uses are in the lucene index).

If we were versioning unresolved records in the repository then maybe we could handle situations like you mention below using the svn:externals property to create a connection in the repository to a particular version of a fragment. At the moment I’m more in favour of the versioning resolved records though.

Fragments are not versioned in the current implementation (as far as I recall) but it would be easy to add this and that should be checked/done.

The idea with the current proposal is to get workable base functionality into the next major release and then improve upon it.

Cheers and thanks,
Simon


From: heikki [tropicano@anonymised.com]
Sent: Friday, 13 January 2012 2:29 AM
To: Pigot, Simon (CMAR, Hobart)
Cc: geonetwork-devel@lists.sourceforge.net
Subject: Re: [GeoNetwork-devel] CFV: Proposal to add Metadata version history to GeoNetwork

dear Simon,

one question about this: how does it deal with metadata “snippets” (“directories”), which are separate metadata documents ?

Suppose metadata A has an xlink to a contact info in directory B. To be able to correctly reconstruct a particular revision of A, you must know which was the particular revision of B at that time.

Kind regards,
Heikki Doeleman

On Tue, Jan 10, 2012 at 8:53 AM, Simon.Pigot@anonymised.com wrote:
Dear PSC,

A proposal to add metadata history or ‘versioning’ is available at http://trac.osgeo.org/geonetwork/wiki/metadatachanges

Basic summary:

  • A user can choose to start ‘versioning’ on any metadata record or group of metadata records using the ‘Actions’ menu
  • Changes to the metadata record and the properties of the record (privileges, categories, owner, status) are recorded in a subversion repository
  • Versions in the subversion repository are stored as XML files, the version history can be viewed using graphical tools such as viewvc-standalone or the command line subversion tools
  • This proposal initially provides an audit trail but will also provide the basis for future enhancements that will allow the user to make use of the version history in GeoNetwork

A patch is attached to ticket #726: http://trac.osgeo.org/geonetwork/ticket/726.

Cheers and thanks,
Simon

Write once. Port to many.
Get the SDK and tools to simplify cross-platform app development. Create
new or port existing apps to sell to consumers worldwide. Explore the

Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join<http://appdeveloper.intel.com/join>

http://p.sf.net/sfu/intel-appdev


GeoNetwork-devel mailing list

GeoNetwork-devel@lists.sourceforge.netmailto:[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


RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2


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

Hi Jesse,

This would be a good improvement - I think you should go ahead and propose it.

Cheers and thanks,
Simon
________________________________________
From: Jesse Eichar [jesse.eichar@anonymised.com]
Sent: Friday, 13 January 2012 6:21 PM
To: Pigot, Simon (CMAR, Hobart)
Cc: tropicano@anonymised.com; geonetwork-devel@lists.sourceforge.net
Subject: Re: [GeoNetwork-devel] CFV: Proposal to add Metadata version history to GeoNetwork

Hi,

Recently in Geocat.ch I changed the xlinks to have a local:// protocol which essentially calls the local service without an http connection making the xlinks quite a bit quicker to resolve.

Should I propose that to be merged to trunk?

Jesse

On Fri, Jan 13, 2012 at 6:38 AM, <Simon.Pigot@anonymised.com> wrote:
Heikki,

At the moment, the metadata record is versioned with links to fragments (xlinks) resolved, that is, the complete record with all fragments included is versioned. However if one or more of the fragments changes, this would not be captured in the subversion repository until the record or its properties were updated and a new version created in the subversion repo. This approach seemed to be the simplest to me and it could be augmented by creating a new version of a record if a linked fragment it uses is updated (the links a record uses are in the lucene index).

If we were versioning unresolved records in the repository then maybe we could handle situations like you mention below using the svn:externals property to create a connection in the repository to a particular version of a fragment. At the moment I'm more in favour of the versioning resolved records though.

Fragments are not versioned in the current implementation (as far as I recall) but it would be easy to add this and that should be checked/done.

The idea with the current proposal is to get workable base functionality into the next major release and then improve upon it.

Cheers and thanks,
Simon

________________________________________
From: heikki [tropicano@anonymised.com<mailto:tropicano@anonymised.com>]
Sent: Friday, 13 January 2012 2:29 AM
To: Pigot, Simon (CMAR, Hobart)
Cc: geonetwork-devel@lists.sourceforge.net<mailto:geonetwork-devel@anonymised.comurceforge.net>
Subject: Re: [GeoNetwork-devel] CFV: Proposal to add Metadata version history to GeoNetwork

dear Simon,

one question about this: how does it deal with metadata "snippets" ("directories"), which are separate metadata documents ?

Suppose metadata A has an xlink to a contact info in directory B. To be able to correctly reconstruct a particular revision of A, you must know which was the particular revision of B at that time.

Kind regards,
Heikki Doeleman

On Tue, Jan 10, 2012 at 8:53 AM, <Simon.Pigot@anonymised.com> wrote:
Dear PSC,

A proposal to add metadata history or 'versioning' is available at metadatachanges – GeoNetwork opensource Developer website

Basic summary:

- A user can choose to start 'versioning' on any metadata record or group of metadata records using the 'Actions' menu
- Changes to the metadata record and the properties of the record (privileges, categories, owner, status) are recorded in a subversion repository
- Versions in the subversion repository are stored as XML files, the version history can be viewed using graphical tools such as viewvc-standalone or the command line subversion tools
- This proposal initially provides an audit trail but will also provide the basis for future enhancements that will allow the user to make use of the version history in GeoNetwork

A patch is attached to ticket #726: #726 (Add support for versioning metadata and metadata properties (privileges, categs, status, owner...)) – GeoNetwork opensource Developer website.

Cheers and thanks,
Simon
------------------------------------------------------------------------------
Write once. Port to many.
Get the SDK and tools to simplify cross-platform app development. Create
new or port existing apps to sell to consumers worldwide. Explore the
Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join<http://appdeveloper.intel.com/join&gt;&lt;http://appdeveloper.intel.com/join&gt;
http://p.sf.net/sfu/intel-appdev
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net<mailto:GeoNetwork-devel@anonymised.comforge.net><mailto:GeoNetwork-devel@lists.sourceforge.net>
geonetwork-devel List Signup and Options
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork

------------------------------------------------------------------------------
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!

_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net<mailto:GeoNetwork-devel@anonymised.comforge.net>

GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork

+1 for me Simon.

Francois

2012/1/10 <Simon.Pigot@anonymised.com>:

Dear PSC,

A proposal to add metadata history or 'versioning' is available at http://trac.osgeo.org/geonetwork/wiki/metadatachanges

Basic summary:

- A user can choose to start 'versioning' on any metadata record or group of metadata records using the 'Actions' menu
- Changes to the metadata record and the properties of the record (privileges, categories, owner, status) are recorded in a subversion repository
- Versions in the subversion repository are stored as XML files, the version history can be viewed using graphical tools such as viewvc-standalone or the command line subversion tools
- This proposal initially provides an audit trail but will also provide the basis for future enhancements that will allow the user to make use of the version history in GeoNetwork

A patch is attached to ticket #726: http://trac.osgeo.org/geonetwork/ticket/726.

Cheers and thanks,
Simon
------------------------------------------------------------------------------
Write once. Port to many.
Get the SDK and tools to simplify cross-platform app development. Create
new or port existing apps to sell to consumers worldwide. Explore the
Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
http://p.sf.net/sfu/intel-appdev
_______________________________________________
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