 Good morning and welcome to this week's edition of Encompass Live. I am your host Krista Burns here at the Nebraska Library Commission. Encompass Live is the Commission's weekly online event, is what we've called it, or a webinar, a webcast, an online show. I don't know what else you want to call it. But we're online and we're live here every Wednesday morning at 10 a.m. Central Time. The show is free and open to anyone to watch. Both our live show on Wednesday mornings and our recordings. So if you are unable to join us on Wednesdays, that's fine. We record our shows every week and they're all posted up to our YouTube account and all linked to from our Encompass Live website so you can get all our recordings from there. We do a mixture of things here, presentations, book reviews, mini training sessions, interviews, basically anything library related. We are looking to have it on the show and share with everyone. We do have the Nebraska Library Commission staff that do presentations sometimes and sometimes we bring guest speakers. And this morning this is one of our mixtures today. It's also our monthly tech talk with Michael Sowers. Michael is the Technology Innovation Librarian here at the Nebraska Library Commission. Good morning Krista. And once a month, usually the last week of the month, last Wednesday, but it varies depending on scheduling. But generally you can find him here. We're the last Wednesday the month doing something definitely more techie related. That's the idea. We do techie stuff throughout the month too, but the tech talk will always be something like that. And he's got a guest with him today so I'm going to hand over to you Michael to talk about who's on with us and they're going. Great. Thanks Krista. Yeah, this month we're definitely going to get techie. There will be code involved. So, you know, there you go. So about a month ago I attended a multi-session webinar from the New York State Library Association. And I'm going to say one of the most interesting sessions that I intended, if not actually the most interesting one, from my point of view I attended, was one that we're having the speaker do here for us today. On the line we have Juan Denzer, the library system specialist at Binghamton University, which Krista, I understand, is your undergrad alma mater. Yes, it is. Michael and I are both actually native New Yorkers. This is a New Yorker show today. So, and then transplanted, both transplanted here to Nebraska. But yeah, Binghamton was my undergrad. I went there. My major was major in English with specialization in literature and folklore. Wow, all right. I was American Studies at Brockport. So anyways, Juan, good morning. Good morning. And at this point, so you've got a system set up to do what you're calling true SMS out of the catalog. So, why don't you just go ahead and show us what you've done? Okay, great. Yes, thank you everybody for attending. And so, to start off, let me just talk a little bit about SMS service. Sure, many are familiar with SMS, which stands for short message service. And a lot of libraries, they use this system so that patrons can go ahead when they're searching the catalog, they can search for something, and then they get the call number. And rather than writing it down, one of the nice things about SMS is they can put their phone number and they can go ahead and get that text message to their phone. So, when they're going around looking at the stacks, they'll see that it's on their phone. They don't have to write down a piece of paper. Sometimes, often, they can't find a pen or a piece of paper. I mean, libraries do their best to have scrap paper and pencils there. But one of the things that patrons enjoy is having that convenience of being able to carry their mobile device and have, you know, it's nice to be able to send several messages to yourself. So, if you're looking for several books, you can just go through your message service. So, one of the things that a librarian here at the university, when she was telling me about this and I was new to libraries, is she was showing me this system. And one of the things, and here's just an example of the University of South Florida, and when she was explaining to me the service, I said, you know, this is great. I thought, wow, what a great thing to have. But one of the things that I noticed is when you click on the SMS button, and again, this is what typical libraries use, is it'll bring up kind of like this pop-up box. And one of the things that I noticed is, especially in this example, is the SMS service is using email. So, basically, it's sending the message through an email server, and then the email server relays it to your phone and sends it a text message. And what I found interesting was that with this kind of setup, it asked the person for their service provider. So, one of the things that I discussed with her is I said, you know, it's very difficult because patrons, some of them often don't know what there is, you know, if they're international students, they might not even know what their service provider is. They just have a phone and they know it works. Others might have a service that's not even listed. Like, if you have, say, for instance, one of those track phones, you don't necessarily know which service to provide or to choose, rather. And that makes it difficult for the patron, because one of the things that the patron wants to be able to do, as we all know, is they want to be able to just put their number in and go. They don't want to have to think about what service provider I have. They want a nice, clean setup where you just put your number. So, that got me thinking. I started thinking of, again, the drawbacks about how users need to know their carriers, how all carriers are not listed. And of course, the one thing that patrons really don't like is that extra step. We noticed that when filling out these pop-up boxes, it's nice to just put your phone number and go. You don't want to have to click on this to ask for, you know, ask for more information. It's nice. Patrons like a nice, clean box that they can just go and use. So, when I decided to go to a true SMS service, I wanted something, again, that was easy to implement. Although the mail to SMS service is not difficult to implement, it's easy to maintain. Like I said, many libraries have used it. I also didn't want to make something so complicated that wasn't scalable that other universities couldn't do themselves. And the other important thing is I wanted to ensure that it costs next to nothing because one of the things about the email to SMS service is it just relies on your email client. So, whatever email server you have for your institution, that's what you use, and it's virtually free. So, I wanted to ensure that it was either low cost or, in our case, since we're using Google Voice, it's absolutely free. And the other thing is I wanted to make sure it proved to work that it actually was a true SMS service and not this email to SMS service. So, basically, this is how the system works. You have your library catalog. In our case, we're using Aleph. And what it does, it makes an HTTP request. That request then sends it to our Windows server. We have a 2008 Windows server that we use for other web services. We use it to list our library hours. We use it to do what is called on our website a special resources feature where it looks through a database and every week it randomly picks a different resource to profile on the website. So, since I was comfortable using that server and we already had that server running web services already, I decided that the route we were going to choose is to use a Windows server to run this API call service. So, basically, the catalog, when a person requests to send a text message, it's going to send it to the Windows server which makes an API call. That API call then makes it to the Google Voice server which is going to do the part of sending the SMS. From there after the Google Voice gets the request, it sends it back to our server which our server then relays the response to the library catalog which sends the SMS message and then the patron gets it and then they're all happy. So, again, talking about how we implemented it, we added the SMS call number service. Our goals were to have a system that was easy to use, again, low cost, and have this unique solution. Again, what I wanted to do is to have this true SMS service that is unique that everyone can implement it. There's multiple ways of implementing. We don't have to implement it with a Windows server. You can use different servers. I'll talk about that later when I explain to you how the Google Voice works. But we wanted something that others could use. It wasn't just dependent on an ALF catalog system. If you have a different catalog system, you could put this in your system. You don't necessarily have to have the code that we wrote in ALF in our server to run it. You can create your own system. So, basically, the parts behind it is we have the ALF web front end. Basically, it's made up of just CSS code and some JavaScript that goes ahead and makes that request for you. One of the difficulties, if those are familiar with ALF, is dissecting this kind of like what we call an ALF puzzle. ALF was designed early on before all this fancy web stuff was done. And the way they do wasn't really designed for what we now use, like we use jQuery and we use all this Ajax and stuff, all this fancy kind of web stuff. It was just a simple design, but they also broke it up in parts. So, what you're normally used to is like an HTML file, a CSS file, a JavaScript file. ALF has this way of piecing it all together in separate files. One of the things that we found difficult was having to find those pieces and know exactly where to put our code. Which also, if you're going to implement this yourself, you might have some difficulties in your catalog, finding which pieces where exactly you're going to stick your front end code. But once we found that out, it was really easy to maintain. Actually, we used to host our own server or ALF server. Now we host it in the clouds on the ex Libris servers. And one of the nice things about this system is when my coworker, who manages the ALF server, he said, you're going to have to rewrite all your code to make sure it works on our server. And I said, actually, no, I don't have to rewrite any code. All I have to do is just change the, instead of pointing to our hosted servers pointing to our one that's hosted in the clouds on the ex Libris site. So the nice thing about this system is that I didn't have to change any code when we went from our hosted to hosted in the clouds, which was really nice. The only thing I had to change was one line of code, which I'll show you later, which was really easy to change. But there was no files I had to update, which he was worried about, and everything just moved smoothly. So again, the solution we used was we decided to use or was Google Voice. We already use have a Google Voice account that the librarians use for reference. So the nice thing about that is we didn't have to create a new account. They're used to using it. They have an email address that's associated with it. They have the password. And the Google Voice allows you to send messages, send SMS messages. We're also looking because one of the things that has been, if any of you notice or have heard in the news over the years is that Google is going away with Google Voice. They've consolidated, they've had it separate. Their API has changed over the years, but the rumor is that eventually it might go away. So one of the things that we looked into is maybe switching over to a paid service called Clickatel, which basically does the same thing as Google Voice, but they would charge you a fee. But until then, we haven't had any problems with Google Voice. It seems to still be around. It's not going anywhere. But there is that in the future that we would have to change our code so it would use the Clickatel API instead of the Google Voice, which won't be that difficult because you would just change the API that makes the calls and you wouldn't have to change all the other front end that goes to Aleph. That will all remain the same. So then we, again, we also decided to use a Windows server, which is our SMS Relay server, which we call Live Help Desk. And that one, as I said, runs multiple services. It runs our hour services, featured resources. It uses some internal websites that we've created for our staff that work with students. So that's basically our service server. And then what we did is we added, we embedded CSS code and HTML code within the Aleph HTML pages. And then all this does is just reference a JavaScript file with some functions that makes a call to the Google Voice to send that SMS service. So let's just switch over and actually see how this true SMS service works. So if I go to our library catalog, and I'll just type in a search, and I'll search for Gone with the Wind. And then you'll see that our search results here, you'll see that we have this little button that has the text or that has the text telephone or rather mobile device. And when you click on it, it will bring up a box. And here this box will say basically it's a simple box. We want that simple design that says just put in your phone number, hit send text message and go. And what it'll do, it'll send the call number and it'll give a description as it says here, it's in the Bartlestacks and the title of the book. So if I go ahead and put my phone number in there, and then what I'll do is I'll hit send text message and then it'll say that it's sending the message and then you can either close it when it says done send or it'll just naturally just go away. It says it's sending the message and then that box will just go away. And then if I switch to my phone in a few seconds, you should see a message here and you'll see that it comes up on my phone. And then I can go ahead and I can put in my code here and you can see the messages that come up. And as you can see it gives, since there's quite a bit of text and it sends two messages, but depending on how you set it up, you can just send the call number. You know, if you just want to send one message, we can strip out things that say like regular loan, we can condense it. But this is what the librarians chose to have sent as a message. So basically that's what gets sent. And the nice thing about this system too is if I want to go ahead and send another message and this is just a practice of what your browser does, that it kind of remembers your number, I can just go ahead and send this message here. So basically I can just keep going down the list and as that box goes away, I can just continue to just send messages, which is kind of nice because you can just rapidly send it. Now, some people have asked in the past that perhaps that stores their number. Nothing in the systems gets stored. The only reason why this number tends to stay in their browser if they're using like a public machine is because that's the effect of what the browser does. And if you set up your browser to clean the cache and then delete all the auto-completes and all the auto-fill-ins, you won't have that problem. Right now we don't do that until after a person logs off the system or something like that. So that's how the system works. And if I quickly go to our server, I'll just show you exactly what's going on with the hosted server. So this is the SMS Relay server. And basically all it is is a web service. And if we look at this lines of code here, I could just quickly explain it. One of the things we didn't want, excuse me, is to have the system abused to where any bots could use it and they could just start sending out messages. So what we do is we just make an HTTP reference to make sure that it's coming from our site. Then what we do is we use this thing called Sharp Voice, which is a C Sharp DLL. Basically it's a wrapper class that somebody created to send SMS messages. And it's real simple. It just gets the request that comes from the query string that has the phone number and the message you want to send. And then it just puts in the credentials for Google Voice and sends the message. It's that clean and it's that simple. And if we just quickly switch over, this is the Sharp Voice. It's a DLL that we use on our server that sends that message. And basically what this person did was they took this other well-known that's written in Java, this Google Voice Java that does the API calls and they just ported it to C Sharp. So they kind of did the work for us. I've created my own and I was going to create my own, but it was a lot easier to download this one and just implement it into your system. So that's basically it. The basic system is just a relay server, your front-end, and then using any API such as Google Voice or Click-A-Tel to send the messages. And it's pretty straightforward. If anybody has any questions, I could probably answer it more in detail that way. Okay, thanks Juan. I've got a few questions for Juan, but obviously folks in the audience, if you have questions, please go ahead and submit them through the Q&A interface. We will happily pass those along. The first question I had you kind of almost answered, which was, yeah, what are you planning on doing if Voice goes away and becomes Hangouts, which is what, you know, I think everybody thinks Google is going to do, although Google hasn't said it, all indications are that. Can you talk a little more about the service you're considering to replace that, as you said, was Click-A-Tel, I think? Sure, yeah. So again, like you said, one of the things that people have been feared is that Google Voice is going to go away and it goes to Hangouts and you'll no longer have those API calls to send those messages. Also one of the things we also worried about, which we haven't hit before and I've done so much research looking for, is what Google Voice caps you at, like how many messages per month, and I can't seem to get a solid answer. People on the web have said, you know, a thousand, someone said five hundred, so one of the things we worried about that the system was going to be used so much that we were going to get capped and then Google would either, you know, suspend our account for a few days. So we started looking into other services and we looked into Click-A-Tel and we contacted them and they actually, if you contact them, they will give you a trial and you can try their system and you can actually make API calls. So basically what I did was I signed up for a free account and I took their API, I developed my own DLL and started to use that to send out messages. I ran into some trouble trying to send those messages with their API call because I had to create my own DLL and I'm still working on that. But basically Click-A-Tel, the service is not that expensive, maybe for about ten dollars a month you get, I forget how many, exactly how many messages you get, but it's relatively inexpensive. They have a cap to where they charge you, I think .0003 sense protects message or then it reaches like a certain cap and then you're paying like a monthly fee. So we know that it will work and actually one of the things that I'm also looking to is to add this SMS service into our Primo that we use and one of the things that the Primo lists in their documentation is they actually list Click-A-Tel as one of the companies that is kind of like works with it, so that's one of the reasons why we were also thinking of switching to Click-A-Tel. Cool, you kind of partially answered this but somebody asked it as you were answering which was is there a limit on the API calls for Google Voice and you said basically there is but you're not clear on what that number is or Right, yeah I've looked and there is no documentation that really says on Google Voice that says there is a cap and I've searched multiple forums people like I said people said they were capped at a thousand some were capped at five hundred some said they've never been capped I could never find a true solid answer it's like one of those mysteries Couldn't Google it, couldn't Google it exactly So actually that to me raises an interesting question what sort of what sort of use have you been getting and are you collecting any sort of use stats so you obviously haven't hit a number but are you even tracking the number of usages on your end Right, so right now the system doesn't track anything I didn't initially I didn't because one of the fears is the librarians always make sure is that you know don't track any stats without coming to us first and no one actually requested this kind of stats so I don't know the usage and it could be easily implemented to where it could just have like a ticker that just tells you how many messages I believe you can also go into your Google Voice account and you could track I think and I'm not sure I'm not sure on that but it's just as you can see what phone messages and phone calls have been made and Google Voice you could probably track that as well there's kind of some statistics for that but we haven't tracked anything yet and I don't think we've nearly come I mean we've I've heard from students that they love the system and they use it but I don't think we've come nearly close to anything anywhere like the five hundreds or the thousands per month How long have you has this been implemented So this has been implemented for a few years now actually I don't recall the exact date when I implemented it Sure okay it wasn't a month ago Oh it wasn't a month ago No this has been running for quite a while now one of the things is you know it just recently within the year or so we switched over to a new website and it started getting promoted on the front of our website saying you know now you can use this SMS service so before it was kind of like a soft launch and only a few librarians knew about it and they would tell students but now it seems to have gotten more usage with the new website promoting it Are you are you getting any sort of anecdotal feedback from students faculty staff that have been using it No we recently they they did a usability study for our website as a whole but one of the things they I guess they didn't include in the study was the SMS service which is something I would like to you know approach the librarians you know I am on the web working team and and maybe have some kind of usability study or but we haven't done any we haven't gotten any feet you know real feedback from people um we've got a few others you were oh we have a question from the audience we'll always defer to them Troy is asking do you only use this API call through the OPEC or does the ILS also send hold reminders over to reminders through this service ah so could you use this are you and or could you use this to text people about their accounts as opposed to directly initiated call numbers yeah actually um so that's one of the things I've been um researching and trying to implement but one of the things that the ALF system is is that's already implemented on ALF's back end they have their client that we all use they use a circulation desk they have it on their circulation computers so they can turn that feature on we haven't turned any of that on no one sends that we don't use that feature but you know I've approached my colleague he works with me and he he maintains the ALF server and I've looked into that and then asked you know that would be great but one of the things is again it's that um that that puzzle that ALF has is finding where pulling all that information and where you pull it from and one of the dangers that my colleague always stresses is that ex Libris designs the system and they put it into their system so you could use it so when someone like us comes along and starts poking around on the database and pulling this information it tends to like it's sometimes violate like our agreement on the software we're using which is a shame because I believe you know if we own that database or we're using that database we should be able to pull that information and and send it to our patrons any way we want whether it's through SMS service email service whatever and you know but unfortunately sometimes I get told you know you can't do that and yeah this is not this is not an open source system you're working with here this is exactly exactly it's not an open source system yeah okay but it could be done it could be done with other systems if you don't have that restriction which is kind of nice right okay when you were demonstrating the user interface so and you were showing you could send a text message then the next one and then the next one I'm getting the impression you can't batch them is that something you've thought about trying to figure out how to do so like send me these three all at once yeah like I said now that we know what generates this page that lists your results it would be nice you're right if we had something to where we could have text boxes and people could just check off the boxes or they could say select all and then have a regular button on the top that says send this SMS message and it would send it to all of them yeah that could easily be done because again it's just CSS code with JavaScript that just keeps making that call so if you make a list your JavaScript could just shoot one after another just fire it off send this one send this one send this one so the nice thing about this system is this front end you can customize it just about any way you'd like it's all done through CSS and JavaScript and HTML yeah although yeah you just you just raised a point that kind of overshot me as you do have a character limit in most cases on the text message itself so it would have to be it would send multiples but yeah batching would just make it a little faster for the patron but okay right exactly yeah yeah and it would just be multiple messages because you right yeah but I could see if you want 20 call numbers that you know you've got to do that now 20 times so right yeah it is kind of yeah okay it is annoying but like I said the librarians were comfortable with this so far and oh well yeah it's better than not so I mean you know I'm not pretty so yeah I think it's a great idea I would actually look into I think I'm going to look into just trying to you know design show them and say cool all right all right um and so you're using this with a google voice account that it sounds like your reference staff is already using so this this kind of maybe self answers my question I wrote down before you said that which was okay so if a patron gets this text message they go off to the stacks has anybody ever tried to like reply and is somebody monitoring that number for incoming text messages yeah actually we have gotten replies um you know I log into because we also uh we we have a quite a bit of gmail accounts because we use gmail as our main source for our library or for university so we do often create a lot of accounts like we have lib ipads account that sends we will send messages for people who are reserving rooms that's another system we have a room reserve system and people will reply to it they'll be like you know I can't find it or but nobody really monitors that because no one is going to reply really reply to those but it's not it's very rare that we get people reply some people reply with I love this system maybe you get a pen to the end of the text message you know reply telling us what you think of this I don't know that way you get some feedback exactly yeah yeah um yeah I guess I I mean I guess my only potential concern and and it sounds like you're you're not having this issue is that those replies kind of end up in a black hole if somebody is actually expecting that somebody is paying attention to that I mean I it's just a thought more than anything else yeah yeah yeah people do because it is the ref quest account so the librarians actually do monitor that but they um you know like if it is something that is really pressing you know something that's really important I think they would bring it up to me and they would say you know I got this weird message where did it come from because oftentimes they don't even know how the system works and they don't even many of them don't even know that it's coming from it's using our ref quest which is our Google voice account yeah okay all right cool um and then I guess kind of my last question and remember folks you know so if you've got a question if I'm missing something you know so submit it through the Q&A we are paying attention to that you're obviously doing this through a uh a Windows server based system uh and I don't know I think I think you kind of address this a little bit I asked this question in the last version of your presentation did you just talk about whether or not this would be an issue implementing this in a in a linux situation or or anything but windows yeah um yeah so the great thing about this uh system and because it's using uh API calls is you can implement it in just about any kind of system you want you don't even have to go this route I mean you can let's say you have a uh a lamp server that's running PHP you can use PHP web services to run you know if you're someone who's comfortable using linux and you have a PHP server running you can use python you can whatever um you're comfortable with which is sending these services because this is not specific to windows it's just making these HTTP HTTP requests um so if you're familiar with web services you can pretty much create any service you want like I said the um I used the uh sharp voice was which was ported the DLL was ported from the Java version which is called Google Voice Java which is quite popular that people use to make their API calls because one of the things is when you're making software and you're making API calls you can either roll your own as they say or you can just use some kind of wrapper class or a DLL or some kind of um library that someone created that makes it really easy to where you don't have to do all that back end stuff you just use it and plug in you know your credentials and stuff and it does it for you which is kind of nice um so yeah definitely any just about any server you can use so other than say these slides for this presentation um if somebody wanted to take a little look at your code is that posted anywhere could they email you oh yeah they can definitely they can definitely um contact me I'm always helpful you know as far as like showing them code if they have any issues like setting it up you know setting up a server a web service sure they can easily contact me one of the things is I don't post a lot of code unfortunately because my director says one of the things that I might get in trouble for is if I actually post code that I created because the university owns it so it's easy for easier for me if someone just contacts me and then I can just show them and tell them you know how to set it up rather than making it available in some kind of a you know github or something like that sure okay um and and have you hmm I mean I kind of have a question I'm having trouble formulating have have do you know of anybody else who has taken this and and implemented it no um actually no I've uh I've yet to hear you know I've I've looked at other libraries I know like I said we're trying to I've been actively struggling to try to get this working in our primo if you're familiar with xlee versus primo um and no one has accomplished that I mean that is like um that's the whole you know me and this other library and we joke around that's like the holy grail of primo people are like we want that if you get that you're you're like a king or something in the xlee versus world but no I haven't seen anybody implement this like I said it's always been email to sms I'm sure perhaps maybe there is but I haven't come across it and I know that when I first presented this a few years ago at a SUNY law conference and people were excited about it they wanted to within our SUNY system they wanted to have some like a central server that would send these messages and then um you know and collectively they could uh all like use it which was a kind of nice way to you know especially if you you have a whole bunch of libraries are in this system so that all they would have to do it rather than having their own server they could just make that call you know to the webpage they would have their separate account but there would be one central web server that would do all the calls for them and that I thought was a pretty good idea but no one's ever done that yeah you have these great ideas and you're like tell everybody and then yeah a lot of it probably comes down in time too so I mean that's yeah it comes down to time and a lot of it like I said one of the things my director you know warns me about is the sharing of code that you know but I imagine since it was within the SUNY system I don't think that would have been a problem yeah but you're right there I have all these other projects and people you know it's hard to get people together and actually make something happen like that um and just just real quick for for those who might not be familiar could you just give us a god 30 second what's primo just just a for the record oh yeah so um you know aleph is our library catalog system but um primo is basically our all-inclusive system that uh had that searches everything your library catalog basically an index is everything it's a discovery oh okay great as opposed to yeah so cool all right chris say any other questions from the audience nothing has come in since last month anybody does have any questions type them in we'll grab them for you yeah um or you can obviously contact one yeah great uh anything else you you'd like to say before we wrap up this here's your opportunity yeah oh no I uh I'm just thankful I'm really glad this is great uh I just wanted to say about this uh show that you have um it's great because uh you know one of the things I enjoy doing is sharing these ideas and getting people you know to know that it's possible and I tell librarians you know they go well can we do this and I'm like you know yeah anything's possible like if somebody's done it we can do it or we can do it better so it's nice to be able to share that information with other libraries yeah librarians like to share things it's kind of what we do so yeah unfortunately developers kind of supposed to be like that but a lot of them yeah I've come across that they're very like don't touch my stuff well just you know sneak your name into the code somewhere and you know and then you'll get correct exactly yeah all right well one thank you very much for not seeing any other questions from the audience so we're going to go ahead and uh take back control for a few minutes and uh just talk about a other few odds and ends here so let me do that yeah I just click the right buttons here okay um and uh usually I have some like news and things going on and uh basically I just kind of have one this time that I think people might be interested in and uh this happened yesterday I'm I'm a pebble smart user and I've had one since the original Kickstarter uh program they have announced their new version coming out in about a month and they have launched it also again on Kickstarter um this is going to be a color e-paper smartwatch uh currently I think you can get one for just under $200 which is going to be about the list price uh when it when it does come out I've ordered mine I think it's it's time for an upgrade and I'll just say too that they broke a record they crossed a million bucks in less than 60 minutes with this and you can see they wanted half a million dollars and those numbers are going up as we speak and they still have a month to go so if you're in the market for a smartwatch I will personally recommend uh pebble uh and and especially this new one looks really interesting so it's something you could you could take a look at I am not I do not work for pebble I'm not being paid for this I just I enjoy mine and it's something I think if you're in the market for a smartwatch you should take a look at um and the other thing that we want to talk about real quick is the fourth annual big talk from small libraries conference is happening in just under 48 hours uh looks like one one day 22 hours yet Friday morning at 845 central time we will be doing uh our fourth big talk from small libraries conference you can still pre-register through midnight tonight we have over 600 pre-registration so far we have a thousand seats folks so let's uh let's get those numbers up there um pull up the schedule here we've got a great set of speakers lined up for you now these are all speakers from small libraries talking about what small libraries are doing and when we say small we mean small there's a pop served of 7400 uh we got a pop served of 1900 uh 1200 I think we have somebody who's under a thousand yes uh somewhere in there 1500 um our largest is a pop served of just over 13,000 there's 8,000 somebody in here I thought was it was a three-digit number in there but anyways um so we've got topics on programming we've got topics on how to do uh passports in your libraries little free libraries here's uh somebody who's going to be hacking the opac to create his own uh online catalog uh fighting back against public image so we're talking marketing there so uh this is going on all day on Friday from 845 central to 5 p.m central there's a lightning round at noon with 10 minute presentations the rest of the uh sessions are 50 minute presentations uh please pre-register if you think you're going to attend at all uh you don't have to attend the whole day you can come and go as you want uh but pre-registration allows you to get that login information tomorrow in a little advanced to make sure you get that but if you fail to pre-register you will still be able to log in we'll post the login information on the big talk website um and we'll come in on the fly if you think about it at the last minute or suddenly have some free time um and we will be recording just just like we do with this show it will be used to go to webinar we'll be recording all of it all of the sessions from the previous three years are available uh under previous conferences uh so even if you miss it we will all of the information will become available uh next week is when we start doing that we get this through done on Friday we go home we sleep for the weekend uh and then come back and worry about editing uh on one day so uh please please please please join us uh it's always a great day and fun and and um a lot of work goes into this both here at the commission and uh with our speakers so um that's the news that i have for this month all right all right um there we go thank you very very much everyone for attending um as mother just said it has been recorded um it will be posted onto our encompass live page as i mentioned earlier we do post all of our our previous sessions down here at the bottom underneath the upcoming sessions of our archive sessions page we have everything we've ever done on encompass live going back to the very first show in january 2009 um they're all on youtube for the um recordings the presentations usually go to our slideshare account or on our own servers depending and any links related to to the show so any websites are mentioned so i do have the big empty university page i've already added to our delicious slinks um google voice stuff that uh the one the click-a-tell that um so anything that was mentioned that might have a website i try and capture so that will wrap it up for this week show i hope you join us next week when our topic is 13 things you might not know about the national library of medicine resources um yeah marty mcgee who is at our local yeah she's great she's our medical person here in nebraska she's at the university of braskas um google library of medicine uh university braska medical centers um and she's got a session about things going beyond medline plus that's the page a lot of libraries use like we'll know but there's a lot more things that are out there that are also via the national library of medicine so she's going to come on the show next week and um tell us all about that so you can please register for that and any of our other upcoming shows um also encompass live is on facebook so if you are a big facebook user definitely go over there and like us on facebook we post um reminders here for like our this morning show so don't forget log in right now and when our recordings are ready we post up here reminders of upcoming shows are put up here so um if you are uh being on facebook and getting things from there um like us there doesn't that help you out for the day thank you very much everyone we'll see you next time and encompass live nah