The newest version of Baasic brought to life two very important modules with apparently similar, yet clearly distinct functionality. To set things straight, let’s first establish their purpose. Media Vault is a module created for application admins as the central control point for creating and managing media files within web and mobile applications. Files module is used to optionally expose those media files to end users.
Media Vault stores all files your application can get, regardless of the module that was used to upload it, or whether the file was uploaded by an application admin or the end user. That, however, does not apply the other way around: files uploaded to the Media Vault will not be visible in other modules - unless you link them, but more on that later.
As we said, all media files uploaded through any application module will be stored here.
You can also add files to Media Vault directly, but it’s more likely you’ll be using it to manage files that came in through other modules.
When adding items directly to the Media Vault, you can change the upload path (virtual folder) and edit file properties, such as file owner, file name, and description.
If the file you’re uploading is an image, you can edit it before it’s uploaded to the Vault by clicking the Edit icon on the thumbnail.
Regardless of the way the media file got into the Media Vault, you can link it and use it in any other module without having to reupload it every time.
For example, we’ve uploaded a document to the Media Vault and would like to use it in the Files module. No need to upload it separately to Files. Just go to Files, +Add File Items, Link, and select media file that you’d like to use in Files module.
Media Vault settings let you define which options to use when creating derived images (cropping and face detection settings), and which media files extensions are allowed for direct upload to Media Vault.
Note: Each module has its own file extension settings. File extensions that aren’t allowed for direct upload to Media Vault will still be stored in the Vault when uploaded through other modules.
Derived images come in handy when you need multiple versions of one image - and you probably do, for responsive web and mobile apps design. Derived images are modified (resized and/or cropped) versions of the original resource image, created on the fly, without changing the original. On the fly means you don’t have to upload the original media file and then edit to have both, original and edited versions, but rather request that media file from the Vault, and then create another, edited version.
All derived images are saved as new files, but with the same name as the original, so you can find them under the original media file.
CROP MODES AND FACE DETECTION
Available crop modes are fill, fit (default) and scale.
The fill mode creates a derived image with the exact given width and height while retaining original proportions, and the resulting image can be bigger or smaller than the original one.
The fit mode creates a derived image that fits in the given width and height while retaining original proportions - both width and height of the derived image must not exceed the specified width and height (all parts of the original image are visible).
The scale mode creates a derived image that fits the specified width and height without maintaining the original aspect ratio.
Face detection option makes sure that the entire face of the person in the original picture appears in the resized/cropped version of the image - not only a part of it.
All three crop modes can be used with or without face detection option.
Here’s an example. This is the original image (size: 850x530px):
The table below shows derived images (resized to 300x300px) for all combinations of cropping and face detection:
You can also replace the original resource image by clicking ‘Upload a new file’ when the file is selected - without changing derived images that were already produced.
By default, when you select an image, you’ll have the option to edit the original one. If you want to edit a derived image, click ‘Swap item’ under the desired derived image to bring it to focus, and then click ‘Edit photo’.
Since Baasic takes a module-based approach to set up permission models, Media Vault module lets you set different permissions for specific users and/or user roles in general (End-Point ACL permissions) - by clicking the Permission icon next to the module title.
Besides that standard permission model, you can use object-level ACLs (Access Control List) to set up access control over individual objects/media files - that kind of fine-grained access control is available in the Files module. These single-object-permissions can also be set for specific users and/or user roles.
More on Baasic modules permissions here.
This post covered only a fraction of the functionality of our new modules - stay tuned for more information, or even better, register for a Baasic account and see how its features work for you.