An operation that can be performed on a specific/batch of records (files/entities/cache, etc.), for example, scraping for files, or batch setting certain fields to a certain value for entities.
Batch operations is performing the same operation on one or more records.
A Multi-Action is performing the same batch operations on each record of the selected records. The Multi-Action page can also be used in Batch operations.
The following operations only apply to library file type records.
Please refer to Scraping
PLM has built-in support for AI. In Batch operations operations, users can use configured AI to generate titles for selected files.
This function extracts the code of Japanese AV movies from the file name according to certain configuration rules (config\batch\bp_code.ini). Users can edit, add, and delete rules by themselves.
When entering a new file name, you can use <field name> to indicate that PLM should replace it with a field value of current record, such as <code> (code) or <cast:1> (first actor) or <pubtime:year()> (release date taking the year). See Database Structure for the field list.
This function will not only delete the record, but also actually delete the media file itself and related items such as cover, preview image, sample, NFO, and subtitles to the OS's recycle bin. If you delete it by mistake, please use the recycle bin to restore these files and re-import them.
Move file options:
This function performs simple statistical work: number of files, size, file type, category, country, release year, rating, tags, ratings, actors, studios, etc.
This function detects suspected duplicate files in the library based on code, file name, checksum, etc., helping users to clear duplicate files and save space. According to the inspection results, users can select the records and perform the file.delete_file operation.
This function is usually used to copy files to external systems. PLM will copy the main and related files.
Combine multiple files, such as multiple parts of a movie, into a folder-type file. These files must be located in the same folder in the OS.
Separate a folder-type file into multiple single files.
Please refer to Normalize Files
Extract media information such as duration/resolution/codec to the file record.
Generate preview images PNG or animated previews GIF for videos or image sets. You can edit config\batch\bp_minfo.ini to adjust generation parameters.
PLM has the ability to quickly encrypt media files, so that the encrypted media files can only be played using PLM and its player PLMPlay. The extension of the encrypted file will also be modified to .plxxx(such as .plmp4)
Decrypt previously encrypted files, which can be played using other common media players, and the file name extension will also be restored.
This operation only verifies and modifies the path of the file, and is suitable for files that have already been moved manually.
Repair and update file information and links, caches, etc.
Generate .nfo files available for KODI. The .nfo file will contain additional PLM fields.
Automatically set the file actor information according to the path where the file is located.
Set the cdnum field value according to the file name.
The following operations only apply to external file type records (during import).
This function will not only delete the record, but also actually delete the media file itself and related items such as cover, preview image, sample, NFO, and subtitles to the operating system's recycle bin. If you delete it by mistake, please use the recycle bin to restore these files and re-import them.
When entering a new file name, you can use <field name> to indicate that PLM should replace it with a field value of current record, such as <code> (code) or <cast:1> (first actor) or <pubtime:year()> (release date taking the year). See Database Structure for the field list.
The following operations are valid for multiple or all types of records (including files/entities, etc.).
This operation is available for all types of records. Set certain field values (can be empty values) and check them, and then click OK to batch set the checked field values of all selected records.
Users can install or write scripts for PLM to call for each selected record during Batch operations.
Batch add a specified tag to the selected records.
Batch delete a specified tag from the selected records.
Clear all tags from the selected records.
Check the fields to be translated. PLM batch translates these field values of all selected records according to the current translation configuration.
Export records to .json format.
Export records to .json lines format, suitable for AI processing.
Export records to .csv format.
Delete records only but do not delete the entity files in the operating system.