Normalizing files

Storing too many files in the same folder on your operating system not only looks cluttered but also affects its access performance. Furthermore, for management purposes, each file record, in addition to media files (videos), may also contain accompanying items such as cover images, preview images, NFO files, subtitles, etc. Therefore, PLM provides an normalize function that allows all relevant items for a single file to be stored separately in a folder on the operating system. For example, files can be organized by "Actor\code" or "Director\Title."

The "Normalize" function involves a "Target Path" feature for tags. For example, if the tag is an actor, you can specify in the tag properties that the actor's films are organized into a specific default path (level 1 path).

The options for normalizing files are as follows:

  • Under current directory / Move to new directory: Organize in the current path or move to a new target path.
  • Target Path: If you choose to move to a specified path, select the target path here (select using the "Browse" button).
  • Level 1 tag path format: If the tag does not have the default path specified here (e.g., <cast>), use this value (usually a field) as the first-level path. For example, the result corresponding to <cast> is "JULIA," or the result corresponding to <series> is "SONE" or the result corresponding to <cat> is "Sci-Fi."
  • Level 2 sub Format: After PLM determines the level 1 path, you can create level 2 subpaths below it to further subdivide the film directory. Usually, you can use the <code:1> or <title>, for example, create a "SONE-136" subdirectory under "SONE".
  • Rename format: If specified, the filename will be renamed in this format after organization, such as <code:1>, used to unify the filename or if you find the current filename too complex.
  • Save tag Path: Whether to save the tag and target path specified in the editing box below for convenient reuse in the future.
  • Force redo: Force re-organization, otherwise, files that have already been organized will be skipped.
  • Skip blank field files: If you encounter empty values for the specified fields above, such as an empty code, skip the organization.