Changes between Version 16 and Version 17 of metadatachanges
- Timestamp:
- Jan 9, 2012, 10:13:04 PM (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
metadatachanges
v16 v17 42 42 Not all records will be tracked as the compute and systems admin cost of this tracking for every record, particularly in larger catalogs is too high. Instead only those records that are edited and updated within the local !GeoNetwork instance will be tracked in the subversion repository. 43 43 44 The database will remain the point of truth for GeoNetwork. That is, changes will be tracked in subversion, but the database will continue to be the facility used by all services. For example, although it is possible to extract the latest version of a metadata record from the subversion repository, all services will continue to extract the latest version of the metadata record from the database table.44 The database will remain the point of truth for !GeoNetwork. That is, changes will be tracked in subversion, but the database will continue to be the facility used by all services. For example, although it is possible to extract the latest version of a metadata record from the subversion repository, all services will continue to extract the latest version of the metadata record from the database table. 45 45 46 46 Using a subversion repository in place of database history tables, forces us to think about maintaining both the subversion repository and the database in a consistent manner ie. committing or aborting the database and subversion repository. In developing this proposal we've examined three approaches:
