Thank you all for coming to my project briefing. So I'm Jason Bankson. I'm the Assistant Director IT for K-State Libraries. That's Kansas State University. And so today I'm going to be talking about a collaborative project that we're working on at the library with the Miriana Kistler Beach Museum of Art. And it's, I think, sort of an interesting project. Really what they need to do is replace an application that they currently have which displays their artworks digitally in their website, which is nothing new, right? Most art museums have this in some form or another. Some of them use an actual web application. Some of them just have like Drupal or WordPress templates with varying levels of functionality. Now I should mention before I get started that a big part of this process was my boss, Roberta Johnson. She was going to present with me. Unfortunately, she was unable to make it, as was my boss's boss, Dean Getch. So it's too bad a lot of people know those two because they're regulars at this conference. But so they were also a big part of this, a big part of this process. So we'll see if I can use this clicker without making a fool of myself. I'm pretty good at that, making a fool of myself. We'll try. So this was the essential problem that we were trying to solve. So they have a web application right now to display images, but it had really fallen below expectations on a number of levels. On one level was pure aesthetics. I'm going to show you a couple of screenshots of what this looks like. But it's not a very modern looking application. The way it's presented essentially it's just being packed into the Chrome that already exists for their website, which is just sitting inside the content management system for the university. So it's not that good looking of an application, which is very important obviously for artwork when you're trying to get across that sense of aesthetics. But even more importantly, the application was not very reliable. And they actually had a long-term outage. It was to the tune of about three months where the provider that they paid a lot of money to that hosted the application for them was not able to get that application back up and running within that window. And that looks pretty bad. And it looks especially bad for something like this because the money for this application had come from a very generous donation from the Weary Family Foundation. The Weary Family, they're a group that has given a lot of money to the Museum of Art. They funded this project that I'm about to talk to you about here, that I am talking to you about here. And you really don't want to go back to the Weary Family and say, we've been spending your money on this application and yeah, it wasn't working for like three months. That's just not good. Basic functionality as well, and that speaks to that reliability. As we kind of examined their existing application in IT, we found that the search wasn't working very well, filters weren't working very well. So there was a lot of functionality shortfalls. So I'll show you a couple of screenshots here, the current application. This is the search interface. You can see it's just very plain, very old school looking, frankly some of this looks like something that you might have seen several years ago from the search application, crammed into the website Chrome here. This is an example of search results, and then this is an item level. So I mean, it's fine. It's not terrible, but it's just not very visually exciting, and it doesn't do a whole lot to really accentuate the artwork, that kind of thing, and it doesn't provide a lot of other features and options. So we had essentially two approaches that we looked at for this. One was to use an existing application of some kind, preferably an open source application. Now we talked to Beach Museum about D-Space, so we use D-Space for institutional repository. We branded it as K-Rex, and for some reason nobody is using like a T-Rex mascot for that. I have no idea why. Purple frickin' T-Rex would be perfect. Everybody's listening to me about this. We talked to them about possibly creating their own silo within K-Rex, and it wasn't a lot of interest there. We talked about spinning up another D-Space instance, but really it was really overkill for what they wanted. Essentially the application that they have exists in two pieces. They have a back-end database for inventory, holds all their images, all their metadata. You're not looking to get rid of that, at least not yet. That is currently meeting their needs. In fact, it exceeds their needs. But what needed to be replaced was the web client, which was taking regular ingress of data from this back-end database and porting that out to the website. That was the problem. And so replacing that piece with D-Space was just overkill. They also mentioned Omica. Now we had put up an Omica instance for something with the English department back in the days of your, before I came to the library, which is about two years ago. I haven't worked much with Omica myself, but I'll be honest with you, most folks that I know that have used Omica for various things, it's okay, but they're usually not that thrilled with it. Then we talked about creating something new. And I like that option a lot. Part of that's because I build stuff. That's a big part of what I've always done in libraries. But there are some other advantages to that option. We'll talk more about that in a second. One of the biggest benefits of this entire project was just the collaboration involved. We had a very limited relationship with Beach Museum before this project began, mainly because we had no reason to have more of a relationship with Beach Museum. So this allowed us to create this collaboration, this synergy, and then build on top of it. And we're already talking about and have actually moved forward on some other collaborative projects that have come as a direct result of building on this collaboration. We're able to leverage our different strengths. We have these complementary strengths between our two organizations. Beach Museum, obviously, they understand art and aesthetics. They understand their own collections, the history of art. I don't know anything about that stuff.  But I do know how to build applications. I'm like really good at that. But I have folks who work for me that are also super good at that. I have a great developer team, a Noach, San Giovanni, Marjorie, great developers. I have a fantastic systems team full of people who are able to build the back end for something like this, build it effectively, maintain it, keep it up to date and patched. Fantastic folks. And so by leveraging those strengths together, we can do something amazing. We're creating new momentum for other external partnerships, right? We build a collaboration here that shows other departments on campus and other groups outside of campus. We're open for business. We're thrilled to collaborate with folks. And this also creates a proof of concept for a very different kind of external funding model than what I'm used to. So for a project like this, it's not like I've done a ton of this, but I've had some success in getting grant money and being part of grant applications for other projects. That's what I'm used to for something like that. You have to grant money for it if you need external funding. This is a very different model. We got money from Beach Museum to build this application, but it came from the Weary Family Foundation. Going after donors, going after donations and stuff like that, special collections, those guys have some expertise there. I know nothing about that stuff, but I know a lot more about it now than what I did. And this creates a template for IT in the library, for technology to push forward technology initiatives based on that funding model, which at least for us was a very different kind of approach. And there are a variety of benefits to building a new application instead of using something else. Potential broad use case. So Roberta, my boss, she did a lot of work writing up a memorandum of understanding between us and Beach Museum. And one of the stipulations in there is that we own the code. That gives us the opportunity to reuse this code for whatever we want. And there are a lot of use cases where we may want to put up our own virtual exhibition or something like that using this application. For a revenue stream. This is an interesting one. It's a big one, but it's a tricky one. This is something I talked about from the beginning with administration at the library. We're going to do the library thing with this when it's finished. We're going to push the code out as open source. If other folks want to use it, fantastic. But not everybody's going to be able to. There are a lot of libraries and institutions that do not have the technical back end to stand up a server and install all the dependencies. Set this up. Maintain it. Put all the data into the application. We've got that expertise. We've built that expertise as we've built the app. Now right now a lot of our back end is in Amazon web services. So we spin up another AWS instance. We spin up a box for this. Install the dependencies. Set up the back end. Install the app. Move somebody's data there for them. Maintain it. We come up with version 2.0 of the app. We update it for them. We create a licensed, hosted model with a yearly subscription. That's not a ton of money. And I'm not saying that that is going to happen. It may be that nobody's interested in this thing. But it may be that other institutions are. So if we can come up with our own revenue stream, we're the library. It's not like we're at the top of the food chain for the budget at the university. So if we can come up with our own independent revenue streams, we even have a possibility of that. That's a powerful incentive, a powerful tool. And one that I think other libraries should look at and consider. Salary support from Beach Museum for the project. So it was hard for this to be a lose for us, right? They're providing salary support to develop the application. And enhanced visibility for the library. This is another big one. This is one that gets talked about a lot. But let's be honest, I don't know that it's fully appreciated for what it is. I heard an argument yesterday in one of the sessions about creating a cultural expectation for a certain budget line in the library and using that as a tool to get that budget money from the university. Good luck. Good luck with that whole thing. Because the university doesn't care about the cultural expectations of the library. That is not a viable strategy for getting budgetary funds from the university, at least any university that I've worked at. And I've worked at a few now. I'll tell you what is a great strategy though, because K-States worried about this, they want those students, because right now we rely desperately on that tuition money, because we're not getting it from the state. So if we can raise the visibility of the university and make it someplace that more students want to come to, that more of our talented faculty want to come to, if we can attract other projects and other interests, that changes the paradigm. So when you improve the visibility of the library and show it as an organization that's working on cutting edge stuff, doing cool things, that attracts investment. And it also attracts attention from the institution and to the institution. And that has a visceral value. And if you can demonstrate that value, that's a budget argument you can make. So challenges, obviously we're going to have some challenges along the way. Difficulties in hiring temporary developers. So the idea initially was to hire one freelance developer to build this appliance. Basically they were going to work full time. Based on the salaries that we pay developers, largely we're looking at folks that are on visas. And that's a very difficult, everybody in this room knows right now, it's getting more and more difficult to hire folks that are on an H1B, even for universities. It's even tougher in Kansas because we do not participate in the E-Verify system. So there are whole categories of H1B that we can't even hire for. And in fact, we had somebody basically hired for this position and we had to turn them away at the last minute because they had some kind of stipulation, I believe it was a STEM extension on their H1B visa that required E-Verify for us to go ahead and make the hire on or follow through with and we did not have the capacity to do that because the state of Kansas refuses to participate in E-Verify. So that created some problems. So Roberta, being the awesome Roberta that she is, retooled this into two graduate student developer positions and we hired two remarkable young people, Nathan and Pujita who are graduate students with our computer science program at K-State and they have been doing terrific work for us. But it took a while. It took a lot of finagling to get to that point. And cultural differences and app development between the museum and the library. And even at the library, so I've been there about two years and one of the things that I've done is create more of a versioning process. Right? So we have prototypes, alphas, betas, etc. Getting across that we need concrete specs from stakeholders within the library. That's been a process. Folks at the museum don't do any application development. So it's also been a process with those guys. But we're getting there and some of these are just cultural differences but as a result of that so we have a working prototype for the application now but due to some feedback we're getting at this point we're actually going back to prototype and building a new prototype. So this new design, this new application we've built has a lot of key differences from the old application and for most applications that people are used to. I love playing with new technologies and using cool new stuff and building a new utility. And that's especially important when you're going after grant funding. Right? If you're coming in with an application to do the same thing that the previous 100 people applied for, who cares? Same way if you're going to publish a paper. Right? You need your work to stand out. So we're actually for the data layer we're using for the database use in the academy. Most people are familiar with relational databases like MySQL, Postgre, SQL Server and of course those are great. Relational databases are terrific. They do what they do really well. That's why people use them so much. But they're not all that good at dealing with flexible situations. They're not that good at dynamic changes to attributes in objects and fields and dynamic changes to relationships between tables and stuff like that. What document database is document databases instead of operating on the basis of tables or more accurately relations which is where relational databases get their name from they're populated with documents. In the case of CouchDB, JSON documents, you guys are all familiar with the JSON data storage and transfer language JavaScript object notation. It's a very simple language. You can put all kinds of attributes in a document and it allows us to have an extremely flexible data model for this application. We have one database that has artists and works and collections and various other types crammed in there. We're getting a lot of dirty data from the back-end database that we're transferring data in from. A lot of nulls, a lot of stuff like that. Not a problem. That does not break this kind of database or cause significant problems with this type of database. It's very robust, very flexible. The new application is designed to be visually appealing. It's more so than a bare-bones application that I showed you earlier. It's still designed to accentuate the art, but it's designed to be much more modern in its appearance and leverages more modern JavaScript libraries and presentation layer functionality. It also comes with a few unique features. I'll show you some of that. I like the museum stroll, which I think is kind of cool. As you sort of stroll through your own personal exhibit that you create. As I mentioned, we're currently working on a second prototype for this thing. I'll show you some screenshots here of our current prototype. The second prototype is in a huge sea change. Mostly it's presentation layer stuff, but there are a few minor structural changes that I thought were significant enough for us to go back to prototype instead of saying this was a prototype to Alpha. This is an example of a browse at the collection level. The new prototype will get rid of some of the framing and have a more open look to it, but you can see it's really designed to accentuate even these thumbnails of the art here. It's a more modern sort of open look than what you got from the previous application. These menus up here are actually drop-down menus, on hover drop-down menus, so if you ask for accessibility purposes, I did some JavaScript magic in there so that you can tab through those on hover drop-down menus. I love on hover drop-down menus for the aesthetics, but they create accessibility issues. This is the search interface here. You can see it's a much more modern look. All of this is designed to scale responsibly down to mobile devices as well. You have interface, basic search, advanced search. Instead of everything being input boxes, you've got sliders, drop-downs that are pulling dynamically from the database to get your list of selections, that kind of thing. Just more contemporary. Here we have a look at the object level and in the new prototype, some of this is going to go away. We're going to get rid of this now, but you'll notice that, again, you have a larger image, the whole thing is really designed to draw attention to and accentuate the image. Also, you'll notice these two buttons underneath the image here. And so those buttons are so that you can take individual images and add them to your personal collection in the application or remove them from your personal collection. And the personal collection allows you to do stuff like this. You can stroll through the museum. I've got some CSS awesomage here that's creating the lighting effect behind the image. And you can scroll through this. You can set this on an automated time delay as well. So it'll move between images everything from like ten seconds up to, I think I've got, like a couple of minutes on the upper end for the time delays that you can select. And all that's selected and you can also change what the background looks like, for instance, on this and that sort of thing. You can also set this up in museum view, which there we go. Museum view basically puts this on your whole screen. You hit escape to get your settings back.  So you create an exhibition like this, put it up on a big monitor and set it on auto-stroll. And it will just move through these images for you. You set the background you want and it's just kind of a nice kind of a nice feature and capability for that. I don't know about you guys, but our special collections folks they've got lots of digital applications and things like this quite a bit. And this is just a handy way to set something like that up through this application. That's my big song and dance. Time for stump to chump.


Hi, my name is Arusha Gupta. I work for ST Microelectronics as a field applications engineer under audio. I'm based in the Livonia office. Here we have the power amplifier demo, which has two of our parts, the FDA 901 and the 903. These are only two of our power amplifiers out of our vast majority. I wanted to talk about the things that differentiate us from our competitors. We have the feedback after filter, which guarantees accurate characteristics across the load, such as current readings and voltage readings. We also have a great variety of diagnostics. This includes short to VCC in ground, open load detection, offset on the input and the output to ensure that we are getting a correct signal from the microcontroller, and current sensing and digital impedance meter. The last two I would like to talk about some more. These two diagnostics tell you exactly what is going on with the speaker. As the speaker starts to deteriorate over time, it will change in resistance or impedance. It will change in impedance, and the part will be able to monitor this change. After a couple of years, if you've ever noticed that your speaker will start to sound tinny, the customer can actually take this data and implement a solution which will make the really old, let's say three, four, ten-year-old speaker sound brand new, high definition. I would actually like to show that on our power amplifier demo. So these speakers right here are paper speakers. Speakers are made out of paper, Kevlar, fiberglass, wood, those are also high end speakers. So with the speakers that we have in our power amplifier, we can make our system sound like a high definition system. For more information, please go to ST.com or you can contact your sales representative. Thank you. Have a good day.


Hello, everybody. Andrea Mayeski here with Dental L Mobile Hygiene. How does mobile hygiene actually work? So I have had my own practice for about 2 1⁄2 years now, my own mobile hygiene practice. I do also see patients in my own home for those who do not necessarily want them coming to their home. I've been in the dental profession for 16 years, so I have been doing this for a while. And people do ask me, so how does mobile dental work? So you come into my home, do you have everything you need? So basically how it works is exactly that. I come into your home with everything that I need to clean your teeth. So I do have a fold-out patient chair for you to lie in that's very comfortable if I do say so myself. I have a stool for me to sit. I have my own dental hygiene instruments. I have a cart that I wheel everything in so everything's locked up, protected. I have my disinfectants, trays, toothbrushes, materials, everything. I have a little table that I set up, basically everything. So I set up my own little dental office in your home for that hour while I clean your teeth. I see kids, seniors, I see adults. I see mom, dad, kids all at the same time so I can see all of you. And I do follow all of the COVID protocols. So that's another common question is how does that work with COVID protocols? You've probably all heard the COVID protocols in a dental office. If you have to go anywhere, there are certain protocols, right? So the new thing with the pandemic, well, not the new thing, it's been a while now unfortunately, but now I do send a COVID pre-screening form to you to fill out the day before. I will take your temperature as well when I get to the appointment or to your house. And I do wear the full PPE. So you will see me. I do ask that I use a washroom in your home to get changed in. So I will wear my hair cap, my safety glasses. I do have a mask on at all times. So this is probably the only time you guys will see me fully because I don't have a mask and everything on. And I wear a gown as well. So I'm protected, you're protected, everybody is fully protected. For kids, if you're wondering, I do the same thing. Kids actually love it. So I come in looking fairly normal. I do have a mask on the entire time, but then I talk to the kids about a really cool costume that I'm going to put on. And I kind of look like I'm from outer space. Kids love that. I don't look that bad, but kids seem to love that. So I let them know that I'm going to put on a super cool hair cap. I put on my costume, which is the gown, my pretty funny looking safety glasses, which has a light attached to it. So that's why I do love those. And they love it. I've never had any child be nervous, scared. They love it. They love it that I can come into their home. For kids, adults, anybody, and kids especially, they do feel a lot more comfortable in me coming into your home, into their space. I have toys for them. I have a stuffed animal for them and that they can use a toothbrush to brush his teeth. So I do make it a lot of fun for kids.  It's a lot less nerve wracking, I promise. At least that's what people tell me. So please let me know if you have any questions, send me a message anytime. If you want to book an appointment, just send me a message and I will get right back to you. Thank you guys so much for watching. Again, let me know if you have any questions and I hope to see you very, very soon.


This is Wei Wenchao. Welcome to Discharge and Remedies for Breach of Contract, Module 3C, Part C. We will now start examining the different types of remedies for a breach of contract. So what that is, what a remedy is, where an innocent party sues for a breach of contract, a remedy is what a court will provide as redress for that breach of contract. So there are different types of remedies that a court may order. The first one that's on this list in the table of contents here is a discharge by breach of condition. So we've already examined that when we were talking about the different types of discharge, so we won't repeat that again here. So we'll jump to looking at damages and there are a number of different types of damages. The first and most common type of damages is called expectation damages. Here is a list of the different types of remedies that a court may award for a breach of contract. First is a discharge due to a breach of condition. Second is some kind of damages. Third is specific performance and fourth is injunction. As I mentioned before in the previous slide, we won't repeat again the explanation of a discharge due to a breach of condition. But in this particular part, we will focus on damages or more specifically expectation damages. When a court orders damages, what it's doing is it's ordering the breaching party, the party who breached the contract, to pay some amount of money to the innocent party to compensate for that breach of contract. How those damages are determined will vary depending on the specific type of damages that are being awarded. This is a chart that summarizes a number of different kinds of damages. I won't go through this chart, but I did highlight in red the types of damages that we will examine. So those are expectation damages, nominal damages, liquidated damages and punitive damages. With expectation damages, we're compensating the innocent party to put that innocent party or the plaintiff in the same financial position as if the contract had been properly performed. So the mathematical equation is expectation damages equals expected benefits minus the expected cost. So the expected benefits are the benefits that would have been received if the contract had been performed and the expected costs are the costs that the innocent party would have incurred if the contract had been properly performed. To get a better understanding of expectation damages, let's now look at this quick quiz question. Please pause this video for a few moments so that you may have a look at the question and to try to figure out what you think is the answer. The answer here is B, 20,000. So we get to 20,000 by calculating the expected damages being equal to the expected benefit. The expected benefit that Armand expected to receive if the contract had been performed would have been $100,000. He would have received $100,000 from Melanie. So that expected benefit is, we minus from that expected benefit, the expected costs of Armand. His expected cost is $80,000. The widget cost him $80,000. So it's $100,000 minus $80,000, which gives us the $20,000. We've already pointed out that expectation damages is to put a plaintiff or innocent party in the same financial position as if the contract had been properly performed.  So all of that seems to emphasize that we compensate for monetary losses or dollar losses. But how do we deal with intangible losses, especially emotional distress that arises from a breach of contract? The legal problem is that intangible losses have no apparent economic value. So things such as disappointment, anger, frustration, and sadness, we can't put an economic value or it's very difficult to put an economic value to those types of losses. So the courts in Canada have traditionally denied granting or ordering damages for emotional distress. Now there is an exception to that rule. If peace of mind was an expected contractual benefit, then emotional distress is treated in the same manner as other types of losses, especially monetary losses. So in those types of situations, a court will order damages for emotional distress. So typically a contract where an expected contractual benefit is peace of mind would be contracts such as an insurance contract for disability insurance or life insurance where a consumer is purchasing or entering into that insurance contract for the purpose of getting peace of mind. There is the Supreme Court of Canada case, Fidler and Sunlife Assurance, where aggravated damages for mental distress that the plaintiff suffered as a result of the insurance company's refusal to pay disability benefits were ordered or were allowed by the court. Now just because an amount is determined to be needed to put an innocent party back in the same financial position that it expected to be and if the contract had been properly performed, that is not enough for a court to grant that amount as damages. A court will also look or apply two legal tests or two legal doctrines to limit the amount of expectation damages that a plaintiff would be entitled to. Those doctrines are called the Doctrine of Remoteness and the Doctrine of Mitigation. The case which sets out the principles for the Doctrine of Remoteness is the English Court of Appeal case called Victoria Laundrie and Newton Industry. The facts of this case are that the manufacturer Newton Industries had a contract to deliver a new boiler to Victoria Laundrie. However, Newton delivered that boiler 20 weeks late and Victoria Laundrie sued Newton for its losses that suffered that were caused by that 20-week delay. So Victoria Laundrie claimed a loss of ordinary business income of 16 pounds per week. So these losses arose from their ordinary laundry operations. They also claimed a loss of 262 pounds per week because they lost the opportunity to get a lucrative government contract because they didn't have this boiler. The legal issue in this case is what losses are Victoria Laundrie entitled to be compensated for. The legal principles that the court applied here is that first the defendant is liable for losses caused by a breach of contract that are not too remote. So what does that mean, not too remote? A loss is not remote if either the defendant actually knew that the loss might occur on a breach of contract. So we look at the actual knowledge of the defendant or a reasonable person would have expected or foreseen that the loss may result from the breach of contract. So we apply this reasonable person test or reasonable foreseeability test at the time the contract was created. So when the court applied those legal principles, applied the law to the facts. So what conclusions did they come to? They said that the loss of the ordinary laundry business income, that's the 16 pounds per week, was reasonably expectable even if the manufacturer was not told about it. So that 16 pounds per week Victoria Laundrie will be compensated for. The other conclusion was that the loss of the government contract was not reasonably expectable since it was highly unusual. So it wasn't often or wasn't on a regular basis that Victoria Laundrie had an opportunity to get a government contract from that. So it wasn't reasonably expectable that they would have that loss arising from the breach of contract. So the court ordered Newton compensate Victoria Laundrie for the 16 pounds per week losses but not for the 262 pound per week losses arising from the loss of that government contract. The other legal doctrine that limits expectation damages is the doctrine of mitigation. Under that doctrine the plaintiff for the innocent party has a duty to take reasonable steps to minimize their losses. If they fail to mitigate their losses then their damages that they are entitled to will be reduced to the extent the losses were not reasonably avoided. Back to Drew and Justin. So two weeks before the birthday Justin tells Drew that he will not be showing up at our party. Heartbroken, Drew cancels the party. Drew sues Justin claiming the following expectation damages. Loss of deposits for the banquet hall and the caterer, which is $10,000. Loss of gifts from her friends and family attending the party which is estimated to be about $100,000. Loss of future income. So this incident caused Drew to fall into a depression which caused her to quit school which led to the loss of her promising career as an accountant. So she estimates the loss of that future income to be about $1 million. So would a court award her these damages? Let's now look at each of those three damages that Drew is claiming and apply the three different legal tests that are applicable. The first, if you look along the left-hand column, the first legal test is does those damages put Drew in the same financial position as if the contract was performed? The second test is remoteness. Now, did the defendant know about the potential loss or the defendant being Justin in this case? Or was the loss reasonably expected or foreseeable from the breach of contract? And the third is mitigation. Did the plaintiff, Drew, take reasonable steps to minimize her losses? So let's look first at the loss of the deposits worth $10,000. So by paying her damages of $10,000, then Drew would be put in the same financial position as if the contract was performed. Drew would not have lost the deposits if Justin had performed as required by the contract. The second legal test of remoteness. It is probably reasonably expected or foreseeable that Justin's failure to perform could cause the cancellation of the party and thus the loss of those deposits. So the test of remoteness is probably satisfied. The last legal test of mitigation. Drew could have taken reasonable steps to avoid losing the deposits by trying to find another performer for the party. If she had done that, that could have reduced or eliminated her claim for the loss of the deposits. Let's now look at the loss of the gifts worth an estimated $100,000. So would giving her the $100,000 as damages put her in the same financial position? Probably not. So although she didn't get the gifts because she canceled the party, Drew also didn't have to pay Justin and any other costs associated with the party. Remember expectation damages equals expectation expected benefits minus expected costs. So even though she would have had the benefit of $100,000 worth of gifts, she would have also incurred other costs that would have more than offset that $100,000 of gifts. The second test of remoteness is not applicable. If you don't pass the first test of the damages putting her in the same financial position as if the contract was performed, we don't have to look at the test for remoteness or the test for mitigation. Let's now look at the claim for the loss of the future career income. So would that put her in the same financial position as if the contract was performed? And the answer would be yes. If Justin had performed, Drew would not have become depressed and she would not have lost her accounting career and then she would not have lost that estimated income of $1 million. How about remoteness? That claim is probably too remote. It's probably not reasonably foreseeable that Justin's no show at the party would cause Drew to lose her potential accounting career. So because it's not reasonably foreseeable, this denies her full claim for the loss of income as being too remote. So we don't even need to look at the doctrine of mitigation. But for the sake of interest, let's have a look at it anyway. So let's apply mitigation to that claim. So even if it was reasonably foreseeable, Drew must take reasonable steps to treat her depression and to try to have a productive career. This could reduce or eliminate her claim for the loss of future income. So she can't just do nothing about her loss of career or about her depression. She still has to seek treatment and try to have some sort of productive career if she's either as an accountant or as anything else. So her loss would be somewhat less than $1 million.


from Stanford University in Palo Alto, California. It's theCUBE. Covering Women in Data Science Conference 2018. Brought to you by Stanford. Welcome back to theCUBE. Our continuing coverage of Women in Data Science 2018 continues. I'm Lisa Martin, life from Stanford University and very excited to be joined by our co-founder, co-CEO of SiliconANGLE Media and theCUBE, John Ferrier. What an amazing event, a third annual WIZ event, a third time theCUBE has been here. This event, the energy, the moment and the excitement, you can feel it. I really want to interview with you all day, but I wanted to make sure that we had the right women in tech, women in data science. You're an amazing host, I thought it was awesome. What a great powerhouse of women and, you know, it's just such an honor for the CUBE team and SiliconANGLE to be here. We're listed as a global innovative sponsor on there, so it's like the recognition is because they have high integrity. The organizers, Judy, Karen, and Margo, when we first met, when they first started, can you bring theCUBE, of course we will, and because we knew the network effect was big here. They were early on and they took a great approach. They really nailed the positioning of the event. You, Stanford University as a base, established a global community which they have now done. It is so successful. This is the future of events, in my opinion. The way they do it, the way they bring in the content curation here at Stanford, but it's open, it's inclusive.  They've created a VIP network of power women and it's a shortcut to trust. This is the trusted network of women in data science. It's super exciting. I'm so proud to be part of it in a small way. They get all the credit, but just capturing all the data. The interviews are great data. You've done a great job. The conversations were amazing. The hallway conversations were great. It was just fantastic. Yeah, it was fantastic. And thank you for handing the keys to theCUBE to me for this event. The remarkable thing, one of the remarkable things to me about this event is they have, in third year, they're going to reach 100,000 people with this event. There were 177 regional events in the last 24 hours. Hashtag WIDS 2018 in 53 countries. And we were fortunate to have Margo Garrison on a few hours ago and I said, you must be pleasantly shocked at this massive trajectory. But where do you go from here? Sustaining, maintaining, but also reaching out, she said, to even younger audiences in high schools and being able to kind of ignite the bunts and burn it up a little bit higher. What were some of the hallway conversations that you had? Well, I think the big thing was is that, first of all, the panels and the conversation of the content was not about women. It was about data science that happened to be women. So the quality of the conversations, if you close your eyes, you're like, there are some serious pros on here. And they had some side discussions around how to be a woman in tech and data science and how to use your integrity and reputation. But the content program was top shelf. I mean, it was fantastic. So that was equalizing. The hallway conversations were as global. I heard about global impact. I heard that the data science is very mission driven and you're seeing a confluence of technology and innovation with technology like data analytics, data science, fueling mission driven. So standard run your business on analytics, but now run society on analytics. So you're seeing a global framework developing around mission driven. You'll hear the word impact a lot. And it was not just speeds and fees, data science. Oh, there are plenty to geek out about, but it was more of a higher level order bit around mission and society. So this is right in line with what we're seeing at theCUBE around cloud computing, cryptocurrency and blockchain. That you're seeing a democracy being rewritten with technology. Data is the new oil. Oil is powering the new global economy. You're seeing that in all kinds of decentralized forms of blockchain and cryptocurrency. You're seeing it with businesses transforming with data science. So with that comes a lot of responsibility. So ethics conversation in the hallway.  It was like really exciting. And they had keynotes of which we had a few on some tech tracks and a career panel. Did you get to listen to the career panel? The career panel was interesting. And I'd love to get your thoughts on some of your interviews if they cross over because it was really more about being proud and high integrity. So the word democratization came up and the conversations in the audience when they had the Q and A was, isn't it more about respect democratization? Not to say anything wrong with that, but it's about integrity. What is the integrity of us as a community as women in data science? What is the respect, integrity and mission of the role? Of course, democratization is a side effect of good news data. So that was super exciting. And then also stand up, never give up. Never, never, never worry about the failure. Never worry about, you know, any getting a blocker or move that blocker as Theresa Carlson and Amazon would say. So it was definitely the woman vibe of, listen, don't take things lying down, have a tough skin, take names and kick butt, but be proud. That's where a lot of the, when I'd ask some of our guests, what advice would you give your younger self? And a lot of them said the same thing of, don't be afraid to get out of your comfort zone. My mentor says, get comfortably uncomfortable. I think that's pretty hard for a lot. If I look back at myself 20 years ago, I wouldn't have been able to do that. It took a mentor, and just as Maria Clave has said on theCUBE before, the best time to reach and inspire the next generation of females to go into STEM is first semester university. That's exactly what happened for me, and I didn't plan it, but it took someone to kind of go, you know, like Maria said this morning, don't be focused on the things you think are not good at. So that failure is not a bad F word. Was a theme that we heard a number of times today, and I think incredibly important. And the tweets, I tweeted it out, but it was kind of said differently. I don't know the exact tweet, but I kind of paraphrase it by saying, Maria from Harvey Mudd said, look at this plenty of opportunities in data science, go there.  Another venue being a growth market. So the message here was there's plenty of opportunities in data science than just data analytics. There's math career paths, there's cryptocurrency, there's blockchain, there's all kinds of different elements. Go where the growth is. So if you go where the growth is, you can pioneer and find like-minded individuals. That was a great message I thought for women because you're going to find men in those markets that love collaborating with anyone who's smart. And since everyone here is smart, they're saying just go where the growth is. Don't try to go to a stagnant pond where all the dogma and the structural stuff is, it's going to take too long to change. That's my take, but I think that's kind of the message I thought was really, really powerful. And that's the message I'm going to tell my two daughters is look at, stand tall and go after the new territory. You can do anything. And that was also a theme of don't be afraid to take risks. In any way of life, if we don't take risks, we risk losing out on something. That was something that we heard a lot. I'll ask you a question then, because you did the interview, I was jealous.  I know you. And I love this event because it's super awesome. What were some of the highlights for you? Was there a notable interview? Was there some sound bites? What were some of the things that you found were inspiring, informational or notable? Oh, all of the above, everybody. I love talking with Maria Clave this morning who, to your point earlier, had to, from many generations, face the gender bias. And has such a, that her energy alone is incredibly inspiring. And what she has been able to do it as the first female president of Harvey Mudd and the transformation that she's facilitated so far is remarkable. Marco Gertzen also was a great inspiring guest for me. She had said, you know, they had this idea three years ago, you were there from the beginning and I said, how long was it from concept to first event? Six months. Whoa, strap on your seatbelt. And she said it was almost- And they did it on a limited budget too, by the way. Sure. She said it was almost like the revenge conference. Like, tell us we can't do something. And I heard that theme as well from people saying, tell me I can't do something and I will prove you wrong in spades. And I think it's an important message. There's still such a gap in diversity. Not just in diversity in gender and ethnicity. There's a diversity, there's a thought diversity gap that every industry is missing. That was another kind of common theme. And that was kind of a new term for me, thought diversity. I thought, wow, it's incredibly important to bring in different perspectives. And on that point, one of the things I did hear in the hallway was a conversation of, this is not just a movement. It's a collection of movements. So it's not one movement. This one is, or women in general, it's a collection of movements, but it's really one movement. So it was interesting. It was kind of like, hmm, as being a guy, I'm like, can you women explain that to me, please? So, yeah. Well, the momentum that they... What kind of movement is this? They're achieving, I'm sure there'll be a hashtag for that. And speaking of hashtags, I did think it was very cool that today is Monday, hashtag motivation Monday. This whole day was motivation Monday to me. And I asked Margo, where do you go from here? You've achieved this in the third year. And she said, doing more WIDs events throughout the year, also starting to deliver resources on demand for folks, not just females to your point. This is people in data science globally to consume. And then going sort of downstream, if you will, or maybe it's upstream, and starting to reach more of that high school age, those girls who might have a desire and interest in something, but might not think, I don't think I could do this. Well, I think one of the things that I'm seeing is that I was glad to be one of the men that stood up and there's men here, is that men being part of it is super important because these newer markets, like I was just in Bahamas for a cryptocurrency blockchain event, and it's a lot of younger generations. The whole gender thing to them, they think is nonsense. They should be all equal. So in these new growth areas, they're kind of libertarian, but also they're really open and inclusive. It's because they're open source ethos. So I think for the younger generation in the youth, we can kind of set the table now, right? And men got to be a part of that. So to be that kind of world where the conversation isn't about women in tech means it's all good now, right? So the question we've had on theCUBE is, when we're done with the diversity and inclusion discussion, that means we've accomplished the goal, which is there's no longer need for that discussion because it's all kind of leveled up. So I mean, long ways to go for sure, but I mean, that's the goal. And I think the younger generations are like, you old people are like, we don't view it that way. So we hope that structurally, you have these kinds of conferences where the conversation is not about just women, it's about the topics and their gurus at their field. To me, that is the shining light that we want to focus on because that's also inspirational. Now, the stuff that needs to be fixed is hard conversations and it's tough, but you can do both. And I think that's the message that I hear here, phenomenal. Great to hear though, from your perspectives, from what you're hearing with the millennials on the next generation going, why are you even talking about this? It would be great if we eventually get there, but some other things that are really key and some of these companies are with sponsors, Intel and SAP and what they're doing to achieve really aggressively, much more gender diversity. We heard Intel talk about it, we heard SAP talk about it today, Walmart Labs as well. And it's still obviously quite a need for it as we're just showing you. The pay gap is still off, right?  So that is like, that conversation needs to happen. I'm not trying to minimize that with my other point, but I've got to get there. The other thing that's really off, the pay thing has got to get leveled up and people are working on that, that's great. Let's see the progress, let's look at the data. But the other one that no one's talking about is that not only is the pay a problem, the big problem is the titles. So we've been looking at data amongst the large of the big companies, women are getting some pay leveled up, but their titles aren't. So there's still a lot of these little things out there that matter. She's only a VP and he's an SVP, but she's actually offering an SVP level or senior director, I mean, this is happening. So much more work to do, but again, the more that they come in with the skills that they got, like in here, and the curriculum that are forming, the network set of forming, the VIP trust influence networks, it's just phenomenal. I think this is going to really accelerate the peer review, the peer relationships, access to the data, it's just, it's just the more the merrier. Shine the light on it, turn the sunlight on. Exactly, shining a light on the awareness that they're generating, and also that we have a chance to share through theCUBE and bringing more light to some of these things that you talked about. The faster, like you said, the more we're going to be able to accelerate making this a non-topic. It's our mission. theCUBE's mission is to open the content up, get the conversations, document the folks, get them ingested into our network, share our networks, open content. The more that that metadata and that knowledge can share digitally, that is the mission that we live for, as you know. We'd love doing it. You did a great job today. Thank you, it was my pleasure. It was, it's an inspiring event, even just getting prepped for it, and you can hear all the buzz around us, everyone, that it's probably, it feels pretty, it is cocktail party time, it feels pretty darn good. Well, John, thanks so much for being our fearless leader and allowing us to come here. We want to thank you for watching theCUBE. We have been live all day at WIDS 2018. Join the conversation, follow us at theCUBE. Join the conversation with hashtag WIDS 2018, and please join the conversation and share the videos of some of these fantastic leaders and inspirational folks that we had on the show today. For my co-host, John Furrier, I'm Lisa Martin. We'll see you next time.