Michelle Eichelberger: Good morning everyone and thanks for joining us for advanced DRM troubleshooting linking
Michelle Eichelberger: Just get back to my slides. Whoops. Today we're going to build on some of the basic troubleshooting. That was explained by Elena, a couple of a couple weeks ago in her session on testing linking in Alma
Michelle Eichelberger: So she really did a nice job laying out the different places to start your troubleshooting, you would check in Alma you check on the vendor platform you look at your easy proxy. We're going to go into more depth on all of these
Michelle Eichelberger: Let's get started.
Michelle Eichelberger: Okay, so if you're testing and Alma and your links are not working. There are a couple of places you could go to get more information.
Michelle Eichelberger: One of the places is this link to the cross product integrations online so FX
Michelle Eichelberger: This is a document that shows you different purser parameters for collections. So if the link that you have for your collection isn't working, you can go to this site and see if there's a different option.
Michelle Eichelberger: You may have to play around with it a little bit. Worst case if you can't get it to work, you would submit a Salesforce case. And actually, this can help you get it working.
Michelle Eichelberger: Another place you can go and check is this resource management managing electronic resources document.
Michelle Eichelberger: And then again, if nothing is working at all. There might be a problem with the CZ settings if you're using a CZ collection.
Michelle Eichelberger: An example of this that was in Salesforce Salesforce recently was a UB case where the MLA International biography wasn't working the error was Aaron HTTP.
Michelle Eichelberger: HTTP handler and it had to be fixed in the knowledge base. So if you can't get something working, don't assume that it's you. There may be a problem with the actual collection.
Okay.
Michelle Eichelberger: So the first thing we're going to talk about today is this area that you might get if your
Michelle Eichelberger: Collection is not authorized for access, you might get something like this product not recognized it might just not let you in. It might prompt you to log in to get to the resource so
Michelle Eichelberger: There are a couple reasons that this could come up. So this could also happen within your campus network outside of your network or in both places.
Michelle Eichelberger: There are several reasons why this might happen. You could be missing an ID on your edit service linking tab, you might have activated the wrong version of the package, which is pretty easy to do. In some cases, or your proxy might not be set up correctly.
Michelle Eichelberger: So the first thing we're going to talk about is what if you have a missing ID.
Michelle Eichelberger: What you would do to check and make sure that this is not the case is you would go and look up your electronic collection. You do edit service and check the linking tab.
Michelle Eichelberger: On that tab, you'll see general linking information if the person parameters have something like this, this local ID, it would have $2 signs in front of it. That means you have to provide this location ID.
Michelle Eichelberger: You might also see something like this group alias. That means you have to put that in. And if you scroll down to the bottom of this page you're going to see this linking parts are parameters area.
Michelle Eichelberger: And it will have a spot for local ID or group Alias, and then you would need to enter your specific information.
Michelle Eichelberger: We've gone over this in a couple other sessions. So this is probably familiar to you, but I thought I would mention it again.
Michelle Eichelberger: And Shannon put together this really good FAQ about what collections that are pretty generally used across soon you do require special parameters. So that's one thing that could be happening.
Michelle Eichelberger: Another thing that could happen is that you might have activated the wrong collection.
Michelle Eichelberger: Probably at this point in using on your collections are set up correctly, but if you get a new one, it can sometimes be hard to figure out which one to pick from the CZ
Michelle Eichelberger: For example, psych articles. This is offered by a bunch of different vendors, you might be getting it directly from a PA, you might be getting it through ABS go
Michelle Eichelberger: There are different ways you can get access to this and if you pick the wrong one, then it's not going to work. When your patrons, try to get to the content or when you try to test it. So, for examples like articles. If you search for that by title in the CZ you're going to get 10 matches.
Michelle Eichelberger: If you're not sure which one to activate. You could try out just testing one portfolio and see if you're authorized to get in.
Michelle Eichelberger: This was a suggestion from Heidi web and I thought it was a really good idea. Instead of activating the entire thing. Just try one of them and see if it works for you and you can test it all from the portfolio as Elena demonstrated in her session on testing from Alma
Michelle Eichelberger: If this is something that was purchased Sunni wide. You could check and see if other Sunni libraries have activated this specific collection.
Michelle Eichelberger: And here's an FAQ about how to figure out what things have been activated by Sunni some of those can take trial and error. You may have to play around with it.
Michelle Eichelberger: Okay, another thing that could happen is your proxy might not be set up correctly or you might not have activated it for the service. So your collection might be working locally, because
Michelle Eichelberger: Of IP recognition from the vendor, but you may not have activate it to work from outside of your regular network.
Michelle Eichelberger: So again, you're going to go to the Edit service and on the general linking information page, there's a place where you can say if you should use the proxy or not.
Michelle Eichelberger: You would want to pick your default proxy. And then if it's a new collection, you're going to want to make sure that you have a standard in your easy proxy config file. And we're going to talk about that a little bit.
Michelle Eichelberger: Okay, so if you do have it marked as yes to proxy, but you get an error, like this. What this means is you're trying to proxy it with your proxy.
Michelle Eichelberger: But the collection or the URL or whatever you're trying to get out to isn't recognized by easy proxy. So you're going to have to do some work to make it
Michelle Eichelberger: be recognized. So what you want to do is make sure you know the URL that is trying to use. So in this example here. It's a credo URL. So you want to make sure that that's included in your easy proxy file because if it's not the proxy doesn't know that that's something that should be authorized
Michelle Eichelberger: The other thing you can do is, so keep track of that URL. You're also going to want to check. OCLC for the most current stands up to us for this collection. And again, we'll talk a little more about this.
Michelle Eichelberger: Okay, so if you're self hosted you have control of your config file and the config file is what tells the proxy what to look for, for each collection. What to allow
Michelle Eichelberger: And how to get your patrons out to this particular content. So you would open up your config file, you would want to look for the stands up in the stands. Is this group of code here.
Michelle Eichelberger: That tells it how to work with each collection. So in this case, I'm using the psych article stands up, they're pretty straightforward. Some of them are a little more complicated, but it's usually pretty easy to just copy and paste the most current one.
Michelle Eichelberger: From OCLC if there's an here's the link to the OCLC list of current stanzas. If there's nothing in OCLC for this particular thing. You can take a stab at creating it on your own.
Michelle Eichelberger: This one only has three lines, the T is just the title. And that's really for your benefit. That's not something that's being used by the system. It's more just to identify it.
Michelle Eichelberger: But then the URL, you do need the URL that you're trying to use to get into it. D stands for domain. And that's really just the end part
Michelle Eichelberger: Of whatever URL, you're using. So again, play around with it. It could take some trial and error, but you should be able to update this particular file to allow you to get into it.
Michelle Eichelberger: If you're hosted instead of self hosted you would just need to contact your vendor and ask them to add the collection or if you have a way that you can manage your config file through the vendor. You can use your account to go in and add it yourself.
Michelle Eichelberger: Okay, so those are the basic problems that you're going to run into. But now we're going to talk about some of the more complicated and weird. And just very weedy things that we have found in the first six months or so that we've been live with Alma. So let's get into the weeds.
Michelle Eichelberger: There's some tools that you can use to try and help you identify some of these problems that you're seeing or you know why things might not be linking correctly.
Michelle Eichelberger: This display CTO, this thing is so helpful to figure out what's actually going on you know what metadata is being used either
Michelle Eichelberger: On the record from a search and primo or also you can use this to identify what's going on. If you have a link resolve or service page that comes up if you're trying to come in from Google Scholar or a standalone database.
Michelle Eichelberger: This is a really great tool. So what you would do is at the, you know, once you do your search at the top of the screen you have your URL and you would just go to the end of it and add these letters. So you want to add and display CTO equals true.
Michelle Eichelberger: And hit Enter. And then once you do that, you get this little button here.
Michelle Eichelberger: On the actual record that you're looking at. And if you click on that. It's going to bring up all this code and show you what's going on behind the scenes. This can be great if
Michelle Eichelberger: You're getting weird linking that you don't understand, and it might even be things that are in here that aren't even displaying on the record.
Michelle Eichelberger: So again, I would really recommend that you practice using this tool. It can be really great. We do have a little more information about it in this FAQ
Michelle Eichelberger: If you want to. This is really good, especially for article data.
Michelle Eichelberger: That's coming from the PCI, if you want to see the alma data source, this would be something like a print babe record. There's a view source, usually at the bottom of your full text. And that's a place where you can see
Michelle Eichelberger: The mark tags that are coming in. If you're trying to figure out why. Something's displaying the way it's displaying
Michelle Eichelberger: Another tool you can use is an shopian X equals true.
Michelle Eichelberger: I'm not as familiar with this one as I am with the CTO, but this is what x Lieber says about it. It shows the record in JSON format and they say that it's useful to understand what metadata is being used in pre movie.
Michelle Eichelberger: So it's similar to the display CTO, but I think it can give you slightly different information. You can see the format is slightly different from what you get in the seat display CTO
Michelle Eichelberger: Okay, so now let's talk about some of the specific problems that we've seen so far.
Michelle Eichelberger: As go apps. Go is continually a problem. There's all kinds of weird things that can happen with apps go linking and we'll talk a little bit about what you might be able to do to try and fix some of this.
Michelle Eichelberger: Sometimes you're not going to be able to fix it. And you may have to submit a Salesforce case. So this is a known problem. It's not just a known problem for us. It's a known problem for everyone who's using Alma
Michelle Eichelberger: Lots of other schools have reported these kinds of issues they they just go just does not play well with x leavers probably because their competitors, but it's a it's an ongoing issue, as you can see from my next slide. This is a really great presentation by Katrina Collingwood at the
Michelle Eichelberger: Conference, which was a conference for Allah and primo users in Australia. And this made me laugh.
Michelle Eichelberger: So again, we are not the only people who are seeing problems with apps go linking all of you I'm sure have seen this dreaded go sign on link because your link won't go to the place it's supposed to go.
Michelle Eichelberger: So thanks to between off for putting this together.
Michelle Eichelberger: Alright, so what are some things you can do to try and make your abs go linking better. One of the things you can do is add an ethical link resolve our API.
Michelle Eichelberger: Which is confusing because this is not the same thing as the API scope. When we first went live with Alma primo we had a lot of discussion about, you know, should you implement the Cisco scope.
Michelle Eichelberger: If you implement the disco scope the problems with that are that people have to be signed in to get results from it.
Michelle Eichelberger: It doesn't use the same facets as things from Alma or the PCI, there are a lot of issues with it. So the discovery working group actually recommended that you did not activate the scope but
Michelle Eichelberger: The link resolve API is different is working in the background. And it's actually pretty helpful in terms of trying to make your abs go content link better
Michelle Eichelberger: doesn't fix everything. But it can really help. So the place you go to set that up is general integration profiles, you're going to add a new profile and the kind of profile is link resolve or plugin.
Michelle Eichelberger: And then in the API user ID, this would be your escrow account number, which you can get if you log into ABS go
Michelle Eichelberger: Main sometimes as part of your abs go links. If you're, you know, if you have standalone databases, so it's
Michelle Eichelberger: Usually an ass with a series of numbers after it, and then main that he it AWS and there's probably a place in your abs go admin where you can see this full thing.
Michelle Eichelberger: But I've had pretty good luck with just kind of, you know, copying this format with a different number. It seems to work pretty well then you want to make it active and that can help with your linking
Michelle Eichelberger: Okay. Another thing you can do is report to Salesforce and it seems like this might be silly that every time you have a link that doesn't work, reported to Salesforce.
Michelle Eichelberger: But what we've seen in monitoring the Salesforce tickets, depending on which Salesforce tech person you get
Michelle Eichelberger: Sometimes they will go out and try and add information to the particular journal that you're having trouble with. So Finger Lakes reported a problem.
Michelle Eichelberger: And actually said that their problem with linking was that there was a missing volume parameters. So what the tech person said, is they've created a linking exception for a title for this particular journal
Michelle Eichelberger: And actually what happened with this case was they didn't add it for the acquisitions library and journal they added it for different ones. So we're still waiting for them to fix this particular journal
Michelle Eichelberger: The good thing about this as there'll be fixing it in the CZ so it should fix for everybody who's using the CD. CD. CD CZ collection for this episode database so
Michelle Eichelberger: I cannot imagine going to fix every single journal out there and it seems like a real pain to have to report it every time there's a problem but
Michelle Eichelberger: You know anything they fix will help everyone else who's using all my. So I would say, don't hesitate. Go ahead. If you're seeing problems do report them. They do have to fix one journal at a time.
Michelle Eichelberger: But again, sometimes it's hit or miss. Who you get as a Salesforce tech and what they'll be willing to do to help you. But that is
Michelle Eichelberger: Something I see there's a post from Susan in the chat. Yeah, I totally agree fingerpointing progress next goes really frustrating. Yeah.
Michelle Eichelberger: Completely and then Joe the apps. Go API slide I'm going to post these slides after this session, so you'll be able to both copy from the slides or watch the recording or whatever. So that's a good question. Thanks, Joe.
Michelle Eichelberger: Cool. Alright, so here's another example of a report to Salesforce. So the previous slide, you know. Yes. Great. They're going to go fix that particular journal that'll help everybody this particular case from Corning
Michelle Eichelberger: Same kind of problem. It's not linking correctly. This one did make me laugh out loud because
Michelle Eichelberger: The link is supposed to go to an article called rivers of plastic and instead it's going to an article called misled penguins.
Michelle Eichelberger: Which just thinking about misled penguins made me laugh because who knows what that article is about
Michelle Eichelberger: So in this case, what the tech person at x Libra is recommended. Was that the person that Corning should implement DevOps go scope which, as a group, again, the discovery. Working Group suggested that you don't use that. So,
Michelle Eichelberger: The SLS S is trying to keep an eye on Salesforce cases. In this case, I did chime in and say, Hey, you know, if you implement this scope here are the ramifications that that could cause for your users. So
Michelle Eichelberger: You know, we don't recommend that you do that but
Michelle Eichelberger: The other thing I thought was really interesting about this case is that they're saying that Academic Search alumni edition has no alternative coverage, which I think is very strange because there's so much overlap and all of the apps go databases that
Michelle Eichelberger: You would think if if there's alternative coverage for something similar, there would be alternative coverage for this.
Michelle Eichelberger: And then they also said that Scientific American didn't have other indexing. So again, your mileage will vary with various texts, who you get for support and, you know, again, we're, we're kind of keeping an eye on things. But there are a lot of things that we can't fix locally. So
Michelle Eichelberger: Hopefully, you know, if you have a problem, report it and hopefully it will get fixed. I'm going to just check
Michelle Eichelberger: Okay, it looks like Bonnie has a question. Let me just scroll back up and look at that.
Michelle Eichelberger: Okay, Bonnie. Will this still be useful when we moved to the CDI do they expect that to help the linking issues and upscale
Michelle Eichelberger: In doing our testing with the CDI task force we have found mixed results, some apps go stuff links just fine and is better because we're using will be using a merged record. So the metadata will be a little more stable.
Michelle Eichelberger: But it's not going to fix everything. So yes, all of these things that I'm showing today will still be relevant with the CDI. That was a good question.
Michelle Eichelberger: Okay, so let's forward.
Michelle Eichelberger: I mentioned early either the link resolve or service page. And this is the page that comes up when you're coming in from an outside source like Google Scholar or a standalone database.
Michelle Eichelberger: We've seen a lot of issues with these pages, again, you know, missing.
Michelle Eichelberger: Metadata and it's sometimes hard to troubleshoot is that because the vendor has bad information. Is it because it's just not matching right in primo what is going on with it. So I just wanted to highlight a couple of cases.
Michelle Eichelberger: This first one is a UB case where they were missing do eyes that were coming in from Google Scholar. They knew that the articles had to do I on the Google Scholar page.
Michelle Eichelberger: But it wasn't coming in with the metadata and then the problem with that is that they use browsing.
Michelle Eichelberger: Which is also called lip key. And that's a really cool thing that shows the PDF right there and it's great for patrons, they can just open the article right from the, the, you know, from that page, but it wasn't working. So
Michelle Eichelberger: Again, just weirdness. We don't know why we're continuing to work on that.
Michelle Eichelberger: optometry. This is a really interesting one. So they use a standalone citation database called vision site.
Michelle Eichelberger: And vision site had some mixed up metadata, where a title changed and the old ISS and was coming up instead of the new one because it was the wrong title and there was all kinds of weird stuff happening.
Michelle Eichelberger: Another title. They see coming in with genre book instead of journal. So, you know, what's primo supposed to do with the data that's coming in as a great and how do you resolve that you try to work with the vendor to fix it. There's lots of weird things that can happen.
Michelle Eichelberger: This one is fascinating. And thanks so much to Nancy Bab for investigating this and and figuring this out. So what Nancy was seeing is that content coming in from Google Scholar.
Michelle Eichelberger: Didn't have all of the fields necessary to retrieve the holdings from Alma or to populate and I ll we crossed. And what she found was
Michelle Eichelberger: If she changed her library settings in Google Scholar to come from a different SUNY library. Sometimes it was bringing in all of the
Michelle Eichelberger: Necessary information. So like for upstate it was working fine. There were three authors all three authors were showing on the service page, but for BUFFALO. IT WASN'T
Michelle Eichelberger: Everybody's publishing to Google Scholar works the same everybody's link resolve is basically set up the same so she did a lot of investigation with this.
Michelle Eichelberger: And what she found was, there's this thing called the augmentation implementation profile.
Michelle Eichelberger: And if you set that up by creating a cross traffic account, it can actually enhance your metadata that comes in, no matter where it's coming from.
Michelle Eichelberger: So I do have an FAQ about how to set up a cross reference account and I would highly recommend that you go out and do that, and then you may see one in your integration profile.
Michelle Eichelberger: It would look like this augmentation. There was some testing done during implementation and some campuses got it set up by actually Burson some didn't.
Michelle Eichelberger: So I would definitely recommend going in, because that can really improve your results, both for the linking because the metadata is better and just sort of general metadata.
Michelle Eichelberger: So this is a pretty short session today, just know that there are all kinds of different
Michelle Eichelberger: Kinds of different things that can happen with your metadata. I wanted to give you guys some ideas of what you could do about it, but we definitely have time to talk about it and answer questions. So is there anything that people would like to discuss
Michelle Eichelberger: Are you seeing particular things I've heard vague things about Gail issues, those don't seem to be as bad as the abs go ones, but the ones are definitely bad
Joe Riggie: Hey this is Joe, can I ask a question and share my screen.
Joe Riggie: Yeah, absolutely. Okay, it's probably a really simple one, actually.
Michelle Eichelberger: That would be awesome. But I doubt it.
Joe Riggie: Okay. Can you see my screen.
Joe Riggie: Supremo
Joe Riggie: Can you see that
Michelle Eichelberger: Yeah, we can. Oh, sorry, I couldn't get to my unmute button, you're good.
Joe Riggie: Okay, so this is a search for an E book that we have. And you can see there's two duplicate results in the very beginning.
Joe Riggie: And I as well. I think I know what the problem is. I just, I'm looking for a little bit of feedback.
Joe Riggie: There is just too many windows open
Joe Riggie: This existed Alma is just one record. It's coming from academic complete
Joe Riggie: But it's also turned on in the primo Central Index. Am I getting the duplicates there because it exists in both places.
Joe Riggie: Like if I turn this off. Well, I fix that duplicate
Michelle Eichelberger: I think so.
Michelle Eichelberger: But I don't know that for sure. So I would say try it and it's probably going to take about 10 days for you to see if it changes because it comes along for the PCI stuff.
Michelle Eichelberger: So I i think that that's the case. And you can tell that Joe, actually, if you go to the full record and do that displays CTO
Michelle Eichelberger: Or actually, you could even tell if you scroll down, if it's an Alma record the bib record from the alma it's, yeah. So see how it says display source record library catalog. So that's the one that's coming from Alma. And if you look at the other one. It'll probably say something like
Michelle Eichelberger: Yeah. Yep. That's exactly right.
Joe Riggie: I just had been under the, I guess I had hoped that the two would be
Joe Riggie: Stitched together so that we would get searching from both pretty central which should have. I'm guessing richer metadata than what we have it all mapped, but that's okay. I will have the same blood and see if it works.
Michelle Eichelberger: Like yeah, and with the CDI it will be emerged record. That's my understanding. Anyway, so that's something to look forward to.
Michelle Eichelberger: Yeah, and ebooks are going to be
Michelle Eichelberger: Handled slightly differently.
Michelle Eichelberger: In the CDI because it's you won't be able to set it up so you just search the alma record right now what you can do if you just want to search it by the title, author, that kind of thing. You cannot activate it in the PCI, you know, if you don't care about getting chapters.
Joe Riggie: Or that kind of
Michelle Eichelberger: more thorough indexing. You can just have it turned on and Alma but not the PCI, but in CDI
Michelle Eichelberger: You're going to be searching chapters reference entries everything all together with the bib record info. So we'll have a lot more information about that as we start working on training for the CDI but just be aware that that will be changing.
Joe Riggie: Thank you.
Michelle Eichelberger: Okay, so let me just take a second to look at the chat.
Okay.
Michelle Eichelberger: Yeah, Nancy for I'm checking record IDs, does that show up when you do the pn x
Michelle Eichelberger: shopian x i think the record ID thing is great and I can never remember how to get that to show
Michelle Eichelberger: And then Rebecca in our testing of the CDI is absolutely nothing better than with the current PCI, it's better, but it's not perfect. It's not going to fix all the problems. So I would definitely still set up that EPS go linker is over integration.
Michelle Eichelberger: And then Nancy says there might be slight data differences.
Michelle Eichelberger: One has a trademark symbol and one doesn't let me keep Liz. I'm going to come back to you.
Susan Davis (UBUFF): Well, this is Susan at you be in the issue that Liz talked about. I mean, sometimes we've seen where
Susan Davis (UBUFF): What do you call the the linking level is only let's say at the book level or the journal level, not
Susan Davis (UBUFF): You know, deeper in. So I mean, check that first because sometimes we've been surprised. You know, it's a journal and why aren't we getting to the article level, but maybe you know the collection you've activated might not really be indexed, you know, at the article level so
Susan Davis (UBUFF): Not solve everything. But sometimes
Susan Davis (UBUFF): It happens.
Michelle Eichelberger: That's a really good point. Susan and you can tell that right in Alma, it'll tell you if it's article level or journal level.
Michelle Eichelberger: I know specifically with Gail virtual reference library. It's not chapter level searching
Michelle Eichelberger: Or it might be chapter level searching. If you have something in the PCI turned on for searching, but it's not meant to be chapter level fulfillment, because the collection and Alma
Michelle Eichelberger: Is book level fulfillment. So I know that's annoying that I think actually is going to be better with the CDI but currently with the PCI that can be annoying and Liz, I just want to read your question more carefully.
Michelle Eichelberger: Okay so problems with linking and Gail, going to the search results page instead of going right to the article.
Michelle Eichelberger: I have seen that happen. But if it's going to the search results page where the, the actual result is right there. And you can link on it. I would
Michelle Eichelberger: Think yourself lucky. No, it's not ideal but like Susan said it may be just how that particular collection links, it's, it's great if it actually works and gets to your thing. So I would count that as a win.
Susan Davis (UBUFF): Right. But, but I would also say we have seen on occasion.
Susan Davis (UBUFF): Again, you know, actually versus getting tons and tons of data from these providers, they have a schedule for which they're updating
Susan Davis (UBUFF): Sometimes they don't have the current you know list of the titles that are included and you're getting sort of like a false lead because that
Susan Davis (UBUFF): That journals not even in that product anymore so that sometimes you have to do that, look at the title list in in that product to see is that journal, you know, the source actually still being indexed, because the the almost side can be behind
Susan Davis (UBUFF): And I've heard that from publishers that sometimes it takes a couple months for their updated information to actually be loaded, even if you know I mean actually Brazil telling you. Yeah, we're loading every week. But that's not everything every week.
Michelle Eichelberger: Yeah, there's definitely a delay and I would just say that I know that in the standalone databases. There's also, you know, often data issues where it says it should be full text, but it's not really full text or their, their
Michelle Eichelberger: Coverage date information isn't correct. So those kinds of problems are just going to be out amplified and Alma
Michelle Eichelberger: So you know problems you're used to seeing out in the standalone. You're also going to see in primo because it's the same vendors giving everybody the same information. So unfortunately, that's just the nature of it.
Michelle Eichelberger: And thanks, Nancy for the the show record ID. I think that if you Google show record ID and Alma, you can get information about how to set up that and also I can follow up after this session and post that information when I post the recording.
Michelle Eichelberger: Yeah, good point. China forget even a store can have things accidentally missing sometimes
Michelle Eichelberger: I wish that Alma would just work beautifully and not have those issues, but
Michelle Eichelberger: That's not realistic.
Michelle Eichelberger: Any other questions or things that you've been running into and I'm curious about
Michelle Eichelberger: All right, well, if there are no other questions. I really appreciate everyone attending today and I will have this posted as soon as possible. So thanks everybody. I hope you have a great rest of your day.