DigaPorter: Export selected files of a database entry with DigaPorter
Either DigaPorter or DigAlign with FilesDI.dll can be used to automatically export material from a DigaSystem database table to a folder. DigaPorter comes with some nice features which allow exporting selected files and it also updates the timestamp of the target files while DigAlign is using the original timestamp.
A typical use could be exporting just the WAV file and the ZIP file of a database entry which was delivered from PhonoNet. Usually such database entry comes with lots of files like JPEGs, text files, etc.
To setup this workflow the source of DigaPorter must be set to a folder. This folder will be the media folder of the table you want to export. This allows setting the export rules to file based selection.
The target is of course another folder.
Inside the control section you need to set the search to *.dbx or *.dbx based on your global UseDBE settings. Of course the table must be configured to write backup files.
Now you need to create a rule for every file type you want to handle. The first rule should handle the .dbx file. You need to do this because you need to parse the file for getting metadata out of the database entry. This can be used for creating speaking filenames. Therefore the .dbx rule should have these enabled options: Metadata file + Don’t add source to destination. The naming rule can be set to <CGUID>.<EXT> but you won’t need it because you don’t export this file.
Afterwards you need to create a rule per file type. Example: .wav
You need to set this to be an optional file. This is useful if you are not sure if the main audio file has always the same extension or if a file type always exists. If you don’t set it optional you will only get an export for database entries where all created file types exist.
You can also set the checkbox that this file is the primary file.
Inside this window you can also add the naming rule for this file. Here is an example: </ENTRY/TITLE> - </ENTRY/PERFORMER> - </ENTRY/ALBUM> - </ENTRY/MEDIUMNAME> - </ENTRY/GEMAID>.<EXT>
Please create such a rule for every desired file type.
Now it should be possible exporting the database table to a folder.
You can also set the destination to a database table. This will create database entries which only exist out of the selected file types. This allows you to set deletion rules for the target. The filenames will be speaking and you can set this target table to do not write DBE/DBX to avoid having other files inside the assigned media folder. So the users can access the media directly from the folder while deleting it can be triggered by e.g. DigErase.