Colleague tickets are tickets that individual staff can provide to visiting colleagues. The member of staff who issues the ticket is responsible for the visitor's network usage - the ISSS rules apply. Academic visitors staying in Cambridge for more than a month should normally obtain a Raven password rather than using the ticketing system.
To create a colleague ticket, go to the Console, and log in using your CRSid and Raven password. Select the Colleague Tickets tab.
Complete the information for Created For Valid From and Valid Through then select the + button under Password to generate a random password. You can now choose to send the information to them by email or SMS, to delete the ticket, or to print it out and give it to them in person.
Institution tickets - including bulk tickets
Tickets may be issued by members of the "University Wireless Service Admin Group" for the institution concerned; this is a group within the Lookup directory whose membership is determined by the institution. As well as individual tickets there is provision for bulk issuing of tickets for an event such as a conference. The period of validity is fixed at issue; it is also possible to set a duration of validity from first use.
To issue tickets, authorised users should go to the Console, and log in using your CRSid and Raven password.
Visitor Tickets (single user)
The process for this is identical to that in Short-term colleague tickets above. However, note that tickets are really intended to be short-term; academic visitors staying in Cambridge for more than a month should normally obtain a Raven password rather than using the ticketing system.
The system provides for the creation of large batches of user tickets. To create an event select the Events tab and then the Click here to create a new event link. Complete the form (inline help is provided), then select the Save button to save the event. Note that you cannot change the number of tickets for an event after you have saved the event - if you find that you need to create more tickets for the same event you will need to create a new event (probably with a name related to the original).
The system will create the number of tickets you specify, all with the same date/duration values. The event functionality also includes the ability to export the tickets as a CSV (comma-separated variable) file for loading into a spreadsheet or to print the user tickets in a one-per-page format suitable for stuffing in envelopes or handing to users.
You an also edit the event if you need to change the name, valid dates or duration, or expire (cancel) an event. These actions affect all the associated user tickets.
Each ticket should be assigned to an individual and, if problems arise with the use of the service, the person to whom the ticket was assigned will be held responsible for its use. Issuing institutions must keep a record of the person to whom each ticket has been assigned (and similarly if they issue a spare ticket to a user who has forgotten their details, this must be recorded).
Last updated: February 2014