Intermediate

The IWE Framework project focuses on facilitating application development across the UCLA campus by providing services and tools available to all developers in order to create consistency throughout applications within the MyUCLA umbrella hassle-free. The MyUCLA web portal houses many applications for virtually every type of campus affiliate, justifying a need for a centralized utility to handle the diversity in functionality and user base.

Software as a Service is the new normal for many of us due to cost, staffing and speed of delivery.  There is a perception that SaaS means no IT is needed.  In reality IT is critical for most SaaS implementations to be successful.  IT’s role is more focused on business analysis, integration, authentication, security and vendor management.  This presentation will focus on key areas where IT can provide value to the organization by partnering on SaaS deployments  including lessons learned and key IT skills for the future.    

As healthcare providers open up patient access to their digital health records, it presents scenarios where patients use mobile apps to “pull” their health records from different providers in one place, or direct a provider to send their data to another provider. However, before such pulling or sharing can begin, a provider may need an explicit patient consent or authorization form (often paper-based) signed by the patient. Today, a patient would typically do this by signing a paper form and the provider would hand over a DVD containing scanned PDF copies of the patient’s health records.

In 2014, Vanessa Kaskiris joined a team in IT at the University of California, Berkeley. Subsequently, and after repeated escalations to management, she would initiate one of the largest investigations in University history and prove a hostile work environment based on gender.

Higher education needs to graduate students on time. Some benefits include: decreasing the student's cost of education and more space for new students. 

To achieve this, one component includes helping students understand what their schedules might look like for the degree they are considering. Another component is giving academic staff visibility on course demand so they can plan appropriately.

Come see how the UCCSC 2018 Mobile Application was developed! Talk to include technical details about platform, language, and tools used.

When crafting access models for content management applications, there are two interconnected standard models: that of role assignment, and that of permissions assignment. Typically, a modern application will have customized roles ("admin", "approver") which are in turn fine tuned by the addition/exclusion of specific permitted actions ("can update forms", "can delete users"). These roles are in turn assigned by managers to users of the application, explicitly, giving them access in proportion to their needs.

The University of California System is big. Like, really really big. 10 campuses, plus a couple auxiliary units employ 21,200 academic staff, 144,000 administrative staff and serve 251,000 students.

Because of the distributed nature of the UC System, each campus has their own Drupal 7 distribution. If they were lucky. Some campuses had more than one. Most campuses had a dozen other web solutions too. This was indeed the Wild West of Web platforms.

All too often, we select technologies based on their abstract capabilities and feature sets -- or worse, on their ability to fit in a budget -- rather than on their strategic appropriateness for a school's mission and culture. This is an unavoidable consequence of the world we work in. Sadly, it all too often can lead to the mis-application, misuse, and in the end the underutilization of a technology or set of tools, and a loss of value, resource, and effort. 

But wait! All is not lost!

When we set out to re-write Ilios in 2014 the most important metric we targeted with every decision was confidence. Developers had to be confident in every change,  and users needed to be confident in every release. This meant building code on well tested foundations, choosing technologies that favored stable releases over breaking changes, and adopting a culture of agile project management and test driven development.