Checklist. Remove Before Release
- Troels Holm (Unlicensed) Basic SEO
- Stefan Fodor (Unlicensed) 3rd parties
- Stefan Fodor (Unlicensed) PDF
- Stefan Fodor (Unlicensed) design and colors
- Stefan Fodor (Unlicensed) Print
A great feature that was launched in the 4.7.0 release of Media Manager, will improve the user's experience "BIG TIME"! Inside Media Manager it is not possible to preview / read PDF files.
The only thing we changed in the Asset Preview is EVERYTHING.
It is required that you republish existing PDF assets after upgrading to MM 4.7.0 is you wish to be able to render them in the PDF viewer.
How to access/use the new implementation?
Search Engine Optimization
Step 1 of our SEO initiative is part of this release. It makes it possible to specify and control search engine tagging of the Media Manager at a global level.
PDF Reader
The PDF Reader is available for PDF assets in the asset preview. It can be accessed from the asset manager list, by click on any PDF asset in order to open the preview. The Reader will dynamically load the PDF asset and render it. The user will be able to navigate though the PDF pages, zoom in and out and print the document.
Managing Third-party Dependencies
In 4.7.0 we improve the way we manage third party libraries like Google, Dropbox and SkyDrive. This allows us to slightly optimize the initial loading time, as well as insuring that the application will work on networks where providers such as Google are not being allowed(*cough* China *cough*).
Printing the Asset and its Metadata
Starting with 4.7.0, the asset metadata will be printed separately from the asset itself. This change was made to reduce confusion over what the print functionality does and to allow printing the metadata on all asset types.
Media Manager Skinning
Starting with this version, we will make sure that all the colors used in Media Manager are declared as variables and therefor can be modified using the methods described in the Style Guide. This will allow you to customize to an even greater extend than before.
How the new implementation works?
Search Engine Optimization
The implementation renders <meta> tags in default.aspx which are picked up by search engines.
PDF Reader
When opening the preview for a PDF asset, the reader will open at 100% zoom level on the first page of the document. By using the scroll bar on the right-hand side, the user is able to scroll through document and navigate to other pages. On the center bottom of the screen, the reader will display the current page being rendered in the document and the total number of pages available.
By pressing the ellipsis icon from the bottom right corner, the tool will open, from where the user will be able to change the zoom level of the PDF, print the document or open the reader in full-screen.
Note: Full-screen view and printing is available only on desktop browser that support this features.
Printing the Asset and its Metadata
In order to print an asset, press on the ellipses icon from the bottom right corner and open the toolbox. In there, you will have the option of printing.
Note: currently only image and PDF assets can be printed.
In order to print the metadata, press on the info icon from the bottom left corner and open the asset information panel. Inside it, a new link will be available which will allow the user to print the metadata associated to the asset.
Managing Third-party Dependencies
When the application is being accessed, a check against the configuration is made. If a service does not have the required API key present in the configuration manager, the code will not load any third party libraries or dependencies associated with it.
How to configure the new implementation?
Search Engine Optimization
In the ConfigManager there is a new sub-tab for Meta tags. Here you can control the http meta tags (name, content pair) that the default page renders. Notice that this is only for global entry level tagging. More granular content specific SEO control will be available in a later release. You may specify any number of meta tags that will be automatically rendered in the page. However, take a notice on SEO best practices as having vast amount of tags might turn out to be counterintuitive.
Notice:
The system is pre-configured with some common meta tags that you probably want to edit to match the usage of the Digizuite™ Media Manager.
PDF Reader
Changes in Searches
The new PDF Reader requires that the GetAssetsById and DigiZuite_System_Framework_Search searches will return a value field named pdfUrl. This update is normally made automatically when running the upgrade scripts. However, if you are using a modified version of any of the searches upper-mentioned, you will need to update the XML of the search and add the following value field manually:
<valueField id="pdfUrl" fieldName="asset.urlAbsolut(B1BB6F18-6FE5-441A-A3FA-E6FCA2769ACB,DA6EAD4E-6259-489C-98DF-8581C23C0F0E)" />
Asset Republishing
It is required that you republish existing PDF assets after upgrading to MM 4.7.0 is you wish to be able to render them in the PDF viewer.
Printing the Asset and its Metadata
Two new variables are introduced in order to allow styling of the print button in asset info.
@color-assetMetadata-print-link : #f1c312; @color-assetMetadata-print-link-icon : #fff;
DOs
DON'Ts
Tips & Tricks
Clippy
In response to the numerous request from important clients, we have started to integrate Clippy into Media Manager. Clippy will analyze your usage behavior and using advanced neuronal networks and cutting edge Roy-Floyd algorithms, will determine when you need help or instructions in using the site.
What has been released?
What is in the next release?