Starting with material bank – how does it work?
The entire material bank deployment project can be carried out even in a couple of weeks. The deployment project starts with the adoption of a service-level package in a technically deployed server environment. Then we’ll define the content together: we’ll choose the visual elements such as logo and wallpaper, categories, metadata, and user groups.
In connection with the general settings, we determine whether a public category should also be included in your material bank, ie. whether the material bank can also be accessed without logging in, for example, only into a public media category. In addition, we’ll define whether an open registration to the material bank is needed to allow anyone to register for the service. The language of your material bank interface is freely selectable and the default language is defined at startup.
A well-designed category structure creates the foundation for a smooth operation of the service. It is good to think about the category structure to serve the needs of the end user. In most cases, the users of the material bank tend to use category navigation instead of the search function, so categories should be named as descriptive as possible and the use of empty categories should be avoided. For the search function, file metadata is also good to define during deployment.
Finally, content can be exported to the material bank, for example, in a single transfer. After that, the application is ready for deployment and can be published at an agreed location.
We wish you nice moments with material bank!
Find out more about ImageBank Independent and download the material bank buyer’s guide by entering your email below or book a free demo.