Right, we are back down at Cardin Park. Fairly gloomy day but someone is here that will brighten it up. I have brought the Yorkshire weather with me. You certainly have mate. How are you? What are we going to do? We're going to do it now! Got it? That's almost illegal. What we're going to do this morning is a really interesting video which is James Robertson's top five products of 2022. And I'm also going to guess what those five products are. Have you wrote your guesses down? I will reveal that at the very end. Right, got you. Right, so we're going to do this as very much five down to one and we'll start off with, well number five. Is there an order? There's no order. There's no order. I can probably think of an order but it'll take me a while. No, no. There's no order. The first thing Andy, I never told you but I went to the Masters. It isn't the head cover. This is probably the number, not quite the number one. And similar to one of the clubs that you did on my channel, it's not exactly brand new. Shall I hit it first? Yes, hit it first then we'll do the reveal. So the big thing for me here, I love Versatile Golf Clubs. I love being able to pick a trajectory, a ball flight, a window if you will. And this, for me, I've got a broken tee peg here Andy. Oh look at that. I'm going to use a full one. I can't look down because I'm not going to reveal the club. So keeping this on the wraps. As well as being heavily Versatile, I love the sound this makes. That might give people a bit of a clue as to what it is. And they are being replaced actually at the end of this year, which I'm slightly worried about. So I'm not sure how they can make them better. But for me, did you get that sound? That's a stinger of a shot as well. Like that's everything that I want out of this kind of club. And the club is Andy. Here we go, big reveal. The Titlist TSI 33 Wood. I've been a huge fan of Titlist fairway woods since I was a junior golfer. I just think that nailed it with this one. I'd never really changed the adjustability on it. I've always kind of left that way. It was a given to you where it is, where it's fitted to. It's in the heel, that weight. And I just have it A1 setting. Jam Pat for the technology. Sounds fantastic. Just a wonderful golf club. They're very much a go-to club for you? Absolutely. If ever I'm struggling with driver, which is most of the time, this is certainly a club that I go to. You can see there. It's gone a long, long way. Yeah, it has gone a long way. And it's a nice low trajectory. It gets quite windy where I play a lot. And generally, we're going to hit the fairway most of the time with it. That's number five. That is. Are you going to have a go? I'm going to have a go now. I'm slightly worried about my selections because... So what are your thoughts on this, Andy? You're tested this, will you? I've tested it. Interesting enough, I don't carry a three-wood. Right. And again, just going back to, I don't know which video is coming out first, but my top five selection had easier to hit options, let's say, at the top end of the bag. So I kind of stay away from them. It's a beautiful looking club. I mean, the one thing about this tight this range, it's stunning to look at. I will tell you what, I haven't hit it for a while either. I can't believe how far your ball has gone, by the way. That's absolutely mild. I'm going to tell you something in a second, Andy, where I wish something was slightly different on it. And I hope it might change on the new ones we've seen being ceded. Well, that was a really bad strike swing from me, sorry. I've leaked that out way to the right. And it's probably why it's not in my... One of the first bad swings we've seen from yesterday, actually. It is. It wasn't a great shot, to be fair. So I'd be hard to judge it on that alone. But I will say for me, like I said, the three woods in particular, in general, slightly more difficult for me to use than obviously the half of you. Very good. The one thing I'd changed, do you remember the three woods of old? I wish it had that fulcrum on it for the centre point. Yeah, yeah. Not the TS. I think they've lost a bit of identity with that. But apart from that, I think it's a wonderful club. I'm going to have another go of it. I can't judge it on that. You can't. To be fair, you'd probably be more TS-I too, would you, maybe, if you wanted to have the ball? Yeah, I would, without a doubt. Yeah, yeah. Love that golf bag as well. That's lovely, isn't it? There's a similar sort of swing, wasn't it? Yeah, sort of a heely strike. Identical ball flight. Very much across it. Right, so James first club out of the way. In general, what has been your thoughts on 2022 in terms of club releases? What do you think? Club releases, I think it's been an interesting year. I think obviously we kicked off with the stealth driver, the rogue ST driver, which I've sort of I'm torn between them because I do enjoy tailor-made drivers. A lot of people think I've got some kind of prejudice towards them or some kind of bias towards them, but I just think they're good. Like, I really enjoy them. I don't think the carbon age is going to be as long as we maybe think it is personally, because it's just not that much different, is there? Like, if it was that much better, you would hit 15 yards further than every other club, but we don't. So I found that interesting. I think the Callaway feels and sounds amazing, but the CUDA marketer, that better with a different name. I think going back to an old name is never really something that people want to see. I think it'd be interesting in terms of tailor-made what they do next year and whether or not carbon faces appear in their hybrids and ferns. I said this yesterday in my stealth, D, as I say, DUI, DHY and UDI videos, because when we first saw TwistFace in the drivers, we were like, well, why on earth isn't that in? And then it came. And it came. So I wonder if that's just a little bit of a... It will be interesting. Right, okay, so first of all, huge of the impress with where James Manning's to get that three word down to on this car for. I'll stop it, Danly, stop it. Carry on. We'll have a look at that in a minute or two, but you say we can actually stop here where you've landed. We can stop here if you promise, one second. This is for, this is for club number two from James. This isn't a club. Promise not to lose this. Hello. This is very special to me. Not your last one. That was my last one. This is the, so for me, I'll let you, oh, hold on. The, is it a tall response? Tall response, but the stripe version. So this is the ball. It's my last one that I had hauling one with. Oh, wow. The Wakefield Trinity Rugby League Golf Day with a couple of my mates. So we've got water on the next dole. Did you trust me to play it off the tee? No, absolutely not. So I'm going to show you something as well. So I was going to include the Kirkland ball in this because I think the Kirkland ball for the value is exceptional.  Unbelievable. It just, it fights its corner, doesn't it? But I've actually gone for this one because I thought the story behind it, this was a four round from like 220 yards and it was in an actual golf day as well. So it was just a nice feeling. But I had a hauling one with Kirkland with Chris up in Scotland at Archfield Lynx. That was 140 yards of the pitching. So you've had two hauling ones this year. Two hauling ones in two months. And I'll show you so we got it framed because Archfield gave me a lovely flag with hauling one on. And then I got the course planer and the ball. So you can overlay this on now because I'll send it to you. And you're going to get another one today in the match. Maybe. But it's not going to be with this because when I chip this onto the green, we're not going to lose it. Put it away again. And I'm going to put it away again to frame it. Right, let's see the shot from here then. So we are, this is where James's three wood finished. Did you get any yardage or anything or? As to where we've got to go, I mean. No, I'm going to feel it. I reckon it wants to land about 55. Okay.  So I've got, yeah, I mean, we need to be on that hole over there where there's a huge pond. And then that's exactly why we've come so close.  We're not going to discuss that. But I'll just hit this one in and then want to see if you can get closer. You mentioned that. I thought we'd agreed we'd forget about that. I didn't film that bit. Right. Yeah. Nicely played. Right, Andy, let's see if you can get inside my shot. I'm putting your wedge back in the bag because I've got, I've got one of my top fives. Okay. I know what this is. Yeah. This is probably the top one, is it? It's the most interesting one. And yeah, it's a chipper. It's a chipper. It appeared in my top five. Probably the weirdest club I've seen from anyone this year. So it's a thing. It's not probably designed for this 55 yards and I've not played many from it, but we'll give it a bit of a go, I think. Nice. Yeah, that's a good effort, that's on the green, you flag high. Yeah, I mean, it's not bad. I mean, the interesting thing is that's a real awkward position 50 yards again for kind of average golfers. And it got there. Now isn't the best, but it got there. The reason why I chose that ball is mainly predominantly foreputting. Okay. So we'll get down there and I'll show you a bit more about it. Right, James. So I've just switched the ball out from where your wedge just landed. This is a birdie, isn't it? That's a birdie, Otmer, yeah. So you said there's something interesting, particularly about the ball with puttin, which...  But the idea that you can get great feedback from a golf ball like this, there's a few... I don't understand why they've made it green. Like, you put it down almost, you can't see it as well as maybe if they made that stripe red or blue, even a black stripe or something like that. I think knowing tailor-made, they will probably make it... What do they call it? They call it my... Oh, yeah, yeah. That my tailor-made. Yeah, costumisable, yeah. Yeah, so I think eventually they might do that. They did a similar thing with the picks, didn't they? But I find that so easy to line up. So if you've got the right line, that's the first thing. And then I know if I make a good stroke on this... See the feedback on that ball there? So all I've done there is hit it too hard through the break, the ball's finished right behind the hole and on its axis. So you're happy with the strike in other words, yeah? Yeah, I'm happy with the strike. Yeah, it was fine. So almost like a training aid as well as... Yeah, you're learning as you go around. Training, but you're learning as you go around. So if I hit... So say if I hit a bad put towards you now and you focus it on that ball, you'll see that that loses that axis. So then you almost know, right, I've come across that, I've come too far from the inside, I've shut the face, et cetera, et cetera. The next club, for me, the best bit of equipment we both agree on this. Yeah, we do, yeah. Like this has been, for me, an absolute game changer. So stroke lab when it first came out, I thought it looked a little bit gimmicky. I wasn't too sure. And then the more you get the feel of it for long puts especially, like my lag putting has been terrible, but then I sort of match it with this... I'll always call this a number seven. Yeah. Like I'll always call it a number seven shaped head. It's a two long Las Vegas design. It's not anything special. It's off the rack, 35 inches, I believe. But then I went to the Callaway specialist and said, guys, I'm putting exceptionally well with this. I've been hot. I've also... You know, you know Chris, don't you? My mate Chris Davis? Yeah, yeah. I've hold so many puts against him and Gazz. Yeah. Literally, they hate it. Yeah, I've seen so many. They despise it. So I went just go and see... Because it wasn't fitted. I'm a massive believer to go and get fitted for your golf clubs so that you then know there's nothing better out there for you. And randomly, the fitter said, you know what, James? I would fit you into this. The same, right. The same club. Perfect. So whether or not that was a bit of a confidence boost as well, I'm not entirely sure. But I matched that with this and I must become a little bit more just happier. Obviously, that wasn't the best attempt at the birdie putt. But if we... Well, these kind of things, it's all about confidence, isn't it? Absolutely. And it's also, Andy, thinking about your expectations. So me and Chris, Chris is a really good putting coach and we work a lot on tour stats. So say from there, I had what? 12 feet maybe for birdie. So make percentage on tour there would be around 50%. Yeah, I was going to say 40%. Yeah, so why would I expect to stand up on video with you and hold it first time? Wouldn't necessarily happen from here. It's even less. That's a terrible read. I've given you a horrible example there, Andy. But for me, my putting stats have improved massively with this. So that's certainly something which... Yeah, definitely in the bag. Yeah, absolutely. I've been not going anywhere either. No. I change putters more than my pants quite often. Yeah, and to be honest with you, the interesting thing is, again, if you watch my channel a lot, then you'll also know that that's very much the putter in my bag, the exact same putter.  There's a bit of... I don't know whether it was in the previous model, there's a bit of perimeter weighting that's in that, which just, again, for me, just helps with... Well, I suppose forgiveness will certainly square that face up a little bit and it's been really good. What I do need to do is, Chris, when am I getting my putting lesson? Yeah, I offered you one, didn't I? Yeah. Right, that's three down for James. The next up is... Well, we've got a place, asked me to drive into a position with 150 out. So... You know what's not next up? Yeah. This. Yeah, that's going back in the bag. That's going back in the bag. But, obviously, it gives away a little bit of a clue from 150. I'm assuming this is going to be an iron, James. It's just going to be an iron. It's the irons that... I'm not going to mention the Halloween ones, again, because it's game boring, but it's an iron that I was fitted for this year. Let's get an exact yardage on that. I've got 164 playing 166. That's actually a nice number for my 7-Eye, and if there's no wind, I don't think there is. I loved my old Mizuno JPX921 Tores. Loved them to bits. They felt great. They were brilliant. I have tried to change my game a little bit. It's not quite where I wanted, but I feel like it's improving. And the shafts weren't quite right. I had Project Xs in there. I went down to Mizuno when the new stuff got fitted, like we do when we get to test products, and actually moved into the KBS S-Taper. Yeah, so the first kind of... First go out with them, really. I just played really well with them, and it's something which I didn't really want to change the iron makeup in my heads. But the guy's Matt at Mizuno highly recommended that I did, because I was just getting a lot less movement on that golf ball. So let's go straight to this flag. See. Yeah, good strike. Yeah, middle of the green, isn't it? And that's something where perfect yardage as well at their top deck. That's something where with the JPX-921 toss that I was using. Yeah, but hang on just before you review it. So what is that close? It's the Mizuno 223 irons. Okay, stunning. Really, really nice. I think it's just a head and a shaft combo, which for me works great. It's something which I'd probably go as far as saying, go and get fitted. Yeah, absolutely. Like this is something massively for me that generally works. I feel that ball flight you saw there, if I hadn't put a shot trace trying it, which I'm sure he did. Yeah, we did, yeah. That was quite a straight ball flight to the middle of the green. Yeah. A little bit. It's not a flag you're going to miss right by any stretch. Yardage spot on though. Absolutely, yeah. And that's something which with the strike was great. Yeah. But with the old clubs may have turned over a little bit. Okay. Only a couple of yards, but that's enough to miss the green take of our bounce. Yeah. And then duff a few chips and make it double. And does anything feel like a Mizuno? No. No. They are real. I mean, to be honest with you, I just said that I knew these were the irons in James's bag and I come really close to swapping out to them. I wanted to do a mix of HMB's and 223's. And out of the range, to be honest with you, this year the 223's were very much the kind of standout product in... Yeah. There's still a bit of forgiveness in them really, isn't there? 221 and 225, isn't there? With the others, yeah. Yeah. And for me, the 221's tiny. Yeah. And the 225's a little bit too tight. Yeah, yeah. Matt said, do you want to go 225 in the four iron? I was just like, no. Why? Yeah. It just doesn't look the same as the five iron. Yeah, which was the other odd thing they done. And then we had a hole in one of the four irons, so it worked well.  Brandy, are you going to have a go with... Yeah, I'm going to give it a go. In fact, no, I won't use that. I'll... I shouldn't... No. No. It's only a little bit of water. It's 150 carry. Surely you trust me to hit that. I'll tell you what then, yeah, I'm going to give you all hybrid. There you go. Have that back. Right. So, I mean, first of all, I am a big fan of these clubs anyway, from my initial review. I came so close to buying these things. Probably a different shaft than I would use, but what I really love about these clubs is they feel so good. Yeah. Nice middle of the road club, aren't they? Oh, they're beautiful. Great strike. Yeah, just... I think it's probably shaft that's done that. Cut across a little bit. But again, you know, the interesting bit for me was this. Two, two, three. Almost, you know, it's very much a player's eye, definitely off the bottom grooves and still manages to get somewhere down there. Like I said, it wasn't perfect, but that's the, you know, that's the thing that's changed for me in modern irons. Even these kind of things have still got plenty of forgiveness for not so good shots like that. Not quite pin high, that one. Not quite, bud. One thing I was going to say about Sandy as well, is you actually got a urethane cover on it. Yes. So although a lot of the balls where you maybe see this kind of technology on, they don't have the urethane cover. They have... It's not a premium ball or elastomer. Yeah, it's still... I mean, first and foremost, it's got to be a really good performing ball, hasn't it? Yeah, yeah. Right, so we're four down from James's selection. And I can tell you, we're a hundred yards out in terms of his final choice. And I'm going to treat you here, mate. Okay. This is three for the price of what? All right. So I'll show you them all, because people are obviously guessing. This is my wedge set up. Okay. It's the Voki SM9. Now, I've used Voki all my life. I've tried different wedges. I've tried Callaway wedges, Taylor made wedges, even Ping wedges. And nothing for me quite feels as good. I've tried to think the better word than good, but I can't. It's literally, it's simply, they are the best for me. Okay. And I know a lot of people kind of trust these wedges as well. Now, interesting story. I went and got fitted for these, like I recommend everyone should, like I said, about the irons. And I looked at my stats from kind of where I miss greens and stuff. Looked, obviously, when I edit videos like yourself, you see where you miss greens. Whenever I would hit a gap wedge and miss a green, it would be short. So I moved from a 52 in the SMA to a 50 in the SM9. Okay. Because for me, that's just a little bit more long. So what are you counting? 50. 50, 56, set at 55. Okay. And 60. So it's just a five yard gap. Which is quite a nice gap, I think. I love the 56 and the 60. Nice high floaty shots. I can open the 60 up and play it really nice. Get a little bit of stoppage on it. It's versatile enough. So the 60 for me is eight degree bounce M grind. Quite a bad, but I have to look at that, isn't it? But for me, that I can just open that up and it sits nice and flat to the floor. So we've just seen you play a bunker shot there on the previous hole. What would you play from the bunker then? Lobwadge. Try and get the ball up. Land it as close to the flag as you dare with hopefully a good strike. So it's going to have some neutral spin on it and it's going to stop. Okay. And again, there were two decent shots, weren't there? So Chris, my shot game coach, thinks I should bin my 60 and just use a 56 all the time. But then it's my club that I'm comfortable with. So I'm not going to do that. The confidence, yeah. I've got 120 yards here and we're going to try and just not this as close as we can. 50 degree. It's a beautiful strike. Sit. Oh my God, that could go in. That's not a bad representation, is it, that one? To be fair, a great demo when the wedge is full stop. I'm just going to see if we can zoom in on that. That is literally, well, it's probably a gimme from back here. I might even let you knock that in for birdie, Andy. I was like, I love the pressure. In fact, Andy, you can use that ball from there. That's the trust you've got to see in that last seven iron. I've got to say a hugely impressive demonstration of how to play wedges. Those vocies clearly work. He's actually, he's now prepared to give me his ball. You take that next shot with them. Thanks for the trust. I will just hang on. I will, we're going to end it there. That was first of all, come back on, sorry for the shot. Really enjoyed that, mate. Yeah, me too, really fun. Great five clubs. I will put on screen now what my five guesses were. I can tell you, I got two out of five right, yeah. Only because I thought the irons was a, I knew you, I knew you really loved the irons. And I had a feeling that the putter would be in there as well. Because I think that again, watching your videos, you're very keen on those two in particular. Yeah, we share those, don't we? Yeah, we do, yeah. So thank you for watching. No doubt you'll all be aware of James's channel. Get over there. We've got a couple of videos that we're filming each today on each other's channel. So make sure you're joining and watch out. And yeah, we've had what's up next, the match. We're going to swap clubs, aren't we? In fact, that one might already be on. There you go. There you go. Make sure you're keeping an eye out for it. Bye. Bye. See you tomorrow. See you all soon and thanks for watching. Soon, we'll be back tomorrow. Tomorrow's far too late.


Ever wondered why you feel all stiff the day after doing lots of exercise? Well this video will explain why but first let's try a little experiment. Put your left hand as high above your head as you can, stretch your fingers towards the sky as far as you can and then clench your fist as tight as you can. Now I want you to keep doing that throughout the whole of the video if you can. Stretch and clench, stretch and clench, keep going. In order for you to contract your muscles they need the energy that is released in respiration. However when you are doing heavy exercise for a long time the muscles can't always get the oxygen they need to carry out aerobic respiration. In this case the muscle cells can switch to carry out another type of respiration called an aerobic respiration. This is respiration without oxygen. So why don't we just do this respiration all the time if we don't need oxygen? That we don't need to bother breathing? Well unfortunately anaerobic respiration is not as good as aerobic. Firstly it only produces a small amount of energy compared with aerobic respiration and also it produces a nasty waste product called lactic acid. So how is your arm feeling now? It's probably started to ache. The muscles in your forearm which control the fingers are now carrying out anaerobic respiration. After a while the lactic acid will start to build up in the muscles and it causes pain. You can stop now if you like or maybe carry on to the end of video if you're as hard as nails. When you stop exercising you will need to break down this lactic acid. To do this the lactic acid needs to travel in the blood to the liver. Here it is broken down using oxygen into carbon dioxide and water. After vigorous exercise you may find you are still breathing very heavily for a time afterwards. This is to get the oxygen into the blood needed to break down the lactic acid. We say after doing anaerobic respiration that you're an oxygen debt. That you need to pay back the oxygen to the body. So to answer the question at the start of the video why do you feel stiff after exercise? It's all to do with with lactic acid. If you stop moving straight after exercise then the blood does not return to the liver and the lactic acid stays in the muscles. This is what makes them stiff the next day so it's very important to warm down after exercise with a gentle job and stretching. Okay you can really put your arm down now.


When my younger day, my dad worked with George Powell, he was an equipment operator. And then when I've grown up seeing guys climbing poles and all, I'll say, I want to be a lineman. Growing up as a lineman son, it was pretty hard at times, but it was fun because you knew when you passed by a George Powell truck, say you're on a school bus and you see some guys up a pole. Well, I was able to say, hey, my dad does that. Well, he started asking me a lot of questions. Dad, what you do?  As I was coming up, I always watched him be a role model in the community, watching him be there for others, whether it's guys on the crew or kids in the community. He was just always a given person and caring and always gave his best and whatever he did. So that pretty much shaped me into the person I am today. I went, Tyrese, he won't be a lineman. I fell proud. So I know the things that I went through. I said, well, that'd be a great job, great investment in the company. Because this position as a lineman, and more like a motivator or a trainer. You know, as a lineman on the crew, you're kind of seen as leadership of the crew and you have a lot of responsibility to take care of the guys, kind of take those guys from the start and train them and get them to where they're able to be a lineman one day and train someone else. The advice I gave Tyrese when he first started with Pilecome, I tell him I always remember that. He always an in the learning stage.  I really fell proud when he followed me in my first step.


Good afternoon and thank you for joining the webinar. This webinar is being recorded on Tuesday, September 22, 2015. All lines have been muted to cut down on background noise. You may ask a question at any time using the chat link on the left side of your screen. I would now like to turn the floor over to Martha Kira-Lidu of the Association of Research Libraries. Martha, please go ahead. Thank you, Amy. Welcome everybody. We're really delighted to have all of you here interested to learn about the latest pilot experience experiments that we did on the well-known live call survey. As Amy said, everyone is muted to cut down on background noise. So please type your questions in the chat box on the left-hand corner. And a recording of the webcast will be posted on ARL's YouTube channel after the event. And I'd like to welcome in this webcast beyond myself our two presenters, Rachel Llewellyn from the University of Massachusetts Amherst and Sarah Murphy from Ohio State University. They will be the main presenters for today's webcast. We also want to remind people that we have three more webcasts. We have captured with colleagues from other institutions implementing and speaking on different aspects of improving library services. And we've had colleagues from McGill and Texas A&M and from the UK, from Cranfield University and there, webcasts are available on the ARL YouTube channel. We do promote this series of webcasts as one of our offerings that promote one of our new strategic directions, a strategic direction known as Libraries That Learn. And this webcast series is known as the Libraries That Learn webcast series since it features ways for libraries to learn and use the evidence they have been collecting. So I do want to say a few things about what inspired the pilot we are going to talk about. From time to time we have heard our live call participating libraries bemoan a little bit the fact that they have to send reminders to everybody without knowing who has responded and who has not. So historically the live call survey protocol was developed and has been promoted as being anonymous. So as a result people were burdened with unwanted reminders. And there was no way to really know if someone had filled in the survey more than once, for example. And these were two motivating factors that led us to consider the development of the confidential survey approach to doing live call. And we are really grateful to both Rachel Wellen and Sara Murphy for stepping on the plate and being willing to test it. So what have we done with the confidential protocol that sort of makes it interesting and useful to libraries? The key feature is that you are able to send reminders only to those people who either have not viewed the survey or have not submitted the survey. And as a result you minimize the burden of sending subsequent reminders for filling in the survey targeting only those who have not responded. And you are also able to calculate more accurately response rates because there are controls behind the things that tell you who has responded and a person can only respond once. So they cannot go to a generic URL and respond multiple times because every URL is unique and is tied to the email address of a respondent. So this also I think brings forward a number of issues that we will have to sort of discuss as a community and as a profession. You know, with the anonymous protocol we do not link perceptions and behaviors with any other data that ability is not there. With the confidential protocol though the ability to link perceptions and the responses to the behavioral questions that the survey includes you can link that information to potentially other data and eventually one could even go to as far as doing real outcomes assessment by linking these perceptions and expectations of library service quality to other outcomes that the users are achieving, you know, graduation, completion time, graduation rates, future plans. But all of that I think will have to be discussed and vetted and understood a lot more thoroughly as we move forward. So the last bullet point I have there is about the importance of ethical considerations both on the anonymous survey protocol and on the confidential survey protocol. You know, even with the anonymous survey protocol oftentimes people come back to us and they say, well, you know, the computer IP could be unique.  Well, theoretically yes, but we do not release IP addresses to the participating institutions. And, you know, another consideration, ethical consideration is about the incentive price winner emails.  We have set up actually the anonymous survey protocol in such a way that the survey responses are disassociated from the table where we capture the emails for the incentive price winners. So we have taken steps in building the anonymous protocol that address the ethical considerations of maintaining anonymity. On the confidential side there are also similarly, you know, ethical considerations that one needs to consider. A key consideration is, you know, is this programmatic assessment or are you doing this more as a research project? There are different regulatory and each institution actually varies in a little bit in the way they approach programmatic assessment. You will have to talk with the institutional researchers in your institution to get a better sense of how your institution is approaching some of these ethical guidelines. And, of course, what we end up having now that we, on the confidential protocols now that we know who's responding and all that, we also capture their emails on the email, you know, incentive price winner database. Sometimes these two lists of emails do not match because on the incentive winner email database, for example, we eliminate those that have, you know, included the same email more than once. And there are, there's a cleaning process and a vetting process so the two lists can be different. So, you know, as you are getting more sophisticated in implementing whether it's live call or other surveys and you are considering whether you do it in an anonymous fashion or a confidential fashion, know that all those ethical considerations have to be thought through, taken into account. Ultimately, you know, we have a responsibility to do the best we can to respect and protect the subject's opinions and their identity. And I would recommend actually that you consider as professionals engaged in library assessment. You consider doing on a regular basis a certification course that's known as the city training certification that's available in most academic institutions. And there is also, you know, a time limit for this certification. It's good for, you know, three to two years. So every three years you go through that again because as our environment changes, some of our understanding of how we need to approach some of these research protocols and ALCX also shifts over time. So this was a little bit of an introduction on some aspects of doing anonymous and confidential surveys. And without any further detail, I'd like to welcome Rachel Llewellyn who's going to tell us in more detail how the live call confidential pilot was implemented at the University of Massachusetts Harris Libraries. Rachel. Thanks, Martha. Hi everybody. So I'm happy to share some of our experiences with the confidential pilot. I can tell you we first did live call in 2004 and we've done it in 2007, 2011, and this past spring in 2015. So we were especially interested in being able to customize and personalize messages to our users and to target the follow-up reminder messages only to people who had not yet responded. So that was what we were most interested in getting started. So just to give you a little bit of background of how we set things up, we drew, we did a combination of a population and a sample. We sampled our undergraduates and we pulled this over 3,000 names. We surveyed all library staff, all faculty, and all graduate students. So we did a population survey of those groups. A few little pieces around that, we were pulling them from our integrated library system, which we get that data from our campus system. So faculty, we were able to limit that to active faculty. So we felt like we had a pretty good population of the faculty who were actively on campus, and you can see that that was where we had a very high response rate. We have a lot of people in the library catalog under the user group of graduate students because they tend to be graduate students for a long time and sometimes their status changes. So that number of 6,682 is a little bit higher than what the campus numbers represent for actively enrolled students. We saw our response rate in that group lower than it had been in previous years, but in previous years we had pulled that sample differently. So we weren't too worried about it because it's sort of where we were in terms of the number of responses. So that gives you a little bit of background about how we got our sample and how we got started. So what we did is we wanted to send the mail from our Director of Libraries mailbox. So it would come directly from JShafer Director of Libraries and not with a heading that said all campus mailing or bulk mail, which is a good giveaway to know when you're getting a message on one of the lists. So we used Mozilla Thunderbirds and we used their mail merge add-on tool that you install. We made sure to schedule these mailings with the campus postmasters so it didn't appear that there was some kind of bad actor activity or any kind of spamming or any kind of other thing that was inappropriate happening on campus. So they would know that we were going to be producing this volume with mail. And the unique survey URLs were provided to us by ARL after we provided the list of emails to them. And ultimately we sent an invitation and two reminders. This is just a little sample of what the spreadsheet looks like. We blocked out the names, but we pulled the information from our ILS and then we separated the first name, the last name. We had an email. We had a user group designation for undergraduate-graduate-library staff and faculty. The URL was given to us by ARL as well as the information about the submit date and the start date and whether it is valid and complete. And as we would sort through the different iterations, we could make a choice to say whether or not somebody submitted something, whether or not it was true. So if you look down, oh, maybe the third. It might be a little hard to read online. There was a submit date of March 2, 2015, but it was not valid. So we had a choice to say, we chose not to send reminders to people based on the status of being valid or invalid. We sent it if they submitted any survey. We didn't send them a reminder. So we had that sort of different level of information that was around. We also added some additional fields. So to the far right is a coupon code. So we handled our incentives a little bit differently in that we offered everybody in the invitation as well as an each reminder the opportunity to have a free beverage at our cafe by printing the message and redeeming it whether or not they took the survey. But we were tracking redemption according to user group and whether it was on the invitation or a reminder. So we have a different coupon code for each user group and with each mailing. Similarly, there are some other columns if you keep going that customize the message further. There might be a custom line that says something about undergraduates or about faculty. But this gives you just a sense of the kind of standard spreadsheet. It had the URLs. It was matched up to the email. And it had our custom information as well. This is a little bit about how we got it started. So we used the double curly brackets which was the Thunderbird protocol for doing that and it would reference the fields in the spreadsheet. So when the message was complete you can select mail merge because you can merge and send it in two steps. So it connects to the spreadsheet and you can have the option to send it later and they're compiled and stored in your mailbox or you can choose to send them right away as soon as it compiles them. So those are the steps kind of briefly that you go through and you can see where the curly brackets are referencing your custom fields. And here's another version of that. So here's the first name. So this first name is pulling out of here and this is SurveyURL. It's coming from this column. And the constituent saying how we should make improvements for undergraduate students or for users depending on what kind of message we want to send. And this could be long. It could be a couple of sentences. We could put whatever we wanted into that spot. And then here I mentioned earlier with the coupon code where we were pulling from here. So this is to give you a little bit of a sense of how it worked. We didn't know how long it would take or what it would be like when we were in the process of doing that. So we started on a Friday afternoon and we merged the messages. We did a number of practice runs to make sure the formatting worked and that the links were active and that things were appearing the way that we hoped that they would appear for users. It took us about two hours to merge 11,000 email messages. That was great. We merged them. We put them together. We held them in the mailbox. And then Monday morning, right in early 5.45, we did the send. And it went very quickly. It only took an hour and 40 minutes. Monday morning was apparently a really good time to send mail on campus. And we didn't really have any trouble. We did see a bit of variation. We did reminder the following Monday but we didn't get started until a little bit later in the morning. So even though we were sending fewer messages, it took a lot longer to both merge and then to mail. And we did those back to back. And for the third and final message, we did it again on a Friday Monday split. That Friday though it was a morning rather than Friday afternoon and that took a long time. Now, it's definitely not an exact science around the merging. One thing that we learned is you have to kind of pay attention and I'll show you here. If you're in the process of mailing and you get an alert message, it will hold up the mailing. If you're not attending to it, click OK. So we did stay close by. We didn't leave it for long periods of time. But that was certainly a factor in how long it took because that might not have actually, it could have gone a little bit more quickly if we were being more attentive to any error messages that came up. That said, we really didn't get very many error messages at all. So that was really nice. We get a regular update from our campus in terms of the email addresses. So they're very recently updated and that's a pretty good source. So we don't have a lot of error messages. So that was actually really helpful to be sure that we were sending messages to real users. The one thing that we did learn is that when we merged the messages on a Friday, even though we sent them on a Monday, the timestamp on those messages was from Friday. So if that changes the order in which the mail appears in the recipient's box, that's something to think about. It could be good or bad, depending on your intention, but we didn't realize that until we actually received our own Monday morning messages with the timestamp on Friday. So that was something that we tried to pay attention to as well. So I don't know, Martha, if you wanted to take questions anytime here or just wait until the end, but that was a really quick introduction to how we managed the survey here. Let me unmute here. Thank you, Rachel. Let's take questions at the end and I'd like to encourage again people to put their questions in the chat box and then we're going to read them. So please do use the chat box on the left-hand corner of your computer screen to add your questions. Thank you, Rachel, and let's move on and hear from Sarah Murphy at Ohio State. Great. Thank you, Martha. Here at Ohio State, we've been administering live quals since 2002. We've done the survey nine times. And in the early years, our main reason for our interest in doing live quals was in part to support the renovation of this building here, the Thompson Library. And as time has gone by since we finished that project, now our interest in live quals is more to serve as one of the benchmarks on our scorecard for our library strategic plan. So, for instance, on this slide here, it shows that we're looking at the library's place dimension and really we're just trying to maintain or improve our score by bringing this gap number closer to zero. And so we have something here from a teaching and learning scorecard for libraries place and the affect of service dimension and in our research and innovation scorecard we're looking at information control. So our process for administering live quals confidential here at OSU was very similar to Rachel's process at UMass Amherst. We did do mail merges, however, we used Outlook and ARL sent us a spreadsheet that had unique URLs. We sent ARL a spreadsheet with all of the names for faculty, undergraduate students, graduate students and our library staff. So we took the unique URLs that we received back and we plugged in to an Outlook mail merge and this was the message that we sent. And, you know, in the middle, under take survey now we had the URL here and it's one little quirk that we found out through this experience is that if you do emerge with the URL and the recipient opens the message via an Outlook client on their desktop, the URL link stays live. However, if the recipient opened the message through a web mail application, that link sometimes was live and sometimes was not and we spoke with our IT department and we really never found an answer why. So if we do this again we will change our language a bit to say click here now or copy and paste this URL into your web browser because that upset some of our respondents. So this graph here shows our respondents in relation to the total population and by doing live call confidential and just sending out reminder emails to individuals who had not taken the survey our response rate was not affected. It did not go up or down. It was about the same as it is whenever we have administered the survey in the past we had a 16% response rate and we distributed a total of 11,981 surveys. Now this slide here shows one report that we were able to make with our raw data from our results and in the past because of the way we administered live call and not having any identifying information we weren't able to parse out our data in a way that was... I guess how to describe this. We could parse out our data but we were restricted to OSU colleges and schools which for a campus like OSU which has many diverse populations and departments and unique departments such as veterinary medicine or landscape architecture and pharmacy and our librarians are assigned to multiple departments and their departments are not always in the same college or school. This makes parsing out of results at times difficult and so with live call confidential this next slide shows we were able to take the unique IDs and match them back up to some local data sources so that we could obtain codes that were codes for majors and codes for faculty departments and those codes to match them back up to a reference data sheet that we have here in the libraries it's just an Excel spreadsheet that maps these codes to the assigned librarian and so now if we have a librarian who's assigned to veterinary medicine and environmental sciences and psychology that individual could review the results for the live call survey all by her user group population to the results for that population only. So we're using Tableau to run this and it works pretty well and that's basically I think all of my comments. And we are at the question slide again. It's really interesting that you can now actually tell the different subject liaison librarians that here's the data from your own subset of users. Have you had any direct feedback from those liaison librarians about the ability to mine the data this way? Well, let me go back a slide or two. You know, one thing I do want to mention too is that this is set up so that if the N is less than 10 no results will show and that's one way that we're respecting confidentiality of the individuals who took the survey but also since we're delivering these results using Tableau and Tableau Reader the underlying data, any identifying data is not part of that delivery. So your question though is how is it received? I think, you know, so I cannot claim credit for presenting the results this way. I got this idea from Jeremy Bueller over at University of British Columbia. They were really happy there were no radar charts. They liked the bouncing balls.  So if it's, you know, within the gray bar here that means it's acceptable service but if it's red that would be the red you would see on a radar chart. If it was green that would be the green you see on a radar chart. So these results are limited to our faculty right now and all of our subject librarians so that gives our subject librarians some more richness to the results too because then they can see the results just for their user population and color coded in a way that's meaningful to them. So you tried to have any meetings sort of with the subject librarians as a group to discuss how they are interpreting these data? We've had a faculty meeting and we've presented this at the departmental meeting for our research and education department. So you've had some. And Rachel are you thinking how are you thinking in terms of how this information can be used by the subject liaison librarians at your institution? You may have muted yourself. How about now? Is that better? Now we get a voice. We haven't mapped the sort of individual information back to a department level in the same way that Sarah has. So we are looking at our results at the school and college level according to the live call categories and putting together sort of versions or reports of the ability to look at that data by those broad areas. So sometimes that might be pertinent to one or two selectors or subject liaisons and sometimes in the humanities there might be more people that would be connected to those departments. So we're not looking at them at this point with that level of specificity but the nice thing about maintaining the email address with the data is that we have the ability to do that easily because that's part of our ILS data and all of the other patron data that we have and have that ability to look at it together. And actually one of the participants, Arielle Diordorf was asking specifically about how you are planning on matching the respondents to other data based on their name, email, what kinds of data are you hoping to compare it to? It sounds that at this point you don't have a specific plan but the ability is there if the need to do that comes in the future. Yes, and I expect as we look more closely at certain pieces there will be questions that are raised that then we'll be able to answer as a result to say, oh what does this mean and then we can look more closely but we don't have a particular question in mind at this point. Thank you. We have another question from Brian Roberts from Brigham Young University. Brigham Young University we opted to use Qualtrics to administer our survey and thus maintain anonymity as well as allowed us to personalize the surveys and track those that had gone to the live call survey though we had no idea if they ever completed it. It did improve our response rate somewhat from our 2013 effort and certainly minimized the number of reminders that were sent. So Rachel do you want to say something about the reminders and the burden on the respondents? I know that was a big driving force. Sure we were really pleased at the potential to not send reminders to people who had already responded and to not have to craft the explanation if you've already received, you know if you've already responded then you can ignore this or the explanation again that we don't know whether or not you responded it just seemed inelegant and we felt like we would be losing people and burning capital at that point so we were really pleased to have that and then it cut down on people sending messages saying oh I already returned to my survey we're introducing confusion about whether or not we had received their survey so we were really glad to be able to do that it's hard for us to know what the impact was it turns out that we sent fewer reminders so in the past we sent the survey coming here's your survey and then send three reminders depending on the user group we stopped after two reminders we may have that may have just been a result of our our experience knowing that they were people who were not responding and being able to follow that and then seeing the numbers that we were getting back we felt okay and we said you know we don't need to send another reminder in some ways just having more information about what was happening allowed us to make a choice not to send another reminder which I don't think we were anticipating at all and in closing this is going to be my last question I know both of you work very closely with your institutional research offices on your campus would you like to say a word about how that relation is helping enhancing the implementation of live call because that good relationship I think is important to be able to do a confidential version of the survey Sara do you want to step into well sure I have a pretty good relationship with our institutional research office over the years after sending many many requests to them they said well how about we just give you access to this data so for instance I used to have to ask our institutional research office for lists of names for various surveys and so they coached me through what I needed to do here on campus to take the appropriate training and get the appropriate certifications so that I could start mining some of that data on my own I can't do all of it for instance faculty data I still have to request from our HR department but I can generate my own samples for students for these surveys Rachel we have a nice relationship with our folks on campus as well and much of our work really does fall under the programmatic assessment as you explained in your introduction since we have access directly to much campus information through our ILS through the load that's already given to us as part of the work that we do and because there is a lot of programmatic assessment both in the library and on campus in terms of how are we serving users and what are we doing and how are we being responsible so it's sort of less in the research arena and more in the assessment end of things we had been originally had done the full IRB proposal back in 2004 and since then had an exempt status around the survey. I can say we had always put it forward as confidential rather than anonymous in that as you mentioned the IP information was retained and it was possible for those connections to be made even though all the appropriate safeguards were in place so that that wasn't didn't prevent us from doing the survey so it really wasn't a big shift in terms of changing the parameters I mean it certainly was in terms of our ability to have that information but it was already information we had connected to a lot of other kinds of library use. Thank you, thank you both of you I do want to remind everyone that we do have an opportunity to share our emerging and shifting practices and new ways of engaging with assessment questions and issues at the upcoming library assessment conference which will take place in Arlington, Virginia at the Crystal Gateway Marriott so mark these dates on your calendar October 31 to November 2 I hope we will have opportunities to do a live call share fair there and at this point from an ARL perspective we would like to engage a few more libraries to sort of do the next phase of the pilot where we're going to build an online interface and much of the back and forth we did with Rachel and Sara through emails it is going to be done through a web interface and we would be very interested in having a couple of you test this environment before we launch it as an integral feature of live call for future years so hope to see many of you at the library assessment conference hope to see a couple of you into the next pilot thank you very much to Rachel Wellen and Sara Murphy and thank you to Amy Jaeger and to all of you who have been with us remember for those who want to listen to any of this information again it will be available on the ARL YouTube channel have a great day


hear me? Hey guys, the back. All right, all right. Okay. I don't have, I didn't have much time to prepare but when Steve told me to do a presentation today, just in time that I need to do some Terraform stuff for this morning. So I'm going to be talking about two things. So why am I using Terraform and what I've learned? So if you all know, I work for Trend Micro, Security Company. We're an advanced partner of AWS and I'm a solution architect there. So I work only on AWS platforms. So I need to build demos. I need to build demos for events. I need to emulate the entire Trend Micro line, product line on AWS and I need to build a hands-on lab for customers. This morning, just in just no kidding, just this morning, we had an event that basically did an emulation of our attack simulation.  So basically that's what we did in 30 minutes. So you have to protect us a very vulnerable machine in 30 minutes. So that was the story. So not four, not five, not six, but there's 50 participants this morning. So when you use Terraform, building for one project, second project, third project, but it's okay. But what if you need to build 50 different setup, 50 different Terraform steps? How does it work? I'm not an expert of Terraform. I don't work for HashiCorp. This is just what I've learned. So instead of giving you one by one, I just tell you what I've learned. So modules, they do not have a count. So if you know count, it's a way of multiplying things. So for example, I want to build 50 instances. I'll just type for times 50, but I build everything on modules. So I'll show you my setup. Can you see? Can you see the back now? Clear. Kind of clear. All right. So this is my Terraform folder. So what I do is I have different projects. So I got bar, bill, L, dart, dust, ego, L. So these are all stranger things characters. So that's the name of my project. I name all my projects to stranger things characters. Now, and then I have modules. So I have modules where, for example, I need to create Jenkins module. So every project, I can just go to my, for example, I got a build project, not this one. That's not a good example. I got a bar project, and then I get to say, I need an email server. I have a ddan server. I have an endpoint server. I need a bastion host. I need the victim. I need an attack machine. I need the manager. I need DNS. And the first one I do is I need the VPC. So my VPC is pretty well defined. It contains it contains those stuff like flow logs and stuff like that, because I also teach AWS security to people. So now, if I need to create 50, for example, 50 servers, what I can do is just, for example, here, I have my Linux server here, and I can just put a count 50. But that doesn't work on modules. So when I go to modules, so modules is basically to give you a perspective, right? Modules is basically how you replicate each individual Terraform mini stacks, to say. So I cannot put a count here. I cannot do a count here. It won't work. So you know what I did? Because I only have basically half a day to replicate my setup to 50. I did it the best way possible. So what I did is I copy pasted everything. So 01, 02, 03, 04. And I could have done better. I could have used Jenkins and I could have set up like a Docker based setup to multiply it by 50 and make 50 individual copies. But I simply didn't have time. I only have three hours to get it done. So I just did the best thing ever, just do a copy. So I have my first 10, and then I just put the rest. So rest as 40 items. It's very, very painful to set up to run because it will take you one hour to create this entire stack. And in Terraform terms, it's super frigging slow. When we build stuff in Terraform, we only count like one minute to build an entire stack. But this one took one hour because I have to multiply everything by 50. All right? Okay. Okay. All right. Oh, another thing. What I learned is you need to review your limits. So there's a limit for VPCs. There's a limit for EC2 instances. There's even a limit for EBS volumes. A big mistake that I did yesterday is I used magic. I used the magic of creating an instance and it created magnetic EBS volumes. But I asked AWS for limit increase on the SSD volumes. So I was scratching my head.  I realized that Terraform, they build only magnetic instances. You have to specify to your instances that you want to use SSD. So what I did was after like two hours in chat with the AWS guy, hold on. What's that? Where is that? We realized that we have to change the volume type to GP2, which is the SSD. Yeah. Okay. Next. CloudFormation Terraform. So it's not really true. I used to use CloudFormation for five years. It's a love-hate relationship. So when I moved to Terraform, it's also a love-hate relationship because it's, you know, people say breasts are greener on the other side. Not true. There's a merits in CloudFormation because the state is stored by AWS. If anything happens, it will roll back the state for you. A lot of things that CloudFormation doesn't Terraform doesn't. Okay. And it's not just for infrastructure. It's not only for servers. So because I didn't have time to, you know, I really hate using the console with AWS. I've used AWS since 2009 and I just click, click, click. That's very tiring. So I also wrote run commands. So I actually put the run command. If you don't know run commands, basically, if you want to run a command to any instance on AWS, you use a run command to execute it. So basically, I have a run command on an instance that will attack another instance, basically. So I have a Python script that will issue an attack to another instance. So you don't just use Terraform to create servers. You can also use to upload documents, right? So don't despair on the EOD. So if you're new in Terraform, basically, they allow you to insert stuff like user data.  So like EOF. So you'll do an EOF and then you'll insert a JSON document inside your template. This can be very, very dirty because it's hard to edit. So what you can do is you can actually use a data function that can import a shell script. So I have a shell script here. So if you look at my shell script, I can variableize everything, but I will edit it because code looks at it as a shell script. Now, you might be wondering, what's my setup, right? So I always used to work like this. I have an ultrawide at home. So I always have three screens of like this. It's just big now because we're doing a demo. And then I always put my Terraform stuff here. I always put my Terraform at the bottom. So when I'm working on the two windows there, I always have Terraform at the bottom. So wrong spelling. So when I hit Terraform refresh, I can work here and then I can see the update there. Never restore state in local. So if you look at Terraform, it uses state management. So basically it's a state. The default is it will store the state of your servers, of your infrastructure in local. Try to use Dynamo DB and SRE. There's a combination where you do not have to save the state in your local machine because if you put a control C while you're doing an apply or when you're building the infrastructure and you cancel it, it will break the state. Basically you break your infrastructure.  And I've done it three times before. So don't be like me. All right. Now if you're very certain, you know the thing that takes the most time in building Terraform Star is refresh. So if you look at this refreshing state, this actually eats the most time. And it consumes a lot of bandwidth because what it does is it will make individual API calls to AWS to check if that stuff is built, if it's there, if it's running. Now if you're very sure in your apply, if you don't want to do a refresh, you can just hit refresh true. And then when you do a refresh true, it'll just apply the changes that you want to do without checking. Risky. But if you're certain and if you're running out of time, like this morning the demo, my demo doesn't work. Like my event is at 9.30. I was in the Uber at 7.30. I was still fixing the demo on the Uber. So because I'm just gambling, I just apply, apply, apply without refreshing because refresh takes around one of my big stacks which has 3000 resources. It takes around 10 minutes to refresh it. Okay. All right. You can also use it to create AMIs and clone them. So yeah, I've done so many times like right click create AMI in my life. So I have this tip you can use. So I have a cloner project. So what it does is okay, let me make this bigger. So I have a cloner project and what it does is it will basically clone all my AMIs to another region based on a specific tag. So and then everything is dynamic. So what I do is on the variables, I just look at these tags DSM or D2008. So basically all AMIs that has that tag that is the latest clone it. So that's how I clone AMIs and build AMIs. Set workable defaults in your variables on your modules. So I'll give you an example. People like put the variables without values. So for example, list, without the value. So that means Terraform will always ask a value from you.  And what I'm trying to do is like on my VPC, what I do is I put a lot of defaults on the variables so that I don't have to put variables that much. If I need something quick, I just put VPC. It will build it. So I'll show you how I build the VPC. It's just like this. I just need to put the name. I just need to put the environment. That's it. Everything else pre-populated. But if I want to change the IP address, I want to change the subnets, I can add. But if you're really doing something quick, you can do this. Check API limits. So I was talking to AWS support yesterday about my project. And they told me to be careful of my API limits when I'm running this kind of things because there's an API limit to AWS. So I hope I'm happy with it. And study the Terraform syntax. So I've been using this Terraform apply. And then I put parallelism. So parallelism is how many times it can do stuff. So for example, I have 2,000 resources. It's going to run 100 operations every time. But that can, if you have a fast, what I do is I don't run the Terraform in my machine. I create an easy-to-instance. And then I run Terraform from there. So it's just a respect to depend. It's just make it faster. And then I put auto-approve because I learned it when I'm doing Jenkins, when I'm deploying in Jenkins. Yeah. And that's about it. So other stuff, because I only have 15 minutes, planning is important, very, very important when you're building because you can get to a lot of mistakes when it comes to building up your stuff. This is like my fifth or sixth project like this on Terraform. So I learned a lot already. And I'm not a master yet. So I have customers that have more complex environments and very, very complex Terraform setups. Yeah, have fun. So for me, it's a very fun tool. It's a very fun product. If you have time, just try to study Terraform.  It depends on how you want to do it.  And I just, YAML support for CloudFormation just came out a few years back. So when the YAML support came out for CloudFormation, I'm already using Terraform. I already transitioned. All right. So yeah, that's it. So thank you very much. Any questions? I think you can export the plan file and then you can use that plan file to make up applies. So you do a Terraform plan. You can actually export that out of that and then you can apply using that plan. Well, if there's a lot of magic in Terraform, maybe, you know, there's a lot of magic. So for me, my goal is like in me. My job, my goal in life is not to be seen. My goal in life is to be up in the environment to


Let's make the coolest lasagna hack you've ever seen. Check it out. Take your cooked lasagna noodle and we're gonna roll it like this. We're gonna lay it in our cupcake tray just like that. We got our melted butter here, Parmesan cheese, dano's original. You can find it at Kroger or Wal-Mart. I'll add that in. Now we're gonna blend this up. Drip it right down in the middle of these noodles. Throw in our green pepper in there. The dano's OG. Pop, pop, pop, pop, pop. Get it with some fresh garlic. Now it's time to add your favorite sauce. Favorite rich. Transfer your marinara to a bowl. Do a little mozzarella.  Three quarters of the way.  Now we're going into our oven at 400 degrees. Let's see how they turn out. And that's the yum yum. Get you some, my friend. Mmm.


Today we're going to talk about referencing and how to use the library's referencing guide for your assignments. There are two parts to referencing, the citations within your paper and the reference list at the end of your paper. You must include a reference any time you use another person's work, ideas, or quotes in your writing. The way you format your references will change depending on the referencing style you use, but each in-text citation should always have a corresponding entry in the reference list. If you don't know which referencing style to use, check your unit guide or ask your unit coordinator. There are three steps you'll need to follow to create your reference list, finding and identifying your resources, recording information about the resources, and formatting your references according to your referencing style. So say you have a resource you want to reference in your assignment. First you'll need to determine what it is. Is it a book, a journal article, a website, or another type of resource? Once you know the kind of resource you'll have, you'll need to record information about it. This will include who, who created the resource. This is usually the author, but it could also be an organization, an editor, or an artist. What? What is the title of the resource? For journal articles, you'll need the title of the article and the title of the journal it was published in. For book chapters, you'll need the name of the chapter and the name of the book. Where? Where was the source published? For print resources, this means the place of publication and the name of the publisher. For online resources, this means the web address or the digital object identifier or DOI. When? What year was the source published? For resources like newspaper articles, you'll need to record the exact day. And whatever the resource type. Don't forget to record the page numbers of any quotes you use. Once you've collected the information you need, you're ready to create a reference. To find the referencing guides, start on the library homepage. Scroll down to referencing guides, and then select your style guide. The All Examples tab will show you how to write in-text citations and reference list entries for a range of resources, including books, journals, websites, conference papers, images, and newspaper articles. Always check that the example material type is the same as the resource type you're using. If you need help with in-text citations, the Citation Examples page breaks the process down step by step and shows you how to put citations into your writing. If you need help with the reference list, the Sample Reference List page will show you how to format your list correctly and has tips on putting the list together. So now, let's practice referencing. Here's a resource I've found on library search that I want to use in my assignment. First, I need to determine what type of resource it is. From my search results, I can see that it's a journal article. So now, I'll need to record information about it. Here's the title of the article, the authors, the journal title, the year of publication, the volume number, the issue number, the page numbers, and the DOI. Once I have all my information, I can go back to the referencing guide and find the right example to double check I have everything I need. Then I can use the example to put my information in the right order and format it correctly. Don't forget to check the use of punctuation and capital letters when putting the reference together. Maybe I also want to use my textbook as a reference. I already know what kind of source it is, so I can start looking for the referencing information. I've found the title, author, and publisher on the front cover, but I'll need to check inside the book to find out where and when it was published. Once I've found those details, I'll go back to the referencing guide again to make sure I have all the information I need and to see how to format my citation and reference. If you need any help with referencing or with using the referencing guides, ask a librarian.


Live from Orlando, Florida, extracting a signal from the noise. It's theCUBE, covering Pentaho World 2015. Now your host, Dave Vellante and George Gilbert. The 600 customers and partners here and obviously a few Pentaho folks. Pentaho is a company that solves the problem of data integration and blending data to operationalize analytics. And it's a company that's been around for 11 years. So they started about the year before Doug Cutting and his colleagues put forth the first idea of Hadoop into the ecosystem. And so the timing was actually very good for Pentaho because what's happened since then in the last decade, if you think about it, you and I are going to talk about this, a huge amount of data has surfaced. And in that decade, data went from being a problem that had to be managed, a liability that could get you sued for a smoking gun email or some other type of evidentiary issue that could take you to court and cost you hundreds of millions of dollars to one that is now an advantage, a business advantage, people driving analytics, driving machine learning, driving real time, trying to affect business outcomes, what we at Wikibon call systems of intelligence, some of the work of George that you've done in that area. And the interesting thing about Pentaho is it's not an out-of-the-box BI tool. It's a robust platform that includes governance and a lot of capabilities and tooling around blending data, a lot of customization capabilities, some relatively lightweight visualization tools, a lot of integrations with other partners, and they've built out that platform and hardened that platform over the last decade. And in my experience, George, it takes about a decade to really harden the platform. When you look at Pentaho and you compare that with some of the other tooling that's out there, it's much deeper, much more robust, and has a lot more stickiness within the customer base. The other thing is very strong affinity with cloud. We heard customers like FINRA today talking about how they're extensively leveraging AWS as a platform, how they could not have done this with a bunch of heterogeneous stovepipes. And the other thing I'll mention is, Pentaho is a company that just was recently acquired by Hitachi. Now, Hitachi is this giant $80 billion conglomerate. Ironically, the combination of Dell and EMC will be about an $80 billion conglomerate. The difference being that Hitachi is much more diversified. Hitachi obviously competes historically Hitachi data systems with EMC and hardware. It's interesting to note how Hitachi is diversifying away from hardware, something that EMC has done a little bit obviously with VMware, but largely has focused on infrastructure hardware with its acquisitions. Hitachi now diversifying, leveraging a company like Pentaho to drive its internet of things and its big data strategy, George. So that's kind of my overall summary. A lot of energy here, a lot of hardcore Pentaho practitioners. What's your take on what you saw this morning with the keynotes and what's happening in this world of big data? Well, what's interesting is that we're evolving to a model that's very different from what we saw in terms of tools for traditional data warehouses. Business intelligence tools then, or the tools we had, they were either, for the most part, ETL tools which helped you get data into the data warehouse, or they were the business intelligence tools which helped you visualize and report on that data. And those were kind of the two big categories. And we had some niches with statistical modeling and things like that. What's different here is that we've got a new data platform in Hadoop that is really an ecosystem. And the ecosystem is about mixing and matching data processing capabilities, something that we didn't have in the data warehouse world. So the mix and match could be something as simple as the extra transform load. It could also include the sort of summary and aggregation that you would expect from a SQL database. It could include also the predictive and prescriptive analytics. It could include drawing in data from many different sources. The key point here is, and there are other analytic capabilities as well, including machine learning and graph processing. The main point is it's a mix and match world. That gives great flexibility, but at some cost. The cost is complexity. And the role that Pentaho is filling is to put a layer above that mix and match flexibility and complexity and to start to hide that from customers. And they're not trying to fill in every piece of functionality. They put functionality that is very strong in each of the areas, but then they're beginning to open it up for others to plug in. So let's unpack the keynotes a little bit. We heard from Quentin Gallivan, who's the CEO of Pentaho. Chris Zeichan, who's the Chief Products Officer. FINRA gave a great talk on how they are ingesting different types of data sources, blending them with Pentaho, running them through Amazon with S3 and EMR, and then delivering self-service analytics to the business users what Pentaho refers to as embedded analytics. We heard a talk from a forester analyst talking about the different types of analytics. So he did a very good job breaking those down. Mike Olson picking up on his themes from a couple of weeks ago at Strata and Hadoop World about making Hadoop disappear. I say it's more invisible. It's not really disappearing, but it's becoming invisible. And Kevin Eggleston from Hitachi talking about where the fit is within Hitachi. So I thought that was very interesting. Some of the highlights from Quentin Gallivan, there'll be five billion people, 50 billion things, so he really struck an Internet of Things chord. He also said big data's getting cloudy. Now, I tweeted out, I totally agree. So in our recent big data survey, 70% of the organizations we talked to that are doing big data analytics are using the public cloud. I thought that was an astounding figure. We had some excellent examples today of AWS. Google actually, with Microsoft, was number one and two basically tied with Amazon sort of a close third. But it's clear that the public cloud guys, and you've talked about this, George, are building out end-to-end data pipeline capabilities incorporating systems like Pentaho, giving you access to them in order to simplify big data analytics and deliver it as a service. That is a key trend that we're seeing. I couldn't stress that more, which is the cloud vendors are trying to marry the mix and match flexibility with the simplicity that came from the traditional data warehouse where the entire software platform was created by a single vendor and all the data was sort of curated by a single set of staff. Those native services, it actually turned out in our data, I think that it was half were using just on-premises Hadoop. Of all the people who were using Hadoop, half were using it just on-premise and half were also using either cloud-native or Hadoop on the cloud. But that was a really shockingly large number because it says that that's hybrid scenario which has only just been possible in the last really year or so is really taking off. We also heard this morning, Mike Olson talked a lot about Spark. We're going to have Mike Olson on later today. We're going to ask him about Spark, we're going to ask him about Kudu. A lot of discussions in the community about does Spark replace Hadoop, our survey showed that a large percentage, almost 100% of the people that we talked to in our survey said they're going to take workloads and move what they normally would have placed on Hadoop using MapReduce and HDFS into Spark. And then of course the data stack survey that showed that a huge percentage, of course they were... Day Bricks, yeah. The data Bricks, data Bricks survey showed a huge percentage of people doing Spark with no Hadoop. About 40%, I think was the number. Now of course that was very much weighted to their customers. And then of course Cloudera bringing out Kudu. A lot of people think it's a replacement for HDFS and H-based. That it's complimentary. Of course Mike Olson discussed today. It's really not ready, it's not hard. And so of course they're going to have that positioning. But essentially what's your take on Spark and the move toward data in motion in real time? Well, it's fashionable, especially among us analysts, to set up a battle royale. But it's not entirely. Basically Spark, think of it as the next gen MapReduce. That was for many years the core... For Hadoop 1.0, that was the core execution engine. Anything you wanted to do on data, you did on MapReduce. If you wanted it to do SQL, you did it SQL on MapReduce and we called it Hive. So now, because hardware is different, we can rely more on memory because the folks at Berkeley did a sort of a better job in creating an execution framework. We have something much, much faster and more expressive. So all those workloads that used to depend on just MapReduce are sort of migrating to Spark. And when I say workloads, I don't mean necessarily all the things that are in production. I mean the sort of the new workloads or the hives and the pigs and things like that are being ported so that they run on Spark instead of MapReduce. But just last point, they all still have to fit into the... For customers who've deployed Hadoop, there's management and security and data lineage sort of part of the ecosystem that keeps it enterprise ready and that's not going anywhere. So Spark would run in that context for people who have Hadoop. For people who don't have Hadoop, that's a little more of a jump ball. They could use Hadoop as a... Spark is a service from Databricks, for instance. So we're going to be impacting this today really trying to understand how organizations are operationalizing analytics. We heard today that, I thought it was great, Hadoop has gone from the sort of awkward teenage stage into the hipster with the beard stage so that's where we are today. I'm still waiting for that transformation. So you're pretty hip, George. You're going to get a beard. So we're going to be talking to customers today. A number of customers are coming on today. Fenra being one of them. Mike Olson is coming on. We've got the analyst perspective from Forester. We've got the Hitachi perspective and what that means for IoT. So stay with us. This is theCUBE, SiliconANGLE's flagship program. We're here at Pentaho World 2015. The hashtag is P-World 15. So definitely tweet us, join the conversation. This is theCUBE right back after this work.