MySource Matrix has been superseded by Squiz Matrix. This site will remain available for archival purposes only; it is not intended as a current source of Matrix information. For all the latest on Matrix, including documentation and release information, visit the Squiz Matrix site.
On Friday 17th October 2008 at the International MySource Matrix User Conference, Squiz hosted a fun and innovative event designed to seek users' input on Squiz funded feature development - the MySource Matrix Feature Bazaar.
Squiz committed to funding $120,000 worth of new feature development for MySource Matrix and the MySource Matrix Feature Bazaar allowed conference delegates to 'buy' fantastic new features using "Squiz money". Each conference delegate was issued with 1,500 SquizDollars and a list of features available for sale at the Bazaar, which was insufficient to buy all features for sales so some items were sold while others were passed in. You can find details of how the Bazaar operates here.
The Feature Bazaar was a huge success with many clients pooling their "Squiz Dollars" to buy the features they wanted. The following list of features were sold:
When you edit a division on the Edit Contents screen, there is no indication as to whether or not it has been linked to another asset in the system. For example, you may be changing the content of five different pages in your site and you may not know, as there is no indication on the screen.
This feature will add a visual indication that a division has been linked. This will mean that when you edit the content of the division, you will know whether or not it will affect more than one page in the site.
Currently the Trigger event User Logout is available. This event is fired after the user has logged out. This means that if you wanted to use the conditions and actions for the current user it will be the public user as they have already logged out. For example, if you wanted to send an email to the user letting them know that they logged out, you could not use this event, as the current user will be the public user, which does not contain the correct details.
This feature will add a new event that will allow the Trigger to be fired just before the user has logged out. This means that you will be able to access the details of the users account and achieve the Trigger that is outlined above.
Currently, the Redirect Page uses the 302 redirect. This type of redirect is used when the page temporarily exists in a different location (i.e. it has a different URL) but you want your users to use the original URL. For example, say you had a hyperlink to the latest user manual on your Home page and it to points to the URL http://example.com.au/latest-user-manual.
When the user clicks on this hyperlink, you want to take them to the latest user manual. Today, the URL of that manual maybe http://example.com.au/user-manual-1 but tomorrow it may change to http://example.com.au/user-manual-2. As you want users to still use http://example.com.au/latest-user-manual to view the latest manual, a Redirect Page can be used with the temporary (or 302) redirect.
The 301 redirect is a permanent redirect. This type of redirect indicates that the page has been moved permanently and your users should update their information for this URL, for example a bookmark. For a normal user, their bookmark will still work and they will be redirected to the new page. For a more technically savvy user, however, they will get an extra bit of information letting them know that they should update their links. These types of users include search engine robots. They will see the 301 redirect and updated their information (i.e. change the URL for the page). Any inbound hyperlinks to the old URL will also have their search engine ranking values attributed to the new page.
This feature will allow you to select which type of redirect to use for a Redirect Page - the 301 or 302 redirect.
Currently, when you use a Nest Content division, to locate the asset that is being used in the Asset Map, you need to find the id of the asset on the Edit Contents screen and enter it into the Quick Search field. Once you have found the asset, you can click on the icon in the info bar to find it in the Asset Map.
This feature will add the icon to the division so that you will not need to perform a search for it. Instead, when you click on the icon, the asset will be highlighted in the Asset Map on the left hand side of the screen.
The What's New asset does not have the dynamic parameters field on the Details screen; hence you cannot dynamically change the root node of the asset like the Asset Listing. This feature will add these fields onto the What's New asset.
This feature will add the total size (in bytes/kbytes) of the output of the asset on the Preview screen. This will allow you to monitor the size of the pages and ensure that the figure stays below a standard size.
This feature will add a Do Not Delete option when you manually create a remap in the system. When you select this option, the remap will not be deleted from the system unless you un-tick the option on the Details screen of the Remap Manager.
On the Asset Listing page you are able to filter the list of values by a Link Value. This value is checked against the Value entered on the Linking screen of an asset. For example, if you enter a value of landscape or portrait on the Linking screen of each Image in your site, you can create an Asset Listing that will only shown landscape images by entering landscape in the Link Value field on the Details screen of the Asset Listing.
This value on the Linking screen can only be set against a TYPE_1 or TYPE_2 link, as shown in the figure below.
This feature will allow you to set this value against NOTICE links as well, allowing you to create relationships between assets rather than linking assets. You are then able to create an Asset Listing page that is based on this relationship. For example, you can create a relationship between a user and their favourite products and then list these products via an Asset Listing page.
Currently any user who has Write Permission to an asset can add or delete a division on the page. This feature will allow you to stop certain users from being able to do this on the Edit Contents screen. The user, however, will still be able to move, link, clone and delete divisions in the Asset Map. For example, on the Edit Contents screen of the Home page, the user will not be able to add a division. They can, however, clone a division from the Contact Us page and add it to the Home page in the Asset Map. They will also be able to change the Content Type of an existing division.
This feature will allow you to select the default presentation type for a division when it is first added to a page. The options available will include Block-level, Inline and Raw HTML. When the division is created, the value that is selected in this field will default into the Presentation field on the DIV Properties screen.
Currently when the workflow email is sent for an asset it will include each of the dependant assets. For example, if you have a Standard Page with five divisions, it will send six workflow emails - one for the page and one for each division.
This feature will change this behaviour so that the workflow emails will only be sent for the dependant assets if they have been linked in more than one location. For the example outlined above, only one email will be sent as none of the five divisions have been linked to another asset in the system. If say two divisions have been linked, then three workflow emails will be sent.
Currently, if you want to create a hyperlink similar to Contact Us at squiz@squiz.net or Click here to go to http://squiz.net, you need to enter the content into the WYSIWYG Editor and use the Insert Link pop up to enter the details for the hyperlink.
This feature will add a new plugin that will allow you to create hyperlinks with the text that has already been entered into the WYSIWYG Editor. For example, you can enter Contact Us at squiz@squiz.net, highlight squiz@squiz.net and click the button to create the hyperlink. MySource Matrix will use the text that has been highlighted as the hyperlink. A preference will also be available to allow you to turn off this plugin for certain users.
This feature will allow a System Administrator or the Root User to log into the system as a different user. This may then allow them to reproduce a problem in the system that has been reported by a specific user.
When you add a new asset to the system, it can take some time to use the Add menu option. You have to click the Add menu button, go to a sub menu, select the asset type you want to add, select which area of the system to add it to and then create it. Sometimes when you do this, you may want to add several of the same asset type to the same part of the system. For example, you may be creating a new site and want to add five Standard Pages under it.
This feature will add an Add new <asset_type> here option to the menu, where <asset_type> is the type of asset you just added. For example, if you just created a Standard Page, when you right click you will see Add new Standard Page here in the menu. If you then create a PDF File, this will change to Add new PDF File here.
This feature will add a WYSIWYG Editor plugin that will allow users to embed a YouTube video into the page. This will be similar to the Insert Image or Insert Movie options, where when you click on the button in the toolbar, a pop up will appear where you can set the options for the YouTube video. A preference will also be available to allow you to turn off this plugin for certain users.
When you create a Trigger and use the Set Future Status action, you can only set the date and time for this job to:
A certain number of days, hours and/or minutes after a date and/or time that was entered in an attribute field on the asset. For example, set the date and time to 10 days after the value that was entered into the end date field for a calendar event.
This feature will allow you to set the date and time of the future status job to a value that is entered into a Datetime field on the Metadata screen of the asset.
Currently, before you can add an image onto the page you need to upload it to the system by creating an Image asset. Once you have created the Image asset, you can use the Insert Image pop up on the WYSIWYG Editor to insert it into the content of the page.
This feature will allow you to create a new Image asset from the Insert Image pop up. You will be able to select where to create the Image asset and which file to upload.
Currently on Cache Manager you can change the cache settings for certain asset types. For example, you can turn off caching for the Standard Page or Custom Form. By doing this, you will be affecting the cache for all assets of this type in the system.
This feature will allow you to change the cache settings for a section of the system or an individual asset. So, for example, you can turn off caching for all assets in your intranet site but leave it on for all assets in your intranet site.
SOAP (or Simple Object Access Protocol) provides a way for applications that are running on different operating systems, with different technologies and programming languages to communicate with each other.
This feature will add a SOAP server to MySource Matrix. It will allow external applications to perform basic functions such as adding assets, linking assets and publishing assets.
To be able to use the Simple Edit Interface, currently a user needs to have at least a Backend User Account. By having this type of account, however, they can also access the Administration Interface. There is no way of stopping them from doing this, so that users who have been trained to only use the Simple Edit Interface can still access the Administration Interface.
This feature will add a new type of user account. This user account will only be able to access the Simple Edit Interface and not the Administration Interface. These users will still be able to perform the same tasks that a Backend User with Write Permission can do, but they will not be able to log into the Administration Interface, only the Simple Edit Interface.