Timeline for Prohibit / prevent spaces in file names
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 4, 2018 at 20:37 | vote | accept | puk | ||
| Feb 4, 2018 at 5:50 | comment | added | Nasir Riley | @Mezvek That would work in theory but in practice it would be a mess. If the directory where the files are moved if the naming convention meets the requirements isn't accessible to the users then how would they do anything with the files from that point on? Even a link wouldn't work as they still wouldn't have access to the original.. Besides, if they can access and use the files with the non-adherent names then what would they care since they'd just be able to use those files instead of being concerned with the directory that they can't access? | |
| Feb 4, 2018 at 5:30 | comment | added | Patrick Mevzek | You are too short on specifications but what you could do is: 1) having one space openly available for people to create files it, separate from the true space, 2) having a process monitoring files arriving in previous space, checking name per your convention and 3) moving it to another space only if accepted (and eventually finding a way to alert initial poster if not), and this space should not be directly accessible to users. | |
| Feb 4, 2018 at 5:23 | history | edited | Vlastimil Burián | CC BY-SA 3.0 |
edited tags
|
| Feb 4, 2018 at 3:14 | answer | added | Nasir Riley | timeline score: 3 | |
| Feb 4, 2018 at 2:03 | comment | added | cas | Probably your best option is to publish a file naming convention that everyone is expected to adhere to, and then run a nightly or weekly cron job that emails each user a list of files owned by them which don't match...similar to cron jobs warning about quota usage. i.e. policy + automated nagging. If you want to keep track of whether users are renaming their files or not, you could generate each user's report as a file before mailing it (should do so anyway so you can avoid mailing people without any bad filenames) and store it in a git repo. | |
| Feb 4, 2018 at 1:34 | comment | added | puk | @PatrickMevzek files can be created/modified/destroyed either through Windows (it is mounted) or directly through the shell | |
| Feb 4, 2018 at 1:30 | comment | added | Patrick Mevzek | How do they put/create files? Also your naming convention is probably not something that can be enforced only be automated technical tools. | |
| Feb 4, 2018 at 1:00 | history | asked | puk | CC BY-SA 3.0 |