This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
pergamonmystic:linkedhelp:bison_package_manager [2021/10/09 17:31] admin |
pergamonmystic:linkedhelp:bison_package_manager [2021/10/09 17:32] (current) admin |
||
---|---|---|---|
Line 63: | Line 63: | ||
It is best to ensure that a database backup has been copied to the archive using the [[PergamonMystic:linkedhelp:file_manager|File Manager]] prior to **Destroying a Package** in case it is decided later that the action was incorrect. | It is best to ensure that a database backup has been copied to the archive using the [[PergamonMystic:linkedhelp:file_manager|File Manager]] prior to **Destroying a Package** in case it is decided later that the action was incorrect. | ||
- | The main purposes of //destroying a package// as opposed to simply removing it, is in the identification of catalogue items for removal from library followed by the deliberate removal from the database. Even then, is often wiser to //deactive// then items rather than remove them for future interrogation of the database. | + | The main purposes of //destroying a package// as opposed to simply removing it, is in the identification of catalogue items for removal from the library followed by the //deliberate// removal from the database. Even then, is often wiser to //deactive// the items rather than remove them so that they can be part of future interrogations of the database. |
The recovery of items destroyed in a package can only be performed through the selective data recovery from an archived database, made immediately prior to destruction (so that the package contents can be identified). As time progresses, identification and recovery becomes increasingly problematic due to everyday operations within the library changing the database. | The recovery of items destroyed in a package can only be performed through the selective data recovery from an archived database, made immediately prior to destruction (so that the package contents can be identified). As time progresses, identification and recovery becomes increasingly problematic due to everyday operations within the library changing the database. |