... | @@ -7,7 +7,7 @@ Sharing code and documentation among researchers working at microbiology is key |
... | @@ -7,7 +7,7 @@ Sharing code and documentation among researchers working at microbiology is key |
|
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).
|
|
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 difficulties 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.
|
|
|
|
|
|
|
|
|
|
|
|
|
... | @@ -15,7 +15,7 @@ Wageningen University & Research has created an environment for researchers to s |
... | @@ -15,7 +15,7 @@ Wageningen University & Research has created an environment for researchers to s |
|
|
|
|
|
|
|
|
|
|
|
|
|
By using this infrastructure we ensure code is stored in a shared and safe environment protected by Dutch law. We also control who can access our source code and documentation and collaboration with external parties is possible by requesting an account for a non-Wageningen University & Research employee. If codes and methods are published in this environment, a persistent identifier can be linked to your research paper. This way both publications and source code become more visible.
|
|
By using this infrastructure we ensure code is stored in a shared and safe environment protected by Dutch law. We also control who can access our source code and documentation. Collaboration with external parties is possible by requesting an account for a non-Wageningen University & Research employee. If codes and methods are published in this environment, a persistent identifier can be linked to your research paper. This way both publications and source code become more visible.
|
|
|
|
|
|
|
|
|
|
|
|
|
... | | ... | |