| 38 | | a. It is always a good idea to get a printout of the current state of MeLuDI, e.g. a lab protocol, before starting to change anything in BASE. |
| 39 | | b. It is often a good idea to completely remove an erroneous item, and then re-create it with correct data in MeLuDI. Trying to modify item properties in BASE, may have side effects in the way MeLuDI treats the item. An exception is modification of comment text for an item, that normally can be made without software consequences. |
| | 38 | a. The information in this section covers the technical aspects of correcting erroneous MeLuDI entries in BASE. Please check the local lab procedure for the correct way to handle erroneous entries, which for example may require special documentation (on paper or digital) to accompany the action. |
| | 39 | b. For details on how to perform specific actions in BASE, please see the BASE documentation. |
| | 40 | c. It is always a good idea to get a printout of the current state of MeLuDI, e.g. a lab protocol, before starting to change anything in BASE. |
| | 41 | d. It is often a good idea to completely remove an erroneous item, and then re-create it with correct data in MeLuDI. Trying to modify item properties in BASE, may have side effects in the way MeLuDI treats the item. An exception is modification of comment text for an item, that normally can be made without software consequences. |
| | 42 | e. If an erroneous entry happens, when a series of entries should be made, it is often best to fix the erroneous entry, before commencing with the rest of the series. This is because of the side effects, an erroneous entry may have for following entries, e.g. recommended serial numbers or locations on storage plates. Fixing a problem later on is possible, but more steps may be necessary. |
