Been awhile since my last update and so, because of that, I thought I would start with information about Smart Mover’s latest features.
Smart Mover v10.4 was actually released back in November of 2019. It included the following:
- Support for MacOS 10.15 (Catalina) has been added.
- The Copy Files Task now includes the option “Copy Files that have been stable for X seconds”. This option can be used to insure that each file is not still being written to by another application. Background: Before any Task operates on a file it checks to see if another application has the file open. It does this by briefly opening the file with write access. If the file cannot be opened then it is assumed that another app is still writing to it and it is skipped until the next time the Task runs. But there are some situations where this technique may not always work. To work around those times, using this option, the Task first gets a list of all the file sizes that it will be processing. It then waits for the designated number of seconds before it tries to copy each file. If the file size has changed during that delay or the file was not in the original list, it is skipped until the next time the Task is run.
- Elvis Update Bulk Task added. This Task does the same as the Elvis Mod MetaData except that all the processing is done server side with a single command. The Elvis Mod MetaData runs the desired query and then updates each asset one at a time, logging each update. If you are updating more than a few hundred assets then you should use the Bulk Task. It is much faster but does not provide a detail log of the assets that have been updated. Once completed, the Bulk Task will log how many assets where updated along with the number of errors. No detail is available though.
- Both Google and AWS Translate Tasks now include the option to “Add Translation Language Code to File Name”. This allows you to translate the same file into multiple languages and place them all into the same folder. So a file named “sometext.txt” translated into Spanish would be named “sometext-es.txt”.
- Both Google and AWS Translate Tasks can now dynamically translate into languages designated in an associated -metadata.xml file. This is done by picking “-metadata.xml XPath” in the Translation Language pop-up and then providing an XPath valid expression.
- Example: If I have a custom Enterprise field called “Languages” and a User enters “es” (the code for Spanish) into that field for a particular article, I can then use the Enterprise Download Task including both the “native” and “metadata” for that article. If I enter “//ExtraMetaData/ExtraMetaData[Property=’C_LANGUAGES’]/Values/String” into the XPath field then the article will be translated into Spanish. Additionally, if a comma-delimited list of language codes is provided in that field then the file will be translated into each of those languages. So if I entered “es,de” into the Languages custom field for the article, it would be translated into both Spanish and German. Each Translated file name will include the language code to differentiate them and prevent overwriting.
- The AWS Translate Task now includes: Hindi, Malay, Norwegian, and Persian.
- The Enterprise Check Out-In Task now includes the option to set the Status to any given value. This can be done for both the Check-Out and Check-In functions.
If you have any questions either hit me up here or send a note to ‘firstname.lastname@example.org’ and we’ll get back to you ASAP.