 Welcome to our session, Incorporating Library Wiles in Campus Digital Experiences, Enabling Secure Access to Library Resources via OpenEssence. My name is Houma, I joined by my colleague Margaret Harner. We're both from Loyola University, Chicago. We are a library system. I'm head of library system, Margaret is our digital services librarian. Today, we are going to present to you about our experience about Incorporate us into the campus technology roadmap. Next, please. As we all know, digital age just forced everyone, the campus or technology partner as a whole institution including library into the digital transformation journey. So, started with years ago, the library systems technology department really repositioned ourselves as a driver of digital transformation for the entire library. So, we did a lot of effort in terms of realign with our technology priorities with the campus technology roadmap. And also at the same time kept to worry close up to date library technology needs to build, try to build the bridge between the two. As we all know, campus technology partner and the library and other unit, we share some priorities about in terms of privacy, security, similar user experience, but however, we might have a different aim or different priority at a particular time. We also limited in the local managed infrastructure. So, the preparation of understand each other better, understand our common user community better is become very important. So, here just some example about we are gradually in bandit ourselves into the campus it in the campus committee committees such as academic technology committee information security council and research technology walking groups. So, library really particularly library systems technology department we try to very proactively advocate the seats in those committees really understand the agenda spring to those campus centralized the committee also brings a timely update from library point of view to those initiatives. In addition to that library system team also initiate to try to maintain and develop a very strong pointed to point to relationship with a particular campus it teams based on the project or maintain regular communication making sure we understand each other where we are in terms of a digital sense of information and to do our best to deliver best value to our common customer and our user community. Next please. So, the example like about two years ago, the light by the campus it as they started running out of the whole five years of Loyola digital experience with the three faces, as you can see here, the basic is a fundamental one is is a face one is focusing on infrastructure and architecture. As we highlighted here identity and access management is security and the single sound become the major part of this phase. So, at the same time, we also again the library word what happened in which we started everybody start realize IP based on the occasion is not secure it's not in good best practice in terms of a technology involving. It's no longer because users have been tensed multiple mobile that multiple devices different more complexity computing environment that's no longer the case. So, we're helping also follow closely with the trending like I 21 same is access to the less so initiatives through the variety of avenues such as the year and now conference and other avenue. Next, please. The maintaining since we are positioning ourselves as a driver of this trans digital transformation. So, we really laid down where made made sure we are kind of a well situated in understanding the campus IT technology roadmap, as well as a trend from the academic library technology sector. With that, I'm going to turn over to my colleague, Margaret, she will that make sure she will dive into the particular project and about how we make our start our journey in this project. Yeah, so this was a very, it's been a very intense year working on this project so let me go over a little bit of a timeline about this. So, we, we first sort of thought about open Athens is the spring of 2019 so it sort of came to our attention as how we could get access to it. And through through Epsco, and we started to think about at that time, there were a lot of appealing aspects of it but overall we sort of were really warm because of the money aspect. While we knew it would solve a lot of problems and give us a lot of opportunities. We felt like it was, we couldn't justify that expenditure at that time. However, later that year in November 2019. So about a year ago, we were offered a very good deal through our consortium, and then that started to bring the pieces together that it was possible to do, because we knew over throughout the course of that rest of 2019. We could really see that this would really work well with the way our campus IT was moving. So we decided to move ahead with it. And we had our first meeting March 5 with our Epsco representatives to kind of kick off the project. So we all know what happened shortly thereafter. And we sort of thought like, well, what do we do? Do we go forward with this? But, you know, we're all working from home. But one of the things that became very clear to us is that relying on local infrastructure and local access was not going to be the easiest thing to do with everyone working remotely. We had a fire in our data center shortly after everyone started working remotely that kicked access for everyone for a whole day. So that sort of indicated to us that this really was going to be very important to keep moving forward with making our infrastructure a little more distributed. So yeah, we started meeting with our team weekly or bi-weekly later on since in April. And then so shortly after this presentation, we will then finish our implementation in terms of working with our implementation team. However, of course, we still will have work to do. And I'm going to talk a little bit about what some of that work is. So there are a lot of challenges in doing this project. Number one was navigating different federated solutions and or IP based authentication among different content service providers. Our second challenge was performing layers of configurations among library systems in a volatile time environment volatile system environment, which I'll explain in more detail, and then providing tailored ongoing education for library staff and our user community. So get into these challenges in more detail. We started this project. I think the idea of federated authentication was somewhat new to us. We sort of understood it at a high level, but didn't really know how to implement it. And so we had to really work with our campus. I teach understand a lot of these these issues early on and now I think we, you know, we've come more partners on this but So we just have a little background our campus directory services active directory and there's multiple services tied to that so it's used for as your active directory shabla as other things like that. We are also a member income in addition to open happens. So like I said our internal discussion or internal understanding with somewhat cursory. We work very closely with our IT colleagues who actually joined our implementation team meetings for weeks and weeks. Early on in the project, so that we can make the correct selections for integration between Azure active directory and open Athens, which is what had the way they wanted to go. And I think that was really valuable that we had them there all the time and no complaints they just showed up to meetings and kept being really helpful. And I think we also didn't necessarily appreciate that our vendors that we work with have different expectations and knowledge levels when it comes to federations or their support of them so some of them kind of what nothing to do with it and they say, it's still IP based authentication. And so we had to work on setting those up as proxy resources. Others of them sort of, maybe, you know, have one they prefer. So we do have some that are sort of, you know, unsure, so to this day whether we want in common or open Athens so working through that as an ongoing challenge. Our configurations for library systems we have a lot of different projects going on at the same time so while we were trying to do this project we also were moving over to the X labor central discovery index as part of our on the premise suite. And also in this summer, we're migrating to Premo VE. Those projects had mostly been planned to farm advance, and it just was sort of a coincidence the timing all worked out on all of it. Meanwhile, an open Athens project we had different aspects where we had to check all our links internally on open Athens that they were providing to make sure it was working for authentication at a basic level but then also how do we manage to get to resources for our Research Guides A to Z list and links on our website A to Z list which had to be rebuilt for multiple proxy prefixes. And another piece in here that I don't is important to realize is that we also had to update links within and Premo again complicated somewhat by the fact that we were migrating to a different system of Premo at that exact time. Our layers of staff training was another piece that we are still kind of working through but but I think early on we sort of understood that our patrons of course are at the center that's why we're doing it. And our public services staff work directly with those patrons. We certainly work a lot with them as well. But they need to have a sort of enough understanding to help library patrons, our implementation team has to be able to train our public services staff and then sort of the, you know, how and I and other people in our systems department and our IT staff have to understand the sort of technology at a different level to train everyone else at those different levels so I will say getting that first that the systems and I to training took enough time for implementation team to work it out. So there's certainly things where we're still working on how do we actually train and users at this point. So this is a sample staff communication and this is what I'm showing this to indicate the amount of things we had going on over the last over this year. So from May to August, so many different moving pieces and projects and groups getting together. Again, also in a very volatile time so it was a lot to take on, but I, you know, in the end we do feel pretty good about the fact that we did all these things because we feel our infrastructure is much more secure at this point. This is a kind of example of an early open Athens explanation we gave them just a really basic level. We're sort of finding that this level is we're kind of beyond that at this point like we, we have more information to give them we have more nuance to this. So we are actually now rolling out more training for our public services staff to explain more about open Athens and more about troubleshooting. One thing that's really important to our library is collaborative documentation collaborative understanding of projects across departments. So we worked with public services and other liaison libraries to create documentation. So for example, this is our off campus access page on our website. We had a group edit this page together to make sure that it made sense to everybody they could explain it. And there's certainly more that could be done this but it helps clarify our questions and training needs it certainly didn't answer all our questions but this kind of process we find is really critical and making sure that our projects are success. So pros and cons of our open Athens project. So this infrastructure definitely works more seamlessly with our campus infrastructure. I think we really appreciate the fact that we can now offer people a much more seamless experience where they're not if they've logged in to their campus services they don't have to log in again to access material from off campus so that's great. We have somewhat more control over user experience with sample attributes than we did with our previous all that easy proxy integration but that I will say is not always it's a mixed bag sometimes because sometimes we have too much control. I would say our cards where it was much more a complex project than we entirely understood at the beginning we sort of knew it was a big tool that could do a lot of stuff but we did not necessarily know all the bits and pieces we were going to need to know and maybe the way that the project was going to be managed. I think overall was a project any project that was done this year I think it's going to have a similar con here. We started this project right as we were all working from home and trying to adapt to a new environment so we had a very slow start so And we had a lot of people with personal issues over the summer that meant that things got behind but I think that's sort of the nature of this project of any project done this year was going to have this problem. So, in conclusion, we now feel that doing this project has put us in a much better place in terms of our integration with library or library technology with campus technology. I think we really appreciate the knowledge we've gained and cementing the relationships that we have with our IT colleagues. As Hong mentioned, we really work on building those over time. And this was yet another example where we were able to make that happen. So we would love to talk to you about if you have questions about your own implementation or have some feedback you'd like to share with us about our project. We'd love to hear with you. You can email us or you can contact me by Twitter. Thank you very much.