Standards
File Naming Standard
Make every file findable and attributable without opening it, and set the convention up so filenames become system-derived rather than manually typed as the platform matures.
- Owner
- Administrative Coordinator
- Governs
- Naming pattern for every uploaded file.
- Applies to
Requirements
Each requirement must eventually be verifiable — not policy prose.
Every filename must include the Project ID, a category code, and a date, in that order.
Evidence: System recordVerification: SystemBlock
The Project ID and date segments must be system-derived, not manually typed, once uploads go through IETEL OS — these are exactly the parts a person is most likely to get wrong by hand.
Evidence: System recordVerification: SystemRequire
The category segment must be selected from a controlled list, not free-typed.
Evidence: Form submissionVerification: System
- Future system rule
Upload is rejected if the filename doesn't match the pattern.
Compliance measurement
Files matching the naming pattern ÷ total files uploaded.
Required data
- Filename
- Pattern check result