filnavngivningsstrategi

Filnavngivningsstrategi refers to a plan for how files are named in order to improve organization, searchability, and traceability in a repository or shared workspace. The goal is to create descriptive, consistent names that make it easy to identify the contents, origin, and version of a file without opening it.

Key principles include consistency, descriptiveness, and compatibility. Names should be easily readable by humans and machines, use ASCII characters, and avoid or replace spaces with delimiters such as hyphens or underscores. A naming strategy often specifies a fixed order of components, limits on length, and rules for capitalization. It also covers versioning, language or locale indicators, and how to handle updates or revisions. Metadata such as date, project code, activity, and author can be embedded in the file name or stored in accompanying metadata.

Common components are project code, activity or document type, date, description, version, and extension. Dates are frequently represented in a sortable form such as YYYY-MM-DD or YYYYMMDD. Descriptors should be concise and unambiguous. Versioning can follow simple v1, v2, or more granular schemes like v1.0, v1.1.

Examples of patterns:

- YYYYMMDD-prosjektkode-aktivitet-v1.0.ext

- prosjektkode-aktivitet-YYYY-MM-DD-v1.0.ext

Extensions should follow the standard for the file type and remain consistent across the set.

The strategy benefits collaboration, backup, and automated processes, while potential pitfalls include overcomplication, inconsistent adoption, and frequent renaming. Clear documentation, default templates, and automated checks help maintain consistency.