Ooh, look at your glasses. I love them, man. Well, thank you, Karun. Super excited to be here on the main stage with you guys. Thank you so much for joining us. I wanted to get the show started with some T-Mobile branding. That's why you see the T-Mobile branding. But let's get started with the main show here. Ever wondered what's this thing with the Joker? Are you trying to scare people out? Not really. That's not my intention. I'm sure everybody here at some point has seen the movie The Dark Knight, where Heat Ledger played the Joker and he did absolute justice to his role as the Joker in this movie. It's a shame he's not here with us today, but like they say, a wise man would live on forever. And notice what he talks about chaos, and he calls chaos a fair event. So let's talk about chaos, chaos engineering for Cloud Foundry. But before that, hang on. Violent, chaotic Joker, and now peace and charismatic Mahatma Gandhi. What's the connection? I don't understand this. I promise there's a connection to all of this. First off, I'm not a crazy guy to relate Mahatma with the Joker here, but Joker talks about chaos. The Mahatma talks about customers. And coming up from a family of medical professionals, my dad who's 72 years old, psychiatrist by profession, never loses focus on one element in his life. And for him, that's his customers, and his customers are his patients. So I always wondered what that perfect definition of a customer is. And in that search, I found this definition of a customer, and Mahatma summarizes by saying, like, the customer is everything. Indeed, the customer is everything. Moving on. This is our charismatic and energetic leader, Brian King, senior vice president for Technology Services Division and Operations at T-Mobile. In fact, this inspiration leader will not stop talking about his customers. Every stage he is on, he opens up with this mission statement, which is focused on delivering an awesome customer service and awesome customer experience to his end users. In fact, we're so proud of this mission statement that this year, we've launched this new campaign called Powered by TSTNO, where it's all about delivering awesome capabilities to our customers. And we fundamentally believe that somewhere, somehow we're making an impact on how we deliver capabilities to our end users. Thinking about Cloud Foundry, it's really that enabler for developer productivity. I'm sure you all know about it, where it focuses on helping your developers rapidly build, test, deploy software in the cloud. Our ecosystem with Cloud Foundry at T-Mobile is easily the largest in the world. We have 13 plus foundations, roughly 39,000 containers, 700 million daily transactions happening with 3,000 plus mission critical applications and over 100 plus project teams. Did you say 39,000 or 36,000? Yeah, good call. So, when I did the slide deck last week, it was around 36,000. And just recently, as of last night, we've just shooted up to 39,000. That kind of shows the revolution that the container strategy is having at T-Mobile. These numbers are not convincing. Focusing more on agility and agility redefined. Cloud Foundry is all about these rapid changes that it's bringing to our ecosystem. It's all about faster apps, more frequent changes, in fact, all day time changes, roughly 1,000 changes that have happened over last year, fewer incidents, zero downtime deployments, fail fast and fail forward, elasticity. These are some of the various benefits that Cloud Foundry's brought to our ecosystem. Everybody here knows that DevOps is a buzzword at many companies, but at T-Mobile, it's no longer a buzzword where we fundamentally believe that you write a piece of code, you code it and you own it all the way to production. Now, you may be wondering what's going on with all of these connections here. I spoke about chaos, I spoke about customers, I'm talking about agility redefined. But for me, the one thing that keeps me up is what's gonna happen with chaos? How do we focus on that delightful customer experience? Great. So T-Mobile is not a single application company. We have 3,000 plus applications belonging to multiple internal customers running in a shared foundation. So performing a chaos attack on the infrastructure is definitely going to create customer impact at multiple levels. Hence, we came up with the concept of performing chaos attack at the application level. So what it means is you take an application belonging to a customer, do a specific targeted chaos attack on that application and also its dependencies. So we have Turbulence++, an open source, it's based on a wrapper on an open source solution called Turbulence. And Monarch is a brand new open source solution from T-Mobile that we are using it for the application level chaos attacks. Let's zoom into the infrastructure level chaos attack. So Cloud Foundry is a collection of multiple virtual machines. So in this context, application instances are the containers they run inside the Diego cell. So what happens if one of your virtual machines goes down? What happens to the application instances or the containers running in it goes down? And what happens if a process running inside a Diego cell, say rep process, which is responsible for maintaining the lifecycle of the containers running in that Diego cell goes down? And what happens? Like Cloud Foundry is based on timeout mechanism like it's designed by default with a timeout. Now what happens if you're injecting a latency between the go-router and the Diego cell? All these sophisticated and very targeted, specific, proactive attacks can be performed with Turbulence++ today. Now let's look into the infrastructure level chaos attack. Like I said earlier, you can pick up a specific application and do a targeted, sophisticated attacks on your application and its dependencies without impacting any other application running in that Diego cell or in that cluster itself. That is what we mean by application level chaos attack. Now I would like to explain this with a demo. So if we have a front-ending web application UI, that's a Spring Boot application. And it is backed with an Apple and a Samsung microservices. Both microservices are back and with MySQL, a shared database instance. Now what can go wrong in this? Let's say the latency is injected between Apple and MySQL database. What happens to the UI behavior itself? And what happens if the Samsung microservice goes down? Imagine these are single instance of microservices. What happens if the Samsung instance itself get killed? And what is the UI going to look like? And what happens if the connectivity between MySQL database and the Samsung microservices blocked? So now all these three attacks can be injected with Monarch. Now we wanted to make sure the UI looks absolutely fine even when these attacks are happening. So that's the reason we are using Circuit Breaker, a Spring Cloud service on our UI component. So whenever the Circuit Breaker gets triggered, you will see the next generation, Apple phone and Samsung phone. I'll show you how it looks like. Can we go into the demo please? So we are using CFCLI and we are listing the applications. As I said, there are Apple and Samsung microservice with extra S and then there is a UI component to it. So these are the three services running, three applications deployed. And now these are three services. You have Circuit Breaker bound to only UI component and you have database service of Type MySQL and Apple and Samsung are the applications that are bound to this database. And service registry to discover all these three applications, they talk to each other. So you have all these three applications bound to it. Let's go into the UI. So this UI is a very simple UI. It's going to list random Apple and Samsung product by click of a button. So this button on the top, when you click on it, it makes a call to two microservice, Apple and Samsung service. And that's how it keeps listing all the Apple and Samsung service. Now, the response time is the time that it takes for like from the time at which the request is gone and the response is returned from the microservice. So you can see the response times here. So the UI looks good, right? So now let's get into the first attack. The first attack, we'll be doing it with Monarch is first of all, we need to discover where your application is running. So the first attack is on the Samsung service. So we use a discover API method is written in Python. For that, we have to provide where that application is deployed by providing org name, space name and the application name. In this case, it's Samsung service. So the first attack is on Samsung. So it takes a while to load the app object. Once you have the app object loaded, you are now ready to perform a block service attack on database component. So you are blocking a traffic from Samsung to P list hyphen DB, which is a database component. So when I trigger this, again, it takes a couple of seconds and then the block service is initiated by Monarch. And when you go into the UI, you see the next generation product of Samsung. That's the next generation. I love it. So what is happening here is a fallback service is getting called and circuit breaker is put into action without impacting the Apple microservice. There's no impact on the UI whatsoever, but still it's falling back on the circuit breaker. Now rolling back this attack is very simple. Use unblock underscore services and takes a few seconds and then once unblocked, you can see that the UI is back into action. There you go. So the Samsung is again back into action. Now keep an eye on the latency times there, the time taken by these two services before I get into the next attack. So the next attack we would be performing is on Apple service now. So the same thing, we go and discover where the Apple service is running. So we provide org name, space name, and app name. Once the discovery is complete, we're going to, yeah, just let's look at the UI. The response times are pretty good, like it takes 100 milliseconds, probably, yeah. Now I'm going to introduce latency by using a method called manipulate network. I'm going to inject 100 millisecond of latency with a standard deviation of 10 milliseconds. So when I do that, the app object is now manipulating traffic into the Apple service. As you can see, the latency of Apple is four times more than the Samsung service. So that's how you can simulate introducing latency at the service level or the service to the database level. So let's get into the third attack. Again, we just do the rollback of the latency attack by unmanipulate underscore network. Now, crash random instance. What happens if the Apple instance, the only Apple instance is crashed? How is it going to impact the UI? So I'm going to show you the CF events on the Apple, doesn't have crash events. And the UI looks perfectly fine. Now I'm going to trigger the crash random instance of instance count one on the Apple service. So when I do that, you go to the UI. That's the next generation Apple product. So it's falling back onto the Apple service. And the circuit breaker is into action. And Samsung has no issue at all. That's the beauty about Cloud Foundry, Circuit Breaker. So Cloud Foundry is self-resilient by default. So when an instance is crashed, it will bring back a new instance in its place. You can see the CF events of the Apple, the crash events are done by the Monarch. And if you see the application of Apple itself, you have the desired state and the actual state count set to one, which means the Apple is back into action and you have the UI. So that's the third attack. Now, can we go back to the slide, please? Yeah. So what do you think about this Monarch? Do you want to show this to your internal team? Yeah. I'm actually very impressed with the toolkit itself. So thank you so much for the demo. In fact, I want to take this a step further and talk about some of our Chaosim customers.  Chris and Rob are here somewhere with us. If not, they've been parting hard last night. Oh, I see you here. So these gentlemen are fond users of Cloud Foundry. They have several of the development teams who are our fond customers. And these are true inspirational leaders that are doing bigger, larger things with Cloud Foundry at scale. And one of the questions that often comes back to us is, what else can they do with Cloud Foundry? How else can they achieve better application resiliency? So I'm very excited to take Monarch back to them and say, hey, this is how we can achieve better application resiliency. So are you with us? Thank you, guys.


Preventing workplace stress is in everyone's interests. Per AXA Insurance Company, work-related stress costs the UK economy £28 billion per year, with around 23.3 million sick days taken. If you or your team members are not able to work, you or they can't contribute to company success. And a certain level of stress is good for productivity as it motivates us to be better and deliver more. Some stress is good. Once you go past the OK level of stress, mental and physical health problems develop over time. Without good health, so many aspects of your life are limited. Keeping your stress levels at or below an OK level for you and your team means more time at work and more capacity to do great work, as well as having a much more enjoyable time at work. These four big causes of stress in the workplace are worth learning how to avoid or at least reduce for you personally and for your team members. Firstly, being poor at saying no. Secondly, having difficult relationships with your boss or colleagues. Third, not getting the support and help you need to do your job well. And fourth, suffering organisational conflicts. I'll be explaining why each is a big cause of stress at work and how to deal with stress at work caused by each of these as an individual. I also provide suggestions for managers to reduce the impact of stress on your team caused by each of these two. My name is Jess Coles and if you're new here, Enhance.training shares people management expertise, resources and courses teaching you how to build higher performing teams. I've included links to additional videos and resources in the description below, as well as a video timestamp. So do take a look at these. And if you like this video, please give it a thumbs up and subscribe. So let's talk about how to deal with stress at work. One of the biggest causes of stress at work is being poor at saying no. Being overworked or unable to complete all the work you've agreed to do is very stressful. Nobody wants to be always working late or letting colleagues and bosses down. Neither are good for us personally. The teams where we work in or ultimately our companies. When you are poor at saying no, you are always going to be overworked. It is that simple. All companies I've worked in have more work to do than people available to do it. How to handle stress at work effectively starts with getting better at diplomatically saying no. Becoming good at saying no starts has been clear what is important to the team, your boss and the company. Prioritise saying yes to the important work and practise saying no as much as possible to the unimportant work. Companies, strategy and functional and team objectives are both good places to start to work out what is important. Next, ask your boss in what are the top five areas you need me to focus on over the next month. Keep asking until you get specific answers which ideally align with the strategy and objectives. Keep your focus on five areas or less. Pay attention to what your boss focuses on, what they ask questions about and demonstrate interest in. Learning how to say no diplomatically is so useful in how to deal with stress at work. How you say no is important. Always provide the reason why you can't do something you are being asked to do and ensure the why is clearly business related and not personal. An example might be I'm very sorry I can't add that to my list right now as I have five other deadlines which I believe are more important and these are and you can explain what they are. As a manager it is just as important for you to say no on behalf of your team as it is for you to get good at saying no on your own behalf. Stay close enough to your team so that you know and understand how much spare capacity they have at any time and how important what they're currently working on is. Both actions are vital in judging when to say no and how to say no on behalf of your team. Being good at saying no diplomatically is one of the best ways for how to manage stress at work. The second major cause of stress at work is having a difficult relationship with your boss or colleagues. Your relationship with your boss is the most important relationship you have at work because of the daily influence they have on what you work on and how your career progresses. Have a difficult relationship with your boss and your stress levels will be a lot higher and dealing with stress at work a lot harder. Reduce your stress at work by proactively managing your relationship with your boss. Even if they're a nightmare boss the following actions will help improve your relationship. Firstly work out how you're going to help your boss. This starts with your mindset. Then actively seek out what they are focused on stressing about or struggling with and work out how you can help them even if it's just a small bit of help. Secondly focus as much of your work as possible on areas that best help your boss meet their personal and team objectives. Speak to your boss and find out what they really want you to work on. Third train yourself to actively look for areas that you admire about your boss. No matter how horrible they are they will have good points find them focus on these areas and compliment them for what they do well.  Fourth work on finding out your boss's interests and passions and get them talking about them. Do some research so that you can contribute to the conversation even if it's just demonstrating a desire to learn more. Fifth be a good team player and help the team do better in any way you can sensibly can. Every boss likes team players who are trying to push team members to hit team goals. A great way to reduce stress at work is to work on improving your relationship with your boss. Many of the approaches we have been through work equally well for improving relationships with colleagues. Work consistently and expect the improvements in relationships to take a little bit of time. The third big cause of workplace stress is not getting support and help to do your job well. Yet I've worked in single swim environments and I know how stressful it can be to trying to deliver on your job without very much support or help. Getting support and help to do your job well comes in many forms including if firstly understanding what exactly is expected of you and having clear direction. Secondly having clear job responsibilities and boundaries. Third being protected from interdepartmental politics and the maneuverings of those more senior than you. Fourth getting helpful and considered answers to questions that you have. Fifth being listened to and actions taken to sort out problems that you're experiencing. Sixth working in a team in which team members help each other out and work together towards common goals. Seventh being coached through dealing with the many people challenges that all managers face. And then eighth being given the right resources at the right time. Trying to learn and do your job well by trial and error takes a lot of time is stressful and usually gets you to okay rather than great. And there are lots of sources of help outside the digital route of speaking to your manager which covers much of the list that we've just gone through such as books, courses, mentors and coaches. You should absolutely help yourself rather than expecting to be spoon fed. For example you could write your own job description and agree it with your manager. You could set your own objectives aligned with the team or functional goals and agree then with your manager and so on. Proactively take steps to get help from any areas outside and inside of work. Yes your company should be helping you but if they aren't why go through all the stress of not getting help from elsewhere? When you are managing a team try to provide as much support and help to your team members as possible and do this as proactively as possible. They will experience a lot less stress and be able to handle stress at work that much better. The fourth major cause of stress at work is suffering organizational conflicts. Organizational conflicts are fairly common. A classic example of organizational conflict could be the sales team are targeted with increasing sales and the finance team are targeted with increasing profit. With very different goals the two teams are going to experience conflict with each other. How to manage stress at work in this situation might be to task both teams to work together to grow gross profit. Differences in goals at team, functional and business unit level create conflicts. For managers the best way to reduce conflict is to work on creating more aligned goals. The stress levels will drop and team working will increase which will increase performance. Alignment of goals within a business reduces conflict and stress and increases the effectiveness of teams. Competition for the limited resources within a business inevitably create conflict and stress at work. Managers are best placed to negotiate on behalf of their teams and should focus on what use of resources is best to reach business goals. Different processes create conflicts and stress at work when they are not aligned to goals or seek to achieve conflicting results. In an example might be processes and systems to standardise contractual terms so the business can scale more easily conflicting with sales teams processes to promote contract flexibility which helps drive higher sales. When you spot organisational conflicts or are on the receiving end of conflicts either negotiate changes to the source of the conflict or highlight to your boss the conflicts. Explain why they are happening. Ask your boss to take action to minimise the conflict. This will reduce the workplace stress experienced by everyone. And managers should be on the lookout for organisational conflicts and minimise the workplace stress caused by changing or minimising the cause of the conflict wherever possible. So in summary there are lots of reasons that workplace stress does arise. How to deal with stress at work is important particularly when it's outside your personal control. Practise saying no on your own behalf and then on your team's behalf. Say no diplomatically and always provide the business reasons why you are saying no. Take proactive steps to improve the relationship you have with your boss and your colleagues. There is a lot of actions you can take that will make a big difference quickly. Improve these relationships and you'll have a lot less stress at work. And when dealing with stress at work think about what help and support you need and how you might get help earlier when stress levels are low rather than later when stress levels have got too high. And finally look out for organisational conflicts which are causing workplace stress for multiple people or teams. Change the causes of stress at work by minimising or removing these conflicts. If you have any questions on preventing workplace stress for major causes of stress and what to do please leave them in the comment section below and I'll get back to you. Thanks very much for watching and I look forward to speaking to you again soon.


The program you didn't even have a proper title of the presentation just mentioned you from data side. This is because I'm a sort of last minute invited to this session. Normally, there should be a more technology related speaker here, which what I am not, but the technology guys weren't available, obviously. So this is a slightly more general presentation about data side, but I come to technology at the end. I start talking a little bit about do is and also about publishers. So this is here you see a table of contents of a journal, which is, by the way, high impact factor open access access journal, nuclear acid research, and you have in all these articles, you have the do is this is well known. This is used by almost all publishers. Now these do is are provided from crossref. And if you go into the detail of one of these articles, and you go, the do is mentioned again, when then you go into the references and the bibliography list, then you have all these references where it's mentioned crossref and if you're clicking on crossref here means you click you go to you link to another article via do I. This is not standard standard presentation in some cases presented differently here it is by clicking on crossref. But the the principle behind is that you this is what is called crosslinking and then you get go to the article the next article and which has another do I and so on. And we think that in this chain of the resources linking data set data sets should have the same should be should be linked to in the same way as articles and this is something that that is starting to happen. Of course you can happen to you that here in this particular case probably this this will this will be the case that you haven't access to the to the to the full text for data. This should be slightly different because, for instance, we had something that we often remind within data side this publishers Brussels declaration and STM publishing where they say, for instance that raw research data should be made freely available to all researchers. And in particular sets of subsets of data that are submitted with the with the paper to a journal should wherever possible be made freely accessible to others. So this is something that we normally should always remind the publishers this declaration staying staying with publishers. You also know that many publishers require as a condition for publication to make the underlying data available for pure you in particular and not only this is from from nature. Not only they want to make it to make them they require to make them freely available but they also indicate precisely what kind of data in which discipline should be put in what kind of data repository. And then we have something different. This is an Elsevier journal and there you have the guide for authors guideline for authors and there is something called data at Pangea Pangea is a very important big data center in earth sciences in Germany. And they have a good agreement with with Elsevier in particular particular about bidirectional linking of day of articles and underlying data sets. So if you have a look here this is this is made this is explained in the in the in the guidelines. As soon as it will be startable you might want to refer them to them in your article and in any case data supplements in the article will be automatically linked. As in the following example we will see the example and then they also also also say that the eyes are guaranteed never to change. In fact what is guaranteed never to change is what what is behind the do I think this is the idea of persistent identifier. So and then this is still from this the same journal. This is how it how it works in practice. You have the the article and you have a button to click on to go to the data set and here's even a nice additional application with Google Maps where you can see what what this where this happens because it we're in the earth sciences here. This is the do I home page the international do I foundation home page in fact and do I's are registered by registration agencies if you want to have a do I today you have to contact a registration. Typically your local what I would say registration agency and data side is such an agency. And what we could what can also be mentioned is that do I's are now since last year I think in an ISO ISO standard and you may also know that do I's are strongly linked to handles and this is the home page of the handle system which is developed by the CN CNRI which is cooperation for national research initiatives yes cooperation national research initiatives in the US and and in fact technically it's the same thing on the do I web home page. They you can read this they say at the infrastructure level do I names are handles because sometimes there is some confusion about it. Do I's are opposed to handles but it's they're not exactly at the same level. Some two or three slides from from a workshop I participated in in 2011 knowledge exchange workshop on persistent identifiers and handles were presented. Do I's were presented others as well but I focus here on handles and do I's and you can hear the list of you of users of clients of handles and IDF is here. Listed international do I foundation as such a user of handles and in particular. Below the IDF you see the different today existing agencies there are not so many crossref and data sites being being the two main today and then in this workshop there was a particular question put to. Yes though this to highlight that IDF is user of handle it was a particular question on quality of persistent identifiers put to all those who were present and hand this is the was the answer of handle. They say use is not actively monitored and they also say that prefix holders must agree to be good citizens something like that. And do I goes much further than that and at this to the same question was do I answer the question do you have a policy on quality of persistent identifiers. The answer was yes this is the result of our organization that's what we are there for essentially we want to build this trustworthy infrastructure needed behind behind this identifier system. Okay oh yes this is slide shouldn't be there it's a French one but nevertheless this is the French Wikipedia page for for for DOI where they you very usefully point out that first of all do I say in fact special cases of handles that do I has this social what they call social infrastructure. And we also should also be mentioned that digital object identifier is to be interpreted in the sense of digital identifier of objects not digital. Not identify our digital objects because do I names maybe of any form digital physical abstract but this becomes a bit philosophical but something that should sometimes the question was put to me do you do we have also physical physical entities can we can we assign the eyes and the answer is yes. Now I come to data side data side global consortium carried out by local institutions focused on improving this the scholarly infrastructure around data sets promotion of data sets in the information services in particular. Initially but not exclusively based on the UI system we are we have members who register handles of course but also things like arcs. It started all in 2009 with with just six members six research libraries. Well yesterday there was some discussion or comments on the future of research libraries. This is an initiative in which research libraries engaged in three years ago. We were six and today we are twenty two seventeen regular members around the world and five affiliated members members that just support data side but we don't assign the eyes themselves. The different roles of the data side registration agency on the one hand and the what we call publishing agents a generic term for data centers research institute data publishers. In particular it is important to point out that the publishing agents data centers remain responsible for quality assurance storage. They also create the identifiers and they have to create and update the metadata we the data side members sign agreements formal agreements with with the publishing agents where all these. Responsibility responsibilities are mentioned. What type of what type of data are we talking about anything we have a very broad definition of of of data here you have some you have some some examples. We have for instance a member who essentially assigns do is to great literature. But of course the the the idea is that the the the large majority of objects should be and will be and are already data sets. But in fact it's anything data is anything that is a foundation of further research. Data is evidence in fact. This is a structure we are a member of the International Doi Foundation. And as such data site pays a membership fee and the member institutions in that turn that don't pay a membership fee to the data site. And as I said the data centers have to contact up one of these member institutions to to to get the eyes. Bridging the gap here it is the case that is also your your your goal. But here it is particular the case for bridging the gaps between publishers and data centers. And there is a formal sort of agreement with Crossref who assigned the do is for for article journals for journal articles. And they as it is mentioned here data site and Crossref have committed to the interoperability of the do is. And there should be this what we call bi-directional linking between data articles and data. This was formalized or officialized last year by a formal statement between STM the publishers association and data site on best practices on. On making data available on how to site data. And this statement was then also joined by Crossref later. As I said we will see an example that we have here a data set which is a supplement to an article. This is a data set within this Pangea data center. Here's the the record of of this data set data description on the Pangea platform. And then you see that this is a supplement to an article the article itself as a do I you click on the do I you go to the article. And on the bottom on the right there have this supplementary data button button and you can go back by clicking to the data set. Which in the gap to sum up we data site provides services for for for the different. Players involved the researchers themselves the data centers and also the publishers and then you see a long list of services. In forms of specific URLs related to to to data site. And I just mentioned some of them also what the data site has has a lot of a lot of some working groups on specific topics. Like for instance the metadata working group who has worked worked for the release of the metadata schema that was mentioned yesterday. Metadata store this is this is the the DIYs have can only be created minted as we say together with metadata. We have a limited number of mandatory fields in our scheme. And as we heard yesterday for the for the need for the purposes of open air plus this would have would have to be changed. Although in principle you you would as far as I understood use this this metadata scheme. This is more formally an interface for data centers. In fact, a well organized data center does not is rather autonomous in creating their their their DOIs they just link to this to this platform. We are just giving them an access code login and then they can create the DOIs and they they upload the metadata. And this can then be these metadata can be searched for this is the French interface. In fact, this what we call MDS metadata store is kind of central portal allowing access to the metadata from all registered objects. In particular, it's can be harvested via or I or I or I PMH. So this is the you find this the schema on the on the website. We are at version two to but the version two three will come out in the in the coming months I think you have also the XML. This is the document you can you can visualize on the data site on the website. This is the XML version that you can see as well. And this is the search interface. We have a simple search here. We have also an advanced search and I as an example I looked for for the from the advanced search. I looked for I looked for Minio and I wanted to see a data set. Not sure because the general resource source type can be things like text of video. Yes. Databases and we have general resource type and we also have resource type which a bit more specific. You can have thesis and reports and things like that. And I saw just one result. And then if you click on the do I hear you go in fact to the landing page of this data set. And this was a data set hosted by the UK data archive. And they received the do I from the British library and then you can download if you have the the right to download. Of course talking about open data we always encourage all our data centers all our customers to make the data as open as possible. But this is not always the case. And at least there should be some information on how to get the data. This is something that is made precise in in in the contracts that we signed with with data centers. This is some information about harvesting that you find on our website. And then something that this is becoming slightly a technology more technical data site content resolver. It's a service for displaying data site metadata in different formats. And if you make a search you you see all the formats that in principle are available. And this can be done. This is also done by Crossref and even in cooperation with Crossref. This can be done either by something that is called content negotiation. It becomes a bit really a bit technical documentation that you have on the bottom is about that. Or by using the DUI proxy the DUI proxy is the DUI formulation as in URL. The form you see here is the sort of gateway between the handle server system and the HTTP. And you can put in a URL of this form and then specify the type the mime type type which is the the the internet format of the of the resource. It can go directly to the data to the metadata in the requested format. So I have two slides about explaining more more detail how content negotiation works. But I think I have to skip them. These are the slides. So I go don't go into the details here. And just to mention that we have also a list of repositories of research that are within our services. And you may know that Thompson Reuters has created launches like data citation index and they started they all want to work with data site. They started to to to all these repositories that were listed in on our website to to get in touch with as a starting point. Orchid and data site work together in a European project called Odin. It's about connect information across multiple servers and infrastructures for scholarly communication. Orchid is the author or contributor identifier initiative. And we are also involved data site is involved in a group in a co-data group on data citations standards and practices. Co-data was mentioned yesterday by Jeffrey Bolton together with Ixu as one of the international bodies who can could possibly do much advocacy work for open data. And I think this was almost the last one. Yes, and we had just a colorful slide with all the logos of our current members. Thank you.


Have a quick listen to this mix, preferably not using your phone speaker and try to spot what's wrong with it. Hi folks, I'm Mike and I hope you're well. Hopefully you spotted that that mix was extremely lacking in the high frequencies and was sounding kind of muddy and you could correct that in the mastering process or by applying high frequencies to individual tracks in the actual mix and that would fix it right. But what if your speakers were lying to you? What if those high frequencies are actually fine and you've now added them unnecessarily and actually ruined the mix? Well, regular speakers actually do lie to you and so will studio monitors if you're not using them correctly. So today we're going to be looking at why we use studio monitors and how to use them correctly. And I'll also be explaining why I'm now delighted to be using these new Adam Audio A7Vs. So I'm assuming that you wouldn't actually use your phone speaker for mixing even if you could, right? Right? And that's because you instinctively know that these speakers are extremely lacking in certain areas, especially in the low frequency ranges. And the same is true for other regular speakers, especially the type that you would use for a hi-fi system. They'll either be hyped in certain frequencies or exaggerated, or due to low cost manufacturing and components just won't be that great. And that's fine. They're not designed to be tools for critical, accurate listening. And that's where studio monitors come in. Most studio monitors like the A7Vs are near field monitors. They're designed to be used within a few feet of the listener at ear level. Ideally, you'll form an equilateral triangle between yourself and your two monitors. Now unlike regular speakers, these will have amplifiers built in. They also have the connections you require to hook up to your audio interface. Now these are superior than regular speakers because they're built in amplifiers can be tailor made to the speakers or drivers inside. Now some studio monitors have many drivers, but most near field monitors will have two, a woofer and a tweeter. The woofer in a monitor takes care of the lower frequencies. In the case of the A7V, which reaches as low as 40 hertz, we have a seven inch multi-layer mineral woofer, which gives a cleaner response and less distortion. We also have for this woofer a dedicated 90 watt amplifier used specifically with it in mind. It's this kind of attention to detail which separates these monitors from regular speakers and even from lower quality monitors. Tweeters are used to hear the higher frequencies, in this case up to 45 kilohertz. Now we commonly see them in a dome shape design, but I must say I do prefer these ribbon style tweeters that we see on the A7Vs. I've just found that during long sessions, not only are they accurate, but they do help to reduce ear fatigue as well. Now these particular tweeters have a dedicated 15 watt amplifier and you may have noticed this shaping around them. This is called the wave guide and it's not just cosmetic. It actually affects the way we hear and use these monitors, but more on that later. Ports or the large holes that we see in studio monitors are there to relieve pressure so that the woofer can move more freely and depending on their size and position, they will affect the perceived frequency response. Now if you buy monitors that have rear facing ports, do make sure that you don't have them right up against a wall. Ideally you want them to be at least six inches or so away from the wall. Now these A7Vs have forward facing ports, so they're really versatile in terms of positioning within a small studio especially. Apart from making an equilateral triangle as we discussed earlier, I do find that I get the best out of my studio monitors if they're on stands and placed with the tweeters at ear level. I find that monitors which are placed on desks reverberate through the desk and really do muddy the sound. So definitely one of the cheapest ways that you can really improve the sound is to get your studio monitors on stands. Now the wave guides in these Adam A7Vs tend to disperse the sound horizontally. So you can still get a decent sound actually even when you move from your central position. However they do come into play also when we're talking about speaker orientation. The V in A7V denotes vertical which means that these monitors are intended to be used in a vertical orientation. Now as we discussed earlier, the woofer and the tweeter in a monitor handle different frequency ranges. The signal is split between the two and then great care is taken in terms of timing to make sure that it leaves both of those drivers at the same time and arrives at your ears at exactly the same time. But for that to work we have to have the same distance between your ears and the tweeter and your ears and the woofer. The problem is when we change the orientation of a monitor and we turn it over onto its size we can change those distances. The sound can arrive at your ears at different times and we can get phase issues which can greatly affect the accuracy of what you're hearing. Now thankfully with these A7Vs Adam Audio have allowed you to rotate the tweeters inside to a different orientation to help with that. And if you did angle the speakers in more aggressively towards you you could make those distances the same and get a decent experience. But for me personally I still prefer to use them in the vertical orientation. Studio monitors of course exist in an environment, your studio where you're not only hearing the monitors but you're also hearing reflections and build-ups of frequencies as well. So I believe that you must use studio monitors in a treated room. Now that could range from DIY solutions making the best of what you already have to professional solutions which include broadband absorbers, bass traps, clouds and diffuses etc. But even the best of studio monitors won't be helpful to you if you're in an untreated environment. Now in terms of tuning your studio monitors to that environment I will say that these A7Vs have some great features. The rear panel of the A7V reveals four bands of equalization so that we can tune our monitors to our room. We can even use the Adam Audio software to make these adjustments from the comfort of our listening position. But how do we know which adjustments we need to make for our room? Sound ID reference is a system for analyzing your room and determining how the output needs to be adjusted to account for it. It essentially outputs a profile which you can use within a plugin in your door to correct the sound for mixing.  Now Adam Audio with the A7Vs have cleverly allowed us to be able to upload your sound ID profile to your monitors correcting at the monitor level so you don't need to use a plugin in your door anymore. In fact you don't even have to have a computer connected. If your room is untreated then you may still be better off with a good quality pair of studio headphones. However I still believe that the ultimate mixing experience is with good studio monitors in a well treated room. Studio monitors are designed to have a wide flat frequency response and have features leaning towards someone doing mixes for many hours in a studio environment. You will hear things with these monitors that you can't hear on other speakers and if you can't hear things you can't fix them. Now of course better design, better quality materials and even better manufacturing tolerances will result in more accurate sound and that's why moving forward I will be sticking with these Adam Audio A7Vs. Unfortunately however they have already revealed to me some problems with my older mixes which I hadn't noticed at the time. Are these budget monitors? No but I do feel that with that extra you pay you do get noticeably better results. Check the links in the description below to find out how much they cost in your part of the world. Now if budget is still a problem for you I can still highly recommend my previous monitors the Adam Audio T8Vs. I made a review about those a couple of years ago which you can watch right here.


Nick Nocturne is not an SCP, but if it were, how would the SCP Foundation contain it? Nick Nocturne is the designation for the Keter Class Demon-Human Hybrid that runs the YouTube channel Nightmind. Nick's demonic capabilities are in line with Foundation understanding, shape-shifting, greater-than-human strength at human size, creation and manipulation of hellfire, spirit manipulation, etc. The entity's weaknesses are also well-documented, subject to influence of those who know its true name, as well as various sigils and wards of the Abrahamic Fates. Unfortunately for our containment specialists, we have yet to discover the true name of this entity, and as a child of the first demon, Lilith, the power of the necessary wards is currently beyond Foundation knowledge. Even SCP-4357-J, our best source of advanced demonic containment procedures, is unwilling to talk about wards at that level. Due to our inability to successfully contain Nick, the next step in maintaining normalcy would be destruction of the entity. While within our capabilities, doing so would cause a level of collateral damage and civilian loss of life equivalent to a medium-sized city. Not that we wouldn't disappear an entire city, consider the case of Stockton, South Carolina, but we like to avoid that whenever possible. Luckily, Nick is also half-human and has taken a liking to living a mostly human lifestyle. This allowed the Foundation to work out a truce with the entity. Nick maintains public-facing normalcy, and in return, the Foundation doesn't have to resort to extreme measures. On top of that, there is the added benefit that the Nightmind YouTube channel does lend a hand in research of anomalies from time to time. That's a gift horse who's hundreds of demonic mouths I am not looking at. Make sure to like and share this video, comment any creatures you would like to see containment procedures implemented for, and if you want to help us make bigger and better SCP projects, become a patron at the link in the description. Secure, Contain, Protect.