Before locking a database, what must a Data Manager ensure?

Before locking a database, a Data Manager must ensure that all data have been entered and queries are resolved. This step is crucial because locking a database typically signifies that it will no longer be accessible for data entry or modifications. If data entries are incomplete or queries remain unresolved at this stage, it could lead to inaccuracies or gaps in the dataset, which could compromise the integrity of the research or management processes that rely on that data.

Having all data entered ensures that the database accurately reflects the intended information and that any potential issues have been addressed before finalization. This process contributes to robust data quality and reliability, essential components in research, especially when working with sensitive populations such as prisoners. The other choices, while important for overall data management, do not directly pertain to the immediate requirement prior to locking a database.