Can voicemails and videos be stored in a Laserfiche Repository? If so, are there format limitations?
Streaming Audio and Video Files in the Web Client
By default, opening an audio or video file will stream that file to your browser, allowing you to watch or listen to it without downloading and then opening it. When you open the audio or video file, it will automatically begin streaming. If you choose to open the file in the document viewer instead, you can press the play button to stream in the document viewer.
Laserfiche supports streaming for MP4, WEBM, OGG, OGGV, MP3, WAV, OPUS, and OGA file types. However, note that streaming media also requires the correct codecs to be installed, and that your browser version support the file type. For more information, refer to the browser's help files.
If you want to download an individual media file instead of streaming it, you can select the file and then select the Download button. If you want to download media files upon opening by default, you can configure this as an option. Click your user name in the upper right corner and select Options. In the Display section, clear the option Stream media files. If you have media streaming enabled, but want to download a specific media file instead of streaming it, you can do so by right-clicking the document name, pointing to Open, and selecting Download and Check Out.
Thank you, Steve! This is great information.
Would you happen to know if voicemails and audio files can be stored in the desktop application of a repository? I don't use the web based repo . . .
Laserfiche is File Type agnostic, it can ingest any file type regardless of Web or Desktop client.
That being said, their is no playback capabilities built into the Desktop client, so you would have to have a local app installed for playback. You may have to checkout or download the files to your desktop to be able to playback in the local app.
That is the benefit of the Web Client in this case, where the identified file types can payback from within the client. Unsupported file types would have to be downloaded for playback through a locally installed app.
Right, all good information. The most important takeaway is that you can put literally any file type in, but you need to plan ahead for it to be usable by your users. For instance, if these files are types that are not widely supported, it may be easier to convert them (in an automated way) to a more supported format than to install and maintain a required application on every user's machine.