pergamonmu:readers:deferredupdates
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
pergamonmu:readers:deferredupdates [2017/09/05 07:50] admin |
pergamonmu:readers:deferredupdates [2017/09/19 12:50] (current) admin |
||
|---|---|---|---|
| Line 31: | Line 31: | ||
| For a tutor group update for example, the search criteria is easy: simply select the **current** tutor group from the drop down list in the tutor group criteria row. If the selection is displayed with a number that you do not recognise, simply ignore it: this is a unique internal identification number used by the search system and for support purposes (if required). | For a tutor group update for example, the search criteria is easy: simply select the **current** tutor group from the drop down list in the tutor group criteria row. If the selection is displayed with a number that you do not recognise, simply ignore it: this is a unique internal identification number used by the search system and for support purposes (if required). | ||
| - | **NOTE:** Trying to perform updates of this nature using **criteria** is extremely dangerous - update group 1 to 2, group 2 to 3, and group 3 to 4 for example, results in everyone in group 4 (think about it...) unless you are very clear about the criteria and order in which you perform updates. As a result, we have deliberately implemented a system where only the **specific reader** identified at this stage is used as the target of the modification. The change therefore becomes very targeted, and removes the chances of making an error when configuring a deferred update package. In other words, **if the reader is not in the results list, it will not be affected by the changes**. | + | **Why do we search for and identify the individual readers, instead of just using a group name?** |
| + | |||
| + | Trying to perform updates of this nature just using wild-card **criteria** (e.g. the group name) can be extremely dangerous - update group 1 to 2, group 2 to 3, and group 3 to 4 for example, results in everyone in group 4 (think about it...) unless you are very clear about the criteria and order in which you perform updates. As a result, we have deliberately implemented a system where only the **specific reader** identified at this stage is used as the target of the modification. The change therefore becomes very targeted, and removes the chances of making an error when configuring a deferred update package. In other words, **if the reader is not in the results list, it will not be affected by the changes**. | ||
| ===== Attaching Changes ===== | ===== Attaching Changes ===== | ||
| Line 37: | Line 39: | ||
| {{:pergamonmu:readers:deferred_update_change1.jpg?direct&200 |}} Once a set of readers are identified, changes can be attached to the package. Click on the left-hand side of the **Changes** list to display the context-sensitive menu, containing the list of changes that can be made to the readers (in this version of the software). Select what type of change is required and a new row is added to the list. | {{:pergamonmu:readers:deferred_update_change1.jpg?direct&200 |}} Once a set of readers are identified, changes can be attached to the package. Click on the left-hand side of the **Changes** list to display the context-sensitive menu, containing the list of changes that can be made to the readers (in this version of the software). Select what type of change is required and a new row is added to the list. | ||
| - | **Note:** Not all areas can be changed by this method - you only have access to fields that are logical yo receive bulk changes - tutor groups are available for example, but the reader Date of Birth is not as it is unlikely that a large number of readers would have the same date. | + | **Note:** Not all areas can be changed by this method - you only have access to fields that are logical to receive bulk changes - tutor groups are available for example, but the reader Date of Birth is not as it is unlikely that a large number of readers would have the same date. |
| If you need to remove a row added erroneously, click the row and select the [**Remove Row**] option in the meu. | If you need to remove a row added erroneously, click the row and select the [**Remove Row**] option in the meu. | ||
| - | {{:pergamonmu:readers:deferred_update_change2.jpg?direct&200 |}}In order to set a new value, click the **right-hand** column of the selected row - phrases and dates will display and edit box, while known values (such as tutor groups, gender, circulations profiles etc.) will provide the available values in a drop-down list. | + | {{:pergamonmu:readers:deferred_update_change2.jpg?direct&200 |}}In order to set a new value, click the **right-hand** column of the selected row - phrases and date fields will display an edit box for you to enter a value manually, while known values (such as tutor groups, gender, circulations profiles etc.) will provide the available values in a drop-down list. |
| More than one change can be made to the selected readers if required. In order to add another change, click the left-hand column again in order to select a new change from the context-sensitive menu. | More than one change can be made to the selected readers if required. In order to add another change, click the left-hand column again in order to select a new change from the context-sensitive menu. | ||
pergamonmu/readers/deferredupdates.1504597847.txt.gz · Last modified: 2017/09/05 07:50 by admin
Page Tools
