RATS 2.0 launched two weeks ago today and we have already seen lots of activity in the new system. While the protocol application in RATS 2.0 is very different from what you are used to in legacy RATS, rest assured that we are here to help you! We continue to provide basic and advanced training to the community as indicated below:
|Monday, July 6 (basic)||2:00 – 3:00 PM|
|Thursday, July 9 (advanced)||3:00 – 4:00 PM|
|Tuesday, July 14 (basic)||2:00 – 3:00 PM|
|Friday, July 17 (advanced)||1:00 – 2:00 PM|
|Monday, July 20 (basic)||3:00 – 4:00 PM|
|Thursday, July 23 (advanced)||3:00 – 4:00 PM|
|Tuesday, July 28 (basic)||2:00 – 3:00 PM|
|Friday, July 31 (advanced)||1:00 – 2:00 PM|
Basic training provides an introduction to the new system, covering navigation and terminology.
Advanced training is limited to those who have already attended a basic session; attendees will receive tips for completing their protocol smartform.
Registration is generally capped at 15 people in order to allow sufficient interaction among attendees. Contact RATSHelp@research.ucla.edu to register for an upcoming session.
We look forward to seeing you at an upcoming training; meanwhile, here’s a quick tip regarding research teams:
RATS 2.0 Quick Tip:
When you log on to RATS 2.0, you will notice that we have created a research team for you (when you click on “My Inbox,” you will find your research team on the left hand side of the page). When we migrated protocols into RATS 2.0, we added all personnel listed on your Legacy RATS protocol(s) as research team members. As such, it is important that you review and update your research team members list to only include personnel that you would like to have access to your research team substances and procedures (research team members also have the ability to create team substances and procedures). Research team members DO NOT have the ability to create and submit protocols on your behalf, however you can assign a PI Proxy (or multiple PI Proxies) to your protocols to allow them to submit and create protocol applications on your behalf. You can find the “Assign PI Proxy” activity in the protocol workspace (please see screenshot below).