Setup, Installation & configuration

The setup can be divided into following steps

  • Workshop(s) with stakeholders and reference groups

  • Setup, Configuration and customization of QBank (editor platform)

  • Training 

  • User acceptance testing (UAT)

  • Data Migration


Workshop(s) with stakeholders and reference groups

Each project starts with a workshop where topics listed below will be discussed with the stakeholders and reference group. This workshop will result in a Setup and Configuration Specification (SCS) document and a Customization Requirements Document (CRD). Some of these topics have been well addressed in this RFP and the specifications we have received. However we believe that, with our experiences from similar projects we will have valuable input.

Roles, groups and users

Here we will discuss the different types of users, groups and roles in the system. This will result in a security matrix that will be included in SCS document. Following questions will be addressed among others

  • How will the Roles and Users provided in the RFP map into QBank. What type of users and groups will there be in the system (external, internal, editors, administrators, content providers, agencies etc)?

  • Does the groups have different access to assets. For example should Product Catalogue editors group access the assets that belong to the Marketing editors group?

  • What functionality in QBank does the different roles have access to?

  • Is there any workflows and subscriptions to events connected to any groups?

  • How were the groups, roles and users setup in the old system? Any Pros and cons?

  • Which plug‐ins and customizations are needed?

  • In what extent should IT‐department be involved?


Metadata structure

QBank has a dynamic metadata structure where the assets are divided into different categories (media types). Each category has its own setup of metadata fields. A metadata field can be of type textbox, text field, date, number, dropdown (enum), multiple‐dropdown (enum), keyword or checkbox. The categories and metadata structure can be changed and reconfigured at anytime.

We will review the current metadata and improvements and address following

  • Are there any mandatory fields?

  • Are there fields with default value if nothing has been added?

  • Should all editors have access to edit all categories and metadata?

  • Are there any metadata fields that are internal for editors and administrators in QBank? 

Image and Video templates

All assets should be uploaded to QBank in high‐resolution/original format. Users can choose to apply an image or video template* to an asset depending on which channel they are going to be distributed to. As an example, QBank can be configured to convert all images or videos to one or several different sizes and formats when publishing to the web‐server or a CMS. All converted versions will also be available for other applications/users.

 * A template is a setup you can apply to your images / videos to get a specified format and size of the media when downloading it.

Distribution channels

Distribution of assets via QBank is an out‐of‐the‐box function that can easily be configured and designed. Here we will discuss whether there is any other channels that assets need to be distributed to for example to an FTP‐server at an agency or through a third party client such as InDesign, Photoshop, Illustrator etc.


‐ QBank Workshop document
‐ Setup and Configuration Specification document (SCS) ‐ Customization Requirements Document (CRD)
‐ Final Project plan


Setup and configuration of QBank

The set up and configuration of QBank will be according to the QBank SCS document. During this part of the project we will also install and configure the plug‐ins and/or possible workflows.

Customization (plug-ins) & Development

 All Plug‐ins and customizations will be thoroughly documented for the purpose of future maintenance and enhancement.


‐ Plug‐ins and customization overview



This training session will be held for administrators in QBank (editor platform). These are the users that will be responsible for User Acceptance Testing (UAT) of QBank editor interface.

Besides the basic functionality such as uploading, search, indexing etc the users will also learn how to update categories, metadata structure, setup of video and image templates and handle users/groups and roles.
During this session we will also emphasis the importance of correct indexing of images for better search result quality on an end‐user interface and search engine optimization (Google image search).


- QBank User Manual


User Acceptance Tests (UAT)

User acceptance tests are performed on the staging environment, by the customer (users of the system). The test cases will be designed based on the SCS document and CRD. The results of these tests give confidence to the customer as to how the system will perform in production. Since there have been thorough tests performed during the functional testing, any possible issue will be of low severity or cosmetic. These issues will be reported on a daily basis and handled by QB during the UAT period. At the end of this period the customer will give its approval for launch.


Data Migration

For data migration please read following article. (Requires login)



Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Powered by Zendesk