pergamonmu:readers:deferredupdates
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
pergamonmu:readers:deferredupdates [2017/09/05 07:53] 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 ===== | ||
pergamonmu/readers/deferredupdates.1504598017.txt.gz · Last modified: 2017/09/05 07:53 by admin
Page Tools
