This post is a brief overview of the process in designing for large web-based systems. This includes understanding what makes up an interface and how to start fresh to create a good foundation that won't be regrettable later.
The open source software Hydra is, by its name and nature, modular and complex. Using this technology gives the University of Michigan the opportunity to participate in the development of an increasingly-adopted suite of tools with the flexibility to accommodate a host of needs and engage in the spirit and philosophy of open source software development. With open source, we must concern ourselves not just with our own institution’s needs and priorities, but those of a broader community.
For the past year, the University of Michigan Library IT (LIT) division has been devoting time & resources to conducting a thorough self-assessment. These efforts have included discussions focused on our application infrastructure, our division communication patterns, and our service workflows. And while these discussions were instrumental in helping identify challenges and potential solutions, we wanted to begin to collect hard data to help better understand the complexity of our work.
Over the past few years, the University of Michigan Library has progressively updated and enhanced the way we manage our subject, course, and specialized information guides with Springshare's LibGuides product. This post talks about the various customizations and integrations we've made along the way.
In an upcoming LTT blog post (hopefully, before the end of the calendar year), we will discuss U-M Library's process of enabling page insertions to Google volumes for our HathiTrust Digital Library.
Lately I’ve been looking back through the past of the Digital Library Production Service (DLPS) -- in fact, all the way back to the time before DLPS, when we were the Humanities Text Initiative -- to see what, if anything, we’ve learned that will help us as we move forward into a world of Hydra, ArchivesSpace, and collaborative development of repository and digital resource creation tools.
The next version of Mirlyn (mirlyn.lib.umich.edu) is going to take some time to create, but let's take a peek under the hood and see how the next generation of search will work.
Page 4 of 18