No flash message
Some of the content and features delivered by this site requires JavaScript to be enabled in your browser
Wednesday 12 December
My.Anglia > Academic > Astra > Academic Registry - ASTRA


ASTRA Strategy and Governance Board

The ASTRA Strategy and Governance Board was established in March 2015 as part of the SITS Core Capabilities (SCC) Project with a remit to review data related amendments arising during the project. A review of the Terms of Reference and membership of the Board, including a proposed revision to the title of the Board, was undertaken during the summer of 2016. The Board reports to the Digital Strategy Delivery Group (DSDG). The Head of ASTRA Strategy and Governance, Nikki Dibb, co-ordinates the work of the Board.

During the SCC Project the Board considered items relating to user access and security, the data retention policy and the introduction of the role of the Data Steward. In the period following the SCC Project go-live in January 2016 the focus of the Board moved towards formalising data governance principles and procedures to ensure the improvements implemented during the SCC Project could be maintained and protected. This included consideration and approval of a set of overarching Student Data Management and Governance Principles for ASTRA and the implementation of the Data Stewardship role. The Board has a number of standing agenda items which enable the group to keep a watching brief on various items, for example, updates on ASTRA related projects and the use made of ASTRA tools where there is a degree of risk e.g. the proxy login facility.

The Board's current priorities are to:

  • Working in collaboration with the Information Compliance Group progress all actions related to GDPR compliance;
  • Working in collaboration with IT Services oversee the upcoming, strategically driven, ASTRA related project work and escalate any concerns or issues to DSDG;
  • Oversee the required changes to ASTRA (and related systems) which follow from the Faculty reorganisation proposals.

Reference Data Stewardship

The Board has approved the Reference Data governance protocols and procedures which detail the processes Data Stewards must follow to propose changes to reference tables under their stewardship.

Training for Data Stewards was held in June 2017. A recording of the session is available to view here, along with a copy of the accompanying notes. A Summary of the process is provided in the table below for ease of reference.


Principles Process
Data stewardship is a broad role that incorporates processes, policies, guidelines and responsibilities for administering our student record system related data in compliance with business and/or regulatory obligations. A Data Steward’s responsibility stems from an understanding of our business processes and the interaction of business processes with data entities/elements. At Anglia Ruskin Data stewards are responsible for ensuring that the data contained within reference data tables is regularly reviewed to ensure its continuing accuracy, currency and compliance with the seven principles outlined in paragraph 1.2 of the Reference Data governance protocols and procedures document.

1. Process relating to changeable reference data tables

The business area with stewardship for an entity where the table is categorised as changeable makes the proposed change in the ASTRA QA environment.

A request is logged on the ASTRA Data Steward request log on SharePoint detailing the proposed changes. All data stewards will receive an email notification that a new item has been logged and will have 5 working days to raise any concerns or comments. After the 5 day period has passed, providing no issues or concerns are raised, the change is made by the data steward in the production environment. When completing the log please provide all of the requested information and ensure that you have made the changes in the QA environment.

2. Process relating to dynamic reference data tables

The business area with stewardship for an entity where the table is categorised as dynamic adds to and maintains the accuracy of the records within the entity as appropriate. However, the following principles apply:

  • New records always follow the existing coding protocols and naming conventions used within an entity;

  • Proposals to repurpose an entity (i.e. adding a new set of records to an existing table which deviates from the current or primary use of the table) or to deviate from the current primary key coding strategy always require formal approval by the Governance Board.

Reference data is an essential characteristic of any system as it classifies all other data. It is used to ensure consistent reporting and to direct business rules and processes. Reference data has key strategic business value and needs to be governed as such. A controlled approach to handling flat code lists, hierarchical reference data, or mappings between various versions and variations avoids broken business processes and costly integration challenges.

Each reference data table has been categorised as dynamic or changeable:

Changeable:  Data held in tables categorised as changeable will be added to or change occasionally.
Data stewards are able to Read and Write data within these tables but must communicate proposed additions or changes using the process detailed in section 1 on the right;

Dynamic:  Data held in tables categorised as dynamic will be added to or change frequently, for example, Course (CRS) or Module (MOD) records.
Data stewards are able to Read, Write and Delete data within these tables in the course of normal business activity referring to the principles detailed in section 2 on the right


ASTRA Strategy and Goverance Board quick links:


Back to Academic Registry Homepage