From e6cb8584d890c0b976b0d959668e5d6bc7ba518e Mon Sep 17 00:00:00 2001 From: laurentheirendt <laurent.heirendt@uni.lu> Date: Wed, 4 Aug 2021 13:46:33 +0200 Subject: [PATCH] fix broken link --- external/integrity/naming/file_naming.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/external/integrity/naming/file_naming.md b/external/integrity/naming/file_naming.md index 3c96f7d0..91692d7b 100644 --- a/external/integrity/naming/file_naming.md +++ b/external/integrity/naming/file_naming.md @@ -56,7 +56,7 @@ Beware of typos and avoid using multiple names varying in small ways unless it h ## Exploiting machine readable names You may already have a lot of files collected for your project or you have received big dataset from one of your collaborators. Then you might think about organizing and renaming them to be compliant with your new or existing naming policy. -If the names are consistent and you don't want to loose time renaming them by hand, you may try to use dedicated tools (e.g. [PSRenamer](https://www.powersurgepub.com/products/psrenamer/index.html)) or simple commands in your command line (**rename** for Mac and Linux, **ren** for Windows). +If the names are consistent and you don't want to loose time renaming them by hand, you may try to use dedicated tools (e.g. [PSRenamer](https://github.com/hbowie/psrenamer) or simple commands in your command line (**rename** for Mac and Linux, **ren** for Windows). Once your skills develop, you will be able to use machines and machine readable file names to perform advanced operations on them, e.g. search using regular expression. Imagine folder with thousands of files. Running simple R command -- GitLab