Naamgeving van mappen en bestanden/en: verschil tussen versies
Nieuwe pagina aangemaakt met '<blockquote> To quickly find the right archive documents, it’s important that folders, documents and files are given good names – so you can avoid having to rea...' |
Nieuwe pagina aangemaakt met '* [https://archives.ncdcr.gov/government/digital-records/digital-preservation-and-access/file-naming State Archives of North Carolina: File-Naming] * [https://regio...' |
||
| (7 tussenliggende versies door 2 gebruikers niet weergegeven) | |||
| Regel 38: | Regel 38: | ||
** Special characters: / * % @ | # § $ | ** Special characters: / * % @ | # § $ | ||
* Choose a meaningful and unique naming system – short but strong – which everyone can understand. | * Choose a meaningful and unique naming system – short but strong – which everyone can understand. | ||
* It’s best to limit the number of folder levels to | * It’s best to limit the number of folder levels to five, or eight at an absolute maximum. If you go deeper than this, the ''path length'' becomes too long for the document and you run the risk of computers no longer being able to locate the folders or read the files. Avoid file paths longer than 255 characters, as they can cause issues when reading, copying, moving and deleting files. | ||
* Use the same structure for every folder name. Avoid using a person’s name or words such as ‘Various’ or ‘Other’ as folder names. | * Use the same structure for every folder name. Avoid using a person’s name or words such as ‘Various’ or ‘Other’ as folder names. | ||
‘2014_Photos’ is better than ‘Photos from 2014’, for example. | ‘2014_Photos’ is better than ‘Photos from 2014’, for example. | ||
<blockquote> | |||
'''Why avoid spaces, diacritical marks and special characters?''' | |||
* Spaces: operating systems, programs and scripts can struggle with files that have spaces in their folder or file names. It’s better to use an underscore (_) instead of a space. Spaces signal the end of a string to the operating system, which can prevent the full file name from being recognised. | |||
* Special characters: punctuation and special characters (such as \ / : * ? “ < > | [ ] & $ , .) should also be avoided. These characters often have special functions within systems and can lead to unwanted effects. For instance, the backslash (\) is used to identify folders in Windows, while macOS and Linux use the forward slash (/). Dots are used to indicate a file’s extension; using them in a file name can cause errors. | |||
* Diacritical marks: the English language doesn’t use diacritical marks, and since computer development mainly occurred in the English-speaking world, many computer systems aren’t equipped to handle them. Even though you can now use these marks in file names, many programs still don’t support them. Errors can also occur when files are moved from one system to another. Want to know more? Read [https://kennisbank.meemoo.be/inzichten-en-praktijk/tekencodering-character-encoding this article on character encoding (in Dutch)]. | |||
</blockquote> | |||
Just like with paper archives, it is recommended to start each folder name with a number. Computers generally want to organise folders alphanumerically, and this enables you to retain the logical order you have used for the folders. Numbering can also add a hierarchy to limit the number of levels. | Just like with paper archives, it is recommended to start each folder name with a number. Computers generally want to organise folders alphanumerically, and this enables you to retain the logical order you have used for the folders. Numbering can also add a hierarchy to limit the number of levels. | ||
| Regel 52: | Regel 60: | ||
The same naming rules and basic principles apply for files as for folders [only use a-z, A-Z, 0-9, _ and -, and do not use ! ? . , ; : ( ) é à ù ç è / * % @ | # § $]. | The same naming rules and basic principles apply for files as for folders [only use a-z, A-Z, 0-9, _ and -, and do not use ! ? . , ; : ( ) é à ù ç è / * % @ | # § $]. | ||
<div class="mw-translate-fuzzy"> | |||
Filenames must be short but strong, and preferably follow a fixed structure which you establish in consultation with your colleagues. The document’s contents partly determine how to name the file, which can include the following components: | Filenames must be short but strong, and preferably follow a fixed structure which you establish in consultation with your colleagues. The document’s contents partly determine how to name the file, which can include the following components: | ||
* '''Type of document''': report, agenda, expenses form, grant application, etc. Agreed abbreviations can possibly be used for this, but make sure they are explained in a centralised list. | * '''Type of document''': report, agenda, expenses form, grant application, etc. Agreed abbreviations can possibly be used for this, but make sure they are explained in a centralised list. | ||
| Regel 59: | Regel 68: | ||
* '''Version control''': always make a distinction between different versions or iterations of the same text, so you can be sure you’re always working with the latest version. It’s best to use abbreviations such as: v0_1, v1, v1_1, v2. | * '''Version control''': always make a distinction between different versions or iterations of the same text, so you can be sure you’re always working with the latest version. It’s best to use abbreviations such as: v0_1, v1, v1_1, v2. | ||
* '''Date''': always include the document’s date of creation in the title. This is because computers only show the date of the last modification, e.g. in Windows Explorer, which can cause confusion. Always use the structure YYYYMMDD. Placing the date at the start of the filename means you can easily order your digital documents chronologically. | * '''Date''': always include the document’s date of creation in the title. This is because computers only show the date of the last modification, e.g. in Windows Explorer, which can cause confusion. Always use the structure YYYYMMDD. Placing the date at the start of the filename means you can easily order your digital documents chronologically. | ||
</div> | |||
Each filename is followed by a dot and an extension (e.g. .docx, .ppt, .jpeg). These are automatically added by the computer. Some operating systems, such as macOS, do not display the extension but it is still there in the background so you don’t need to add it yourself. Never change the extension as this could prevent the file from opening. | Each filename is followed by a dot and an extension (e.g. .docx, .ppt, .jpeg). These are automatically added by the computer. Some operating systems, such as macOS, do not display the extension but it is still there in the background so you don’t need to add it yourself. Never change the extension as this could prevent the file from opening. | ||
| Regel 82: | Regel 92: | ||
* [[:Bestand:20160407_handleiding_NameChanger.pdf|NameChanger (OSX): NameChanger user guide]] | * [[:Bestand:20160407_handleiding_NameChanger.pdf|NameChanger (OSX): NameChanger user guide]] | ||
* [https://www.bulkrenameutility.co.uk/ Bulk Rename Utility (Windows)] | * [https://www.bulkrenameutility.co.uk/ Bulk Rename Utility (Windows)] | ||
* [https://www.snapfiles.com/get/denrenamer.html ReNamer (Windows)] | * [https://www.snapfiles.com/get/denrenamer.html ReNamer (Windows)] (paid subscription) | ||
== Sources == | |||
* [https://archives.ncdcr.gov/government/digital-records/digital-preservation-and-access/file-naming State Archives of North Carolina: File-Naming] | |||
* [https://regionaalarchiefnijmegen.nl/images/praktische-informatie/archiefmateriaal-aanbieden/PDF2020LeidraadArchiveren/20191021_Folder_LeidraadDigitaalArchiveren_webversie.pdf Regionaal Archief Nijmegen: Guide to digital archiving for individuals (in Dutch)] | |||
''Author: Het Firmament, Sanne Van Bellingen, Florian Daemen ([[AMVB - Archief en Museum voor het Vlaams Leven te Brussel|AMVB]])'' | ''Author: Het Firmament, Sanne Van Bellingen, Florian Daemen ([[AMVB - Archief en Museum voor het Vlaams Leven te Brussel|AMVB]])'' | ||
[[Categorie:Primaire Tools/en]] | [[Categorie:Primaire Tools/en]] | ||
[[Categorie:2. Ordenen en beschrijven/en]] | [[Categorie:2. Ordenen en beschrijven/en]] | ||
Huidige versie van 12 dec 2025 om 14:08
To quickly find the right archive documents, it’s important that folders, documents and files are given good names – so you can avoid having to read each document to find out what it’s about.
In this article, you’ll learn:
- Why should I give my folders and files good names?
- What should I consider when naming?
- How do I best name digital folders and files?
- How can I best rename digital folders and files?
One important aspect, when drawing up a plan for how to organise your archive and/or collections, is how to name individual files and folders. A good naming system is important for both paper and digital archives. Below, we list some guidelines that can be useful when choosing suitable file and folder names.
Naming folders
When drawing up a plan for organising your archive and/or collections, it’s important to devise a good system for clearly naming all your folders and sub-classifications. Make sure that everyone interprets these names in the same way, and there’s no possibility of confusion or overlapping. We advise adopting the naming system used for the model organisational plans, although this is of course not compulsory. As long as the names of the classification levels are clear, logical and consistent, you’re completely free to choose them for yourself.
Giving all classification levels or folders clear and unique names – so that all employees interpret them consistently – creates order and a good overview, and means you can find the documents you need faster. A clear folder name also makes it easier to create full dossiers on specific subjects, which benefits collaborations with your colleagues.
Avoid excessive use of abbreviations, which might not be immediately clear for everyone and can lead to confusion. New colleagues in particular can often have difficulties getting to grips with a system that uses too many. But if your organisation still wants to use abbreviations in this plan, it is recommended to create an overview that lists them all to help your colleagues.
It is also recommended to use hierarchical numbering to provide added clarity when naming your classification levels. A system like this makes it easy to find specific folders in the organisational plan, and communicate a certain document’s location in the folder structure to your colleagues. You are free to choose your own numbering system.
Naming in a digital archive
There are additional rules for naming files and folders in a digital archive, mainly for technical reasons. The use of certain characters and symbols in the names can for example cause computers to interpret them incorrectly and perform unwanted actions.
Stick to the following rules when naming digital files and folders:
- Only use the following characters:
- Letters: a-z and A-Z
- Numbers: 0-9
- Underscore _ and dash -
- Never use the following characters. The computer might interpret them as commands to execute certain operations or replace them with other characters.
- Spaces
- Punctuation: ! ? . , ; : ( ) ’
- Diacritic characters: é à ù ç è
- Special characters: / * % @ | # § $
- Choose a meaningful and unique naming system – short but strong – which everyone can understand.
- It’s best to limit the number of folder levels to five, or eight at an absolute maximum. If you go deeper than this, the path length becomes too long for the document and you run the risk of computers no longer being able to locate the folders or read the files. Avoid file paths longer than 255 characters, as they can cause issues when reading, copying, moving and deleting files.
- Use the same structure for every folder name. Avoid using a person’s name or words such as ‘Various’ or ‘Other’ as folder names.
‘2014_Photos’ is better than ‘Photos from 2014’, for example.
Why avoid spaces, diacritical marks and special characters?
- Spaces: operating systems, programs and scripts can struggle with files that have spaces in their folder or file names. It’s better to use an underscore (_) instead of a space. Spaces signal the end of a string to the operating system, which can prevent the full file name from being recognised.
- Special characters: punctuation and special characters (such as \ / : * ? “ < > | [ ] & $ , .) should also be avoided. These characters often have special functions within systems and can lead to unwanted effects. For instance, the backslash (\) is used to identify folders in Windows, while macOS and Linux use the forward slash (/). Dots are used to indicate a file’s extension; using them in a file name can cause errors.
- Diacritical marks: the English language doesn’t use diacritical marks, and since computer development mainly occurred in the English-speaking world, many computer systems aren’t equipped to handle them. Even though you can now use these marks in file names, many programs still don’t support them. Errors can also occur when files are moved from one system to another. Want to know more? Read this article on character encoding (in Dutch).
Just like with paper archives, it is recommended to start each folder name with a number. Computers generally want to organise folders alphanumerically, and this enables you to retain the logical order you have used for the folders. Numbering can also add a hierarchy to limit the number of levels.
Bear in mind that a computer will place folders that start with numbers 10 to 19 between 1 and 2. You should therefore combine the number with letters or fill in the ‘empty’ spaces (01, 02, 09, 10, 11).
Naming files
Giving digital files a clear, identifiable name means you can find the file you’re looking for faster without needing to open all the documents one by one. A fixed structure in your filenames also ensures that your computer can order the files alphabetically or chronologically.
The same naming rules and basic principles apply for files as for folders [only use a-z, A-Z, 0-9, _ and -, and do not use ! ? . , ; : ( ) é à ù ç è / * % @ | # § $].
Filenames must be short but strong, and preferably follow a fixed structure which you establish in consultation with your colleagues. The document’s contents partly determine how to name the file, which can include the following components:
- Type of document: report, agenda, expenses form, grant application, etc. Agreed abbreviations can possibly be used for this, but make sure they are explained in a centralised list.
- Author: if different authors are working on the same version of a document, or it is protected by copyright (e.g. a photo), it can be worth including their names in the title. You might want to make an agreement within your organisation just to use initials for this.
- Sender and/or addressee: it is best to include these in titles for email messages, possibly as initials.
- Project or classification number: this can be useful for series that are already numbered, such as order forms. Placing the number at the start of the filename ensures the computer automatically orders the files correctly.
- Version control: always make a distinction between different versions or iterations of the same text, so you can be sure you’re always working with the latest version. It’s best to use abbreviations such as: v0_1, v1, v1_1, v2.
- Date: always include the document’s date of creation in the title. This is because computers only show the date of the last modification, e.g. in Windows Explorer, which can cause confusion. Always use the structure YYYYMMDD. Placing the date at the start of the filename means you can easily order your digital documents chronologically.
Each filename is followed by a dot and an extension (e.g. .docx, .ppt, .jpeg). These are automatically added by the computer. Some operating systems, such as macOS, do not display the extension but it is still there in the background so you don’t need to add it yourself. Never change the extension as this could prevent the file from opening.
Some examples of digital filenames are:
- WorkshopDigitalWeek.docx
- Presentation_AnnualReport_20191130.pptx
- 20160817_Report_board_of_directors.pdf
- 20070112_KL_OP_purchase_equipment.msg
Note: the combination of the number of levels (folders in folders) and the length of folder and file names determines a file’s path length. Systems such as Windows can only read a limited number of characters in this path (often a maximum of 255 characters). You can use the simple Path Scanner (Windows) tool to check path lengths.
Renaming files
When introducing new rules for naming files and folders, you of course also need to update the existing names. Proceed with caution! The following points for attention are crucial for ensuring that your files can be renamed without any hitches:
- Make a copy of a folder containing different types of files so that you can experiment safely. Never work in the original folder structure.
- Find a suitable procedure or working method for naming files within your organisation, taking the above principles into account.
- Test the guidelines out on different types of documents and in different folders; adjust your working method if necessary.
- Draw up an internal document to clearly explain the working method.
- Organise an information session to clearly explain the principles to your colleagues in simple terms. Make sure you also keep new employees, trainees and volunteers informed.
- Adapt the internal agreements if problems arise.
Do you want to rename a whole series of files (e.g. images) all at once? Below you can find three programs that allow you to give good names to documents and photos in bulk:
- NameChanger (OSX): NameChanger user guide
- Bulk Rename Utility (Windows)
- ReNamer (Windows) (paid subscription)
Sources
- State Archives of North Carolina: File-Naming
- Regionaal Archief Nijmegen: Guide to digital archiving for individuals (in Dutch)
Author: Het Firmament, Sanne Van Bellingen, Florian Daemen (AMVB)
