Okay, now that we know what the layered architecture is we go into what rest is and rest is a so-called architectural style for network-based application software So for anything that runs on a network like the internet And nowadays most of our applications are somehow network-based, so it covers a lot It's something that was originally developed by Roy Fielding a guy that did his PhD on this kind of topic and what This style does is it tells you how to structure software that runs on a network, so how to Basically decompose it into pieces and how they should communicate so that it's effective Basically nowadays a lot of these kind of network-based applications are web applications that use HTTP or HTTPS So it's a very common use case and that's why it fits into this course it is Used heavily in the design of the HTTP standard and how your eyes are structured, so That's why I have that later But that's why a lot of the things I talk about you sort of you will recognize from the way the internet works So it's sometimes a bit difficult to to get across the point What's so special about this style because a lot of you know many of the things Rest is a is a combination of things. So it's not like a completely new invention Basically, it's a smart combination of existing styles how to structure system One thing rest does is it talks about resources all the time So everything is somehow a resource and that's sometimes a bit difficult to understand. I already mentioned that in the second Lecture and we said HTTP returns a resource, but we'll get into more depth on that Now if we let the guy speak himself Rest is about scalability. So we want to be able to scale our applications And the interactions between them and that's exactly what we have in the internet, right? You can have a lot a lot of interactions a lot of requests at the same time and it's built in a way that's scalable We can have many users The interfaces should be very general So it should you shouldn't have inside knowledge of each application to figure out how to call certain things Then very important independent deployment of components And that's a very important thing in the internet again. We have a heterogeneous Infrastructure so we have different hardware different network standards different operating systems And this style is made in a way that this is easier to do Intermediary components so we can put stuff in the middle that somehow helps us to reduce latency That helps us to make systems more secure And a very important thing it helps us to encapsulate legacy systems. That means We often have systems in the internet that have been running for a long time and it's hard to replace them You don't you cannot rewrite the whole system. It takes a lot of effort And the rest style helps to sort of put a server in front of it so that you can adapt it to maybe a new Interface and a new kind of way of calling it but in the background actually the same old system is still running So you do not have to reprogram it you just sort of slightly change one component in your setup now rest is just a style of structuring a system And you often read about restful web services So that basically means you have a web application a service in the web that is built according to the rest style But rest is not exactly the same as a web service So you can have an application that is strictly speaking not a web service, but it still follows rest so This is confused a lot in the internet when you read blog posts and so on but rest Per se is not only about web services. It's a general way of structuring systems now rest stands for Representational state transfer And that's a bit of a confusing acronym But what it means is we transfer something we send something across the internet And what we transfer is a representation of the current state of a resource Now that does not help a lot I assume so let's go into depth here Let's assume You request a minesweeper board not broad so Assignment to you request a resource in our case. That's a board that tells you how the minesweeper thing looks like the server Sends it back to you it transfers something And it sends it in the HTTP response. So that's the first part of our acronym What the server actually returns is a representation of the board It does not return exactly the same data as in the database For example, it might not return all the IDs like the MongoDB database Internally has has another ID that depicts which version we have or there might be in the minesweeper case I don't have that but we might want to add information about how to solve the board. So The server just returns some kind of representation of that So I could send in our case. I sent back a JSON string But I could also send back a picture for example, that would be a different kind of representation So that's a difference. I don't return exactly the same as in the database I return some kind of representation of it and then finally I return the current state So resources can change over time If I would go in and change the board Manually for example, then the same resource the same minesweeper board suddenly has a new state And the next time you do the same call again, you get a different representation Because the change the state has changed So that's really what it is about. We transfer something which is a representation of the actual resource And we always return the current state of it Now the rest style comes or is defined as a number of constraints as a number of things you have to do If you follow these constraints, you are restful. Your system is restful There is one exception and that's number six that is defined as an optional constraint So something you don't have to do Now as I discussed earlier most of these things you have seen before So there might not be that many surprising things and I'll go in the following. I'll now go through them Five I'll do last because it's maybe the strangest one or the one you haven't seen before Okay number one client server so Rest says the system should be built as a client server system Um, which means there is a server that responds to requests. It does not send requests itself Back to the client. So it just answers. That's a general setup It's essentially as the idea is its separation of concerns So many user interfaces here can use the same server The same data the same business logic. We don't care Also the user interface the front end can evolve separately so I can change it The server remains the same And that's great because I can for example have different teams working on these two components And then finally talking about the heterogeneity of the internet My server code can run in a completely different environment in a completely different programming language on a different operating system than my client So again, we have seen this in the assignment two examples My back end my mind sweeper generator does not care about what hardware you have what operating system you use and so on It's separate The second constraint is statelessness. So That means Whenever you send a request it contains all the information And that's now a bad example because in the mind sweeper case we we did not use that But for example, imagine you are in the gmail application and the first request you send is Login. So you want to log in That's the first thing you do. The second one is for example List the emails Now there are two ways of implementing this you could say First you log in Then the server or the client remember that you're logged in. So when you send list email It says, yeah, you're logged in here are your emails That will not be stateless because the server or the client would have to remember your first request So the second request depends on what came before Now what happens actually in a stateless system is you do the login You get some kind of information back We'll cover that in security, but quite often it's like a number a token That says this is your login information and the next time when you say list email you have to send this information along So you say for example, here's my token And then the system Doesn't remember this request. It doesn't need to know the only thing it needs to check is is this token correct or not? If yes, then list the email And that means each request contains all the relevant information That's an extremely good thing per se because For example, if you want to debug something is wrong You only need to look at one single request if My second request here depends on the first one if the server needs to keep track of it Then I need to debug the entire history Because something could go wrong in the first request something could go wrong in the second one But that's not something I have to do here The next thing is reliability If I have a failure if I if there's an error, I just need to re-send the last request If I would have a stateful system that something remembers then I might have to start from scratch and first do login again Then do list emails again and so on. So it's more reliable. I need I don't need to re Send everything. That's also a good thing for testing. I can test things separately And then scalability is is probably another issue If the server doesn't need to keep track of the clients and what they have done so far and where they are It's much easier to build distributed applications because I could have Multiple servers that do the same thing. So I could have another machine here And yet another machine and it doesn't matter whether the request goes to the first The second or the third thing it doesn't matter because all the requests have all the important information If it would be stateful and I would for example login on server one Then server two would have no idea about that. So I would somehow have to handle That server one tells server two about it. If I have a stateless system, that's much easier We don't have to care about that So it's easier to build distributed applications, which is again a very important thing in the internet There is one issue with this. So most of these constraints are not perfect. They are trade-offs And the issue is the network traffic If you need to send More information in each request, of course, there is more network traffic There is more stuff you need to send over the internet So that's a disadvantage we have Um That's something we have to live with Now the third constraint is cashability. So This means if I do a request The server needs to send back in the response. It needs to tell you Can you cash this request or not? So basically, uh, it has a yes no flag here that says yes You can cash this or you cannot Um What this means is the client knows If I sent the same request again Do I actually need to send the request or can I reuse the last response? So I save Network traffic. I save time If I don't have to do that again Uh And the user of course thinks that's great because the answer sort of arrives quicker in reality I never send a second request. I just reuse the first one But it just means the response has to have some kind of information about whether or not something can be cashed There is again a trade-off with that and that's reliability So if I have implemented this in a bad way, then it could be that the client reuses information that is outdated So for example, uh, I have a website that changes all the time For example, it has live weather information Uh, and if I tell the client you can cash this website for up to two days Then the client would always get Uh, weather information that might be up to two days old. So this might be unreliable. So that's the disadvantage here Constraint number four is uh, basically follow the layered architecture style So that's Exactly what we discussed before use a system that is somehow layered No direct calls across layers. No backwards calls Um And the advantages are as we discussed earlier, you don't need to know the upper layers The back end doesn't need to know the front end the database doesn't need to know the server Uh, many upper layers can use the lower layers and it's easy to replace and to add and remove layers So that's uh, there's nothing new here. That's just what we discussed earlier The trade-off is uh There's always a trade-off here We have additional overhead if we could do a direct call to the database it might be quicker Uh, so there is more there are more HTTP requests. There's more processing going on Compared to doing it directly, uh, which might take longer because each request takes time each processing takes time That's a disadvantage Okay, now we jump over the fifth one. I said I'm doing that last and we go to number six So remember this is an optional thing. You don't have to do it But it says You can send executable code back to the client code on demand And this allows the client to be extended with additional functionality So our business logic does something but on top of doing something it can also send some code to the client to the client and execute it And that's the advantage the client does not have to implement this functionality because it comes from the server already The trade-off is somewhat visibility I mean the code Is being sent to the client so the client can of course see the code can change the code and so on This might sound like a very strange constraint to you because Uh, we have been doing this all the time. So every time we had an html file then included javascript That's exactly what we did. We sent the javascript file to the client and the browser executed it So that's something we already did a lot But i'll do an example later based on html which explains all these parts Now finally, uh, we have constraint number five Which is called uniform interface. What this says is there should be a uniform way a general interface that is used by all the clients So whether you're you have a laptop or a mobile phone or another server you call exactly the same Interface in the same way and it doesn't matter where the request goes if it goes to a Small server a large server or the post office the call is exactly the same That's actually one of the key differences to to other existing styles for network systems Um, but it's again something that you're very used to so you might not be Seeing the point here directly. This one has four sub constraints, which I'll go into There is again at disadvantage and that's efficiency if you can tailor an interface specifically for a component It might just be more efficient. It's not as general. It cannot be used by everybody, but it's very Suitable for exactly that component. So for example, if you use a mobile phone to Send something to the post office. You can do an interface that is specifically designed for that If you do the same interface to work with all sorts of servers and all sorts of clients It has to be more general Which might not be as efficient Okay, let's go into the sub stuff There are four of them. The first one is about how do we identify resources? So how do they look like? What's the naming of them? Second one is called manipulation through representations, which we'll get into self descriptive messages And then the horrible acronym, which is called hyper media as the engine of application state. Hey, do us That's a tricky one. It's hard to understand The acronym is even more confusing, but I'll tell you all about it Now First one identification of resources. We already talked about that rest is all about resources. Everything is a resource And what we mean by that is typically business objects something in your business domain, whatever you are programming That exists if we're doing a mind sweeper application or a mind sweeper board Is a resource if we do the solution to the mind sweeper thing that might also be another resource In the internet, we have documents. We have images if we have For example, assume you have a logistics application So something that allows you to make orders and maybe send things then maybe we have resources like order or payment We will later on take a look at the PayPal API Which has these kind of things you can order in PayPal. You can make payments and so on So it usually depends on what kind of business are you doing? What are you implementing? Those are your resources Every resource in rest can somehow be identified. So it has a uri And this is again something you have seen on a website. Each image has a specific url There is some kind of way of addressing that image of identifying it. That's exactly what it is here In the mind sweeper case, there has to be a way to create mind sweeper boards there is Even the way actually to receive a board with a certain ID There is some kind of way to identify Each and every board And of course in PayPal is the same if you create an order you have to somehow identify to do something with it So that's the first thing. We want to be able to identify our resources Then We want to Encapsulate them. We don't want to directly interact with the data. For example, directly do database calls Instead what we do is Sending representations. So that's what I discussed when we when when we discussed what rest stands for That we only send back a certain representation of the data Instead of the actual mind sweeper board in my database, you get just get a jason representation of it And if you want to change it In the mind sweeper case, you cannot But in many other cases if you want to change the resource if you want to modify the payment in PayPal You send back jason again. You send. What do you want to change? You do not directly send back. Okay, please take this new piece of data and write it into the database Instead you tell the server how to change it Now self descriptive messages is a very important one that makes it easier to use things the idea is Every request can be understood by the server in isolation as all the information what we need For example, what kind of representation Do I want to have if I send to the server? Please give me a new mind sweeper board I might have to tell the server. I expect you to send jason back because that's what I understand When we use HTTP we for example, that's one way of doing it We typically use the verbs the different methods get post and so on to tell the user to explain How we are what we are Planning to do with the resource so for example if we do a post request We say please create a new resource if we do a get request We just say please read the current state. Please give me the thing back so Again in mind sweeper what you're doing is you do a post request So you're telling the server. Please create a new mind sweeper board and send it back to you There is another call which I have not told you about but in in my application. You can also do a get call And tell the server, please give me the board with a certain id Then there is not a new one being created But it checks in the database. Is there a board with id 5? If yes, send it back So we often use these verbs to identify what exactly we want to do. That's one way of having Messages that are very clear. They're self descriptive. You don't need to understand The api in all detail to know what it's doing and we'll be seeing that in in the paper api Last one Hey to us Forget about the acronym because it's really just a horrible weird way of of describing what's going on What it's all about is essentially whenever you return a resource for example mind sweeper board You also should send back a number of links That tell the the receiver what they can do with it So this is something I haven't done and that's something most people don't implement in their api But what I might do for instance again in the mind sweeper case if you do a post request So you basically tell the server create a new board What I should have done is Send you the the resource back so you get somehow the the board id Five And you get the actual board and so on and then additionally what I might Have sent back is something like links That says okay with this board By the way, you can also do the following you can actually do a get request so if you do get And then a url if you do get five Then you're Additionally able to read the board in the future So it's basically just a way to provide additional pointers what you can do with the resource So in this case you know that you can create one, but then you get the board back and you don't know what else you could do If I add these links, I might be able to tell you well by the way you can also get it You can also delete it. You can also do whatever so it's kind of providing additional links So that's now An overview of what the rest style is and I would expect that by now you are pretty confused of what this actually means So we'll do one example, uh, which is the most common one the one that you're most used to that's just the way Websites work, so we'll look at that because websites htdp the internet follow the rest style And then later on we'll have a look at More practical advice. We'll design a rest api ourselves so Websites htdp is the main protocol in the worldwide web And rest has been used to develop htdp as I said So that's why we see all of these constraints in typical websites So the first one is the client server constrained That's what we do all the time. We go to vikipedia and say, please give me the website the resource That tells me about URLs That's exactly what we do the browser then receives the html file. It draws it. It renders it and you can interact with it Stateless this constraint is fulfilled because htdp is stateless. So that's what we discussed in lecture two By default there is no state in htdp requests, which is for example very different if you look at the tcp protocol So the tcp protocol is sort of first initializing a session a connection to another server Then when that is done, you can send data and at some point you close the connection again That's very stateful htdp is by design stateless cashable Uh in htdp and maybe we'll just look at that if we make a request Let's go into my network view Uh if I for example go to vikipedia And I want to know about url um I've done a request and if you look at the response headers here what it says is cash control So this tells us about how can the caching be done and I won't go into the details Uh, it might go there might be a number of other things cash. That's a bit of uh details but essentially The htdp protocol has In its headers, it has a way to tell me about yes, you can cash or you cannot cash So that's built in into the protocol. Uh, so that's our third constraint um The fourth constrained layered system is also implemented in in this case When when I sent the request, I only know the target url I know that the the url is vikipedia.org slash something Uh, I don't know where this url gets the data from so most likely Behind the the vikipedia server. There's a database or a number of databases And it makes a call there and it gets the data back But I have no idea about that. I don't know where the database is And I don't know how to access it either And that's of course a great thing because if I would be able to directly access the vikipedia database, I might cause a lot of harm Now the uniform interface, uh, is again something that's in built in htdp It's just that we have urls. They are a standard way of identifying resources. So The the u in url stands for uniform and that's exactly what we want to have so the there they are somewhat, uh descriptive I know that if I put, uh If I write a url here, I know that okay, this is the server. This is the protocol And this is the path for example They are somewhat self descriptive If you know details about how the urls look like you are able to understand What it is you are calling And then finally we have the codon demand thing. Well That's as I already said We are loading one resource in this case We are loading the html file But as you see here in the network view, there is a whole lot of other stuff that is being loaded like css javascript More css and that's actually codon demand. We are downloading the server sends us Uh additional code that we are executing on the client side So that's exactly just the sixth constraint Uh, so websites are a very very common way that implement the rest style If we dive if we dive into the details of the fourth constraint, uh, we can look at at all the details So I've already said we use urls. What we actually do is we identify resources We have a unique way with the url to identify what we want to have Uh If we manipulate anything So for example, if, uh, something is changed On the database side data in the database only the representation is sent. So for example, if we uh, if we want to create a user account We do a post request and we send some kind of, uh, body Username password and on the server side something is created some user account But that's not exactly what we send over. So we just send some kind of representation the post body Uh We have somewhat self descriptive messages. So the werbs in htdp tell the server what is going to happen Is it a get request? Is it a post request and so on? uh And hate to us is actually I would say that the clearest case is html because We have in an html file. We have lots of links To other things. So of course, you know all of these things That's basically hate to us. It's telling us what else to do Where to continue from this resource? So we have we don't have to know the details of all the different resources on vikipedia That's what the links tell us. By the way, you can also read about web resources So that's hate to us, uh in the website case All right, so This has been fairly abstract So either you have been confused by it or it has been obvious. So why why do we even think about this? Or both So the question is really what do you get from rest? Uh, and Would like to go back to the the original definition The constraints we're having really give us the scalability we have in the internet So that's why the internet can grow so well The URLs help us to to navigate the internet. They really make things clear But we are very used to it independent deployment is something we don't even think about But we have all this separation in the internet that we have clients server side databases load balancers caching and we don't even see them and All of this is essentially Why the internet works so well why it scales so well? And also why it's so heterogeneous. It it does not depend on a single organization to run it or something like that And that's really the power of rest now That's why the internet works. That's all fair. We know that it works But we now get into how we build our web applications in a restful way. So Similar to the internet the internet is scalable the internet is general If we build a web application in a restful way, it means this application is most likely scalable It's fairly general. You can understand it It's easier to change. It's easier to maintain them other applications And if we do this if we build a back end that is following the rest principles Then we have a so-called restful api or a restful web service. So that's what we're going to do To do that, we'll use one of the many checklists because rest is quite abstract So if you want to build a web service, you often have these checklists like number three that tell you concretely What should you do? I only cover parts of them because I think some of them are more relevant than others Or they may be so advanced that they don't belong in this course, but rather in that web services course And what you'll see is there are a lot of checklists out there that talk about how to do rest But most of the practical advice has nothing to do with with the actual rest style So you can implement rest in a very different way We anyway, this practical advice is usually useful So we consider them sort of to be part of the best practices. So also when I Discuss in the exam or in the assignments to follow these best practices Then it means also follow the practical advice that has nothing to do with rest itself Okay, so this was the theoretical part of what rest is and what it gives us Now in the next recording we will start building or designing a restful api For a certain application and then in the last part I will just show you an example of the PayPal API Maybe another one just to show you that if you follow these rest styles You do not have it doesn't take a lot of effort to understand how web services work If you follow the best practices, the web services are sort of self-explanatory But we'll see about that later


Vice Admiral Nora Tyson was recently nominated to be the first woman to lead a numbered fleet. If confirmed, Tyson will soon lead third fleet, which covers 50 million square miles and dates back to World War II. The Naval Academy and Naval Service Training Command will use crowdsourcing to receive ideas from naval officers and chiefs regarding the future of the Navy and Marine Corps officers. This is an opportunity for senior listed and junior officers to have an impact on the Common Core curriculum for officers. The first Navy Week of 2015 begins today in Bozer City, Shreveport, Louisiana. There are 12 Navy Weeks scheduled for 2015. And finally, the Bone-Home Reshard held a change of command ceremony April 24th. Bone-Home Reshard is currently in port, making preparations for her next deployment in U.S. seventh fleet. For these stories and more, visit navy.mil.


This whole process, the thing that gets me the most is, wow, I really can't believe I'm here. It's emotional. When I said I wanted to be a hospital corpsman, I also knew I wanted to be a chief. To me, in the hospital corpsman, that's who you look up to. To be the chief, I don't think you can put that into words. It's very surreal to be in this moment. It's extremely humbling. Ever since I won this award, I've been sitting back and self-reflecting more than I ever have in my life. One of the things that all of the candidates, part of that I had spoken with, they said through the whole process, just be yourself, be yourself, be yourself. And that's exactly what I've done through this whole thing. Putting on Kaki's first time was surreal. It was a surreal experience. Being in the Navy for 17 years and working so hard and thinking one day you may put it on, but you're never quite sure. Never for one moment in my wildest dreams did I think that this is the manner in which I would get to this level. To think about it in this way that it has happened, I never in my life, if you had told me a year ago, that I was going to get selected as a specific fleet sailor of the year, and be promoted the chief petty officer in the manner that we are, I never would have believed that was possible. It's an incredible situation to be in and to be with this caliber of sailor surrounded by this other sailors of the year. It's just, I mean, it's mind blowing to see what everybody is accomplishing as first classes and why they were selected to be chiefs. It's just really great. It's very humbling to be part of this group. Everyone of us are approachable. I think that's what makes a good chief petty officer. Somebody's approachable and knowledgeable and confident in what you do. It's funny you can kind of pick us out of a crowd. Like you can see what the similarities are between all of us, but the level of enthusiasm that I am sometimes exhausting myself with, I see it in those other sailors. Be who you are and always remember that you can go nowhere without others. You have to have and embrace the people around you because without that you are not able to move forward. And I know that for a fact that I'm only here as a representation of the people that I have been able to serve with. What I'd say to my mentor or somebody that was wanting to be where I am is always be part of the team, always get qualified as fast as possible, always volunteer, be that guy they want to go to to make things happen. I think my favorite thing about the week is that it's here in D.C. and by virtue of being in D.C. we get to go to the museums. We get to go to the national monuments. We get to go to Mount Vernon to get to be here and celebrate this accomplishment with the three other sailors of the year and be doing it here where there's so much of our nation's history and our heritage right here and get to go to those spots and talk about it all together. I think that's just the greatest part of it for me. This is an experience and I will never forget. This is by far the most life-changing experience that I've ever had and I promise to the Navy that I will be the best Pacific Fleet Sailor of the year that I can be and give back. What we've seen and what we'll be able to do and the culmination where my friends and family, Matt Master Chief and C.O. are up there and put on anchors on my cacti for the first time. It'll be a surreal experience sitting in the Navy Memorial and being able to tell that story to my kids and having photos and just the overall experience with everybody at me along the way is going to be amazing. To see such an important stage in a Navy Sailor's life when they progress to the rank of Chief Petty Officer and to have my husband and my daughter, a Master Chief, Cormin Mentor of mine and Chief HMC Mentor of mine welcome me into the Chief's mess is going to be beyond words.


In this presentation, we will enter a journal entry to close out the remaining balance in the factory overhead account. This is typically something that will be done at the end of the period, at the end of the month in our case. We want to do it now because I want to keep it close to some of the other types of journal entries that we've put in for factory overhead. First, a word from our sponsor. Well, actually these are just items that we picked from the YouTube shopping affiliate program, but that's actually good for you. Because these aren't things that were just given to us from some large corporation which we don't even use in exchange for us selling them to you. These are things that we actually researched, purchased, and used ourselves. Here we have a Western Digital WD elements 20 terabyte USB 3.0 desktop external hard drive. We use as part of our backup system, noting that if you lower the number of terabytes of storage, the price will lower dramatically as well. When you're thinking about a backup system, you're usually thinking about an online system or an external hard drive system like this, or ideally some combination between the two, giving you some redundancy. You can also work directly from an external hard drive like this, but there are some drawbacks to doing that. One being, if you use this as your primary drive you're working from, it's no longer a backup drive, and you're going to need a backup system, possibly another external hard drive and or some kind of cloud backup system. And if you're working on something that takes up a lot of short term memory, a lot of RAM as you're working on it, such as video editing, the external hard drive can slow up the system. So you might want to come up with some kind of system where you download the project you're working on to your computer, to your C drive, or possibly to a solid state drive, which is a much more expensive external hard drive as you do the work. Once the work is done, then save the project to an external hard drive such as this. If you would like a commercial free experience, consider subscribing to our website at accountinginstruction.com or accountinginstruction.thinkific.com, where we have many different courses. You can purchase one at a time or have a subscription model, giving you access to all the courses, courses which are well organized, have other resources like Excel files and PDF files to download and no commercials. So the story is this, what's happening here is it's the end of the month now. We're not going to have any more jobs. We're not applying any more information or any more costs to the factory overhead. And we're not going to, we've already allocated to all the jobs that we're going to for factory overhead for this month. If we look at the GL account then for factory overhead that supports this number, we can see, you know, there's kind of a lot of activity that happens in factory overhead because it's going to be that bucket that has everything else in it that we couldn't apply to the job. So that's going to include things like indirect labor, it included things like indirect materials that included anything that we was on the factory. We put in the factory overhead. Now, our goal here was eventually to apply it to the job using some type of estimate. And we did so, we applied it out to the job, but the estimate was not exact. And again, you might ask like, why wasn't it exact? Why can't we make it exact? We see the number right here. Why didn't we apply out the 7100? And again, the problem with that is there's a few different problems. But one is that we typically would apply it out as the jobs are happening, not at the end of the month. So in this particular problem, we kind of waited till the end of the month and did this in an order so we can see the costs going into factory overhead and then us applying them out. But we in practice oftentimes will be applying them out to jobs as the jobs are going. And therefore we wouldn't even know, say that this would be the number for the entire month's worth of factory overhead. We wouldn't know that as we're applying it to the job, the things like the rent on the factory, things like utilities, depreciation, those things wouldn't be recorded till the end of the month. So all we can do is estimate what we think factory overhead will be at the end of the month. And based on that estimate use some type of ratio analysis to apply this information out to the job. And of course that's an estimate and it's not going to be exact. So we applied out 6,720 when the actual amounts, all the debits of the actual amounts added up to 7100. We applied out based on our predetermined overhead rate 1.6 of direct labor. We applied out 6,722 jobs. We have 380 that we couldn't apply out to any job. We didn't know which job to put it to. So that's going to happen every time because it's just an estimate. So now our question is what do we do with that because we want to start over next month. We would like the factory overhead to be zero next month so that we can start over and work through next month. So we've got to kind of clear this out. This is kind of like a forced temporary account here that we're going to have. And the way we're going to do that is we're going to clear it out to cost of goods sold. We're just going to force it to work. We're going to make it zero. And you might ask, well, that seems not right. Why can we do that? And the reason is one, because hopefully this is a small amount. If it's a large amount, we might have to go back and do some reallocations to it. But if it's a small amount, then we can say it's not material to decision making. If it's not material to decision making, what's the easiest thing to do with it? To record it to an income statement account because the income statement accounts will close out to retained earnings and they'll go away. They'll just be part of retained earnings after this time period. And we can kind of get rid of it in that way. And again, it's small, so it shouldn't affect net income or our decision making processes or distort our financial statements, hopefully.  Why income statement account would we choose cost of goods sold? Because ultimately, that's where it would go on the income statement if it went through the entire process. Meaning, if we were able to properly allocate it, it would go to a job. The job would then be sold. And when it was sold, it was going to go to an income statement account in the form of cost of goods sold. So this would be its ultimate destination in any case. So that's the justification for it going to cost of goods sold. So again, we got this difference. It's going to happen every time because we're using estimates. We need to get rid of it. We got to put it to an income statement account to do that because the income statement accounts will close out to retained earnings. We're going to choose cost of goods sold in order to do that because that would be the natural income statement account to choose. Also note that this amount could be a debit or credit at this point. It happens to be a debit now. But if it were a credit, we would still write it off to cost of goods sold. And that means that cost of goods sold could be... We might end up having to credit it in order to do this, which should look a little unusual. Cost of goods sold is an expense account. It usually only goes up in the debit direction. This is an exception to that rule typically because if we have to credit cost of goods sold, we'll do that anyways because we're going to do whatever we need to do to make this go to zero. It's not about cost of goods sold. Cost of goods sold is just an account we're using to clear this out. And the reason it's okay is because it's in material to decision-making processes. Okay, so that's what we're doing. So the journal entry is pretty straightforward once we know that. We're just going to say, okay, I need to make this zero. It has a debit balance in it currently. So we're going to do the opposite thing to it. We're going to credit it to make it go down. So I'm going to right-click and copy that. We're going to put that on the bottom in F5, right-click and paste 1, 2, 3. The credit's just going to be for whatever's in there. It's going to be 380. Then we're going to debit something. We've got to figure out what we're going to debit to. Negative of that number, debit 380. You could just type it in there. We're going to say, hmm, where could I put this thing? Get rid of it because I don't want it there for next mod. How about down here somewhere so then it flows out to retained earnings and we don't never have to see it again. It seems logical to put it to cost of goods sold because that's what would ultimately go anyways at some point in time. Let's do that. So cost of goods sold, expense account. We're going to right-click and copy. Again, it doesn't make sense to think about the expense account here and say, does it make sense from a cost of goods sold perspective in any other way than what we've discussed? Meaning cost of goods sold is an expense account. It only goes up with a debit direction. It doesn't mean necessarily we're going to debit this because we could be crediting cost of goods sold because again, we're doing whatever we need to do to clear out this estimate that was wrong because it's an estimate. So we're going to go back up here and put this into F4 right-click and paste 123 and that's it. So then we'll just post this out. Here's cost of goods sold, cost of goods sold is way down here. So we're going to have to scroll all the way to the right to post this to the GL. So it's going to be in the same order, assets, liabilities, equity cost of goods sold way over here. It's going to be on the debit side. So I'm going to put my cursor in AA18. We're going to use our arrows to do this. I'm going to hit equals, then use the left arrow to just keep going left, left, left, left up, up, up to get to that cost of goods sold and enter. So there's the cost of goods sold goes up to the 380. That 380 then can be found on the trial balance. Actually, the 380 there is fun on the trial balance. We're out of bounds by the 380 and net income went down by the 380. That's a loss because there's no revenue. So we actually did hit the income statement, but it's for a small amount here. And then we're going to record the other side, factory overhead to bring it to zero. That's third to last asset account. So we're going to go down here. It's right there. We need on the credit side. I'm in T 30 where we say equals. I'm going to just scroll up to the last journal entry. And there it is 380 and enter. So that brings the 380 down by 380 to zero. That zero balance is now on our factory overhead here. So that's we achieved our goal here. We did affect the income statement and affected net income for this time period, which may or may not be right. It might be wrong timing wise. It should go there anyways at some point in time. You know, it's only a timing difference hopefully because we will sell the inventory at some point, but it's off timing wise. It should be pretty small relative to our, the rest of our information when we were, and we haven't recorded the sales point, which we'll do later. So it should be small compared hopefully to the rest of the numbers. And therefore it's okay to do that because we need to make this zero so that we can start this whole process over in the next time period, the next month.


Hi everyone, I'm Sophie from Aravillaments and today I will talk about near field and far field. As you may know, antenna near field and far field are two distinct regions around an antenna where the antenna's radiation properties differ significantly. The near field can be further divided into reactive near field and radiative near field. Now let's start with the region that's interest as the most, the far field region. Also known as the radiation field or the front hofer region, it is the region far away from the antenna where the electromagnetic waves have fully developed and exhibit a simple predictable behavior. They propagate as planar waves with the electric and magnetic fields perpendicular to each other. The far field region is defined by the wavelength of the signal and the size of the antenna. Two times the square divided by lambda is then the exact formula for all uniters out there. But generally speaking, the far field region of a 30 degree hot antenna operating at 5.5 gigahertz started 2 meters and extends to infinity. For 24 dbi gained if it's 6 meters and for 20 dbi pejorated sector, this distance is over 20 meters. On the other side, closest to the antenna, we have the reactive near field region. This is a place of electromagnetic chaos. Any object inside this region cause unpredictable changes to the antennas radiation diagrams and vswr, because it becomes a part of the antenna itself. The equation is also more complex. For a 30 degree horn like mentioned before, this comes out to be only 0.3 meters from the antenna aperture. For 24 dbi gained if it's 0.7 meters and for 20 dbi pejorated sector, this extends to almost 2 meters. Maintaining a reactive near field free of obstacles is much simpler with antennas with small form factors, enabling much denser collocation. Finally, the radiative near field is the region in the middle. The EM fields have not yet consolidated into the far field structure, but anything placed in this region is far enough not to have a direct influence on the antenna's performance. If you find this video useful, give us a like or share. To learn more, don't forget to hit the subscribe button to get notifications about new topics. See you in the next video.


You very much Nathan for the introduction. My name is Jack. I am the PhD student at Soas at my work, it focuses on historical fiction in India and kind of dataset. Today the modelling-g Arnold's project that I'm a part of, Soas. I want to start off today by briefly outlining some of the details of the project, the main issue I want to discuss today is more of a conceptual one than an explicitly practical one. I think Mae'r cyffin amser yndw i'r cystafell fy gŷtledd yw'r hyffiniau yn ymwyaf i hygyrch yn ymgylchedd i'r cyfyrdd cymorthaeth sy'n mynd i fynd i argyrchu am arwain, ac mae diso'r unrhyw fawr yn ymwysig. Rydym yn fy nhw'n eu gwneud hynny.  Dedwyd i'r lleiwn am y ddigon nhw, ond â os y project arall, wedi'n blwyddyn nhw'n os y gallwch yma'r dda, ei nghylch i ddau'r projectau â'r project ac mae'n ei rydyn gyfan ydych chi'n cymryd o beraynol bydd y cythiwyd cyfligol yn bwysig, cyn yw rydyn ni'n neudio ni'n gweithio, ac mae hynny'n gweithio arno yn cymryd. Ond ydych chi'n gweithio gyda'i gydag ar gael gwasanaeth a fydd efo'r gweithio ar gael gwyn nharnedau o hypnod ddangos cyfryd ar gynnig iechyd nid yn y gweld, gan hynna powd, gan hynny'n gweithio ar arno. Mae Maith Wrngffi, Camelol, is a European Commission Horizon 2020 scheme which is often abbreviated to monosogy with the acronym there. We haven't standardised the way to say that word so say it however you like and to come to the side yet. The project brings into question the status of world literature as a discipline and the dominance of headymonic languages within it such as French, English and Spanish and German by highlighting the multilingualism of and the many factors that contribute to regional and transnational literary fields. I'll be quoting here from the project description that we have on our website and I've popped the URL just there as well so you can see it for yourself. In practice the project revolves around three sites, North India, North Africa and the Horn of Africa that we're analysing both individually and under comparative focus. This emphasis on comparison is important as to our knowledge there has been no direct link between North India, Morocco and Ethiopia in modern times. This will be a project not about contact zones or connections but rather about patterns and comparison. Unlike certain other methodologies within comparative literature for example which privilege comparison between a centre in the global north and a periphery in the global south, this is a project that really focuses on south-south or south-south comparison as this main methodology between regions that we feel have been previously under or uncompaired. The aim of the project is not to create universalising understanding of literature across the globe as the discipline of world literature often does but to make a significant intervention in or reshape the field of world literature and propose methodologies, training models and case studies that multilingual locals and multiple cinematographies are appropriate for the study of world literature. There are nine of us on the project including a project coordinator and it's led by Francesco Orsini so as who also heads the North India case study on the project. So this centrality of comparison to our work throws up a number of problems when it comes to defining and working with our research data. This is the issue that I want to really hone in on today and talk a bit more about. So there's a number of researchers that have identified this difficulty in delineating what constitutes humanities research data exactly and I've popped a few quotations that I found from presentations made in the event in 2013 at the RDMF that kind of illustrates some of these difficulties and what these researchers saw in this field. The act of comparison that undergirds our project particularly complicates this a bit further I think in the past year or so we have come across a number of problems in asserting what constitutes our research data and what we're meant to do with it either as a team or even individually. As we might get from the description provided the project the data we're using are mainly examples of literary works primarily from our three geographical and linguistic case studies but the process of dividing which or deciding which works of literature should be included for these comparisons is quite a challenge for a number of reasons. And primary amongst these is the inevitable symmetry of knowledge that comes with a group project like this. So we work on three distinct regions with at least six principal research languages and this means we have a wonderful array of resources as this slide I hope illustrates. We have translations of John Bunyan's Pilgrim's present at Oeddu from the 1870s, we have a very modern and hardy literature from Ethiopia, we have Hindi historical fiction from the 1940s and Arabic children stories from the 1920s. This is just some of the things we talked about in the last few months to try and kind of show you a picture of the languages and the genres that we're touching upon and the breadth of stuff that we're doing. But it's these kind of asymmetries in linguistic knowledge that kind of limit how we can engage with the other parts of the project obviously. So my own research focuses on Hindi and Oeddu for example within North India and I studied Arabic and French before so I have some ability to engage with the North India, sorry North Africa case study. But when it comes to the Horn of Africa case study with Oral Moti Grinia and Amharic I am woefully kind of unprepared or unable to engage these things at this point in time. So there is a real issue of kind of, as far as I might try at the moment, linguistically I can't obviously take these things on board. And so I've popped also here just kind of main research language we work in both European languages that obviously have different histories in these regions from the colonial period onwards and also the kind of local and national languages of the regions we're looking at. So as you can see it's quite a range of languages to work with a group of eight researchers basically. And the same limits I suppose also apply to contextual knowledge. So while all members of the case study have a kind of general understanding of the histories and structures of cultures in the region we're talking about there are obviously huge differences in our ability to engage in the contextual knowledge that underpins these things. So a prime example would be the colonial history of India which is a 200 year process that ends in 47 compared to colonial history of Ethiopia which was only occupied by a foreign power for five or six years in the 20th century but had other kind of contacts and interactions with colonial powers whether Italian or German or British throughout the 19th to 20th century. So these things don't correlate and in the project we're trying to bring together these languages and also these time periods in different kind of historical processes that are at play there. So we're looking not only at the pre-modern or pre-colonial work with someone that Francesca has worked on in some length beforehand but the colonial period as well and the post-colonial decolonial period as well. So it's kind of not only linguistic matrix but a kind of temporal and other contextual matrix to work with as well within that. I mean this, I'm not saying this to kind of belittle the comparative focus of the research or the research in itself and I think we have to acknowledge the practical limits of our knowledge and try and work through these together with collaboration. That's one of the main things that I really enjoy about working on this project but on the very basic level of drawing up a suitable list of comparables that can constitute our research data these limits have proved quite a big challenge to our project work and this bind is kind of further tightened by the theoretical basis that forms the kind of contextual undergirding of the project. We're looking at ideas of world literature or comparative literature that have been theorised by different people in different ways using different languages and context as well. So I'm particularly, people like David Danross who've worked on world literature as a concept for a long time but use the Epic of Gilgolmesh for example as their main kind of text to do that. We have no primary ability to engage with that data at all so there is a kind of disparity or a symmetry there that we have to deal with as well. So to head off these challenges we on the project have kind of diverted our own protocols to say to try and create productive and relevant comparisons between the case study regions. So this has primarily been a case of spending time working together to elaborate comprehensive lists of what we're calling comparables. So that is literary works that conform the basis of the comparisons between our case studies. These works are our primary research data towards the purposes. They are the things that we're going to be working from to develop our methodologies and our ideas about what we're talking about. And we've made a kind of effort not to only to lineate them by language but also by other characteristics. So genre, audience, time period, script, materials, provenance, that kind of thing. And so working within this schema allows us to navigate the linguistic barriers that I've talked a bit about just now while at the same time retaining the particularities of each work and not assuming these particularities to a kind of generalised whole as often happens when comparisons are made. And more recently we started an intense period of kind of working within our case study smaller groups. Having spent much of the last year working holistically as a whole project together. And we're using the time to debate areas of interest in our more particular geographic and linguistic regions which we can then hopefully bring to the table when we meet as a project to discuss where we can compare these things. And this flexibility of moving between the big and the small pictures helps us to delineate data that functions on the various micro levels of the case studies of the project but also on the macro level of the themes and ideas of the project more broadly. And so moving forward we hope to use these small lists of comparables to divide our research data thematically and focus our comparative approach within parameters that don't reify language as a defining feature of the literature we're working with. This is something that Karima Larsiwd who's the head of the North Africa case study on the project and Francesca Rossini as well have made a kind of central feature of one of the methodologies they're developing called reading together. So bringing literature together to read them across and between languages much more than within their linguistic silos, if you like. We've also used other more public means to try and make our research data more understandable to both those on the project and those in the kind of wider academic and reading publics. We made it because as an effort in our event planning to try and make our content as accessible to one another as possible and this is a part, an issue of balance so making sure that each of the regions receives equal billing in single events and across our events calendars more generally so as to keep each of the case studies in our minds irrespective of our own focuses and our own abilities in terms of the knowledge that we bring to the project. So we had a project in the summer, a workshop in the summer organised with the CNRS and Taillim in Paris which is the very jazzy flyer for that. We brought together scholars working on each of our three key regions and further afield and we placed them in panels that were not just defined by geography but by other thematic conceptualisations and this might sound quite basic and banal but actually it's something that is not often done with small and large events where you try and think about comparative thematics across different literatures and different concepts for example and what this produced for us was a more well rounded experience in which the patterns and comparisons that we're looking for in the project were more easily to identify and it's kind of also contrasted to an event we held in the first year of the project, a seminar, a workshop at SOAS where we were dealing with pre-modern literatures and trying to get people to talk together or with each other and also with the project and it didn't really work I think because of the way we'd set up the call for papers and that kind of thing wasn't oriented towards that and it's something that we're trying to address in our submissions going forward to make sure these things are done at the events that we can hold. And we've taken a very similar approach in building the website for our project which we're using both as a means to publicise the project and as a constructive forum for debating issues pertinent to the project so the website is structured around three key areas, readings, integrations and itineraries which you can see on the board there which we hope to populate with content that pertains both to the project regions and other geographic and linguistic locales. I suppose the website extends the basis for our comparisons and the breadth of our research data so by commissioning scholars from around the world to contribute content to the site we're able to include sources from a number of languages and cultures that are outside our immediate remit we're also using the website as a repository for educational resources such as collaboratively compiled courses that can be downloaded and used by scholars and teachers around the world so this is accessible on the website which is here. It's open access, you register on the site and then you can download and use them as you wish and our first one went online last week and it brings together Faddan LeBernie who's a post-off on the project Francesco Orsini and Nick Harrison at KCL talking about comparative colonial pedagogies between North Africa and North India so try and bring together different contexts in which colonial teaching was done but looking at how that's ffaddan literature and telling us out in a seven or eight week syllabus that can be used either in its entirety or just for its little readings every now and then and the work that we produce on the website also ticks that ever important outreach and impact box which is aided by our Facebook and our Twitter which I popped on here so if you're on those platforms please do follow or like us and you'll get to see me curating our Facebook content every day which is a fun job for me. So while these efforts have helped us delineating suitable comparables as our research data or are helping us to do that, Molossogy should probably be doing a bit more to both define and develop our research data so one element of our research data management that we are currently lacking is a fully fledged strategy for ensuring that our data are sort of be ordered and crucially reproducible in the future. This is something that has been discussed a lot over the last two days and it's really important for our project partly because we want to use these case studies and this data as a way to influence methodologies and tools that people can use in the future to do similar things even if they're not in the language groupings that we're talking about. I think this goes back to what Getham was saying about linking together data tools and making sure the whole package is there to ensure that they all work together holistically I think. So for this we need something on the lines of a research bibliography which is basically just a better method of collating and recording the data that we're using day to day whether that's reading it once and putting it aside and saying it's not worth it for the project or using it for our main analysis in my PhD for example. I talked to Nathan a few weeks ago about this and I brought attention to the project and I hope that it's going to be something we can build on going forward but as I say this is something that we haven't really thought about until now for whatever reason and I joined the project last year so this is something that we're playing catch up on a little bit we're two and a half years in now and we need to really make sure this data is accessible and reproducible going forward for obvious legal reasons as well. There are challenges to this of course and that's primarily because of the nature and typology of the sources that we're going to be using so one is the variance in the kind of material structure of the sources and the data that we're relying on so there are a number of us on the project that rely on the kind of modern format of the handy and durable book but there are others that work on manuscripts or other kind of less hardy materials that are less accessible from somewhere like the UK or from the US so ensuring that these are all properly indexed to standard criteria is a priority for us particularly because a number of us are going on field work out of this year or next year and so we need to kind of really crack the whip on and make sure we have a way of standardising these things and connected to this is a question of dissemination so as work by Christine L. Borgman has shown there's something of a conundrum in the sharing of research data beyond an individual or project group not least because of the constraints posed by copyright law in the case of more recent publications and this varies on our project some of the work is going to be 19th century or before some of it is going to be as we saw 2016 there are disparities there there are different realms of copyright that we need to work with both in the UK with in Europe and the other geographies that we're looking at so we need to find a way to provide adequate bibliographic and reference information to these resources that are subject to copyright constraints while also making as much of an effort as we can to make these as accessible as possible to people who want to reuse these things in the future and there's another kind of more technical issue there of course in terms of making sure this data is accessible in a physical sense in terms of reading and transitorating these things transitorating systems between even Arabic and Hindi we use similar characters to mean very different things so we have to find a way in which we as a project first of all and then those who might want to use the data after us are able to access this data irrespective of their ability to read exam which is either in their primary form or in a transitorated form and I mean this is also with Amharic we have a very complicated system of transiteration which is not accessible to somebody who doesn't know Amharic or particularly for example so this kind of focus on making sure that the metadata is there and accessible is something that I'm trying to really push with the project more broadly going forward so to conclude, considerations about research data from ROTG are as I hope to have shown today couched in the project search for patterns and comparisons between our three geographical and linguistic case studies it's this comparative focus that makes the process defining and working with research data a significant challenge so a symmetry is a knowledge shape how we as individuals and as a team are able to approach sources and necessitate extra efforts to ensure data are comprehensible to all on the project constructing lists of comparables and making use of public events and digital spaces allow us to mitigate some of these effects and I think kind of extend the epithemic frameworks within which the project can operate ultimately so moving forward I hope we can build something that resembles the research bibliography and make sure that it's useful for people to come who want to emulate the methods that we're going to be using at least in the future Thank you for your attention I look forward to your comments Call for Papers, if you like, for this event people will not talk about the methodology of their research but focus on data management but I found myself feeling as a listener to your talk that knowing more about methodology would help me somehow so I'll be more explicit about that clearly the novel that someone is reading is in some sense research data so there is a question of making that available but I mean it might be available in all the book shops in London but then are there conceptually at least are there discreet moments of where you create data where you create data intermediate between the novel as it exists in a book shop and publish an article or book in literary theory for instance I mean of course there are but what I'm trying to say with this is that it's not the same thing as doing a theological or archaeological work but a bit of it is tangible but you can codify and look at in a certain way what I'm trying to say with this and I appreciate why you don't want to necessarily have methodological concerns here but what I've tried to do with this presentation is say that actually at the moment the conceptual underpinnings of this project mean that determining how we I mean we talked a lot about data is existing and data is generated as I've asked a few days right so that's the question of going out fine of course and there is a difference there at a point in the project where we know what we think we want to achieve with this data but actually it's not a case of saying oh of course all these novels in Amharic, Hindi and Arabic are going to do the same thing hence why we have to take a step back from that and actually assess how we come up with this primary source or primary data in their initial thing because as you say I could go around any book shop in London and find a number of books there's also an issue of of access there and just because a book is here doesn't mean that it actually represents anything about the true culture that we're talking about so we're not at a stage to say that yet and I don't actually know this is why I include those quotes of other researchers saying this because I think there is a difference even within this humanities and social sciences umbrella there are very different methods that we use very different methods and I think a lot of the presentations I've asked a few days are focused on as I say the theological archaeological things that are not more tangible per se but have a particular methodology that I've found to them I think that there is some of that in literary criticism or literary studies more broadly but I think actually there is a difference in how we can engage with that data and then generate our own data from it that's what I've tried to bring to the fore here I don't know what form that generated data would be for us frankly because I don't know when I work on a text there are certain characteristics of it that I'll look for certain facets of the text or functions of the text that I'll use to draw an argument together those aren't always inherent to the text these are normally influenced by secondary material so finding a way to do that is really important for us because we have a hell of a lot of material on scope here so to try and paraphrase it that it's if you're doing a text critical edition or you're doing archaeology there are certain moments where there's quite naturally there's data that your method creates that's easy to file somewhere it's not as obvious that there are specific moments in the methodology that naturally produce exactly data sets but that one thing that you have observed is that one thing that makes doing literary criticism different than reading is the engagement with the secondary literature in literary criticism absolutely and that's what you're thinking about how to model or keep track of more absolutely and that's not to say that doesn't happen in the other fields we've talked about but I think there's a particular type of interaction between secondary and primary in literary studies as opposed to the fields we've talked about these also do interact but as you say I think there is a particular kind of relation that you're taking into account when you're talking about managing or generating your own data just a quick thought the the the fields that we've often been hearing for a final sales position of having to create the digital object that will act as the point that links together the image the meaning of the inscription etc but it occurs to me with modern literature of course you because they're generating the one world they come with that data already attached ISBNs and other things review platforms because review is part of the to what extent do you feed into those to what extent do you tag your data using ISBNs and things like that to link it to the object because the object has a kind of metadata digital identifier already I think in terms of reproducing the data it's exceptionally useful to use those and to make use of them I think absolutely so there's a reason why ISBNs are useful for us finding books because they can help you find something you wouldn't find others but I don't think we can rely solely on those because there's a gear towards a particular way of consuming that material a commercial or whatever a personal form we have to kind of add to that metadata that perhaps deals with thematics or questions of script or language that can also supplement these more practical access data I suppose I know that in some of the app I see on literature is very multimodal because it's also performed and that's an aspect that you haven't touched on at all so presumably you would also have audio visual data that needs to climb your image and scan the data could you talk a little bit about that so I think the emphasis of the project is primarily on written literature but I think to your point these don't exist in a vacuum obviously and so we do have to take into consideration that orature is an exceptionally important thing performance as you said is an incredibly important thing so I think in terms of the data that we're going to be collecting or generating ourselves those things won't necessarily be part of that in fact they will I think book history is one thing the presentation of these books is very important so I think you're very right to bring that up but in terms of trying to navigate this orature literature binarisation that's not always helpful I don't quite know how we would do that particularly with the more modern stuff where there are performances available to them I think this is something that I can take back to the team because actually it's if we do have performances of a Hindi play that we can find being performed then all the better do you know what I mean and there's other layers that we can add to that so thank you for that I think that's where we have to end so thank you


Welcome to Purdue FAQ's Boilermakers Respond. I'm your host, Erin Anderson. Today, we're talking about one of the most important aspects of college, finding your community. There are so many ways to find friends at Purdue, from learning communities, cultural centers, clubs, and organizations, and more. To share her experience with finding community at Purdue, we have a special guest, Ava, President of the Purdue Student Union Board. Ava, can you tell us a little bit about your experiences with PSUB and how you found community at Purdue? Of course. During my past three years here at Purdue, I've been a part of the Purdue Student Union Board, otherwise known as PSUB. It's a student organization that's over 100 years old and aims to provide campus and community with fun, free, accessible events for all. PSUB's a really great way for students to get involved, have fun, and meet new people. Between my involvement with PSUB, my academics, my time in the residence hall, and campus jobs, I've been able to find a really tight-knit community here at Purdue. That's awesome. Purdue has a number of learning communities. What are learning communities? So in a learning community, you and a group of your peers with similar interests will live in the same residence hall, take some of the same courses, and experience networking and skill building activities outside of your typical coursework. Learning communities serve as sort of a built-in group of friends that try to support each other during their time at Purdue. What kinds of learning communities can I join? So there are dozens of learning communities for students of different interests, majors, and backgrounds. We have agriculture, entrepreneurship, education, ROTC, and engineering to name a few, and you can view the full list at purdue.edu slash learning communities. Awesome. There are cultural centers too. What is a cultural center? So a cultural center is a place for students to come together, gather, learn, share, and support the different cultures and identities of our diverse student body. Cultural centers are open to all students to get involved in. What cultural centers can I find on campus? There's the Asian American and Asian Resource and Cultural Center, the Black Cultural Center, the Latino Cultural Center, the LGBTQ Center, and the Native American Educational and Cultural Center. How can I find out more? You can go to the individual cultural center's websites or visit purdue.edu slash diversity-inclusion. What are some of the other clubs and organizations that you can join at Purdue and how do you get involved? Well, Purdue has over 1,000 different student organizations and clubs, and they're all led by students. If you want to, you can view the full list at boilerlink.purdue.edu. Definitely check that out. What types of clubs and organizations can I join? Well, with so many different orgs across campus, I'm sure there's one for everyone. You can join Purdue's largest student-led organization, Purdue University Dance Marathon, or maybe you want to show off your green thumb with the Art of Bonsai Club. You can also make a difference with the Ace Campus Food Pantry. There's so many amazing options, but if you can't find a group that you like, you can always create your own. The opportunities are endless. What are some of the clubs and organizations that you're involved with? So as I previously mentioned, I am very involved with the Purdue Student Union Board and I'm currently serving as the President this year. When I came to campus in the fall of 2020, PSUB was a great opportunity for me to explore my interest in event coordination, utilize my organizational and leadership skills, while also getting involved, which is something I found really important. I think many students will credit their student organization with being something that they can find friends, grow on personal, professional and academic levels, and I'm so happy that PSUB has been able to do that for me. That's great. What are some other ways you can find your community at Purdue? I found if you have the ability to take a few elective courses that appeal to an interest or hobby you have, it's a great way to find what Purdue has to offer and simultaneously meet some people with similar interests. Additionally, Greek life is really big on campus and can be a great way to find community and intramural sports are a great low pressure way for you to meet new people, have fun and stay active. Awesome. Okay Ava, one last question. What is your advice for students that are anxious to find their community at Purdue? I think this is a really common anxiety amongst lots of incoming college students, but I think it's important to remember to be open-minded and patient as sometimes community takes a little bit of time to build and that is perfectly okay. But if students want to start exploring, they should try to go to events hosted by student organizations like PSUB or their residence hall. Overall, with over a thousand student organizations, five amazing cultural centers and an abundance of learning communities, Purdue has something for everyone. So I really encourage all students to try to figure out what's best for them. That's great advice. Thank you. Thank you for joining us today on Purdue FAQ's Boilermakers Respond and thank you to Ava for being our guests today. What other questions do you have about life at Purdue? Let us know in the comments below. Be sure to follow Purdue University for more episodes. See you next time. Boiler up.


There are crises erupting everywhere, north and south, east and west. We can just watch the world blow up, or we can face these challenges together. Together. Together. We can create a better future, the global pandemic, climate catastrophe, financial instability, inequality, sustainability, a jobs crisis, but stand up and get going. Let's develop new economic thinking. It is free of intellectual barriers, resonates with reality, and sets our global society free. It's not going to be easy. We will ask new economic questions. So, bring your perspective and your curiosity. We are going to change the conversation. Join us at our virtual interactive conference. We are the next generation of economists. Join us and let's rise to the challenge together. We need to hear from you. Click here to join now.


What's going on everyone? Sam here with late sports cards, ripping 22 penini honors photo, iMac photo, obsidian hobby and prism football hobby, six box mixer, number seven random team style. So get a look again at your random results. As always, you can find these on the website under the results tab, as well as the link in chat. So good luck guys. Let's do it. Oh shoot. Just closed out the freaking break schedule.  I like photos. I like photos.  What's it called? What? Wikipedia page open. 21 to go guys. On our baseball is back mixer, 21 to go. Check that out again. Diamond icons, definitive, flawless, NT first off the line. We've got a 2018 tribute, four boxes, 22 gilded, 2020 Bowman Chrome choice, 2018 Bowman Chrome hobby, four boxes of that, full case of 2020 HTA jumbo as well. Let's do prism first. Illegal. What happened with the, wait, so Russ brought in the new people? What was that? But I didn't, I knew Russ in Seattle, like their ties were getting like kind of cut. I know exactly why. What kind of people would Russ have brought in? Like staff, players? By staff. There's Charles Cross, Purple Ice, the 220 fun. Trayvon Walker, Drake Jackson. Yeah, Matt Patricia didn't do like that offense, any favors, you know? Matt Patricia kind of stunk. Can he pick it? He goes for it. I don't know. Boy, Moffay to the 99. Did he want, did Patricia go anywhere? Or I think of Daniels because he went to, McDaniels went, he's on the Raiders. Yeah, he's the Raiders. He was there last year. Yeah. Silver or Kyler Gordon. Blue Wave, Dak to 1.99. Skyler Thompson and a Jahan Dotson. Straight up breaking cards, breaking top loaders over there. I'm not breaking the cards. Silver, Silver, Clyde Edwards-Hallaire. Brandon Iock to 2.49. Top loaders are. Not officially on the team, but not fires. What's up, smack? Good eye, smack. Silver throwback, can he pick it? Purple Ice, Corey Davis to 220 fun. Stingley and Alante Taylor. Okay, I see you're saying. I see you're saying. I see you're saying there, Joshua. Silver to Alante Parker. There's a Harrison Smith, Harry the Hitman. Nice one there for the Vikings. That's sweet. Grats on that. Trayvon Burks and Kyvon. Who are yours here, you got left? Few. Yeah, he just looked like they just kept him round for one year. Kelsey, Kipper Cup to 2.49. Malcolm Rodriguez and Drake London. Cook. Joey Bowsett to 125 for the Chargers. Bride, Tressen Ebner. And guys, you need to get that mixer filled up. 50 box madness. Michael Carter to 149 for the Jets. Garrett Wilson, Rookie. Evan Neal. This guy. Silver, Ed Reid. We've got Otto, Kyvon, Thibodeau. Nice one there. Silver for the Giants. Grats in New York. Ikemaquanu and Isaiah Spiller. Silver, Drake London. Emergent. A.J. Terrell to 175 for the Falcons. Here's Strong Jr. and Roger McCreary. Silver, Hype, Najia Harris. Orange Wave, Evan McPherson. Nice color match for the Bengals. Logan Hall, Calvin Austin. Cameron D taking a spot. We're down to 20, guys. 22 go. Thank you, Cameron. Let's go. 20 to go on our mixer. It's going to be so much fun, dude.  I really can't. I've been so excited about baseball for the last month and I'm so like, this is like the mecca of opening baseball products right here. It's like, you really can't ask for much better. Oh, I see what you're saying. So, essentially Russ, I don't know if you saw what illegal said. Yeah. Basically, that's kind of wild. Having your own personal QB coach that comes into meetings. Oh, come into meetings, yeah. Silver, Khalil Shakir. Orange, Andre Johnson to 249. Like, if you have your own personal quarterback coach, I think that's okay. But if you have a guy that's not part of the organization going into like, organizational meetings. Yeah. Because who says that, like, a team that sheets, like, Patriots, were to call him and be like, Hey, here's a million dollars. Give us the playbook for next week. Right. Coral Patterson to 199. Brock Purdy rookie. It's up, Chance. Jack Jones. How you doing, buddy? Good to see you. Yeah, I was going to say, like, if you have your own coach that you like to work with, that's fine. But like, once he's like, involved with team stuff, then it's a bit, a bit much. Kyle Pitts, Prison Break. Got Red Wave, Isaiah Pacheco. Nice one there. Juan Brisker and Terequil. And I got two. I've got two since I've been born. I'm fair. I am more than content with being my being able to see my team win a ring twice. I'm good. Good for now. If in 40 years, we still have not won one, then I might be a little bit more upset. Prison Break, Drake London. Purple Ice, Joey Bosa to 225. Jameson Williams and David Bell. And dude, nothing was better when the Ravens won the last one, because I was in middle school. And obviously, like, everybody in my middle school or patriot fans, that is what's called, I was like the king of that middle school for like two weeks. Yeah. Being a Ravens fan, that was awesome. Then you went down to the bottom again. There's Garrett Wilson. Yeah, I didn't last that long. Alvin Kamar to 99. Zemir White and Lucine. Put it back to getting fully pure lunch money. I'm really, really pinched a nerve here on Joshua and Vaughn. Marquez Valdes, Gantling to 149. Logan Hall and Calvin Austin. What do you need on a sharefall? Yeah, wait, what did we say? We said a lot. Then you went back down to the bottom. George Pickett's immersion. Then you went back down to the bottom. Jeffrey Sibbins to 125. Romeo Dobbs and Tarantino. We need to make the I like full share for sure. Yeah, I'm going to tell Hallie that tomorrow. We definitely need that. That's funny. I would wear that just anywhere I go. That'd be great. Sure. Silver Robert Woods. There's Frank Gore. The inconvenient truth to 75 on the green scoop. Yicama Kiwanu and Isaiah Spiller.  Want to throw there. Malcolm Rodriguez. Nice one there for the Lions. Isaiah Pacheco, Devon Lloyd. Silver Clyde Everett Soler. We're Sean Gary Orange Wave, 260. Malcolm Rodriguez and Drake London Rookie. Oh, gold. Come on, baby. There's a rookie here. Looks like a picket. Gold. Cowboys. Over. Yep. Rookie is Jalen Tolbert on the variation. Nice one there. Eight of ten. Good call. And a Navy Camel Kyle Hamilton behind it. For the Ravens. Wow. Seven of 25. Jealous of that. Peanut butter and jealous of that one. Peanut butter and jealous of that one. Yep, I am. You know what? I would say I'm disappointed, but it's you, so that's true. Yeah, it should be Chris. Still got to sell out a couple of spots. Jill Mixon. Coralyn Sutton to 175. We've moved it to the end of the night to let it a couple Super Bowls were at the points. Yeah, there you go. Hey, Chris, bringing us down to 19. Thank you, Chris. Appreciate you, buddy. Or 18. We're down to 18. Floyd taking a spot too. Thank you, Floyd. 18 spots to go on our mixer. Ladies and gents. 18 to go. Thank you guys so much. Knocking us down. That is awesome. All right. Obsidian now. 22 Obsidian. Good luck, everybody. Are you going to watch basketball now? Yeah, you can go basketball. That David Tyree happened. There's Chris O'Lavet to 50, right? No, 75. Samuel Womack to 100. Montez Adams. Got to 50. Jameson Williams. Three-color patch. Nice one there. Grats on that. Lions. Jameson Williams. Got Julius Chestnut to 99. For the Titans. So you're related to the hot dog guy? Joey Chestnut? Yeah. Probably not. To 50. Michael Vick. Nice one there. Michael Vick. And guys, 18 to go on that 50 box mixer. 21 of 25. James Cook. Cook Rook. Nice one there for the Bills. Grats on that. Bufalo. Second box of Obsidian. Can we get a 50 box football break when the ball starts? Machi Sanders to 100. Probably will, honestly. Green Camakers to 50. Kyle Hamilton. Rookie. That is going to be to 100. Patrick Mahomes. Nice one there. Cutting edge. Jersey cover. 46 of 75. Charles Woodson. Very cool. Chill. If you mess with smack, you mess with me. Nice A-Rod. We've got Romeo Dobbs. Orange Auto to 75 for the Packers. Redemption. Trayvon Walker. Rookie Jersey Inc. Electric Edge Orange for the Jags. Nice one there. Jaguars. Oh, Electric, can you say? Oh, God. It's Electric. Not actually, it's just because it was a redemption. I wouldn't actually do that from an actual card. I'll still freak out a little bit, but yeah, thank you. Nice one there. Congrats again on that one. Jags. So we've got what? One box of iMac photo? I like photos. One box of iMac photos. I'm helping the cause of Sam's. I know.  It's partially your fault. Kind of your fault, too. Zappy. That's pretty fun. It's also true, Joshua. That's a very good point. You could bring up Mahomes and the Rapstar people, too. Zach Wilson. That's gross. It's a 23. Sweet, dude. I got 17 of 25. How about Calvin Austin? Look at the patch on that, dude. That's a full word on it. That's a full word patch right there, Donnie. Wow. Crazy. Whoa. That's actually really cool. Congrats on that Steelers. Nice one there. We've got clearly Immaculate. Skymore. Four of 99. We've got 10 of 10 again for the Sheeps. It's going to be Skymore. This time on a helmet. Let's see. A warning inside. There's a lot of words on this one. Standard, certified, warning inside. Look at that. Look at all the words on that one. Wait, what? You'll see when it comes up. See it on the camera? No. Excuse me. 23 of 92. Dude, that's sick. That is insane, man. That's awesome. 23 of 92. Numbers is Michael Schran. That's fire. Dude, look at this thing for the Panthers. It's an 18. Matt Corral. That's awesome, dude. Look at the Panthers patch on that. It's actually pretty funny illegal. The Panthers patch, dude. And guys, 18 to go. If you want to get into one of the best mixers you're going to have all year. That's awesome. You can make that one because that's insanity. That's genuine insanity. It's an okay, because that's a golden Corral right there. We need to hit a golden Matt Corral, dude, out of something. My life will not be complete. One box of honors photo. I don't know if we have to be honest or not. Probably at some point, I'm sure, but nobody, somebody didn't put two and two together because that would be a lot fun here. Yeah, because you were doing it the only person that would think about it. Yep. That's kind of gross. It's your boy, Donnie. I don't like gross people. I don't know what year that's from. I can't think off the top of my head. Nice. Brock Purdy. 275 for the Niners. Then we've got Purple Sam Howell. Eight of 12 for the Commanders. That's one there. Congrats Washington. We've got Redemption is Honors Rookie Signature Purple. Damian Pierce. This is really freaking cool, dude. It's gross. Not in a good way. That's one there for the Texans. And how about on a pie bag, blue one of one Eli Manning. 2013 Prism, dude. That's cool. That's freaking awesome on the color match, too. Congrats Giants. Who's picking that one up? Giants are going to be Jeffrey R. Congrats Jeffrey. Nice hit for your G-Men. That is very cool. Let's do a quick recap here. It's going to be a Skymore. Skymore. Calvin Austin, awesome patch. It's going to be Charles Woodson, Patrick Mahomes, Jameson Williams, Michael Strahan, Trayvon Walker, Julius Chestnut, Romeo Dobbs, James Cook, Michael Vick, Malcolm Rodriguez, Frank Gore, Kavon Tibido, Harrison Smith. We've got a Eli Manning on the pie bag, one of one on a 2013 Prism, blue pulsar. Damian Pierce, Honors Rookie Signature Purple, and Matt Corral, 17 of 18 on the really awesome patch for the Panthers. That'll do it for the break, guys. Thanks again for the fill. Next up, we've got 10 bucks Tuesday.