FAIR Data and Software - Summary

Video thumbnail (Frame 0) Video thumbnail (Frame 542) Video thumbnail (Frame 2863) Video thumbnail (Frame 3513) Video thumbnail (Frame 6423) Video thumbnail (Frame 6839) Video thumbnail (Frame 7543) Video thumbnail (Frame 7944) Video thumbnail (Frame 8434) Video thumbnail (Frame 8828) Video thumbnail (Frame 9640) Video thumbnail (Frame 10070) Video thumbnail (Frame 10847) Video thumbnail (Frame 11327) Video thumbnail (Frame 11904) Video thumbnail (Frame 13090) Video thumbnail (Frame 13452) Video thumbnail (Frame 14928) Video thumbnail (Frame 15422) Video thumbnail (Frame 16692) Video thumbnail (Frame 17343) Video thumbnail (Frame 17940) Video thumbnail (Frame 18965) Video thumbnail (Frame 20148) Video thumbnail (Frame 22956) Video thumbnail (Frame 23322) Video thumbnail (Frame 25029) Video thumbnail (Frame 25428) Video thumbnail (Frame 25880)
Video in TIB AV-Portal: FAIR Data and Software - Summary

Formal Metadata

FAIR Data and Software - Summary
Title of Series
Part Number
Number of Parts
CC Attribution 3.0 Germany:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Release Date

Content Metadata

Subject Area
Web page Group action Link (knot theory) Planning Expert system Group action Open set Information technology consulting Virtual machine Local Group Degree (graph theory) Type theory Software Point cloud
Point (geometry) Information Group action Expert system Open set Information technology consulting Virtual machine Local Group Degree (graph theory) Type theory Software Different (Kate Ryan album) Well-formed formula Software Energy level Office suite Point cloud
Point (geometry) Complex (psychology) Group action Identifiability Online help Expert system Disk read-and-write head Field (computer science) Local Group Degree (graph theory) Type theory Software Form (programming) Physical system Focus (optics) Key (cryptography) Software developer Feedback Projective plane Interactive television Planning Bit Group action Open set Virtual machine Hand fan Data management Message passing Software Freeware Arithmetic progression
Degree (graph theory) Type theory Repository (publishing) View (database) Software Expert system Group action Open set Virtual machine Point cloud Local Group
Degree (graph theory) Type theory Internet service provider Software Group action Expert system Open set Virtual machine Local Group
Source code Slide rule Greatest element Coding theory Network topology Software Library (computing) Local Group Local Group
Source code Projective plane Source code Student's t-test Vector potential Digital object identifier Revision control Data management Telecommunication Time evolution Single-precision floating-point format Software repository Smoothing
Axiom of choice Scripting language Scripting language Multiplication sign Computer program Archaeological field survey Code Software industry System call Computer Goodness of fit Very-high-bit-rate digital subscriber line Personal digital assistant Function (mathematics) Software testing Computing platform
Scripting language Module (mathematics) Execution unit Information management Functional (mathematics) Building Line (geometry) Feedback Computer file Code Online help Computer Formal language Type theory Software Personal digital assistant Function (mathematics) Code refactoring Energy level Software testing Code refactoring Software testing Process (computing)
Programming language Functional (mathematics) Feedback Weight Computer file Code Computer programming Variable (mathematics) Formal language Revision control Mathematics Function (mathematics) Software Code refactoring Website Software testing Software testing Process (computing) Chord (peer-to-peer)
Feedback Multiplication sign Computer file Code Test-driven development System call Neuroinformatik Type theory Function (mathematics) Code refactoring Software testing Process (computing) Mathematical optimization
Programming language Benchmark Control flow System identification Measurement Mathematical optimization
Game controller Multiplication sign Control flow Mereology CAN bus Word Wiki Benchmark Personal digital assistant Function (mathematics) Software testing Quicksort Cycle (graph theory) System identification
Multiplication sign Series (mathematics) Cartesian coordinate system Table (information) Neuroinformatik Task (computing)
Curve Personal digital assistant Software developer Multiplication sign Object (grammar) Average Mathematical optimization Task (computing) 2 (number)
Personal digital assistant Multiplication sign Projective plane Computational science Principal ideal domain Average Digital object identifier
Type theory Software Personal digital assistant Archaeological field survey Software Information Line (geometry)
Data management Programming language Slide rule Software System programming Videoconferencing Software framework Neuroinformatik YouTube Row (database)
Point (geometry) Slide rule Greatest element Blog Software Projective plane Electronic mailing list Bit Open set Hand fan Storage area network God
so under fair principles just Willard Priestley I would like again to
highlight does open consultation on the fare detection action plan it's on the
giver page here is the link here and not much has there has been happening since it was opened in an and
in June the consultation was opened in June so where please if you want also to be there but on a more on a higher level and 1 2 you want you wise to be head hurts that they have you feel free add to what's your opinion on how to put 2 and the uptake of principles into practice another important point fear that does not mean open and also not open and data we account other lots about this aspect in the in the last couple of days but it is also 1 of the the messages please they take it home and as they die and stuff they can also be fair if it's protected if there are if their sensitive information included so Please do not hesitate but also try this credo as close as necessary as open as possible we learnt that there are different decrease of fairness in the last couple of days also regarding and to such disciplines many of you are also mentioned examples formula where we experiments and AIX experience in dealing with the data and we search software so again thank you also for the this I think Kathleen and I we will also take a lot of you're experience there and back home and will try to improve this verb also according to the examples you mentioned again in a little to the office most if you of
the I haven't value-added than they did not they covered his this weekend we will need some West kids can have that and the the
again also please if you if we if you add a few if their size as something you still want to mention of this may be an example of the only search and discipline that you want to be maybe to have included in the upcoming workshops please also feel free add to include
this in this and I'm so we form and of free text field had to include any more feedback so also if you did not have the chance in this project to in this but to mention it yet it's it's just popped popped up there recently then just please feel free and 2 use this feedback form and of course the and it's all it's all and shows the legions so as we have learned to there is a new development and they're coming and it came up 2 thousand 16 apart head besides the couldn't fear of course and there the points a warning it's like yeah this is an identifier systems and so on they have been alarmed too much Norma as so actually defended the Phayao principles again Web 2 highlights this focus on machine-to-machine interactions we had a little bit about data management plans and a it be on a new side to suffer management plans and said the whole that of course more complicated and complex issues about and licensing I had just as we heard of today to have which help keep and data and software fan but as we have heard a lot of it is there in the 2 still in a transition progress and maybe the most important message here is you as we suggest you as scientists you I've had the key messages in new institutions you can communicate what you have heard in the last couple of days with in your institution and with fewer a fellow we searches and we strongly encourage you please do that also maybe point out some critical aspects your effort at point out that
imposes personal views and opinions and some things you want maybe to improve so please take this home please open up the discussions go to dig it up pages and make our comments Please we have that do as much
as you like and the comment and was also criticism as much as you like because only in this way also dare repository
providers politics only dissuade will start at to change and change it according to your demands and according to add to their things you want to have improved and the again depending
on the discipline of course the can be made easier to implement in your daily work as a researcher or it can be more hot but nevertheless you should maybe just try to start doing it
yes and before that I would like to end would that thing is saw some summaries from the last 2
days so these slides are mostly copied bottom we learn about the cop trees as well and again if you're interested to to set up some local group here please contact us that we can discuss later as well this 1 there we go
so we are about to forget and i'll that I convinced you that version controlling your project leads to a a good this novel had that leads to a to a self-explanatory in the history of your project which is helpful to you in the future
to students to your colleagues to everybody wells interacts with it and in particular this idea of having a single source of truth for everything
that you do will the documents that you create for the call that you write for the the issues that you collect so these platforms have worked for software companies to solve these problems to work effectively and efficiently at high speeds even in some cases in many cases so I think they are really a good choice for scientists as well that's
the then we talked about how how you should to improve your a cold so most of you have stated that they have written script so far and we're very happy that already in the time between filling out the initial survey and coming years many of you have already started
using functions on your own and do we hope that our our lessons both and pi bond and help to improve the skill even further we also talked about packaging and building modules in both of these cases syllables of these languages and again all 3 of these steps scripts functions packages they solve specific problems are not inherently quality level so don't don't feel bad if your problems already solved by a nice short concise then some general remarks
because so yesterday we briefly touched on this refactoring and software hygiene and that and everything prepared then but It's just generally say that this type of activity is accessible to you as soon as you have written tests fully of
functions because then it is basically safe of the riskless you have a safety net of test or even safety net additionally of version control and any kind of chord changes that you think you make your cold more readable more understandable faster it maybe can be sub summarized here and One resources I want to in particularly highlight
because just this week they have a relaunched their site is exorcism I always at community of for the solving a programming problem is I just link to the and the Python examples here but there's many other programming languages and the problems all the same in each language so if you know 1 language already you can maybe work through the problems rather quickly and then try to solve the same problems in maybe a new programming language that you would want to learn and in particular this aspect of of testing of iterating quickly of finding 1 solution then improving the solution is covered really well here because the tests that tell you whether you have already
completed the problem was solved the problem or not they are already provided so you basically do only half of test-driven development in here but really useful and in particular about suffer refactoring I would say I like to highlight here the
sorry the lower 1 and and or this probably the lowest in here you that this should be the 2nd step right after you've gotten your called to work and the 3rd step maybe if it's really necessary because as you know computers are getting faster and faster performance optimization if it should not be in the forefront you will probably wastes a lot of time to start thinking about performance too early 1st as it should work then you should make the call better and then maybe make it faster and a generally by iterating quickly does not mean that you rush things is also nice staying here that if you want to go fast you have to take your time you have to study the problem to understand the problem and so in particular as well cleaning up your cold or whatever the type of research artifact you produce and then if it's easy understandable but then you can also iterate
faster and improve faster just
some resources for performance optimization if you really needed to you should always know what exactly you can improve so there's a profiling or benchmarking tools in most programming languages show so please measure 1st
identify what the actual slowest part is and try to optimize this and in some cases maybe the slowest part will not be accessible to you so in the park
diver example we talked about I did this just last week to check my advice here and this lowest part is to about to which I am communicating sort my control so I don't really I can't really optimize their anything because my own quarters contributed so little time tool for example the test runs that makes no time and no sense to invest much time it but here are some resources in case you need them yeah and and you go through the cycle again so I mentioned iteration after you've identified 1 of the bottlenecks then you can check for the next 1 but definitely don't do it just based on what you think could be the slowest I think generally about speed
and when you think about how much time you invest into a some problem there's already
precomputed tables from the EEC's C. a comic series maybe you've murdered so there is on 1 axis and how often do you do a task and how much time would you safe when you automated and then you can easily compute check for example you can invest 2 hours of optimizing a task if
you do it every day a task which you can speed up by 5 seconds 1st of all so it's of course also but of comedy in there but this is mathematically that correct probably because as you can see this development of some kind of optimization or automation that can also to overtake your actual task and generally you have been hearing about
best practices of lots in the last few days and you want to leave you remove 1 impression to think about anything that is called a best practice has of course been in use widely and has to be recognized so by that time actual object of the best stuff is so already way ahead of the curve here so whenever you hear about best practices it's probably more like the average so it's definitely something that you should do it's not something to be ignored by this not the laurels that you can rest on at the it's the base case and
unfortunately we have the case that many men practices exist so how should you know which 1 is the best for yield sorry
you can't really the most important thing again so referred was PID is for example this is just the start doing it it doesn't matter so much which of the advice exactly you follow it met as that you follow 1 of the advisors and may be evaluated regularly I would recommend probably at the start of each next biggest projects because through a project you learn what works what doesn't for work for you to definitely at the latest when you start a new project is a good time to implement this learning and that's so I
think more effective than switching in between and trying to improve something in between because you may get lost in trying to improve the things over continuing the actual work yeah and here
come just a quick overview of the
resources that's we compiled to help you get through this may in many cases and so because we just had the licensing topic before lunch this is this year flip all of you so I thought that maybe it would be helpful in tool write down some situations that that you may be it so if you're looking for so and type of license there in Germany for example you can look at the fossil dot org they have also nuisance about quite CASIS so not all the licenses for example have been tested in court some half of although we hope that this actual questionnaire becomes relevant to you if you wanted really really quick and short this choose a license that call there's several different cases you can sort yourself into each of the situations that then you would get some quick and usable advice if you want to have a summary of the licenses that exist for example because you notice software that you are using a particular license is required then you can get a very quick summary at TID our legal don't come that that line break their end generally if you will want to read more there's this papers and papers about this as well specifically for German so for example Victoria Stodden in the US has worked of and has worked on this and so I think this this shows or amateur which offer this is but again here 1 of the most important advisers think 1 because if you don't then nobody can be used your cult and too much more
stuff I want to highlight the stuff that had has helped me a lot were conference videos so for each programming language should you have conferences even in Python for exam of general Python conferences and scientific Python conferences many of them
published their their slides and their videos and recordings of there's also that nice in particular are studio I think is a good resource here this is how I
learned a lot most probably mostly everything that's I know this really long list of blog posts this so the to the exorcism again as I mentioned before it's highly recommended and I'd because I was from the bio and background the little bit of the Rosalind in full project is also has a lot of problems that you can solve in Python so if you want to train in this topic that's a good resource and this text some of them new P mentioned yesterday some of them I also can recommend we have an open science mook which has partially also been you developed at TIBE so this is recommended there's so God it's so much more so than the point is we will we will give you the slides and the enter and of course we invite you to have a look at this
and before everybody leaves we definitely want to load of from the all of the bottom of our heart
what to think instructors cementitious still here Martin how much is so you will be here in a minute ago again and how I fit to
have and the cannot and look have already left so it was it was really a pleasure for us to work with these people to work with you as well and we had a great week and therefore would also thank all of
you participated with that question suggestions their own experiences thanks a lot