Comments

Document Feedback - Review and Comment

Step 1 of 4: Comment on Document

How to make a comment?

1. Use this Protected Document to open a comment box for your chosen Section, Part, Heading or clause.

2. Type your feedback into the comments box and then click "save comment" button located in the lower-right of the comment box.

3. Do not open more than one comment box at the same time.

4. When you have finished making comments proceed to the next stage by clicking on the "Continue to Step 2" button at the very bottom of this page.

 

Important Information

During the comment process you are connected to a database. Like internet banking, the session that connects you to the database may time-out due to inactivity. If you do not have JavaScript running you will recieve a message to advise you of the length of time before the time-out. If you have JavaScript enabled, the time-out is lengthy and should not cause difficulty, however you should note the following tips to avoid losing your comments or corrupting your entries:

  1. DO NOT jump between web pages/applications while logging comments.

  2. DO NOT log comments for more than one document at a time. Complete and submit all comments for one document before commenting on another.

  3. DO NOT leave your submission half way through. If you need to take a break, submit your current set of comments. The system will email you a copy of your comments so you can identify where you were up to and add to them later.

  4. DO NOT exit from the interface until you have completed all three stages of the submission process.

 

Data Quality Standard

Section 1 - Purpose

(1) This standard defines the requirements for the quality of data and information of the RMIT Group.

Top of Page

Section 2 - Authority

(2) Authority for this document is established by the Information Governance Policy.

Top of Page

Section 3 - Scope

(3) This standard applies to all staff with responsibility for creating, managing and using data at RMIT, including temporary employees, contractors, visitors and third parties globally who manage RMIT Group data and information, with the exception of research data as defined by the Research Policy.

Top of Page

Section 4 - Standard

Overview

(4) High-quality data supports University strategy and enables quality insights and decision-making, driven by data that is trusted.

(5) This standard provides the requirements for data quality as well as data quality dimensions and measures to support establishing and maintaining high-quality data at RMIT.

(6) This standard should be used in conjunction with the Data Quality Guideline and supporting tools, which provide staff with further guidance on assessing and improving data quality and implementing this standard in practice.

Requirements

(7) Data created, managed and used at RMIT must be of high quality. Data will be considered high quality when it is fit for its intended purpose and meets the requirements of all stakeholders. 

(8) Data must meet stakeholder requirements for validity, completeness, accuracy, consistency, timeliness and uniqueness, in accordance with the data quality dimensions in this standard.

(9) The level of data quality should be defined, assessed and measured so that it can be improved.

(10) Data that does not meet the expected level of quality must be improved at the source, ie., at the point of data entry, creation or collection. Data that cannot be improved at the source must be corrected prior to use, for purposes such as reporting and analytics.

(11) RMIT is required to ensure that the information it collects, uses, and discloses is accurate, complete, and up-to-date in accordance with relevant Victorian and Australian Privacy laws, specifically the Victorian Information Privacy Principles – IPP3 and the Australian Privacy Principle – APP10 regarding data quality.

Data Quality Dimensions and Measures

(12) The following data quality dimensions are most relevant to the RMIT Group, and should be used when defining, assessing, measuring and reporting on data quality.  These may have equal or varying weights depending on the context of use.

(13) Completeness 

  1. Data must contain values for all expected attributes and instances identified as mandatory.
  2. Completeness can be measured by comparing the number of records where data is populated to the total number of records.*

(14) Validity

  1. Data must contain values that conform to the defined data type, format and precision as required by domain specific business rules.
  2. Validity can be measured by number of records where the validity rules are met and comparing this to the total number of records.

(15) Accuracy

  1. Data must correctly represent the true value of the real-world concept or event being described.*
  2. Accuracy can be measured by the number of erroneous records and comparing this to the total number of records.*

(16) Consistency

  1. Data must be absent of difference, when comparing two or more representations of a thing against a definition.*
  2. Consistency can be measured by the number of matched values across records and comparing this to the total number of records.

(17) Timeliness

  1. Data must represent reality from the required point in time.*
  2. Timeliness can be measured by looking at the time between when data was created and when it is made available for use and by looking at whether the most up-to-date version of the information is available.

(18) Uniqueness

  1. No record exists more than once within a data set or between multiple data sets.
  2. Uniqueness can be measured by the number of unique records identified and comparing that to the total number of records.
The Data Quality Guidelines provide further guidance on how to define an acceptable level of data quality and implement practices to measure, monitor and improve.

* Adapted from DAMA-DMBOK : data management body of knowledge

Earley, S., Henderson, D. & Data Management Association, 2017. DAMA-DMBOK : data management body of knowledge / DAMA International ; senior editor, Deborah Henderson ; editor, Susan Earley ; production editor, Laura Sebastian-Coleman ; bibliography researcher, Elena Sykora ; collaboration tool manager, Eva Smith. 2nd ed., Bradley Beach, New Jersey: Technics Publications.