|
|
|
|
|
A huge amount of work, data and knowledge is lost in academic environment because of lack of organisation and communication. The infrastructure and organisation that help researchers make their work accessible to their group members is very often missing or not known or relying on private or external services.
|
|
A huge amount of work, data and knowledge is lost in academic environment because of lack of organisation and communication. The infrastructure and organisation that help researchers make their work accessible to their group members is very often missing, not known or relying on private or external services.
|
|
|
|
One of the missions of the Bioinformatics at MIB is to provide such environment that bring people to collaborate more easily and to make sure the data management policies at WUR meet with the ones at WUR.
|
|
>We want to respect WUR data management policies.
|
|
|
|
|
|
|
|
Sharing code and documentation among researchers working at microbiology is key to create and spread common knowledge and create an environment in which lab members may get a head start in analysing data, learn about methods and get new ideas for their research.
|
|
Sharing code and documentation among researchers working at microbiology is key to create and spread common knowledge and create an environment in which lab members may get a head start in analysing data, learn about methods and get new ideas for their research.
|
|
|
|
|
|
Within Microbiology we encounter the use of multiple types of repositories to store and share code. Often scientists use their private repositories such as a public Github or their local disks. Such practice leads to use and spread of not up-to date or erroneous code (it should be considered bad practice). With such practice it is also not easy to find out about existing scripts and it prevents the development of general pipelines, which is needed (Also no distinction between different version).
|
|
|
|
|
|
Within Microbiology we encounter the use of multiple types of repositories to store and share code. Often researchers use their private repositories such as a public Github or their local disks. Such practice leads to the use and spread of not up-to date or erroneous code/documentation (it should be considered bad practice). With such practice it is also not easy to find out about existing scripts and it prevents the development of general pipelines, which are needed (Also no distinction between different version).
|
|
|
|
|
|
|
|
|
|
Members of one research group may not know of repositories or scripts used by other group members and we encountered several situations where people experience difficulty to find useful utility scripts or methods even though someone else might have already tackled the problem. Relying on private repositories will lead to data/code loss since nobody have knowledge of their existence and such practice does not align with WUR data policies.
|
|
Members of one research group may not know of repositories or scripts used by other group members and we encountered several situations where people experience difficulty to find useful utility scripts or methods even though someone else might have already tackled the problem. Relying on private repositories will lead to data/code loss since nobody have knowledge of their existence and such practice does not align with WUR data policies.
|
... | | ... | |