How to contact ODCF
IT related requests (cluster access, software installations, cluster issues, workstation problems, technical issues ecc.):
06221 42 3568 (currently not operated due to home office)
Requests regarding group management (group changes, new groups), project management (new projects, project changes), project data, sample swaps, DTAs, data access, aspera and OTP operation:
To avoid time and resource consuming call backs and back-and-forth mails please be complete and informative when writing your support tickets:
Always write a fresh-from-scratch mail when reporting a new issue. Replying to old issues will reopen these tickets and a) break the organization and thematical coherency of an issue report and b) might lead to the mail to go unnoticed, as it will be placed in an already solved ticket. Such postings require time-consuming manual work on our side to disentangle them.
Replying by changing the subject doesn't help, as the ticketing system recognizes old threads from hidden mail headers, which are preserved when replying. The only situation where you should reply is, when your current issue is clearly still the old one. If you are in doubt rather open a new ticket and mention the old one. Merging tickets is much easier then disentangling unrelated ones .
The email subject is the first thing we see and we use it to quickly classify and prioritize a support ticket. Please keep it as concise and complete as possible. We don't mind long subject lines as long as they contain relevant information.
Please create an individual ticket for each (unrelated) question. Mixing unrelated topics in a single ticket makes ticket management hard and ineffective for the supporters.
When asking for software add-ons like R or Python packages and Perl modules always let us know for which version of the base package you require the add-on and on which platform (SuSE or CentOS) it is required.
If you mention it in the subject (which is good!) still repeat the complete request in the mail body. Email subjects are sometimes changed within the ticketing system to canonicalize them or the make them better searchable. All relevant content should be contained in the mail body.
Help us reproduce your issue (that helps us to test our solution) by telling us exactly what you did (commands, scripts, loaded modules) and where you did it (hostname, which cluster, which cluster node).
Help us to understand your problem by sending commands and resulting error messages or error logs. Unless you are an expert and already know for sure the cause of a problem, then don't try to be smart by trimming error messages or error logs. Not so rarely the helpful statements are exactly in the cut-out part .
Attaching scripts to the ticket is ok, but please don't attach datafiles. If you need to send us datafiles then please provide them in some place in the filesystem (e.g. in analysis). As administrators we can access them almost not matter where they are stored. If you refer to these files in the ticket we will understand this as an approval to access them or to make copies of them for testing purposes. If that isn't the case then please let us know.
As soon as you have received an answer from us, you can simply reply to it. Please try to keep answers short and readable. As all communication is stored in the ticketing system, there is no need to cite the complete previous thread in the answer. Cut out the non-relevant parts and just keep the parts you are currently answering to.
In cases where you need to update a ticket before you got an answer from us, you can reply to your own(!) stored sent mail or the Bcc you had sent to yourself (don't forget to change the addressee in the latter case). The ticketing system will recognize the hidden headers and email identifiers (see above) and add your mail to the correct ticket.