DARS Newsletter September 2016
- 1 Introduction
- 1.1 DARS news and features
- 1.2 Reminders
Welcome to this month’s DARS Newsletter. Older newsletters can be found at https://www.darscentral.ox.ac.uk/newsletters, with newsletters since May 2015 held at http://darswiki.bsp.ox.ac.uk/index.php/DARS_Newsletters. And remember that you can contact the DARS helpdesk via firstname.lastname@example.org.
In this issue:
DARS news and features
Maintenance of the Begbroke Data Centre
We are happy to report that the maintenance of a power supply component at the Begbroke data centre was completed successfully on Wednesday 14 September.
Landmark for events
The year 2013 saw the first events to be processed through DARS websites (sometimes referred to as Internet Solutions, or BBIS). At the present time, the event booking module is used by fourteen DARS participants for free and paid-for events. Earlier this month, DARS processed the 25,000th event booking through Internet Solutions. This represents a milestone in engagement with alumni across the University.
Reclassification of Interactions
As mentioned in the July newsletter, and the recent superusers meeting, we have been working with Andrew Murton of Balliol on a script to allow moving of communications that were migrated into the Interactions area back into the communications area, or optionally, simply to be deleted. The pilot process for this is well under way, and we will communicate further once we have the results of the pilot and are ready to roll this out to other participants.
North American Office website
Redesign work for the North American Office website was completed on 15 September. This website marks a first for the DARS Support Centre, since it is the first website containing ‘responsive’ elements – that is, aspects of the design adjust when viewed on different types of devices, such as smartphones. The website can be found at https://www.oxfordna.org.
New DARS Participant
We have held discussions with the Department of Biochemistry, who are preparing to join DARS. They have confirmed that they have no data to migrate: it is probable they will be starting to use DARS in early October.
Benchmarking and Moritz-Heyman reporting
We have requested data for Benchmarking and Moritz-Heyman reporting: we have already started to receive replies. We have a slightly different approach this year, in that we are contacting not only the Directors of Development, but also the Data Officers, who are more likely to be the individuals responsible for the production of data, most obviously for non-DARS Colleges.
Disclosure of Alumni numbers
Please be particularly vigilant if you are asked, either by phone or email, by someone who claims to be an alumnus, for their Alumni Number (Lookup ID). Please follow the policy adopted by the University Alumni office, and always check the full name, date of birth, address, college, course and matriculation year before passing it on, and only give it to the alumnus directly – do not disclose it to others, such as partners or parents. Since such an interaction is a significant one, please record it as an interaction in DARS, noting whether you did, or did not, provide the Alumni Number. If you find that alumni are requesting numbers very frequently, you can direct them to the Alumni website, where there is a page that permits them to request their number at http://www.alumni.ox.ac.uk/node/472.
In order to be compliant with the recommendations of our auditors, if one of your staff members no longer needs access to DARS, your authoriser is responsible for informing the helpdesk by completing a UARF when the staff member leaves and sending it to the DARS helpdesk. Please send the form just to the DARS Helpdesk (email@example.com). If you do not know who your authoriser is, a list can be found in the DARSWiki at http://darswiki.bsp.ox.ac.uk/index.php/Authorised_User_Access_Requestors. If you need to notify other impersonal email addresses (such as UAS University Card) that an employee has left, please send a separate email to each address. Please do not send one email to several such addresses, since only one address will receive the email.