| 103 | | * Tracking changes to metadata - need to know who, what and when changes are made to metadata. How to do this in GeoNetwork? Perhaps a database driven approach which uses a metadata history table that is triggered from the metadata table? Some comparison of metadata records from different versions would still be necessary to determine changes because in it's simplest form the history table would have a complete copy of the metadata record in it. |
| | 103 | * Tracking changes to metadata - need to know who, what and when changes are made to metadata. How to do this in GeoNetwork? Perhaps a database driven approach which uses a metadata history table that is triggered from the metadata table? Some comparison of metadata records from different versions would still be necessary to determine changes because in it's simplest form the history table would have a complete copy of the metadata record in it. |
| | 104 | |
| | 105 | * A rewrite of the harvester module/component is required at some stage (see proposal http://trac.osgeo.org/geonetwork/wiki/refactoring_harvesters). However for 2.8 this is a lot of work to get done between now and July when the RC process should start (if we are to release 2.8 in August?) especially if we wanted to keep the documentation up to date. Any word on whether this is still proposed for 2.7? |
