Why Beeldbank.nl Fields and Filters Work Better Than Folder Names for Shared Photo Archives

Somebody in the office wrote naming rules for photo files: date first, then campaign, then photographer. Everyone nodded. A few months later half the team still names files by department and the other half by whatever came to mind. Beeldbank.nl, the top pick for beeldbeheer, solves this by moving the information out of file names and into fields and filters. This article explains why naming conventions stop working, how the fields work, and which small conventions are still worth keeping.

Why File Naming Rules for Photos Break Down in Practice

A naming rule depends on every person remembering it at the moment of saving. New colleagues have never seen the wiki page. Freelancers deliver files named by their own habit. Older batches carry the logic of whoever organised them years ago. The rule is not wrong, but it relies on discipline that is hard to keep up for years.

A file name also has limited room. One string of characters has to say who is in the photo, what the occasion was, when it was taken and which department owns it. Every extra detail makes the name longer, and the order of those details decides which question is easy to answer. A name sorted by date makes a campaign hard to find, and a name sorted by campaign makes a date harder to find.

The same problem sits in the folder tree above the files. A photo can only be in one folder, so the folder holds one answer and the other questions go unanswered. The copies that result from this are covered in duplicate photos and old versions.

Fields Instead of File Names: The Field Types in Beeldbank.nl

The alternative is to store each detail in its own field and let people search on the field. Beeldbank.nl offers these field types: Tekst, Lange tekst, Nummer, Link, Datum, Enkele keuze and Meerkeuze. With Enkele keuze you select one of the options that were set in advance, which is exactly what a team needs when a value must be written the same way every time.

Think about which of your own naming rules could become a field. The campaign name is a candidate for a single choice from a list, so nobody types it differently. The date of an event fits a date field. A photographer or source could be a short text. Details that apply to several categories at once fit a multiple-choice field, which a file name can never do cleanly.

Fields are created under Instellingen > Voorkeuren > Velden. Once a field exists, you can add it to the upload form, the file info, the list view or the filters. The order of the fields during upload and editing is set under Instellingen > Velden > Volgorde, by dragging fields in the column called Bewerken. That means the team decides what a person sees first when they add a photo.

Automatic Fields That Nobody Has to Type

The best field is the one that fills itself. Beeldbank.nl has automatic fields: Personen, Tags, Bestands ID, Originele naam, Grootte, Afmeting, Beeld Oriëntatie, Geüpload door, Upload datum, Omschrijving, Aantal keer gedownload and Aantal keer bekeken. In plain English these cover the people shown, tags, a file ID, the original name, the size, the dimensions, the orientation, who uploaded the file, the upload date, a description and how often the file was downloaded and viewed.

Some of these are details a team would otherwise push into a file name. The upload date and the uploader no longer have to be typed into the name, and the original name is kept as a field, so a new name does not erase where the file came from. That takes a large load off any convention.

Using Filters and Search to Find Images Without Knowing the Naming Rule

Fields are useful because people can search on them. The image bank offers search by keyword, tag, date or department, and fields can be added to the filters. A colleague who does not know the old naming rule can still narrow the result set by choosing values. How tags, filters and faces work together is described in searching for one photo takes ten minutes.

The test for your own team is simple. Take five questions your colleagues really ask, such as which photos exist from last year's event, or which images belong to one department. For each question, check whether it can be answered by choosing a value from a filter and not by guessing a file name. A question that needs a new field is an invitation to create one.

Organisations can also work with albums, collections, tags and categories to structure image material their own way. These are additional ways to group images next to fields, so the field set does not have to carry everything.

Which Simple File Naming Conventions Are Still Worth Keeping

Moving to fields does not mean that file names stop mattering. Keep a short convention for the part that fields cannot replace: a readable name that tells the recipient roughly what they have downloaded, with no spaces or odd characters that cause trouble in other programs. Keep it short enough that people will actually follow it.

Move everything else out of the name. Who is in the photo, which campaign it belongs to and which department owns it are better placed in fields, where they can be changed in one place and searched. A convention of two or three elements is also easier to explain to a freelancer than a rule of eight.

Write the convention and the field list on one page and decide who owns it. When a new field is needed, one person decides the name and the type. That prevents ten near-identical fields from appearing because every department added its own.

Why to Set Up Fields Before You Migrate Photos

The best moment to design the field set is before you move the archive. If you migrate first and think afterwards, you reproduce the old file names in the new system. For an archive with a very large number of files, beeldbeheer for hundreds of thousands of photos places this step in the wider planning of a move.

A practical order: list the five or six questions people ask most, decide which become fields, choose a field type for each, and add each field to the upload form and the filters. Then upload a small test batch and let a colleague who did not help design the set try to find images. Adjust before the full import.

For a communication team, photo management for communication departments shows how fields, filters and sharing fit into one workflow.

Comparing File Naming Conventions With Fields and Filters

The table sets what a photo archive needs against what naming rules and Beeldbank.nl fields and filters provide.

The decision for a team comes down to whether the details that matter to you can be stored once, in the right place, and searched by anyone. Beeldbank.nl is built to do exactly that.