This past fall, the Yale School of Medicine launched the Online Physician Assistant program. This program currently boasts 44 enrolled students from 16 states, including Hawaii, and is set to scale even larger in future cohorts. Since these students will not have the option to come to the library in person, providing the same level of access to materials posed a challenge to traditional delivery methods.
Over the past month Steelsen Smith from the Enterprise Systems and Services group had the opportunity to attend two events related to work we do in Library IT a NERCOMP sponsored security conference and the ILLiad international resource sharing conference.
The first was Boston College’s annual “Security Camp” – a free one day event for IT professionals. The 2015 agenda included lots of timely material, including presentations on identity and access management, docker (a software packaging and containing system), security scanning, DDOS attacks and more. The full agenda is here.
For anyone who manages the deployment of information systems, it has been impossible to avoid docker. In a nutshell, this technology allows users to bundle all of the interrelated parts of an application into a “container” that can then be run on a physical or virtual server. The advantage is that many code packages can share the same server without the overhead of a full virtual machine per application. The platform has proven to be robust, and the presenter (from MIT) made a great case for docker having applications in the classroom or enterprise. The greatest strength of the solution is that applications dependencies, e.g., Java version, can be updated individually without affecting their co-hosted peers. The software can also run on a hardened read-only OS (CoreOS as an example). Docker should not be trusted as fully secure for hosting potentially hostile containers, however. The main vulnerability of the platform comes from its strength – allowing direct hardware sharing. This means that if an application is carefully written to monitor hardware activity it can learn something about the containers it resides with. Also, if an application is able to successfully compromise the kernel it will have access to all other containers on the machine whereas in a dedicated VM it would require a few extra steps.
Another interesting talk focused on handling distributed denial of service attacks (DDoS) effectively. A DDoS is a very basic attack – it drowns out legitimate website requests by triggering an overwhelming number of invalid requests (like shouting in a room where people are speaking) and has become surprisingly easy – there are sites that will let you control their “botnets” of slave machines for a small fee. These attacks are also effective because they rely on the internal operation of fundamental internet protocols (e.g., SNMP or exploiting the TCP handshake) making them hard to protect against. In fact, the two best defenses (note that firewalls are not at all helpful in a DDoS attack) involve using outside providers to manipulate the internet to deflect traffic away from you. For web requests a CDN (content distribution network) can host your website and split it among datacenters around the world which are collectively able to withstand an attack. For attacks based on amplification (requesting a long answer with a short question) a provider like Incapsula or NeuStar can actually intercept internet traffic for you and scrub it – for a sizable fee. While universities generally do not need to worry as much as banks, if the blogosphere takes issue with something done by your institution then a DDoS attack becomes a real possibility.
A few weeks later came the ILLiad International conference in Virginia Beach, VA. Mostly attended by librarians with presentations focused on resource sharing there were a number of interesting talks that applied directly to work in IT both with our support for interlibrary loan software and discovery.
Linked data was one of the unexpected highlights of the conference with the vendor Zepheira giving talks on how relationships between assets as exposed by linked data can drive use. The theory is that discovery necessarily leads to increased use – therefore the easier it is for search engines and link aggregators to discover your content the easier it will be for users to discover it. The natural extension is that, once discovered, your resources should also be easy to request. Consolidated requesting – having your users register once and search and request through a single interface – is one of the ideal outcomes of a library’s analysis and enhancement of its web presence.
Another useful presentation topic addressed how medical libraries handle requests from independent medical researchers and physicians. A service, loansome doc, allows physicians to affiliate themselves with a library to request medical articles. The library then procures those materials on their behalf. There are more differences than similarities, however, when it comes to how these materials are filled. Some libraries have a nearly automated process while others still provide highly individualized service. Some libraries allow electronic delivery to be automatic while others require approval and payment. While it was fascinating to learn about what different medical libraries are doing it was also interesting to think about how article requesting might work as a general service to the public – allowing the “visitor privilege” to be extended to folks elsewhere on the internet. There are no doubt serious legal considerations, but how this could be safely done is a topic of considerable interest.
In both securing information and sharing information IT systems can help the university and the library within it meet institutional goals (or even just comply with regulations). These two events provided great insight into what our peers are doing (or not doing) and the results in their institutions. Although there was far too much covered for a single blog post, please feel free to email me if you’re interested in notes or to talk about any of the agenda topics.
ILLiad, the library’s interlibrary loan and scan and deliver management platform, has been successfully migrated to VMware infrastructure hosted by Yale ITS. The system is used to receive, track, and manage patron borrowing requests including physical delivery of items from libraries worldwide, scanned book chapters, and scanned articles from Yale University Library’s collections. Yale ITS will now provide systems and database administrative support for the service. The Enterprise Systems group within Library IT will continue to act as the owner and primary point of contact for the service and Atlas Systems will continue to provide application support. ITS staff, including Robert Wolfe from the Windows systems administration team, Kathryn Dobbins from the database team, and John Lee from the information security group all worked closely with the library systems group and were instrumental in completing the transition on schedule.