MySource Matrix Resources

Bazaar introduction | Bazaar rules | Features passed in | Features sold

Features sold at the Bazaar

Squiz has committed to developing all of these features and adding them to MySource Matrix before the 2008 International User Conference. We have noted the release version we expect the feature to be available.

Hiding Frames by Default in Simple Edit ($2,000) [To be released 3.18]

Within the Simple Edit Interface, when you add "?hide_frames=1" onto the end of the URL, the bar at the top of the screen and the purple bar down the left hand side are hidden, as shown in the figure below.

You have to know to put this onto the end of the URL to remove these bars. This feature will allow you to tell MySource Matrix not to show these frames by default.

Conditional Design Elements ($2,000) [To be released 3.18]

This feature will allow you to add conditional elements to a Design that will be used based on the Status of the asset. This will mean that you can change the look and feel of your design. For example, if the asset is Under Construction, a different colour or a background image may appear within the design.

Multiple Root Nodes for Clearing MySource Matrix Cache ($2,000) [To be released 3.18]

On the Clear Cache screen of the Cache Manager, you can only select to clear the cache for one root node in the Choose Asset field, as shown in the figure below.

If you want to clear the cache for more than one root node (for example two different sites in your system) you will have to do it twice (i.e. enter the information for the first root node and click Commit, then repeat the process for the second root node).

This feature will allow you to clear the cache for multiple root nodes at once.

Have Jobs in the HIPO Herder be resumed in a New Window ($2,000) [To be released 3.18]

When resuming a HIPO job on the HIPO Herder screen, the job appears in the editing screen of the Administration Interface, as shown in the figure below.

If the job that is being resumed is large, it can be a slight hindrance waiting for it to finish before being able to perform any other work.

This feature will resume the HIPO job in a pop up window, similar to how other HIPO jobs work.

Search for URL in Remap Manager ($2,000) [To be released 3.18]

On the Details screen of the Remap Manager, the remapped URLs are broken up into a number of pages, as highlighted in the figure below.

If you are looking for a particular remapped URL, you may need to look through a number of pages, which may take you a long time.

This feature will add the ability for you to search for a URL in the list.

Expose the user name on the History screen of an Asset ($2,000) [To be released 3.18]

On the History screen of an asset, the name of the user who made the change is not displayed, as shown in the figure below.

This feature will add the user name for each record listed on this screen.

Asset Finder Field – Find by Asset ID ($2,000) [To be released 3.18]

When you are using an asset finder field within MySource Matrix, you have to know where the asset is located in the Asset Map to be able to select it. In other words, you have to click the Change button (the Asset Map on the left hand side will turn purple), right click on the appropriate asset and select Use Me.

This feature will allow you to enter the id of the asset you want to use without having to select it within the Asset Map.

Add a _recache Suffix ($2,000) [To be released 3.18]

This feature will be similar to the _nocache suffix, however, when _recache is entered onto to the end of the URL, it will clear the cache for the asset you are viewing rather just displaying the non-cached version.

Configurable Character Limits on Metadata Text Fields ($3,000) [To be released 3.18]

When you add a text field to a Metadata Schema you cannot restrict the number of characters that a user can enter. For example, the user can enter 600 characters for a description even though you may only want them to enter 200 characters.

This feature will allow you to restrict the number of characters the user can enter into a metadata text field.

Also allow size of the text boxed to be configured by users.

Avoid Remapping Web Paths ($2,000) [To be released 3.18]

When you change the web path of an asset on the Web Path screen, a remap is automatically created by MySource Matrix. For example, if you change the web path of the http://squiz.net/contact_us page to http://squiz.net/contactus a remap will be automatically created from the old URL to the new URL.

This feature will allow you to stop the remap from being created when you change the web path. This will mean, for example, that if you change a web path for an asset that is Under Construction, you can stop the remap from being created and hence, cluttering up the Remap Manager with redundant remaps.

Option to Use Divisions for an Image Content Type ($4,000) [To be released 3.18]

When an Image content type is added to an asset, the <table> tag is used in the HTML source code for that division. This feature will allow you to select to use the <div> tag instead, which is preferred when building an accessible site.

CAPTCHA Field on the Asset Builder ($4,000) [To be released 3.18]

This feature will allow you to add a CAPTCHA field onto the Asset Builder page. A CAPTCHA field is a method of asserting that the submissions that are being made on the asset are done by a human rather than an automated system. This is similar to the CAPTCHA field on the Custom Form, as shown in the figure below.

Stop a Specific Asset from Displaying in an Asset Listing ($4,000) [To be released 3.18]

This feature will allow you to specify which assets should not be included in an Asset Listing. For example, if you have set up an Asset Listing to display all Standard Page assets in your site, you can exclude the "Home" page from the list.

Approving Multiple Steps in Workflow ($4,000) [To be released 3.20]

If a user is part of several steps in a Workflow Schema, they need to approve each individual step in the approval process. For example, say you have set up the following Workflow Schema:

• Step 1: A user from the "Content Editors" User Group must approve

• Step 2: A user from the "Content Approvers" User Group must approve

• Step 3: A system administrator must approve

The user "John Smith" is a Backend User that has been linked into both the "Content Editors" and "Content Approvers" User Groups. When a user applies for approval on a page, "John Smith" will have to approve step one and then repeat the process to approve step two.

This feature will give a user the option to auto-approve the current step and any consecutive steps they are part of. This will mean, for example, that when "John Smith" approves step one, he will be given the option to automatically approve step two without having to repeat the process.

Add an Approve and Reject link to the Workflow Email ($4,000) [To be released 3.18]

This feature will add an approve and reject hyperlink in the email that is sent to the approver in Workflow. Currently, the email contains a hyperlink to the Workflow and Preview screen, as shown in the figure below.

By adding these hyperlinks, it will mean that a user will no longer have to go to the Workflow screen to approve or reject the changes. Instead, they can click on either of the two hyperlinks and the system will approve or reject the changes for them.

Separation of Option/Value Pairs for Custom Form Select Fields ($7,000) [To be released 3.20]

The select field type on the Custom Form does not allow you to add a separate option/value pair in the list. It only allows you to add an option, as shown in the figure below.

This feature will allow you to add separate option/value pairs to the list. This will mean that you can show the user one set of values but store a different set of values in the submission logs. For example, you can show the value "Content Management System" in the list but store the value "CMS" in the submission logs.

Send the User who started the Workflow the Reject Email Notification ($7,000) [To be released 3.20]

When a step in Workflow is rejected by a user, an email is sent to the users involved in the approval process, not to the user who made that changes and applied for approval. This feature will allow you to send an email to this user as well as the people involved in Workflow.

Asset Sorting Tool – Sort by Asset Field ($7,000) [To be released 3.18]

The Asset Sorting Tool currently allows you to sort the assets in the Asset Map by standard asset fields, for example the name of the asset, the short name or the asset or the id of the asset. This feature will also allow you to sort by asset attributes. For example, if you select the asset type Single Calendar Event, you will be able to sort by the Start Date of that event.

CSV Asset ($7,000) [To be released 3.18]

This feature will allow you upload a CSV file of information into MySource Matrix. For each row listed in the file, a shadow asset is created. These shadow assets can then be listed in an Asset Listing, for example.

Use HTML Tidy as an Accessibility Checker for Bodycopies ($7,000) [To be released 3.18]

This feature will allow HTML Tidy to perform an accessibility check on each block of content when it is saved and passed through HTML Tidy.

Metadata Value Cascading ($7,000) [To be released 3.18]

When you enter a value into a metadata field on the Metadata screen, you cannot cascade the value to the child pages of the asset. For example, say you have a metadata field called "Subject" and you have a section called "MySource Matrix Training". You want to enter "Training" in the "Subject" field for each asset in that section. To do this, you need to go to the Metadata screen for each asset and fill out the field.

This feature will allow you to cascade a value that you enter on the Metadata screen. This will mean, for example, you can go to the Metadata screen for the "MySource Matrix Training" page, enter "Training" into the "Subject" field and cascade this value to all assets in that section.

System Maintenance Screen ($10,000) [Expected Release - Unknown]

This feature will add a system maintenance screen where you can view information about your system. The screen will list recommend maintenance tasks that should be performed on your system. Some of these tasks may be performed from this screen.

MySource Matrix Mapping Asset ($20,000) [Expected Release - Unknown]

This feature will add a generic asset that allows data to be passed into Google Maps. This will mean that you can pass through points of interest and show it on a map. For example, you can enter coordinates for all of the parks in your area and plot these on a map. Each point of interest can then link off to another page in your site where the user can find out additional information about the location.

Apply Simple Edit Layouts Using a Root Node rather than System Wide ($26,000) [To be released 3.20]

This feature will allow you to apply Layouts to a root node rather than system wide. This will mean that you can have one set of Layouts for one site, and a different set for a second site.