Recording of Library Mobile Implementation meeting with OhioLINK and Ex Libris.
Andrea Finch 0:03
Great. So we're at the top of the hour. I think we're going to go ahead and get started. I'm recording this meeting and our future meetings in case there's anyone who's not able to attend today's call or any of the future calls. All of the recordings will be stored in Basecamp, so you can reference them later.
All right, so I did enable Q&A for this chat. So if you have any questions as we go along, please post them there. I will try to answer them as we go. So if you do have a question as we're talking through, just raise your hand and I will try to.
Answer the questions as we go.
OK, great. So let me share my screen just a moment.
OK, can everyone see my screen? OK, my presentation.
Anyone?
Detwiler, Melissa 1:09
I'm I'm not seeing it, no.
Andrea Finch 1:10
Not seeing it yet. OK, give me one second. Thank you.
How about now?
Detwiler, Melissa 1:21
Yes, I can see it now.
Andrea Finch 1:23
OK, great. Thank you for confirming.
All right. Um.
Great. So welcome everyone to your library mobile implementation. I'll just start with a quick introduction. I know we have a lot of institutions on the line, so we might not be able to have a full intro, but I will.
At least introduce myself so you know who will be, who you'll be working with from the Ex Libre side. So my name is Andrea Finch. I'm the Senior Team Lead for Project Management. My team is responsible for.
Campus M implementations and library mobile. So we have a global team and I have several project managers on my team that are working with the Ohio Link institutions in different cohorts and different waves.
Of implementation. So yeah, I am in based in Chicago, so I'm, I think I'm an hour behind you. You're in Ohio, I believe. So just an hour apart. I've been with Ex Libris for five years.
Four of them with Campus Sem and one of them with Alma. So I've been with with the implementation professional services team for about four of those years, so.
Beam, Amy M 2:47
Hmm.
Andrea Finch 2:48
Good to meet you all. Thank you for joining. We're gonna go dive right in because we we don't have a lot of time and I I'd like to cover as much as we can. So we'll go ahead and get started. So this this particular implementation again is for library mobile.
You're a part of wave one, which is the first group of customers that are implementing for Ohio Link and your cohort is #3. So you're one of three groups that are going through implementation right now.
OK, all right, let's, uh, hop over here. Let's see.
I have to bear with me just a minute because my team's.
I just got upgraded to Windows 11, so I'm still trying to figure out how to navigate.
Uh.
These updates. OK, let's see if this works.
Nope.
Let's share this. Let me try again. I'm gonna share one more time. It's not sharing the right window.
Beam, Amy M 3:56
OK.
Andrea Finch 4:16
OK.
OK.
Just gonna stop sharing. Try again.
Sorry, technical difficulties here.
I came back from Labor Day, you know, being off on Monday to having a whole new operating system on my PC. So I'm trying to figure out my way here.
OK, I just had it second.
Beam, Amy M 4:53
OK, I'll put in a ticket.
It.
Andrea Finch 5:16
Okay, where are you?
OK, let's try this. Can everyone see my the main screen for the presentation?
Yes, perfect. OK. Thank you. All right, moving forward. Thank you for your patience. So today we're, this is your official welcome call. Today we're just going to talk a little bit about what we'll be doing over the next few months in terms of activities and milestones.
We'll talk about scope and responsibilities during the implementation, who will be responsible for what tasks that we'll be working on. We'll have a look at the configuration form. There's a copy of this form in Basecamp.
And I'll put a link in the chat here for you so you can find it. Basically, each institution will be completing their own configuration form because you're able to customize the app or your part of the app.
Based on your branding and specific look of your institution. So along with authentication details and all that. So everybody needs to complete one of these forms, each institution and then we have a slide here for useful links. So there are a lot of good information there to help you get.
Up to date with library mobile, what it's about, just some general resources, information in our knowledge center, so we'll have a look at that as well.
OK.
So the library your your library mobile app. This is just a preview of what it looks like. You'll be receiving access to the app on the mobile devices, so for iOS and.
And Android. We'll also provide you with access to a web portal version of it for users that may want to access the app on a mobile, I'm sorry, on a web platform. So on their computer, they'll be able to go to a specific URL.
And be able to access the app in that way.
Right.
So in terms of scope and what we'll be working on during the next few months, we'll be working on configuration of the app based on the configuration form that's that's provided to us.
The main components that we're going to be focusing on are authentication, so ensuring that your entrance into the app is secure and that users can authenticate in and be able to retrieve their information that's relevant to them.
Related to their user account, we'll be configuring the Primo V integration with Alma and this integration allows the the user to see various areas of the library in terms of.
Services. So being able to search through your Primo search discovery, being able to see if they have overdue fines, basically all of the information that's in your account section.
In in Primo, so all of the user's information we do have and and then additionally we'll be configuring some static content pages. So these pages are some representations of it would be contact hours, opening hours, any type of information you'd like to highlight.
We'll be configuring four of those pages for you. There's no limit to how many you can, you know, create. We'll provide you with access and tools on how to create additional pages, but as far as the implementation, we'll get you started with with four of them.
And then we have some additional features here that are optional. For those of you who are implementing Leganto at a later time, we do have an integration in the app that that supports Leganto.
So that can come later and we'll talk a little bit more more about that as as we move forward with the project. And then we have some other great features like maps. If you have a, you know, multiple libraries or that sort of thing, we can add a maps feature for you and we can discuss those options.
And then we have a integration for the ID card so we can configure the user's library card and they can access it through the mobile mobile app, be able to present it when they're accessing material or within the library.
And then we have some built-in features in Library Mobile. They're available as as well, which include quick polls. Quick polls is a way to send a kind of a essentially a poll to your to your end users. We also have a notification feature that's built in. So if you.
Wanted to send a notification that the library is closed for some reason, or, you know, special hours or things like that. You can use the notification center to send those announcements.
OK. In terms of timeline, so the given that we're we have quite a few institutions that are are that we're working with in this in this cohort, you know we're we're hoping to stay on track.
A typical library mobile implementation takes about two months at the Max. We've seen some institutions do it in 30 days, so it is possible to get it done within this time frame. I think we just need to be mindful of it and you know.
And do our best to stay on track with the tasks and you know, configuring the the app and getting the information that we need in order to set things up. So.
It's, it's, I'm hopeful that we'll be done by the end of October. That's that's the goal. So in terms of the project, it's broken down into three phases. So right now we're entering that onboarding phase with the welcome call over the next two weeks.
We'll be giving you time to work on that configuration form and we'll talk in a few a few moments about a little bit more about that and when that configuration form should be returned by.
And then once we have the forms back, we are able to start actually configuring your environment based on your preferences. So during that three to four weeks of that activation phase, we'll be provisioning it.
Getting things set up for you, connecting authentication, making sure that the integration with Primo is working, and just applying some of that branding with your logo and your colors and kind of customizing the app for your specific institution.
And then once we're done with that, you'll have time to review and test. We have some forms that will help you with that. Right now, the app for Ohio Link is not in the stores yet. At some point it will be.
So as far as testing goes, you'll be able to test by accessing the the web portal or the web version of the mobile app and that will give you an idea of what the app will look like. And we also have a preview interface in our back end tool which is called App Manager and that's.
tool that we use to configure the app, so you'll be provided with access to that and be able to go in there and see how your app is going to look.
All right. Any questions before we move forward?
OK.
You all are very quiet. OK, so in terms of the flow, this is a high level overview of the the entire flow of the implementation from the onboarding phase all the way to.
Your go live and and following app promotion after that to your your to your patrons or your your users. So again, we're at the onboarding phase. We're going to move into the configuration form and getting that completed and returned.
Once that's done, we will have a kickoff. So again, I will be presenting more information at that time at the kickoff, a little bit more detail about what we'll be doing you'll be provided with with access to.
To App Manager and you'll be able to get in there and start to look around and see you know what it looks like in there.
And then we're we'll work on that configuration, making sure that the app is set up properly and configured, configuring authentication and then once everything that's, you know, in scope and we have everything covered there.
We'll have a small period of time for review and testing and then given approval, we will consider that the app is live. Like I said, right now it's not the parent app as we call it. It's not in the stores yet for Ohio Link, but by the end of.
October. The goal is that it will be and then it will be ready for your users.
All right, so the library mobile configuration form. Again, there's an Excel file. I will put this in the chat. See the.
Q&A here, but I will just put it here. This is fine, so please have a look at that. Like I said, each institution should be completing one of these forms. Within that form you'll find several tabs that will help you.
Navigate the different areas that we need to to to focus on. I think we could actually we could take a look at it in a moment. Let me let me finish this and then we'll hop to the form in just a moment. But the main components there are branding, so that's.
The information that we need to give your app that unique look and feel based on your institution guidelines, applying your logo, your institution colors, things like that, backgrounds and you know, there's a lot of different things we can do there.
So that's one of the components. The other is authentication. So we will need some probably assistance from IT at your at your institution to help with this with the authentication. We're able to to configure that on our end Ex Libris. So we just need if we have the right.
Information, we're able to get things set up. So all of the information that we need is in that form and we once we get that back, we will, you know, go ahead with provisioning it and making sure it's working.
And then there's a tab for static content there. So that's where you'll enter those pages, the information for the pages that you'd like to see in the app, whether it be useful information or opening hours, that sort of thing. And then there's some information that we'll we'll need for your Primo environment.
And.
And Leganto too, if that is something that you'll you'll be implementing, we don't necessarily need that information. Now that will can be covered at a later time after your library mobile implementation is complete.
Our support team can help you with that. We'll also provide you with resources on how that can be configured. So we'll talk about that during our project in a little bit more detail.
And then if you're interested in using maps and positions, there's some information there about that, so you can indicate there that you're interested in that and we will help you configure it.
This is what you'll see in terms of app branding on that Excel file. So there under that tab, there's specific information we're looking for. You'll need to provide hex codes for the color for your text if you have a preference.
And then also for your icons in library mobile we use a tile based app, so I'll show you in just a moment some examples, but it's each tile represents a certain.
You know function of the app and on the tile there's a icon and there's a text, so that represents the information in it.
This is an example here. So this is actually what the an example of what the app could look like. This is what we consider a simple theme, which is flat icons and single color text. So the icons, they're not, you know, they're just kind of linear.
And they have just one color, you know, and this is the preferred option. If you have, you know, if you see something in our app visual document which is linked here, just let us know and we'll see if we can accommodate your request.
But this gives you an idea of what it would look like and I'll share some additional examples in our call today from our some of our current library mobile customers. They're on the library mobile app, which is a separate app from what Ohio Link is is going to be using, but it's it's.
It's the same platform, it's the same information, and really it just gives you an idea of what other institutions may have done and and give you some ideas of what you might like to do.
OK, so authentication, we support either Oauth or SAML protocols. I think we also have authentication through Alma, so that's always an option.
There's a link to our knowledge center. You can see all of the different authentication types that we support, and this is what enables the user to log in securely. And if it's going through Alma, it's pretty seamless. It's a.
Kind of a single sign on experience, so when the user logs in, they'll be prompted to log in once and then all of the information in the app, if it's like the Primo integration or Leganto, those are what we call live tiles, so you'll see actual.
Live information surfaced on top of the tile. So like if they have an overdue, you know if they have overdue books or something, you'll they'll see a count. If they have like 3 overdue books, they'll see that information on top of the the tile, so.
And then like I said, it's a single sign on there, so they don't have to sign in again to get that information. It's already takes that information from the the initial sign on.
OK, so app configuration. Again, these are more details about specific integrations in the app, whether it be the Primo integration or Leganto or the Maps feature. So there's a tab on the form for that as well.
And then in terms of content, there's two ways that we can bring content into the app. The 1st way is is to do static content. So these are pages that are created.
Within the app and represent certain areas of information. So in this example here I think it's useful links. So we have templates out-of-the-box that you can use and customize based on your color and just add the information.
And into the the the web page or to into the mobile app essentially.
The other approach would be to have it to be dynamic. So if you have an existing link to like your library's website or something, we can just put a link out to that page so when the user clicks on the tile.
They get redirected to that URL. So that's another approach. If you don't want to, you know, maintain, you know, static information, that's a a nice approach and you don't really have to maintain it all that often.
So this is what Creative Studio looks like. Again, this is an area inside of App Manager, which is our back-end tool. It works off of HTML and CSS. It's pretty simple to use. We have a drag and drop panel and a preview panel, so you're able to see.
See what type of changes are being made as you're making them. Once you've made your changes, you save and publish and the information is. Once you publish it, you can see it in the app right away.
So there's just some examples here of again, different types of content and what it could look like. You can put images in there, you can embed videos, a lot of different things, links to other resources.
If you have a phone number or an e-mail address, we can make those clickable too so that the user can just click on the phone number and it automatically calls from their phone. So a lot of really great things there and we'll we'll get into this.
You know, like I said, once we start moving through the project, but um, feel free to, you know, to have a look at this in advance. Um.
We do have a welcome kit, so I will be providing that to you and you can start by looking at some of those resources and you know ahead of the kickoff so that you kind of get up to speed with what we'll be working on.
And these are just some additional examples of static content. So useful links, services, contact us, open hours. Again, this will vary by institution and whatever your need is, we'll help you configure four of them.
And then from that point you can configure additional pages as as you wish.
All right, useful links. So this is a a nice page to take note of. A lot of good resources here. All of our product documentation can be found in our Customer Knowledge Center, including a suite of like essential information.
And that's in the first link that you see there. We also have a library mobile overview. I suggest everyone have a look at some of these, especially the overview. There's some, you know, quick videos in there also in the welcome kit, which is linked here.
They give you a better kind of understanding of of what the app is and you know some of the features that it has. And the last link here is for product integrations. And again, when we say product integrations, we're referring to any type of.
You know, source that we're bringing into the app. So an example of that would be like the Primo integration.
Or the ID card.
OK, and here's some apps, some examples of some current Library Mobile customers. We do have an app in the store. The name of the app is Library Mobile, so if you'd like to download that app and search for one of these.
Institutions you should be able to find at least. I think some of them have a guest profile. I know UNC Charlotte does, so if you go to their app and access their guest profile, you'll be able to see some information there.
You won't be able to see the Primo integration because that requires authentication, but you will be able to see at least their branding and some of the content that they have in their app.
OK.
All right, before we talk about next steps, I'm going to just bring up the onboarding configuration form and just to show you kind of what it looks like.
OK.
one second pull up my Excel file.
OK.
All right, can everyone see my Excel file on the screen?
Cobb, Judy 29:25
Yes, we can.
Andrea Finch 29:27
OK. Thank you. So let's see.
So on this this main page here, this is just you know the basically the the status of the different tabs that you'll be working on. It would be great if you could add in you know from your specific institution add in here the roles.
A name and e-mail of the people from your institution that will be involved in the implementation and for what areas. So you might have a specific person on your team that's responsible for authentication. So if you can make that indication here if there's someone on your team that's gonna be handling the content.
Tent or the the branding, that sort of thing. Just make, like I said, make that indication and then we'll know, you know, kind of who that point of contact is as we work through this.
So this is your the App Home tab. This information contains the app branding information that we just discussed, the list of tiles. You'll see here there's a column for mandatory or optional. Some of the information is mandatory.
We, you know, we need to know like what kind of colors you want. We need to if you have an icon, you know we need to get that information from you. So some of it's mandatory, some of it's optional. So there's integrations that are.
You know, you don't have to implement. It's there for you. If you're interested in it, you know, please let us know. But just make that indication on the form. Just, you know, say yes or no. That's something that that you'd like to do.
So these are the list of tiles, and again, those are those different squares that you see in the app that represent different areas of information.
The authentication tab. So this is again where we're looking for IT's help. We're going to need some information on how you want that configured depending on your authentication type, if it's not SAML or Oauth and it's another one that we support like Alma.
Just make that indication in your form and we'll provide you with the information that you need in order to set that up or for us to set it up.
And then the product integration tab. So this is the information that we need for Primo to get things set up and also for the maps we also have a weather integration.
If you're interested in the ID card, we need to have some information there from you of what you would like to see. And then we also have a feature for BCC notifications, so if you have letters configured in Alma, we can send notifications.
Through the app, you know based on specific areas of the library, if you know they have an overdue fine or something like that, or if they have a hold or that sort of information, we can use that feature in Alma to push a notification.
Um, and an e-mail to the app. So that's really kind of a nice feature here.
And again, that's optional, so you'll see that indicated there.
On this tab, this is the static content, so this is, you know, the general information that you want to appear in the app. There's four different areas here. If you don't want to use all of these, if you'd like to, if you'd prefer something else, you can substitute it.
They're all optional, the four pages, but this is kind of a recommendation as as far as like general pages. I think every, you know, every library has opening hours. You probably have lots of useful information. So these are examples if you if you have something different.
And you know, just enter that value here and we'll configure it for you based on that.
And there's a tab here for post implementation. So again, Leganto will happen after your library mobile implementation. We'll talk about that for those of you that are doing Leganto, what that would look like and.
How to configure that in library mobile and what your what your what are your resources in terms of getting assistance with configuring that because this it won't happen until after this implementation so.
It's from what I understand, so, but it is something that can be configured at any time after you're done with this one.
Uh, great. Any questions about the form?
Hopefully everybody is able to access it.
OK. So before we hop to the Q&A, I do see there's some questions there. I do want to just do a quick overview of Basecamp. I'm sure all of you are familiar with Basecamp at this point, but I just wanted to give you a quick overview of our Basecamp for the simple.
and just kind of where you can find some resources and um different different information within it.
So we do have a community message board. So this is something that you can use if it's a message for basically everyone. So you can find here already some messages that I've posted for, you know, every every institution that's on the call.
Um, but everybody's welcome to use this as long as it's, uh, a message that's intended for for everyone.
You'll also find here that each institution has their own message board, so I would encourage you to use your message board for your institution. Post a message.
You know, with a relevant topic, give it a title that's relevant and keep it within your board. This way it's easy for me to identify, you know who you know, what information belongs to who, and it just will help us kind of contain things a little bit better.
Um, rather than having one giant message board.
We have a section here for to do's, so this is going to give you an idea of what we'll be working on throughout the project over the next two months. Some of these tasks here, actually most of them are ex Libris tasks, so.
You'll see that indicated, you know, in the in the title and you'll see my name by it. But these are things that I'll be providing to you and working on, you know, during the project.
There is a section down here. This is for you. This is online training and additional resources. I encourage you to look at, you know, each specific area. There we have, you know, different links to.
Training and videos and things like that. So this is a nice supplement to.
The welcome kit and and basically you know what we'll be covering. So please have a look at that. If if you have any questions about anything, you know please let me know in in base camp, but I think that's a good way to kind of.
You know, get things, um, up and running.
And then lastly, we have the docs and files section. So again, this is the onboarding configuration form. Each institution will download a copy of this and complete it. Once you're done completing it, you'll want to upload it to your institution's folder.
This way we know where everybody's information is and and anything related to the project, any like logos or any type of files that are, you know that are shared should be uploaded to your relevant file or your relevant folder.
And this hopefully will help us stay a little bit more more organized working with such a, you know, large number of institutions here.
And then again, I will be posting information here. So all of our meetings will be recorded. So I'll have a folder for meeting recordings. I'll also post an agenda ahead of each weekly call. So we'll be, you know, covering specific topics as we move through it.
If you have anything that you'd like to cover or specific questions that you'd like to to cover during the call, please let me know, post it to Basecamp and then I'll add it to the agenda so that we make sure that we discuss it during that call.
All right. Um.
That's Basecam.
OK. Any questions about face camp?
OK. All right. So I do see a couple of questions in the Q&A, so I'm going to hop there and um, OK.
Question from Amy. If we use SAML for authentication, how we use all authentication to work for the app? What credentials would they be using? OK, just want to be aware of it. OK, could you explain that? Yeah, so so Amy, I will post a.
I will post a message board here in the Community board about using Alma for authentication. Basically we.
I think it's we just need like the base URL of your Alma instance and then there's an Alma ID that we need. So that Alma ID could be a set of numeric numbers or some representation of your user in Alma.
So those are basically the the two main things that we need in order to configure that, but I will post that information in the Community board specific for that authentication type.
Yeah, and to Heidi, your question as well. I will post a message board here about that. There's also a.
Let's see here. So there's also a link here within the todos for app authentication. So if you click in here, this will take you to our Knowledge Center.
So this is all of the information of the supported authentication types. I'll put this link in the chat as well, but I'll also make sure that this information is clear in.
Um.
And Basecam as well.
Mason, Lindsey 41:46
I don't think we're seeing your screen right now. If we're meaning to be, I'm not sure.
Andrea Finch 41:49
Oh, I'm sorry. Thank you.
I realized I stopped sharing and then I started talking again. So OK, yeah, so if you look in Basecamp, oops, hopped out of my. Here we go. OK, if you look in the to do section.
So there's a right under the getting started task, there's a or I said grouping I should say of tasks. There's a there's one here for app authentication.
So this is all of the information that you'll need to know if you're using SAML or Oauth or Alma. All of that information can be found here and this actually links to our knowledge center, so that's what I pulled up here.
So this is a lot of information, but basically the Alma configuration is found here. So we need like your API key from the developer network and.
I think it's like your base URL or the the server for that key rather not your base URL. That's for Primo and then just some mappings on your user. So you know whatever attributes your your IT department defines, we can map them.
You know username mapping could be like you know the first part of the user's login. Mail mapping is generally like their e-mail address and then first name and last name and then we map an additional mapping.
And that's again that's at Alma ID and that could be depending on your your Alma could be could vary. So it's not gonna it might not be the same for for everyone. So it could be like a a numeric value it could be.
You know, 6 digits, I I'm not sure. So once we identify what that is, we'll map that into the additional mappings and that's what brings in the the information that we need for the product integrations, so for the ID card.
And the Rimo integration.
OK, so I did put that information here in the chat.
We go back to the Q&A, make sure I covered everything here.
OK. And then just a couple questions in the chat.
OK. Yes, Andrea, just you can ignore the Leganto tab on the configuration form. Again, it's it's optional you if you if you're 100% sure that you're interested in Leganto and that's something that you've, you know that you've signed up to implement.
Please feel free to put your information there that you're interested in it. If if it's if, if it's not relevant for you, just just ignore it.
Question from Melissa. Will we go through configuration for my next week's meeting? I think we covered that today, so I think we're good.
Or no, we talked about it today. We will use next week actually our our meeting next week to go to review it again. So if you have any questions specific for the the form, you don't have to wait till the meeting. So if you have any from now until next Wednesday, please post them in base.
Camp in your message board and I'll try to answer them in advance, but we will spend our next meeting basically going through and making sure that you know anybody if you have questions about the form that we talk about it and.
That's basically what we're doing next week, so.
OK, question for Mike. If you want to add people to base camp, there is a.
I believe there is a post here.
So if you want to add additional people, please add them their first and last first name, last name and the e-mail address underneath this message board and I will add them to Basecamp.
started transcription
Andrea Finch 46:16
Their first and last first name, last name and e-mail address underneath this message board and I will add them to Basecamp. I'll put that link in the chat for you Mike.
I'll put that link in the chat for you, Mike.
