So now that we have been talking about classes, we break down into two separate types. We get static and instance. Well, when we think about static, if we think about how we've written out almost every program so far, we've designed it with a public static void main method. Now the big focus here was on that the big focus here was on this guy, this static. So what does that static mean? Well, it means that it's shared across all versions or instances of the class. So every time I implement a class, a static variable means that there is only one and only one amongst all of them, almost like a hive mind. Say for example, I had made a, for our student class, there was a static int count. And inside it, and it started out as zero, and inside every time I did new student, every time I did that, count just went up by one. Count plus plus. Well, what happens is that count, that one variable, that is unique to, that is a shared across all versions of the student implementations. So if I make 30 students, count is gonna equal student dot count is gonna evaluate out to 30 because it kept count each time. And we see this actually a lot. Say for example, if we just think about for our sake the math class, something as simple as the math class has math dot pi. Well, how math dot pi is actually built is that's actually a static constant. Meaning it's shared amongst all versions of math and it is not changing. I can't change it at all. So suddenly I'm able to do, you know, that's built out as final static double pi 3.1 4 1 5 9 2, or something like that This is a static constant. Meaning I can pull it only from that method, from the method itself. I can't create a new math. I cannot do that. But I can, I can do something like math dot pi. And we see this a lot. Now we also get the idea of what's known as an instant variable. An instance variable is the exact opposite. Or an instance method is the exact opposite. How it operates is suddenly now I have a unique property. Again, if we think about the students student, each one of them had first name. This was considered an instance, or sorry, this was considered a class variable. Variable. Which means it changed from version. It changed from instance. This was always going to be unique to the instance. So I have tons of those. That's actually where something like get name. Get name from our previous video. It was unique. Unique, even though it did the same behavior with every class. It was unique. It was going to be a unique response every single time.


What's up everybody? It's Jason here for jaspyskatespace.com. We're giving away a Super Bowl Big Game Mixer spot away with this 2019 Panini Contenders Football Hobby 1 Box Break Round in Team 2. And again guys, we'll do the break first. Randomize Cosby's names, teams that shoot the hits out, Novak, Common Ship out of the box, everything else does. And at the end we'll take all the names, randomize them, and the top name gets a spot in the hip-rate Big Game Mixer. So let's do the break first. Here's the dice roller. Let's roll it. 3-0-4-7 times. Good luck. 1, 2, 3, 4, 5, 6, 7. 3-4-7. Michael P done it. Raymond. There's that. Now, 7. 1, 2, 3, 4, 5, 6. 7 times. 3-4-7, 7, 7. 10-8 bucks out of the New York Jets. Now again guys, you're going to stick to what you got of course, but it is a 1 box break, so I'll leave it up for about a quick minute. So you can see your teams. I'm going to go quickly grab the box too as well. So here we go. Let's do the box first, and then it looks like we've got some points coming up, so we'll be giving away some points as well. Chandler Jones. That should be on this side. Wow! How about a little Danny Dines? That is your RPS rookie ticket. That'll do for a little filler. Easily paced for the spot. That is Giants Andrew B. We've got Jelani. 2.99 for the Lions. Jamie Morlin. And Zach Allen. And there you go, guys. Alright guys, so this is what we're going to do. Number 1 is going to win the Super Bowl Mixer Spot. Number 2 as a consolation is going to win the 250 points. So we're seeing it again. Only one Super Bowl Mixer Spot. Top name. So there's the list. Roll. 1 out of 6, 7 times. Good luck. 1, 2, 3, 4, 5, 6, and 7th and final time. Boom. 7, 7. Good luck, guys. So number 2, going to get something, but not what you really want. Mike N. So you're going to get the 250 points, unfortunately, not the top spot. But number 1, Matt Buckler. Look at that, buddy. Boom. You are in. Congratulations. So let's put you in here into the Super Bowl Mixer. Boom. And I think Jopah Contenders 2. Boom. Appreciate it, man. So another one should be in the store. There it is. And like I said, as long as we continue to knock out a filler or two a day, I think we'll be able to do this big hip parade mixer by Saturday like it's supposed to. Like I said, we still need to sell 6 spots straight up. So 1, 2, 3, 4, 5, 6, at least. But like I said, I think we have plenty of time to knock out those spots. And again, I think a lot of people are going to buy the full spots as it gets closer probably by this Friday so that way we can break it on Saturday. So I'm not too worried, guys. So again, more fillers in the store, jaspyscasebreaks.com.


The United Nations is appealing for a full $7 billion in funding ahead of the upcoming UN Horn of Africa pledging conference shuttle to start later this week. Although no famine was declared in the region, the International Rescue Committee alongside with UN is saying the appeal is necessary to help communities struggling to survive in Kenya, Somalia and Ethiopia. The amount of nutrition rates in Somalia doubled and drought is believed to have destroyed millions of livestock, a major source of livelihood for people living in the region. The $7 billion aid is expected to help provide new innovative ways to evade future crises in the region and assist local communities to be resilient in the face of drought in the future.


Hello everyone, I am Sanjay Gupta. I welcome you on Sanjay Gupta Tech School. So as you can see this is day one for APN bootcamp and I have Ankit with me. So welcome Ankit on the channel. So let's start with this bootcamp. And I think those who are joining this bootcamp live and if you're watching the recording as well. So you might have gone through the day zero or we can say an overview session maybe live or recording. So I hope everybody know what APN is, why we use APN and what kind of certifications you can do with APN and what sort of career opportunities will be available to you. So in these regular sessions Ankit will be sharing all the insight related to APN with you. So that you can understand how you can build some solutions on APN. And in today's session he will be guiding you like how you can do some hands on. Right. So this is the agenda for today's session. So let's kickstart and before starting the session I just want to like request you please like follow Sanjay Gupta Tech School on YouTube, LinkedIn, Instagram and Telegram. And all the important links related to this bootcamp are available in the description. So follow proper session tracker so that you don't miss any of the session and please share a review. So if you see here like if you share a review or feedback so it will be helpful for us to improve the quality and the delivery method and whatever you need. So basis on that we'll be able to improve those things. Right. So with this note I hand over Mike to Ankit. So over to you Ankit please share your knowledge related to APN so that everybody can start learning APN and start working on that. Over to you Ankit. Thanks Ankit. Thank you very much. So in our last session we discussed about you know that what is APN as Sanjay said told and about the benefits of APN why we should use. Okay. And if you know other APN certification and all. So today we will go in more deep like we will learn about the APN environment how it works. Okay. How we can access the environment. How what is how we like and either can access the environment how the developer can access the environment. Okay. And what all components we can build and how the application look like on in APN. So we will learn all those things today. Okay. So coming to the first point that is APN environment. So APN is a web based cloud in cloud environment that allows developers to build and deploy applications. As a developer you can access APN by entering the appropriate URL in a web browser. So in APN you don't need to install any software. If you are a developer you can directly you know fill the URL in your browser and it supports all type of browsers like you can use Chrome. You can use Mozilla you can use like you know that age or Apple Safari and other browsers. Okay. And once you hit the URL so one login window will open to you in which you can fill the APN credentials and can submit. And now you will be able to access the environment. So once you know login on the environment that I will show you you will be able to see multiple components and feature that will we will discuss later. But once once you have the you know access of environment you will be able to access all its feature. Okay. Now the second point is APN environment types.  Okay. So in that case APN support both on premise and on premise or self managed and even cloud based environments. Okay. So in an on premise environment APN is installed and hosted on servers that I located within an organizations on data center. Okay. So like the company which is using APN they know manage the APN environment. They do not have the support. Okay. They have their own admin to manage that environment if there is anything that we need to upload and all. So all the key control they have. Now if you and you can host your APN environment on AWS Google Cloud or Microsoft Azure as well. In if you're talking about on premise environment more. So if you know the install and host it on servers that are located within an organization. So in this one so you know that this type of development provides organization with direct control over their hardware software and security. So it is suitable for companies that specific security or compliance requirement because they have everything on their infrastructure. Okay. So they know need to take care or know about the security and all.  Now come to the APN cloud environment. So APN cloud environment is hosted and managed by APN. Okay. So you know need to manage anything if you have APN cloud environment. Everything is managed by APN itself. You will just have you know get the APN URL. Okay. And credentials so you can directly access as developer. And so in this one this type of deployment eliminates the need for organizations to manage their own infrastructure. Okay. So like everything is taking care by APN itself. Like hardware, scalability, maintenance everything will be taken care by APN. And cloud deployment provides flexibility, scalability or rapid deployment. Okay. Because in that case you will have everything connected with each other. Okay. Now come to APN license. Can you please turn on video I think it is by mistake. One second. Thank you. So now come to the APN licensing customer. Okay. That is for customers. So if an organization wants to use the APN environment or their application in license is typically required. Okay. So this license is required for APN customers not for the developers or any other APN partner. Okay. That can be provided by APN corporation. So we you know if any of the customer want APN environment to use their for their application, then they can request to APN sales team and discuss about their projects and all that. And they will get the access of APN environment. The specific licensing terms, pricing and requirements may vary depending on factors such as organization size, usage, requirements and deployment options.  So in that one you know it has some pricing and the pricing depends on the users, number of users who are using the application or APN environment. Okay. And what you know like the configurations they want, what deployment if it is cloud-based or on-premise server whatever. So on basis of that the price will be decided and it's on subscription module like per user per month or something like that. Okay. So and for you know pricing module you can check on this you know URL. So here you will get all the pricing details of APN like how much you know price will be there and all. And for more discussion you can directly connect with APN sales team as well. They will guide you as per your requirement like what will be the suitable environment and how both configurations will be needed for you. Okay. Now APN licensing that is for developers. Okay. So if you are a developer working for an APN partner company. Okay. So there are some APN partner company like you know that if some company have direct contract with APN. Okay. So to provide the development services. Okay. So for that or educational partner and all. So for that there is no need to you know the APN provide them a demo environment. Okay. On which they can practice. So if you are working as a developer for APN partner company you will also have the access of that demo environment. Okay. And you can do the practice on that you can create your own application. You can access other features of APN also. Okay. Like if you are working for a customer. Okay. Like for a bank or insurance company. Then you will have the access for customer environment. Okay. Because customer already you know if any of the customer is working on APN they will already have APN environment on which they will develop their you know they want their application to host. So you will also work on the same environment on which clients you know a client or customer want their application. Okay. If you are not working for an APN partner company or a customer. Okay. Like you are the start learning of APN. Okay. And you are not working in APN you know any of the APN company. So in that case APN give the access of APN community environment. Okay. That is completely free and you can request by yourself as well. So now that next point is how to access APN community environment. Okay. So you can request for APN community environment by yourself. Okay. You don't need to request to APN or you know but you can create a request directly from its community to request for APN community environment. First you need to log in on APN community. Okay. So before accessing APN environment you need a community environment or community account in APN. Okay. So to get the community account or to access the community account you can use this URL. S-T-T-P-S community dot APN dot com. Okay. Now I can show you how it looks like. So you can see here this is APN community environments login page. Okay. So in the in this one you can see here we have one page that is register now. If you are already a user of APN so you can directly type here your email address or user name and password. If you are a new user you can click on register now to register on APN community. In this on this page you have to fill the details like basic details only like your email address, your password. Okay. And you can confirm the password your first name, last name and just content. Once you submit this form okay there will be one acknowledge you know there will one email you will get on your you know email ID for acknowledgement. And once you acknowledge the request you will have the access of APN community. So then you can directly access the APN community you don't need to do anything else. So this is very simple process for this. And once you have so yeah so once you have a community then you can raise the request for APN community environment. Okay. From your profile page. Okay. So on profile page you will get one button that we get my site. I can show you how it looks like. Okay. So this is my community page. Okay. Now I do not have any community community account so it is visible to me in right side you can see get my site. I can to get the access of APN request for APN access I can click on this button. Okay. And it will ask me some details like select your cloud region language. Can you please zoom in like control plus so that I think it is not readable. Is it readable now. Yeah. Yeah. Now it is okay. Thank you. Okay. So you know so I can reload as I can. So this is my APN community. Okay. And from this I can request for my APN community environment like development environment. Okay. So to that I have a button in right side. Right. Get my site. I can click on this button. Okay. This will show this basic details. Like on which region you want to access the APN language and what is the region to access to APN environment. Okay. So you can select the appropriate details and agree on the terms and can submit the request. Okay. This is all you have to do. Then it can will review this and will give the access of APN environment. So you will get an email by APN with your environment URL and your temporary username password. So you can just fill your URL that is provided by APN on your browser and fill your username password to get the access. Okay. That's all you have to do to get the access of APN environment. But it takes about 7 to 10 days because APN first review your request and then process the request. So generally it takes 7 to 10 days. It depends on like how many requests are there in APN's queue. Okay. So this is all you have to do for to get the access of APN community environment. This is just the page that we just, you know, check in this one you can see here. We have this is AP community dot APN dot com page. From here you can click on the sign in register page. Once you click on the sign in register page, you will have the option that we just, you know, check where you can fill the sign in details for registration details. And this one also we checked. Okay. From here, this one you can get the access. Now come to the APN interfaces. Okay. So Ankit, there is one question. Now Priyanka is asking for learning which community addition we select. Yeah. So for learning, there is an option. Okay. In this one in region you can select here. Like you can select the region India and in this one you can select like, you know, that there will be no option. I'm really, I'm experiencing with the app development or new feature you can select this one. Okay. To get for learning purpose. Okay. I think Priyanka this, this is the answer for your question. Yeah. So I think we can go ahead. So APN interfaces. Okay. So we can, you know, we can categorize APN interfaces in two part. One is end user interfaces and other is developer interfaces and user interfaces are generally, okay, for business users who will access the application. Okay. And work on that application. They do not require any coding. They do not know any coding and also they won't have the access of. APN coding environment but just the application. Okay. That they want to use or that we are building for them. So user, you know, APN provides the user friendly interfaces to interact with applications. So in one environment for a customer can build as many as applications they want. Like if I have one APN environment so I can develop 10 applications, 20 applications, any number of applications that I can, I need to develop. This can be accessed through web browser or mobile devices both. Okay. So APN have an app, you know, app market application also from there also you can access the APN on Android mobile or Apple. Okay. Or app market.  They can complete their assigned tasks. They can review their request or they can check the records if there is any reports they can see or they can check the sites and all. So this is all for business users who are the real users. They want who want to use the application. Now the second interface type that is developer interfaces or we can say designer interfaces. So these are generally for developers or designers who developed the application like who poured into the application. So generally what they need, they need like, you know, that coding at no platform or coding, you know, interfaces and all. Okay. They need to deploy the application from one environment to other environment. So for that they will be needed of the option to deploy the application. Okay. And to manage and configure APN environment like if I want to change the branding of, you know, APN environment if I need to change, I need to create users in APN, new users in APN. Okay. Or if I, you know, need to connect with database, then all these things are like, you know, that to manage the whole environment. So these are, you know, can be done from admin console. So I can show you how it looked like. Second. So this is APN's developer environment. Okay. That you can see here. So from here, you know, that you can see here there are multiple applications are already we have. Okay. And if you know, you can also develop your application. You, you can use any of the features that we provided by APN, like you can see here, you can create new application. You can create, you can import existing application. There will be some component that you can, you know, create from here. You can see the objects. You can deploy the application from one environment to other environment from, you know, this one, this option. And then you can monitor, okay, the existing processes or, you know, that which are already running or request, which are already running. So this is overall, you know, that a high level view of designer or developer environment that APN provides.  Okay. So we will, you know, learn everything in deep. Now this is like, you know, that this is the designer interface to access, you know, that end user interface. We have multiple options that we will learn, like one is tempo, okay, that you can have the access. Okay. And I will show you how does it work. And then there will be some sites and all. So we will read about this one by one. Okay. Now come to the end user interface that we discussed just now. So first one is tempo, okay. It provides four types of end user interface. First one is tempo. Second is sites. Third is portal and fifth is embedded interface. So tempo is like, you know, the oldest APN user interface. Okay. That is like a default user interface that provided by APN. Okay. So it's overall look and feel is, you know, that provided by, you know, set up by APN. So we cannot change in this from this one user can access multiple in sub interfaces or interfaces, like excellence. Excellence is like, you know, that if I want to create a new request or perform new action, then we can use APN actions. Okay. Then tasks. If some tasks are assigned to me, like someone else is assigning me a task, I can complete the task from here. Okay. Then records, like, you know, that if I created a request or if I raise a request, like I can say, like if I'm filling HR form, or I can up, you know, requesting for a job, so I will fill the details. Okay. So that details, which I'm filling is action. Okay. Because I'm taking the decision first time. Then HR, it will assign to HR. Okay. So for HR, it is a task. Right. Records, like if I, I can see my details at any time, like my request, it is anytime from a view or read only that is records. Okay. So from records, I can take the decision on that particular request as well. Like I can add it to the request or I can close the request or I can take other decision. Reports are like, you know, the charts and all that is related to multiple objects. Okay. So, like, we can create metrics, we can create different, different types of graphs to like, you know, to check the performance of a company, like how many requests are raised, how many requests are on this particular status and all.  So I can show you how tempo looks like that. So to access the tempo, you have to just go to this weapon menu and right there. Okay. And you can click on this one. Here you can see we have five tabs on top. Okay. News, tasks, records, reports and actions. Okay. So actions are to create a request. Okay. New request reports are to know, check the metrics, so charts and all that we can check from reports, records, we can, you know, check our, you know, create request which are created by us or which are created, which is created by anyone else, we can check from here. If any of the tasks is assigned to me, I can check from here. Okay. And from news, it is for social collaboration where I can post something, I can do something or I can comment on any other post. It is, you know, similar functionality that other social platform have. Okay. So this is about tempo. We will read about this, you know, deep in, you know, next sessions, but this is like, you know, high level view that how it looked like. Now, come to the second, that is sites. Okay.  Right. These tasks are visible to all of the application, actions are for all of the applications. Security apply here as well, but we cannot, you know, we cannot differentiate with applications. Okay. So this is not dedicated to a particular application, but a particular environment or particular, you know, client or customer.  Okay. So in application, like we can set the branding, like, you know, the particular application will have this particular branding that we can set, like this particular application will have this five or six interfaces that we can define here, we can define that particular security and everything is dedicated to a particular application. So sites are, you know, more, you know, related to a particular application and how these are looks like to access the site. Also, you have to go to the special menu and you will, you can see here, all of the sites which are built already on this environment. Okay. So you can access any of the sites from here, like, this is a demo site, you can see. So this site from here, you can access, you know, different, different forms. This one have only one form. And but, you know, if there are multiple forms, multiple types, you will be, you can see from here, you can access, you can, you know, take the actions on those forms and all. So this is more about sites. Now, third is portal. So sites and tempo are both, you need to, you know, appian credentials. Okay. So portal is a new interface that is provided by appian in latest version only, like one year back only. So in this one, this is for public users. Okay. So tempo and site, you can only have access by login on the environment. You have to, you will be need of your username and password. Okay. And those are chargeable for a customer. Okay. But sometimes customer want a public page as well. Right. Like, if I want to create, you know, design application for text related application that any of the, you know, person from a country can access. Okay. So this type of applications, appian provide the portal. Okay.  There will be no any login credential. It will ask, there will be no login credentials. The screen will come and it will simply open to you. Okay. So this is for unauthorized or public users who do not have any appian credentials. But yeah, it has some limited functionality, not as sites have. Okay.  So from where it can get the data, you can save the data. Okay. Now, for each embedded interface. Okay. So in appian, like, suppose I'm creating one report in appian, I'm creating one created one action in appian. And I want to show that report action or interface on my public or, you know, I can say on my company's portal that is not developed in appian that can be estimate fight or something else or built on the different technology that also we can do. So we can, you know, use one any of the appian component. Okay. In other portals as well, you have to just put some simple command. Okay. And you can access those, you know, interfaces outside of appian also. Okay. Okay. For that also you will be needed of single sign on. Okay. And because it works or it also needed us at nine credentials.  Now, come to the appian interfaces for developers. So those whole interfaces were for end user. Okay. There was no any coding, you know, and anything just appian customer can have the access and can use their applications on these four type of interfaces. But to develop the application or not to design the application develop the application if it provided some designer interfaces as well. Okay. Like interfaces, user interfaces from where user can know we can create some, you know, some type of component we can use some component we can create a grid, we can create forms and all. So for those you can provide interfaces. Other is like business rules. So sometimes we need logic as well to get the data from database to perform some calculation. Okay. For those we are needed business rules. Third is like process modeller. So process modeller like, you know, workflow. So appian work, you know, appian is a process management tool. So it works, you know, it provide the functionality to create a workflow from where from like one step to how it perform from one step to other step. So all steps are connected. Okay. That we can develop using process modeller. So later on, we will read, you know, learn about this to these components more, but yeah, this is overall. And then admin console admin console that we just learned that it provide the administrator functionality to read no branding of your appian environment to create the user or to like another to connect with database and many more features is provide. So how it look like I can show you so designer who can can go here with a menu and you can have the access of design. Okay. From this you can see here we have multiple applications which are built already built. Okay. Now, from here you can see that, you know admin console, you can go to admin console from here. And you can know you can see here in left side there are multiple, you know, a lot of features. So this is first is for branding. So you can set the branding colors, you know, have a font and everything. Okay. And there are many more like, you know, the file upload internationalization languages, mobile permission plugins that, okay, so this have a lot of features that and, you know, see, if an admin can configure from here. Okay. We will read, you know, read about this in our coming sessions because this is just a high level. Okay. Now, one more thing that I want to show you here. Yes. Yes. So you can see here to, you know, check the objects, we can go to object step. Okay.  Okay. We will learn about these. So like there are some connected system, AI skill, constant, we can take data store, data types, decision document. Okay. So there are a lot of components we have to create an application we will be needed of this, you know, components. Okay.  So APN, you know, bucks on sell language or whatever code you are writing, okay, in APN like to, if you are creating an interface, or if you are writing something so that we know is sell language. Okay. Sell language is like self-assembly interface layer. Okay. So sell, you know, sell allow developers to create responsive and interactive way.  So you don't need to take care about like how code different code, you know, different code for different systems and all. It is already responsive. So you have to just write one and you can use that code anywhere. Okay. Now, APN users. Okay. So we just check like we can create APN users from APN admin console. Right. So mainly APN, you know, divide its user in two types. One, you can see in top that is APN system administrator and other is APN basic users. Okay. So like if I'm an end user, and if I just want to access offer, you know, that an application or tempo or site, okay, or, okay, so for that, I will be a basic user. So basic user will not have the access of designer. Now, I can see, you know, I am able to see this designer because I'm not a basic user. Okay. I'm a system administrator.  I can only see the site or tempo. Okay. And these are also as per the security. So if I have the security of one application, then I can see only one application here or one site here. I cannot see other sites. So everything is on based off security. Okay. Now come to the APN system administrator. So system administrator is, you know, like a super user for APN. Okay. This is generally for developer. Okay. Who is developing the application? So system administrator have the access of whatever access basic user have. Okay. Like system administrator can also go to tempo, can check the tempo, can go to any of the site, any of the application, there is no any security works on APN system administrator. Okay. And additionally to that APN system admin have the access of designer also. Okay. So administrator can develop the application. Okay. Can use any of the feature of APN. Okay. Any of the components of APN and can develop the application. Okay. So for that APN have system administrator. To create the APN users, you can go to admin console that we just checked. From this tab, you can create. Okay. So in this one, you will be having the access of create user. Okay. And from there, you can select if it is a basic user, if it is administrator user, as you will be having the access. To create the user. Okay. And then once you create the user, so in that user will have, you know, so for that user, you can create the temporary password, or you can, you know, put it blank so that any of the know that that user will get an email with the temporary password, and that user can access the APN environment with the help of the temporary password, it can change the, you know, password by themselves. Okay. Now, APN application package. So APN application package is like a collection of artifacts or collection of components that we built or a developer, you know, built for a particular application, like some of the constant I created some of the user interfaces I created some of the business logics I did some integrations I used. Okay. So this is not like a collection of those artifacts or like, you know, the container of those artifacts that is come under the particular application package. Okay. So we can to create, you know, the new application package from APN design interface, you can go again to the designer. So you can see here, these all are application packages. Okay. This like your CV is one application package, this D mockups is one application package and every application package have some components that you can see from here. Okay, so you can go to this build, you can see. Okay, so these whole are artifacts that, you know, is built for a particular application to create a new application, what you can do, you can click on this new application. Okay. So you can, you have to just type the APN, sorry, application name, description of the application like I can say contents. You can see here that prefix is already built, you know, come from APN. So it's selected like initials of this text. So APNs A and trainings D but you can judge. So all of the artifacts that we will create in APN will follow this pattern only that all of the artifacts will start with 80. Okay. Now you can see we have one checkbox here. Okay. And in this one, you can see here generate groups and folder to secure and organize objects. Okay. So some, you know, objects are required. So APN automatically can also create those artifacts or you can create manually. So if you click on this checkbox, APN will automatically create those groups and folders. Okay. And you don't need to create those by yourself.  Okay. Now I can click on this create button and it is asking for security. Okay. That we will be learning next session, but I can explain you in a high level that you can see here. These are APN groups. Okay. Custom groups that we will discuss. Okay. And APN groups are like you can see a group of users or a department like you know that in a company we have IT department or finance department or you know that sales department. So groups are something like departments. Okay. And every department have multiple users, different different users. Okay. So groups are also collection of users with some properties. Okay. So, you know, the secure particular application to give the permission to set the visibility we use these groups. Okay. And there are different different level of security also. And like the time you are editor administrator that we will read. Okay. But these are the security levels that we need to set whenever we are working on any of that APN artifact. Now you can see here this application package is created. And if from APN given a pop up screen from where you can create any of the artifacts like new records, new process model, new site or portal that is suggested by APN. Okay. And you can use any of this template. Okay. Okay. Now I can close this one. And if there is already created record process model connected to any of the components you can see from here. Okay. And you can access from here. Now you can go to build interface and you can see all of the artifacts related to this application. Okay. Like these are artifacts that is created by APN itself because we selected, you know, that check box. Now if you want to create a new artifact, you can go to new and you can create the applicant artifact. Okay. Like data type, data store, record type, there are multiple type of components that we will read. But from here you can create any of artifacts which is needed for an application. Okay. Like if you want to create a group, you have to click here and you have to fill some details. Okay. And it will create the group for you. Okay. And you have to set some properties.  Okay. But that's how we can create an interface. Okay. Or so from here we can create any type of component that we need to create for a particular application for a particular requirement. Okay. So that we can create from here. Like we can filter out of the objects as well. Like if I want to filter out all the data types I can filter out. If I want to filter out any of the group I can filter out from here I can filter out any other artifacts also from here. Okay.  Like modified date on this that particular artifact is modified. Okay. So this is the application and this application can have n number of, you know, objects or artifacts, okay, which that we are creating for a particular application. So if you are working on any of the application, you have to first create the application package. Okay. This is the starting stage in APN if you are working on any of the application. Okay. Then you have to create artifacts, okay, which are required for that particular application. Okay. Now, to the next part that is APN database connectivity. Okay. So, you know, that that we discussed now, just know that few slides back that APN provide two type of environments like or one is APN cloud environment and second is on premise environment. Okay. So APN, if APN, we have APN cloud environment. So APN provide us the prebuilt MariaDB database with itself. Okay. With environment itself. Okay. So you can see here this is APN cloud environment. Okay. So you can see here I have database access also. Okay. So I can access the database from here. Okay. And because I'm a system admin, so I have access if I'm basically I cannot have but APN provide the prebuilt database. So you can use, you know, this database also. Okay. That is provided by APN. Now, but if you do not want to use this, you know, database that is provided by APN and you already have some database that you are using, like you are using as you know, Maria MS equal or Oracle or other data relational database you can use. Okay. So that you can also use and for that, you know, configure that additional database, you have to go again to admin console. Okay. And from here, you can see we have one data source option in left side. Right. So from here you can access the data source and you can use add new data source. Okay. So data source is nothing but just to know that the connection between APN and database. Okay. So from here you can type the name that you want to give to the particular, you know, data source, you can select type. So APN support these many database. Okay. Like Aurora MySQL, SQL, DB2, MayaDB, MySQL, Oracle, PostgreSQL, SQL server. Okay. And in this one you can type the connection string of that particular database and username password. Okay. And you will be able to connect with that particular database. Okay. So as many as data source or database you want to connect, you can connect. So cloud environment have one prebuilt MariaDB database and we can configure or connect additional relational database also that is also very easy to connect. Okay. And once you have the access of like, you know, the database, you can create your tables, you can create new or any other database related artifact and that those artifacts you can create. Call in APN by some APN provided components. Okay. That we will discuss. Now come to the on-premise environment. So in on-premise environment APN do not provide any prebuilt database. Okay. You have to add your relational database only in this one. Okay. You have to take, you know, take that particular database on your server and from the server you can, you know, check the connection string and you can configure that. The connection string in same way that we are doing in cloud environment. Okay. So other things are same but you and you won't have APN's clouding database in that case. Now come to the APN app market. Okay. So like, you know, that APN provides app marketplace where you can find prebuilt components or integrations or solutions. Okay. That has been developed by APN community. Like any of the APN partner or APN developer developed the application or, you know, that component or some accelerator type of, you know, small applications or some complete solutions or any of the plugin. Okay. Or any of the other components they can post on APN's app market or anyone can access from, you know, anyone can have the access of that artifacts or, sorry, those applications or those components, those integrations from the app market. So to get the, you know, access of APN, you know, app market, you can use this URL and you can have the, you will be having the access of app market. So in app market, once you, you know, hit this URL, it will open something like this in that one you can see here. So you, so I can log in. Okay. I can access this by clicking on this link as well. Here you can see all of the applications are there that, you know, is uploaded on app market. And you can read about any of the application and you can schedule a demo because some of the applications are, you know, that are free. Some of the applications are paid. Some of the applications you can directly download. Okay. But for some you have to connect with the development, you know, that company or team and you can schedule a demo from here. But you can check the features. Okay. All of the features from here of the particular application you can see the, you know, the interfaces and all that is uploaded by that company. And you can check that, you know, the author or the compatible version also of APN industry and all. Okay. And you can check here. Cost is paid. So that means this application paid. Okay. You have to pay something for that one. But some of the components, plugins, okay, which are free and cloud approved. So you can directly use those components wherever you are required in your application. And if you do not have any, because it can provide some out of the box features as well out of the box components. But in any of the requirement that is not filled by the out of the box features or components, you can come here and you can check that any of the plugin that will fill that particular requirement and you can have that. And you can download that particular one. Okay. Now, so, you know, that for community environment access, okay, you can directly request by yourself. Okay. And please fill this, you know, Google forms as well. It is that, you know, you just need to fill your basic details only. Okay. So, know that we, you know, we, we will get the, you know, request from you and we will, you know, get, you know, APN environment and we can provide you the link, okay, whenever we have like, it will generally take seven to 10 days. So once, you know, we have the access so we can provide you the access of APN environment. So you can practice on that environment. Okay. So you have to just fill the details. Okay, just your basic details as soon as possible. Okay, so that you know that then we can check and we can provide you the access of APN environment. Okay. And we are now open to discussing post-it queries that you are already posted and if any of the queries that you have, you know, in the future, please feel free to share any, you know, queries or questions. You can do, you know, email us at the below email ID that is provided here. Okay. And you can comment on your video as well. So over to you, Sanjay sir. Yeah, thank you and get for this detailed insight and for your help like this Google form link I already shared in the chat and those who are live and listening this thing and those who are watching the recording and listening. So if you feel any doubt, any problem, so you can just reach out to this email ID or there is a telegram group link which is available in the description of this video. So I'm just sharing that link here in the chat as well so that if you have any question, any query related to this thing, so you can ask those in the telegram group. So I'm unable to paste the telegram group link in the chat. So it is available in the video description. It is available in the session tracker as well. Right. So, Ankit, there are two questions. So first is from Saim Ankitash. He is asking any limitation like only these databases, databases can be connected or APN support only few. So he says further like or any database from market can be connected in on-premise mode. Yes, so APN supports some of the database like APN generally support relational database and in relational database also it supports some of the database that you can see here. So APN supports all of these databases like DB2, MariaDB, MySQL, Oracle, PostgreSQL, SQL Server and Aurora MySQL. So APN supports this all type of database. Okay. So we have one more question. Ankit is asking, will you give us the access or do we need to request? You can also request. Okay. First you request and share the details. Okay. So we will also provide, you know, if you have the access like if you are getting the access in 7 to 10 days, so you can use that. Or no, sometimes it takes time also for you. Okay. So if it is taking more time and if you have access before, so we will provide you. Okay, because we have to start, you know, that practicing as soon as possible on this. So we can do both. Okay. So guys, if you want to request like you can go ahead and if you have any issues, so you can just fill this Google form. And still if you have any issues, so you can reach out to Telegram group, right? And you can just send an email to that email ID which Ankit showed earlier. So I think there are no more questions. Yeah, one more question is there. So only relational databases are supported in APN? Yes, only relational databases. Yes, Ankit. So only relational databases are supported. Okay. So I think this is it for today. So thank you, Ankit for sharing this insight to everybody. And I think those who have joined this session live and those who will be watching the recording. So they will find this day one session very fruitful. And once we'll be having the instance created, so they will be able to do some practice as well. So we'll be having one more session tomorrow, right? So right now what we are doing, we are keeping two sessions in a week so that like once you will be having some instance ready for practice. So that will also be helpful for you. Right. So tomorrow also Ankit will be sharing some insight with you. So do watch that session. And it would be better if you join sessions live, because if you join sessions live then you will be able to interact with us directly and Ankit will be able to answer your queries. And if not possible, then just go through the recording in whatever time zone you are, whatever time is comfortable. And still if your question is not answered, so you can reach out to this email ID low code corner mentor at gmail.com or like telegram link is available in the description. So there is one more question Ankit Manish is asking which programming language is required to build application. So APN has its own proprietary language that is cell language. So you know everything you will develop, you will develop on that particular cell language only. You don't need to require any other language. S-A-I-L, right? Yes, S-A-I-L. Yeah, this one. Okay, self-assembling interface. So it's APN's proprietary language that is owned by APN itself. Okay, so I think Manish your question is answered. So yep, so thank you Ankit for giving this insight and thank you for sharing your knowledge. So maybe we'll be coming live tomorrow same time. Okay, so thank you so much. Thank you everyone for joining this session and those who are watching the recording. Thank you to you as well. Thank you. Thank you everybody.


On Tuesday, we found out that the U.S. consumer price index rose slightly more than expected in June. The UK GDP expanded by 1.8% in May on the month, below expectations of 5.5%. Industrial production up by 12.4% in Euro area and 11.4% in the EU. And the Swiss National Bank said expansive policy is more necessary than ever. Welcome to the Tick-Mail Update, I'm Canada and you're the founder of the Investiva movement. Make sure to subscribe to the Tick-Mail YouTube channel and support us by liking and sharing this video with your forex trading friends. On Wednesday, we'll be watching the UK inflation rate, Bank of Canada's interest rate decision, New Zealand's inflation rate and Australia's jobs report. Today I'm looking at the Dollar-Swissie pair, which continues down the downtrend we identified back in May, as it's reaching the lower band of the long-term range the pair normally moves within at 0.9256, so we'll continue to eye this support level once it's reached to determine the next direction for the pair. Do you think the Dollar-Swissie pair can reach this level without being interrupted by US dollar bulls? Head over to the comment section and let me know. Of course, trading in the financial markets involves a risk of loss and it should only trade the money that you can afford to lose. If you liked this video, give it a thumbs up and subscribe to the Tick-Mail YouTube channel. I'll get back to you with more updates tomorrow.


Hello, my name is Adjoa Florencia Jones de Almeida and I'm the director of Education here at the Brooklyn Museum. So my definition of a radical woman is someone who has taken the time to understand who she is and how she shows up in the world. I nominate Mairele Franco, who was a black LGBTQ community organizer, councilwoman in the city of Rio de Janeiro, Brazil, who was gunned down on March 14th. I also nominate my daughter, Zina Almeida-Warren, who is one of the fiercest, most powerful young women I know.


This film is called I. The like. In your head, or you personally? I. The letter? Interesting. Like share.  I'm Corbin. Remember when I started it. Hey, welcome back to our Steward and Accent Z idiots. I'm Corbin. And this is Rick. The Rock Done Person. Not the Sun person. You know what I'm saying? Go and smash the like button. Subscribe. And ring that little bell to be part of the notification squad. And please follow us on Instagram. It's so juicy. Follow us as well. So together. We. We will react to I. To I. We are I. This was a request by somebody on our Patreon. So thank you to everybody who subscribes to us on Patreon. You're so much. And let's get into it. Come on now. No clue what this is about, do you? No. No idea. Hope it's fun. Here we go. In the old days, this will be the end. No one will come here. Only I and you. The colors obviously. The whole life will be the same. It was like Hellboy. Right. It was like DaVinci code. It was like Bruce. Abrant. Bruce Lee. And then it actually felt like a little rom-com at the start. Yeah. It had beautiful colors. Yeah. Then it was a... Wow.  Holy cow. And it looked really cool at moments. And then it looked like it could be like really weird in moments. This is either brilliant or a train wreck. Yeah. There's no middle ground on this thing. Yeah. So once again, as always, please tell us. Wow. How this film is. And that is insane. I don't.  Oh, totally enjoyed the trailer. Right. I mean, it was like 10 different things going on. It's just wild. Okay. Utterly wild. What's the description say it is? A simple bodybuilder's life took an unexpected turn when he became a model by his beloved. When five men made his life better from hell, then story proceeds by how a disabled man took revenge from them in a very gore ways. That was just like the trailer. And that's how it's written. Not very gory in a very gore ways. The description's just like the trailer. It just doesn't make any sense. It's all up for the place. I felt like I'd seen a couple people before in it. Maybe I haven't. Vikram? That's familiar. I don't know if that's the main guy though. That could be wrong. That was the one of the wildest, craziest, weirdest, freakiest trailers. Yeah. Wow. Its budget was 30 million. Is that American dollars? I'm guessing it. I assume it is because it translates it over here. So it was a 30 million dollar budget. I mean it doesn't look like it made its money back. So I'm guessing those numbers aren't correct. I know. It says that the budget was 30 million and that it only made like three. That's really bad if that's the case. So yeah, please let us know how it is. That composer, I know that composer. Would you click on that composer? I know that composer. Slumdog? Slumdog. Legang? 127 hours. He's done a bunch. Yeah, the minute I saw that name I thought wait a minute. I know that person. They've done quite a bit of work. 2.0. I did a 2.0. Those things. Yeah. So. Wow. Anyway, what a crazy, that's like weird as some dreams I've had. And I have weird dreams. Yeah, it started out and it was so, so beautiful. I know. I was expecting this lush, right? Vivid colors and then it goes. It goes like, like, yeah, like Pan's Labyrinth or Hellboy's. Like Guillermo del Toro style. Yeah. Guillermo, it's del Toro. And then Bruce Lee action. Which would never happen in a million years. And then it's like the Hunchback of Notre Dame. Yeah. What the heck was that? Let us know how it was. Man, points for making a trailer that totally just is like I've never seen it in like. It was fun. Yeah. Regardless of if it's good or not. Yeah. So. Haha.


Get this going. So, hi, I'm Nick Weber. I'm from the University of Washington and I'm also representing the qualitative data repository where I'm the technical director there. What I'm gonna talk about today is an initiative that we have called the Annotation for Transparent Inquiry and I'll kind of explain that as I go. But I wanted to thank Gardner in particular for the keynote. So I called a little bit of an audible and making my slides. I think there's an underlying thesis to the work that we're doing collectively here in this room but in particular in the ATI Initiative and that's that we sort of have this thesis that flourishing on the scholarly web is going to require collaborations that maximize our comparative advantage for collective good, right? And we can think about comparative advantage as this kind of basic economic principle that if we have a sort of exchange of goods which is open and free, if we maximize what we're best at doing, we can cooperatively create greater wealth. But I would say that right now the scholarly web is not necessarily creating greater wealth for everyone. That is to say that we have a increasing amount of pressure that is put onto individual researchers in order to conform with emerging norms around transparency, around replication, around verification that puts the onus or the responsibility almost entirely on those individuals. It doesn't necessarily distribute that to a set of institutions or a set of technologies that can assist them, all right? And so this is creating maybe gaps in wealth between different types of research or modes of scholarship. So I wanna also sort of highlight that calls for transparency are somewhat separate from replication or verification initiatives as well. The transparency initiative of the Political Science Association or the American Political Science Association defines transparency in sort of three modes. The first is production. You can think about that as the way that data are collected. The second is around analytics or how data are the sort of methods that are brought to the data. And then the third is data transparency which is access to the underlying empirical evidence itself. And so in the social sciences at least, quantitative transparency has a pretty good template that's maybe slower emerging than we would expect but it looks something like this. This is I think a really good example from Cambridge University Press. It's a set of researchers in political science research and methods. That's the journal. But what we see here is a typical kind of narrative HTML that we would expect but there's also an interactive environment provided by Code Ocean. And so we have a set of actors that are maximizing their comparative advantage, right? We have an executable environment from Code Ocean. We have the data that is backed up and archived in Dataverse. And we have a publisher who has provided this infrastructure and coordinated these different actors in order to have an end user experience that sort of transparency in their research, right? So this is the quantitative model. Transparency in the qualitative domain is lagging for a number of reasons. There's not the tradition of sharing because there's privacy and public, I'm sorry, information about individuals that are often embedded in the types of research that is done there. But there's also sort of not a lot of good existing models that don't do anything more than innovate with a traditional scholarly article. And that is to say that these are sort of bolt-on or supplemental materials to footnotes and notes, et cetera. One of the maybe kind of early progenitors of some of the work that I'm gonna talk about is active citation. This was this idea by Andy Moravchuk at Princeton who said, what we should be doing is providing a set of technologies that will allow people to explicate a particular citation that they have made, explaining why they're making the citation, providing if it's archival access to that resource in something like a transparency appendix, which appears at the end of an article. But this is costly, right? This requires publishers to innovate with and change the model that they typically publish in the other kind of scholarship, right? They're gonna have to make an exception for qualitative scholars. It also requires copyright to be mediated by the publishers themselves, the hosting of the data that may be linked there. So altogether, not a terribly efficient way to provide transparency for qualitative research. Okay, and this is, unfortunately, I guess we can't see this at the sort of big monitors, but I thought this was a great example of another solution. So this was a footnote that was tweeted out by a historian, Kara Shilling. She's, then I'll read the footnote to you. It says, the figure is from the New York Times article of the period and will probably show up if you search for keywords, barge captain, 1258 dead horses, or barren island in pro-quest historical newspapers. I've lost the bloody reference and I'm confessing my carouselness as to the world instead of spending my day looking for the exact piece. Perhaps you could just trust me on this one. If you can, then I thank you. What? Okay, so because Twitter's this beautiful networked world, then pro-quest responded and they actually found the article. Right, but this is incredibly inefficient, right? This is not how we would expect scholarship. This is not how we expect science to operate, right? And we can do better than this in the 21st century, right? We have the socio-technical means to develop a template for qualitative transparency, which is meeting the needs of production analytic and data transparency and is simultaneously compliant with we think of the data principles of fair, right? Findable, accessible, interoperable, and reusable. So the ATI initiative is very much about this and it has three partners. It's Cambridge University Plus, it's the qualitative data repository, which I'm here representing, and Hypothesis. And so what ATI was envisioned as doing is creating dynamic linking for original source material that support authorial claims. Integrating with a range of, or the ability to integrate with a range of scholarly publishers using web standards to anchor those linked materials to published texts. And then a scalable method of preserving underlying data and creating persistent identifiers to that linked content. Okay, so essentially what this means is that we got some funds from the Robert Wood Johnson Foundation in NSF to pay authors to go back and annotate their articles to maximize the transparency along three different lines, right? The data, the production and the analytic transparency behind them. So we picked 40 different authors and we split them into two groups. One was going to annotate publications that were already published. They existed in the scholarly record. These were anything from one to five years old. The other group of authors were still writing their articles. So they were in the process, the formative process of generating and thinking about how to craft a narrative and how to craft a supplemental material that would support that narrative. We also paired all 40 authors with a peer reviewer. The peer reviewer would first read the article unannotated and they would note expectations that they had around the transparency of the article, the claims made, the data sources they expected to see. And then we show them the annotated article that the author produced and ask them whether or not that lined up with their expectations and to overall comment on the quality whether it was improved of the transparency of the claims made in the article. Okay, so some observations preliminarily having run both of these workshops already. The median number of annotations was around 28. So this varied quite a bit between the kinds of different disciplines that were participating. We had anywhere from sociologists to epidemiologists to linguists to political scientists, historians, legal scholars, et cetera. It also differed pretty substantively whether you were annotating a pre-publication or a post-publication. Pre-publications tended to have more leniency. They could create and they had the ability to figure out what exactly they would annotate and why. The median time to assemble a project for ATI, meaning to collect the data to anchor it to the text and to explain the logic of why you were anchoring a piece of data to a piece of text, was around 40 hours. And this ranged anywhere from 12 to about 200 hours that individual spent just not writing the text. This is just going back to revisiting, annotating the text to make it more transparent. And pretty significantly, the time to review was about 12.3 hours for this is the annotated text that we provided to reviewers. And reviewers overall reported this being pretty significant when compared to the traditional methods that they would use to review an article. Okay, so this is what a compendium of an ATI looks like. This is the interface of a software application called Dataverse that QDR runs and we have a particular fork of. You can see that there's kind of, I guess you can't see, but there's a author description about the kind of logic of the transparency that they were trying to facilitate and then there's access to all of the raw data files here. Then what we have is the actual annotated article. So this was, I think, a really innovative use of the ATI protocol. So this was a linguist who was looking at Scottish Annunciation. And so what they did was they would interview someone, ask them with an in-group that is someone from their community to say a set of words and then they would interview someone, record them with an out-group, someone was external to their community. They then do sort of a differential, right, of how people pronounce things with an in-group versus how they pronounce things with an out-group. One of the kind of challenges of this type of comparative linguistic research is providing reliable access to the underlying files and allowing people to experience or hear those files while they're reading a manuscript. And so if you click on one of those, it will take you to QDR where you can listen to the recording of the individuals, but we also had played around with allowing people to just listen within the browser. So while that they were looking at the annotations and looking at the text, they could listen to that sort of linguistic deviation. All right, and so I think this sort of has an analog, right, to what we looked at is the comparative advantage between a quantitative template and a qualitative template. What's emerging is a set of actors who can maximize what they're good at. QDR can preserve the data. Hypothesis provides a set of technologies which allow us to link that data and Cambridge coordinates or organizes this and puts it onto the web, hopefully in a sustainable manner. Okay, so some outcomes of ATI is pretty wildly dependent upon really whom is asked. So reviewers reported saying that they asked better questions, but it required more work to kind of sift through and make sense of and interpret the primary resources. So one individual said, in particular, I have more doubts with more transparency. I would argue as a social scientist, that actually is a pretty good thing for science. All right, so publishers have new modes of engagement, potential for on-ramps and discovery of articles through increased links to the content, both from our repository, but also from Hypothesis Discovery Tools that are built on top of that. Authors sort of were very much split. So there's increased opportunity for the criticisms of the claims that they're making because they're opening themselves up to new lines of criticism. So this person in particular here says, I feel more vulnerable to be honest and I'm not sure what my motivation is for incurring even more criticism. This person went on to explain sort of the feedback that they got, they felt like substantively improved the manuscript that they had under review, but they were super nervous then about responding to what would have been a publication which may have had a reasonably easier review process. Had they not annotated the article? Again, as a social scientist and as someone that supporting a scholarly web that wants to be more reliable, wants to be more transparent, I would argue this is a really good thing for science. We're opening up new modes of criticism, but that should hopefully improve the veracity of the claims that we're trying to make. Okay, so I'll end very quickly by saying one of the other motivations of this is to do all of the linking of annotations, all of the production of data and facilitation of this transparency in a way that's sustainable, right? So as a sort of data repository, we want to be authoritative stewards of a scholarly record, but we also want to do that in ways that will sort of promote annotations as first class research objects. And to do that, we need them to be citable, we need them to be discoverable, and we need them to be shared and reused in sustainable ways. So what our team did at QDR, working with the Dataverse software, which is an open source package so anyone can develop and use an implementation of it, is we created, this is probably hard to see if you're not close to a monitor, but we created in our ingest form, this is what individual data depositors are contributing their data to QDR, this is what they fill out. The ability to link a URL or a group through hypothesis, that is we call the hypothesis API once they enter this, and when they do, what we pull down is a JSON file which has all of the annotations that that author made. And so that author's annotations then come into our repository and become discoverable because we index that JSON object. So that means that we can search against and at the content of annotations, and we also have the links which are embedded to the documents in those annotations. We also, as well as just providing the object and the ability to search against that object created an individual view, which is just the HTML, or yeah, an HTML rendering of that JSON, which is showing the annotations out of context. So straight on the Dataverse repository, you don't have to leave in order to see the annotations and what they consist of. What this also allows you to do though is you can't see the radio buttons at the top, but it allows you to then just by the press of a button go out and find that article in its annotated context where we'd have the rich kind of HTML version of the hypothesis overlay. Or you can just download the file or download a compendium of files that are associated to those set of annotations. Okay, so to sort of sum up or to kind of wrap up what the thesis of the talk was about, we're empowering scholarly communities to collaborate and be cooperative in maximizing their comparative advantage. Publishers organize peer review and mark up the manuscripts. Software nonprofits like hypothesis provide interoperable features by building upon W3C web specs. And data repositories like QDR get to provide persistent identifiers, get to curate that content, and hopefully provide long-term storage and preservation of the data that's underlying the claims made in these scholarly articles. We have a number of future directions and we'd be excited to work with any publishers, any scholars, any people that are doing sort of the social science data archiving in general. One of these that we're pretty excited about is that the articles that have been annotated already, that is they've been published and the author returned and annotated them, we're seeing a boost in the activity flow to those pages, right? So we're seeing people visit the pages more often, we're seeing people download those articles more often, we're seeing increased traffic to those landing pages in QDR. I would say this is a pretty good proof of concept that this can be a sustainable model. So thank you very much for your time. I'd also like to say thank you so much to the hypothesis developers that helped us figure out a number of sort of finicky challenges around how we provide access through closed restricted groups. It was a huge benefit to us that was really paid off for the last two months. So it's been a beautiful collaboration and we hope to sustain it over time. So if you have questions for Nick, it would be great. The reason that we use the mics is not everyone can hear equally well as you and also we're recording and it helps make the recording audio good. So look, Steele's walking toward the mic now, he's approaching, he's almost there. I didn't get that bad for time either. Thanks for the great presentation. I had a question actually, something that was just tangentially mentioned on your last slide. You described a bundling tool as a future direction that would allow people to upload an XML or a Word document file with annotations in it that would become a PDF with anchored annotations. That sounds kind of mind-blowing and I wanna know what you mean by that. Me too. So this is a proposal that we've gotten a bunch of traction on from, the idea of a developer that's on our team. The basic idea is that when you're annotating a manuscript as you're writing it, you're oftentimes leaving notes to yourself and you're attaching data files within the annotation capabilities of a Word document. So that's just an XML encoding, right? We should be able to pull that out to take the file that's associated with that and to take the content of that annotation. And then through some maybe magic, this yet to be seen as whether we can do this, I assume Dan and other developers in the room probably have ideas about why this would be really hard, but be able to try to continue to manage the anchor of that text, right? So whatever the annotation is anchored to, we would try to preserve. If nothing else, that just gives us a bundle that we can ingest and then ultimately curate and if we have to do the annotation manually, it's taking a few steps out of it for QDR. If we can do that somehow automatically, it would be an enormous benefit to scholars that are right now, I think, really struggling with the authoring process. Yeah, so to be determined, I guess is the short way of saying that. So hi, very nice presentation. I have two-part question. One is you mentioned, I think, at the very end that you noticed that data sets associated with articles that had annotations associated with them received more usage or page views. Do you have any data to disambiguate whether this is simply a data linking issue or whether the annotation itself brought more users somehow to? It's exceptionally preliminary. I would hold it as far away from any sort of reasonable solid claim as possible. It's something that we've noticed right in the two months that these things have been published. What's particularly interesting, though, is that some of these articles have existed in their published form for about five years, some even three years, are seeing now a spike in interest. So that spike in interest could be for lots of reasons. It could be just because they were part of this and there's more people going to that. Colleagues are excited so they're sharing a DOI to that article again. But maybe not, right? It's something that I think would keep our eye on and hopefully if people that do innovative alt metrics work would be interested in it. And the other part of the question is, what is it? Oh, if I understood correctly, you showed how people can basically upload JSON annotations to your data repository, right? And that is a way for you to provide discoverability of these annotations. Doesn't that speak, though, to a non-met need for search for annotations on a wider platform rather than, I mean, this seems to be like a hack that you wanted to do to see what, is that? Yeah, absolutely, it's a hack, right? It's dealing with the annotations that exist that QDR has curated and people have uploaded. A sort of more greedy search which would go across different groups and across different maybe tags or collections would be, I think, beneficial. That sort of global search is something that I think other people could probably build tools on top of and facilitate. But yeah, I think that's a really good idea. It's also something we've thought about whether or not we would wanna maintain it and do it ourselves.


Part 2. Troubles. Chapter 3. An Inept Commander Takes Charge. October 18 to November 10, 1929. Although R101 soared through the air on its first flight, the airship was nearly destroyed only three days later, and the clear, still-afternoon air of October 18, R101 approached the mooring tower on its return from its second flight. Clang, clang, the gong in the nose cone alerted Atherston to an incoming message from Captain Irwin in the control car. Atherston pressed the voice pipe to his ear. Pay out main wire 600 feet at Irwin. Pay out main wire 600 feet repeated Atherston to a crew member. He opened a trap door below the largest of the three winches in the nose and shoved out a 150-foot loop of cable, a length that weighed enough to overcome the friction of the winch. As the winch storm spun, its cable clattered in a ring that prevented the cable from moving sideways. When 600 feet of cable dangled below the airship, Atherston commanded, Stop Winch. Stop Main, break on, said the winch operator. Main wire out 600 feet, sir, said Atherston, and do his voice pipe. Main wire out 600 feet, thank you, said Irwin, then added, short pause. As Atherston awaited orders, he peered out the small window in the nose. On the ground, 800 feet leeward of the tower lay the tower's main cable and two guy wires arranged in a T-shape. Near the T on the ground, a small cluster of men readied the tower cables to attach to the cables lowered from R101. Clang, clang, stand by to pay out Port Yaw Guy echoed through the voice pipe. Atherston repeated the order, and his main started the evolution of the first guy wire, the crew's term for lowering a smaller cable, which had to creep earthward and swing freely so it wouldn't twine itself around the other cable. Then, on orders for the control car, the crew evolved the starboard guy wire. With the ship's mooring cables now ready, R101 moved forward so the ground crew could catch hold of the beast, Scott's colorful phrase for connecting the ground and ship cables. R101's nose tilted toward the earth, driven down by its elevators against the ship's natural buoyancy, until a few feet of the ship's main cable lay slack on the airfield. The ship dragged it toward the man on the ground, who prepared to latch it to the tower's 25-ton cable. Atherston braced himself for the moment the cables were joined because, once they were connected, R101 would ascend as it dumped water ballast to draw the main cable taut and prevent it from tangling with the guy wires. That was the plan, at least. Instead, as its cable neared the ground crew, the airship dumped ballast, jerked up, and lifted the ship's cables beyond the reach of the ground crew. The dangling cable was carried by the gliding ship past the tower and into a small grove of trees. The snap of a branch echoed through the nose cone as the cable snagged on a limb. Although R101 yanked the cable free when it revved its engines and circled for a second pass at landing, this movement spun the guy wires wrapping them around the main cable. The gong clanged in the nose cone. Atherston listened for orders from the control car. Instead of Irwin's voice, he now heard Scott's. Scott had taken command from Irwin. R101 circled the tower and returned to try to catch the beast again. As it approached the tealanding, the ship's engines roared and its elevators tilted to bring it and the cables lowered to the ground. Instead, the ship remained level. It was too light. The release of ballast on the first pass had been too early, and it happened before the ground and ship cables had latched. The ship circled to buy time while the air cooled enough to decrease the ship's lift. The hydrogen in the gas bags was warmed by the sun throughout the day's flight. The superheating of the hydrogen above the temperature of the surrounding air increased R101's lift by three or four percent. This false lift would dissipate as the evening cooled. Meanwhile, Atterston and his crew worked to untangle the snarl of cables. They hold in a few feet until they reached a matted section, untwisted it, and then drew in another foot or so. Repeating this tedious task, they rushed to finish before sunset. Otherwise, they would need to use flashlights, a great inconvenience. Near six o'clock, three and a half hours after R101 arrived at the airfield, the airship dipped low enough for the ground crew to connect the ship's cable. The tower then hauled R101 in until the spring-loaded latches of the tower's arm clicked. Scott, still in the control car, issued the command, ship secured. Atterston's crew dropped the nose-cone hatch and shoved the bridge into position to connect ship and tower. Moments later, Major Scott lumbered across the bridge, shadowed by the graceful Lord Thompson, R101's advocate and the sole non-crew member aboard that day. The appearance of the two men contrasted sharply. Thompson tall with ramrod-straight posture, Scott squat with a slouch. Thompson's chiseled features radiated health, while Scott's pasty skin and black rings under his eyes conveyed sickness. Few would guess that Thompson was 13 years older than the 42-year-old Scott. When Scott arrived at the base of the tower, the reporters greeted him as a vigorous hero returning from a long voyage. Well done, Scotty, they cried. They still lionized him for his crossing of the Atlantic ten years earlier. In 1919, Scott had commanded the airship R34, a third the size of R101, from Scotland to New York. With his hallmark press on regardless attitude, he had flown the ship through thunderstorms, overcome unreliable engines that threatened to strand the airship over the ocean, and arrived in New York with enough fuel left for only 40 more minutes of flight. The voyage was so unsettling that Scott's crew demanded rum to calm their frazzled nerves, despite prohibition in the United States. After his Atlantic crossing, Great Britain celebrated Scott as a national hero. He achieved fame similar to that enjoyed by Lindbergh when he crossed the Atlantic eight years later, the 65th human to do so, but the first to fly solo. Scott's display of nerve on the Atlantic crossing earned him a reputation for bravery. Even now, ten years later, newspapers still extolled his press on regardless attitude, and the president of the Royal Aeronautical Society claimed no one had greater knowledge of the handling of such great ships than Scott. Indeed, Scott had invented the mooring tower shortly after the First World War, which led to the giant commercial airships Britain planned to build. Before the tower's invention, airship landings required a large, well-trained ground crew with precision timing. As the airship approached, the men arranged themselves in a V with the tip pointing toward the wind, and the airship pilot flew into the open part of their V, dangling a rope from the bow. When it hit the tip of the V, the ground crew grabbed the airship's rope. This step was the most treacherous because the pilot lost control as the airship slowed, and he could no longer use dynamic lift to position the craft. It became a balloon that either ascended or sank because of its buoyancy. Next, the pilot slowly released gas while the ground crew holed in the bow rope. The airship slowly neared the ground until the crew could grab the control car and guy ropes. If the ship sank too fast, the pilot would be spallased. If all went well, the airship gently touched the ground. However, as airships grew to the size of R101, ground landing became difficult and expensive. The ground crew blossomed from 100 to nearly 500, and the wind had greater leverage in the ship. Even a slight breeze could prevent an airship from landing or could trap it in its shed. If the ships couldn't land safely or couldn't even leave their sheds in high winds, Britain could not run a commercial airship service. Scott's mooring tower solved all the problems of landing a large airship. First, it reduced the number of people required to land the airship to around 20. Second, it enabled the airship to land or depart in almost any weather. Third, the tower offered an easy way to supply the airship with water, fuel, and gas without, as a technical journal put it, the incidence of risk which must always be entailed in transferring a ship to its shed. At the base of the tower, reporters awaited Major Scott's expert account of the delayed landing of R101. They leaned in as he began his briefing. His authoritative yet soft voice competed with the echo of clanking chains and shouted orders from the hollow middle dome atop the mooring tower. Scott explained that although it seemed a perfect day with little wind, a bright October sun, and clear air, in reality the air was full of disturbed currents rising and falling with varying temperatures. For this reason he decided to lay off for better conditions just as a ship lies off the harbor for the tide. Scott added that when he had more experience of the ship and the extent to which he responds to various conditions, he would have no difficulty in coming into the mooring tower. He also noted that the airship had returned early and the tower crew was not yet ready for it. Lord Thompson then chimed in, claiming that the delayed landing was caused by overzeal and a desire to be slick, adding that the ship was a bit light and the conditions for the mooring operations were unstable. No harm was caused and the delayed landing gives experience to the crew. The reporters distilled these comments into two words. Scott was in supreme command. Addiston, though, knew the truth. Scott watched the landing. R101 encountered no disturbed currents, nor did it need to wait for better conditions, nor did its arrival surprise the tower crew. Instead, Scott caused the accident with the mere twist of a stopcock that jettisoned water ballast. Fourteen tons of water were distributed throughout the airship and stored either in tanks or in bags, smaller in size and number than the huge gas bags, but no less critical to smooth flight. The captain used the water as ballast to adjust the overall lift to the ship or fine tune its trim. An airship might become light at its nose or its tail, either due to a gas bag leak or due to gas bags having heated unevenly by the sun. To redress this imbalance, the captain could, from the control car, use compressed air to ship to water between tanks distributed throughout the ship, or he could adjust the trim and the overall lift to the ship by selectively jettisoned water. The two water storage systems, the bags and tanks, were controlled in different ways. The water bags were under local control. To release this ballast, the captain sent a messenger to a rigor stationed at the bags, each shaped like a pair of trousers. The rigor would open each leg to rapidly empty them. The draining of the storage tanks, in contrast, was triggered directly from the control car. The tanks were connected to a pipe running bow to stern. At the control car, a T fitting connected a vertical pipe that passed into the control car and through its floor. Near the floor, a stopcock released the ballast from the intake. One twist and ballast was released during landing. Although this centralized control simplified flying the airship, it also let Scott Irwin moor in it on its second flight. Earlier that day, as Irwin aligned the airship to drag its main cable over the T of tower cables on the ground, Scott announced in his quiet authoritative way that he would now land the ship. As Irwin went near the ground cables, Scott spun the stopcock to release water ballast. His goal was to raise the airship and pull the wire taut, but he discharged the ballast too early, causing the ship to pass too high over the ground cable. He told reporters that inclement weather followed the landing. This was a serious error by an experienced flyer, which caused a three-hour delay but could also have destroyed the airship and killed those aboard. Yet Scott would not acknowledge his mistake. His actions and his dissembling afterward angered Atherston and Irwin, but it did not surprise them. They both had first-hand knowledge that Scott had destroyed airships. Eight years earlier, on June 21st, 1921, Irwin was preparing to land R-36, Britain's first passenger airship, a ship half the size of R-101. Although no passengers were aboard on this test flight, when it did go into service, passengers would ride in a cabin slung under the ship. This cabin would be a sitting room by day but be converted at night by curtains to bedrooms. The Times best captured R-36's passenger experience with a left-handed compliment. R-36's saloon, the paper wrote, was almost luxuriously comfortable. As Irwin brought R-36 close to the tower, Scott took over the landing. He miscalculated the ship's speed and it rushed toward the tower, fouling the cable at the bottom of it. It jerked the airship and ruptured the two forward ballast bags. R-36's nose rose and yanked on the mooring cable which collapsed the ship's nose. The airship hung canted from the tower. No longer could it ride safely there. The ground crew toiled for five hours to untangle the damaged airship, but as they released it and lowered it to the ground, the wind rose. To protect R-36, the current glory of the Empire, the crew prepared to move it into a shed, but the shed was already occupied by two zeppelins, forfeits from Germany under the terms of the Treaty of Versailles. To create space for the damaged airship, crew sawed one of the airships into pieces. It took another five hours until finally by 2 a.m. space was available, but as the ground crew attempted to move R-36 into the shed, Augustine Wynne rammed the airship into the shed doors, destroying the middle of the ship. When the sensitive Irwin saw the damage, he broke down because he knew that R-36 would never fly again. An inquiry exonerated Scott and blamed the accident on equipment failure. Despite this accident and others, under Scott's command, two more British airships were destroyed when they struck their shed doors. Scott's public reputation as an airship pilot soared. Privately, however, many at the works knew Scott was, in the words of one of his colleagues, a sick man, a euphemism for an alcoholic. If he were invited to dinner, Scott would drink two whiskey and sodas beforehand, three cocktails, a stiff whiskey at dinner, a liqueur after the meal, and then, if the partygoers attended the movies, he drank another whiskey there. Scott's visits cost us, complained one of the work's wives, a small fortune in drinks. Augustine himself saw the lunchtime gin that Scott often drank. He had impaired Scott's judgment, stripping caution from his natural inclination to press on regardless. His risk taking extended to his personal life, although married and the father of three children, he engaged in affairs. So public were these affairs that many at the works avoided a pub frequented by both Scott's wife and his current mistress. Scott's domestic troubles were intensified by his worries about the success or possible failure of R-101. I am probably, he told a gathering of airship experts, more interested in this airship than anybody else present. And indeed, for Scott to maintain his public acclaim as a hero and his status as a powerful figure in aviation, R-101 must succeed. R-101 must show that giant airships were destined to hefty empire's bureaucrats, workers, tourists and troops around the globe. Otherwise it would become a footnote in aviation history, a sterile attempt to connect all regions of the empire. And he knew that if R-101 failed, Britain would abandon airships as the nation had done once before. In 1921 the Air Ministry had halted all airship work and shuttered the Royal Airship Works. Airships were revived because of the immense efforts by Scott and others was support from Lord Thompson Nguyen in 1924. He became Secretary of State for Air. When this airship renaissance occurred, Scott hoped to be R-101's captain, but was assigned a larger role at the works. He scheduled the airship flights and set policies for flight procedures. His title was Assistant Director of Airship Development, Flying and Training, often abbreviated as Assistant Director, Flying. He was number two in the works power structure, only the director was above him. But Scott controlled R-101 because his opinions and flying were unchallenged by the director. Scott decided when and where R-101 would fly, which enabled him to take command of the airship whenever he wished from Erwin, the ship's captain. Scott commanded R-101 on its third flight when the ship circled over Sandrogym, the British Royal Family's country house in Norfolk. As the sun shone through the last wisps of fog on a crisp November morning, R-101 circled the Royal Estate three times while the king, queen and their young granddaughter, Elisabeth, the future Elisabeth the second, watched from a gravel path.  A few hours later, in the bright afternoon, R-101 approached the mooring tower at the works. The ship dragged its main cable toward the T of cables on the ground when Scott, unknown to Erwin, released ballast from the rear of the ship. R-101 plunged nose first toward the earth. The alert Atherston ordered ballast released from the front and right of the ship. The ground crew captured the ship's cable and the tower crew safely towed in R-101. Atherston fumed. He said the ship would have dived onto the ground if she had not been so light. Scott again caused problems on the ship's next flight. As R-101 returned from a long night flight, Erwin guided it in its tired crew to a smooth landing. The tower crew hauled in the airship. Erwin adjusted the rudder to meet the tower head-on and ordered the reversed engine to power up. R-101 pulled the cable taut. At this moment Scott took over. The wind changed direction and the ship moved crab-wise from the tower, flacking one of the guy wires and drawing the other taut, causing the ship to twist as it mirrored the tower. Erwin watched for the touch of rudder needed to ride the ship, but Scott did nothing. Suddenly a large metallic crack. Only six feet from the tower's arm, the giant ship lunged forward and broke a spring on the arm and the ship's motion wound a guy wire around the ship, crushing a small girder that held the cloth cover taut. Quick work by the tower crew secured the airship to the arm. Afterward Scott explained the accident to reporters. The ship is still perfectly airworthy, he said, but we think slight repairs necessary before we attempt another mooring. Scott's errors disturbed Atherston and the deteriorating Scott had become aloof, rarely communicating with Atherston and Erwin, the ship's captain. It would be rather more helpful, Atherston said of Scott, if opinions and recommendations of ship's officers were given rather more consideration. When Atherston insisted that Scott issue changes in flying procedures and policies to increase efficiency or to enhance safety, it was never done unless Atherston did much caging. Scott's scheduling of flights, his sole responsibility, irritated Atherston. Scott announced a flight with little notice. This caused Atherston to crash right into full flight within a few hours of taking over. Although this late notice upset him, even more unsettling was the type of flight Scott allowed. Atherston advocated for careful systematic testing of the airship, but what he got, he said, was window dressing stunts and joy rights. The precedent had been set when Scott had allowed Lord Thompson to ride a few weeks earlier on R101's second flight. This photo op diverted the crew from what Atherston called work that really matters, like calibrating the bow strain gauges at the tower head and forced them to engage in titivation. The passenger accommodation, Atherston said, got its face washed and hair brushed, all cabins, lounge, smoking room, dining room frantically furnished. This titivation included converting two births into a private office for Lord Thompson, who arrived with his secretary in a large suitcase of state papers. Also the reporters could swarm like earwigs, Atherston despised the press, around Thompson to hear his florid rhetoric. He enjoyed eating breakfast, lunch, and tea, entirely free from all outside disturbance, high up above all terrestrial dirt and noise. Thompson revealed to reporters that R101 would not soon travel to India. I am told, he said, that my hopes of making the journey at Christmas time will not be fulfilled. That does not matter, as I wish to make it quite clear that the men in charge of these experiments are not going to be rattled while I sit where I do. The delay claimed Thompson occurred because of the time required to build spare engines. In truth R101 could not be tested and ready in two months for a long distance flight, although Atherston appreciated that Thompson's time frame for departing to India had become more realistic, he worried about the Air Minister's reckless thoughts on airship operation. Thompson had told reporters that he regretted that the weather conditions were so fair, because he wished to see the behavior of the airship in rough weather. In every meeting with the press he stated that airships were all weather crafts and he chided the officers if they protected R101 from the weather. He was annoyed when R101 was transferred from tower to shed because of gale force winds, calling this action unnecessarily cautious. Thompson's interference diverted Atherston from important tasks. He should be testing the ship instead of hosting teas on board. He should be drilling his crew instead of playing nursemaid to visiting bureaucrats, and his crew should be running drills instead of cleaning up lunch splattered across the dining room. One of the many PR lunches Auguste of Wendt, Jossel R101 and Sint Dishes flying. Of most immediate distress to Atherston, was the imminent flight with 100 MPs. The airship would be taking a good portion of the Empire's government up into the skies with Scott in charge again. In his diary, written late at night aboard R101, Atherston railed against the flight. He thought it damned unfair of the air ministry to insist on flying 100 MPs on the untested ship. He worried whether the ship could even lift these 12 tons of MPs. How on earth it's going to be done? He wondered, and then despaired. I simply don't know.  He will be taking an absolutely unjustifiable risk with practically nothing to gain and everything to lose.