This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
pergamonmu:readers:obfuscate [2017/08/31 18:42] admin |
pergamonmu:readers:obfuscate [2017/08/31 19:30] (current) admin |
||
---|---|---|---|
Line 1: | Line 1: | ||
====== Obfuscate Readers ====== | ====== Obfuscate Readers ====== | ||
+ | |||
+ | //This feature is only available from v1.0.96 onwards.// | ||
The **Obfuscate Readers** system has been added in the tools menu to allow suitably authorised users to encrypt the readers names in the database in such a way that it complies with data protection regulations in preventing individual identification of readers. | The **Obfuscate Readers** system has been added in the tools menu to allow suitably authorised users to encrypt the readers names in the database in such a way that it complies with data protection regulations in preventing individual identification of readers. | ||
Line 9: | Line 11: | ||
===== Performing the Obfuscation ===== | ===== Performing the Obfuscation ===== | ||
- | - Close down any Reader Management window that is currently open, and ensure that nobody on other terminals are accessing the reader area. | + | - Close down any Reader Management window that is currently open, and ensure that nobody on other terminals are accessing the reader area.\\ \\ |
- | - Login as a suitably authorised user and select [**Manager**] > [**Tools**] > [**Obfuscate Readers**] | + | - Login as a suitably authorised user and select [**Manager**] > [**Tools**] > [**Obfuscate Readers**]\\ \\ |
- | - Read the warning page and then if you still wish to continue, select [**Yes**] | + | - Read the warning page and then if you still wish to continue, select [**Yes**].\\ \\ |
- | - The reader names are encrypted using both your installation license key as well as an internal Pergamon encryption key, then represented in a Base64 display. | + | - The reader names are encrypted using both your installation license key as well as an internal Pergamon encryption key, then represented in a Base64 display.\\ \\ |
- | - The database can still be utilised, but reporting or other display of reader names should be avoided as they will be generally meaningless in their current state. | + | - The database can still be utilised, but reporting or other display of reader names should be avoided as they will be generally meaningless in their current state.\\ \\ |
After obfuscation, refer in any support communications by the reader **barcode** number to identify specific records that need attention. | After obfuscation, refer in any support communications by the reader **barcode** number to identify specific records that need attention. | ||
Line 21: | Line 23: | ||
Follow the same procedure as Obfuscation. | Follow the same procedure as Obfuscation. | ||
+ | ---- | ||
+ | {{:logo.png?nolink |}}\\ | ||
+ | [[:start|Pergamon Wiki Home]] |