Registration Service comprises 5 main activities
- Hardware: a web server (maintained by Infrastructure Systems and Services Group) and a database server ( maintained by the HFS group).
- Front of house: registration specialists in the Help Centre.
- Database-centred data management: direct database operations, data import and export, manual and automated operations. Activities which are difficult to put into an application or are in development. Management of most units email addresses.
- Application development: and application maintenance for users, ITSS and internal staff. Functionality is described in 'Overview of Services'.
- Specialized functions: negotiations with other University groups and long term planning eg identity management, grouping, mail domain management
- Hardware: the expectation is that it is available 24x7. However if there is a problem the service might not be available for 24 hours. If a fault is notified between 09:00 and 17:00 on a working day, OUCS will commence investigation and correction within one hour (provided that no similar fault is also being handled by the same team).
- Front of house: The expectation is that it will be available between 09:00 and 17:00 on a working day
- Data management: This is on a ' best endeavours' basis
- Application development: This is on a ' best endeavours' basis
- Specialized functions: This is on a ' best endeavours' basis
- Correct OUCS records if a completion date or date of birth is not correct (these errors could prevent people from using self-registration services)
- Provide a rescue code when a password and the security question's answer has been forgotten.
- Provide a new activation code when new account details have not been received
- Help users with the web-based services
- Change of email name and/or personal name
- Additional departmental/college email addresses for a person
- Change of routing for an email address
- Addition of generic email addresses for a department/college
- Student Club and Society registration or renewal for use of email and web facilities
- Registration of new accounts in person (if it is not convenient to receive printed details at the college/dept address).
- Requests for non-personal OUCS accounts
- Nexus accounts: setting quota up to 3GB, visibility in GAL, changing sender address and display name, forwarding, delegation :full and send as, 'keep mail on nexus' - for units whose mail is not handled by OUCS.
- Web accounts: set quota
- Setting ex-directory for email address on the University Contact page- the unit head needs to request it if it is the only address.
- Discretionary extension of expiring accounts
- ITSS register - registration, maintenance, deletion
- EZMLM Mailing list creation, update, deletion, advice
- View expiry date of SSO password
- Create/manage, view expiry date for password for remote access
- Set, update or view Nexus mailbox settings (spam filter, preferred address, forwarding, usage, information)
- Register workstations for TSM backup and manage existing TSM entries, reset TSM passwords
- See a list of their usernames, email addresses, and where their email is routed
- Register for and download Sophos, VPN and other software
- Register an alternative email address
- Register a machine for Wake-on-LAN (WOL)
ITSS (registered IT Support Staff) can via https://register.it.ox.ac.uk/itss/index/
- View and download centrally held data about their users
- View privileged information about- the ITSS Register, university card data for their unit
ITSS from registered units can
- View/set mail routings for their users
- View and update the routings for generic email addresses
- Issue Activation or Rescue code for SSO accounts of their users
- Request 'charged for' quota for their users.
- Register groups of machine for WOL
- Register servers for TSM backup
- Register a land line or mobile phone number
- Register for ITSS Workshops and Conferences
- Download software restricted to ITSS
- University Card based.
- Creation of new Oxford single sign-on identity. A registration letter will usually be sent out by the morning messenger on the next working day after creation of the University Card.
- Update of email addresses when a card changes. This will normally be completed before noon on the next working day after the card is updated.
- Exceptions - if there is a clash of email name or other identification problem, there may be a further delay of typically half to one day (we may need to check outside OUCS).
- Daily. Data listings will be produced for IT Support Staff, Oxford Student System, Library, Weblearn and various projects.
- Daily: Automatic mail list creation from database data - e.g. itss-announce and discuss, spss users
- Three-hourly 0700 to 1900, plus 0100. Mail routing data will be transferred from the database to the live email system.
- Half-hourly. Transfer of queued Remote Access self-registration requests to live system..
- Immediately. TSM registrations and password changes requested via self-registration.
- Disciplinary matters or suspicious death of an active user. Registration can give limited advice and the matter will have to be referred to the "appropriate authority" as per ICTC Regulations 17(5) for action.
- Non-suspicious death, or need to access a personal account whose owner has left. OUCS needs confirmation from Head of House/Department level or equivalent to give delegate access to a mailbox.
- Allocation of a new top-level (www.xxxxxx.ox.ac.uk) web address. This involves confirmation from the head of the parent department that the new activity meets specified criteria. In less simple cases, a Divisional secretary or Faculty Board chairman may need to be contacted. It may take several days for the Registration Manager make the necessary consultations.
- Discretionary extension of web quotas
- Advice on major web sites. People sometimes have quite complicated scenarios and the Registration Manager can advise on possible choices of external and internal facilities.
- Management of hosting of external email domains and addresses eg osswatch, ucisa
- Creation of email domains for new units of University and winding down domains which are no longer University units.
- Liaising with Proctors, Sports Federation, Student Records, Central Administration, Libraries on data issues.
- Reconcile database to current state of Nexus, TSM, Payroll, University Card, Register of Congregation, Student Records
- Email address repository for the University by adding email addresses from units for whom OUCS do not route mail eg physics
- Mass mailings related to OUCS services - eg winding down dialin service, @herald as an email address
- Mass mailings for Central Departments which cant be done by other means.
- Stand-by hardware is available, although of slightly lower capacity. In the event of major system failure we would expect to be able to restore service to the web server within 1 working day and to the database server within 2 working days.
- Software items are held in an external file management repository.
- Copies of the data and other files are held on the backup server and the HFS (daily), off site (weekly) and in a fire safe (monthly)
Front of House
- Authorization to enable more people to handle specialized registration queries has recently been extended to the Help Centre Managers and members of ITS3 in order to improve resilience in this area.
It would be possible for Data consumers to work with their existing data for approx 24/48 hours before it will become increasingly difficult for the University to function, e.g. no new accounts generated and no changes to email routings.
Support via email. Queries to standard OUCS support address firstname.lastname@example.org are automatically routed to the OUCS RT (Request Tracker) system with an automatic acknowledgement being sent to the user. All OUCS Registration staff can contribute to the handling of RT requests.
- We use mailing lists
itss-discussto contact IT support staff
- We can use mailing lists such as 'spss-users' to mail to specific groups users.
- We give talks to new IT support staff and yearly to all IT support staff via ITS3
- Direct mailing to users - on account expiry, email address expiry, winding down of Oxford email addresses
- News items - are put on Oxitems for both OUCS front page and internal communications.
- Web pages are maintained to describe the facilities, the processes and plans.