Cms recommendation Report



Download 0.85 Mb.
Page4/8
Date31.05.2016
Size0.85 Mb.
TypeReport
1   2   3   4   5   6   7   8



Capability to view the history of a content item and its various versions, as well as version control over the site or sub-sites.




Highly desirable

Y/FC

Appropriately authorised users may view the history of the system, or asset, or group of assets (sites) and rollback to view information from a specific point of time in the past.

In rollback view you see the entire system at the point in time you roll back too.





Past versions of pages can be retrieved from the CMS (rollbacks).

Please describe.

Mandatory

Y/FC

Individual pieces of old content may be copied and used to replace current content versions. Old versions of content can be restored using one of two strategies:

  • restore from backup

  • copy and paste content from roll-back view over the current content version



Capability to deploy an archived (historical) version of the entire site or sub sites.

Any other method?

Desirable

P/ALT

Clients may use the open source website copier product HTTrack to copy a website and host on a website or save to CD-ROM, tape etc.



Capability to automatically capture web-based records and export them as records for management within an external records management system




Desirable

Y/FC

Squiz provide a script that allows you to export the entire contents of your MySource Matrix repository and move it to external storage. Squiz recommends that archived content is retained in the system until records management policies deem it appropriate for the files to be moved. Administrators may purge content older than a nominated date. Content that has been purged from the system will not be available in roll back mode. Content may also be sent to other backup media such as tape. User intervention does not have to be required as the system can be entirely managed with Cron scripts.

Content is exported either as a dump file (tar.gz), in a proprietary XML format (which can then be imported) or in a custom format as defined by an asset listing. The asset listing allows you to print all information about an asset in whatever format you define using MySource Matrix keywords.

Content can be exported from Matrix in XHTML format, for use in third party document management systems (TRIM).




Ability to display differences between versions of a page.

Functionality was not available in 3.6 of the release – has it since been included or are there any future plans for incorporating it in a general release?

Mandatory

Y/WM

(3.12)


Matrix allows you to visually compare the Safe Edit version of pages to the current Live version by highlighting the differences in content – version 3.12 only.

Content Delivery & Deployment




Content Delivery & Re-use



Output from the CMS must comply with current UWA Web guidelines.

Specifically accessibility and metadata.

Mandatory

Y/FC

Matrix supports HTML 4.01 or XHTML 1.0 and W3C’s Web Accessibility Initiative Web Content Accessibility Guidelines priorities 1, 2 and 3.

Compliance with the web guidelines beyond the capacity to publish valid X/HTML and meet WCAG 1/2 Priorities is a product of how designs and content are implemented in the CMS rather than the CMS itself.





The CMS should produce XHTML compliant output.

Please confirm.

Mandatory

Y/FC

Matrix supports HTML 4.01 or XHTML 1.0. Content created in the WYSIWYG editor is filtered through the open source tool HTML Tidy to ensure it forms valid HTML or XHTML.



A solution that decouples content from presentation, enabling an item of content to be delivered via a wide range of presentation media and devices and into a variety of formats.

Please describe.

Mandatory

Y/FC

Matrix allows users to define their experience by choosing between multiple designs when visiting your site i.e.

- HTML/XHTML page using standard website design

- printer friendly format

- low bandwidth version

- text-only version

- PDA suitable format





Ability to re-use single instances of content in multiple locations/sites in the CMS to avoid the duplication of information.

Please describe.

Highly desirable

Y/FC

Each asset is a separate entity that may be easily re-used in many different places by creating a link to the original data source rather than duplicating it. When content is presented on multiple pages/sites, it inherits the destination page/sites design and style sheet applicable to each location.



Ability to automatically provide and generate printer-friendly versions of pages.




Desirable

Y/FC

Matrix allows users to define their experience by choosing between multiple designs when visiting your site i.e. printer friendly format.



Ability to provide both static and on-demand generation of content.




Mandatory

P/ALT

Matrix uses a dynamic publishing model rather than publishing content to a separate server for deployment.

Third party tool HTTrack (open source) can be used to create a separate, static version of the Matrix site.





The CMS should provide the option to not be the delivery platform (CMS unavailability would not affect the live website).




Highly desirable

P/ALT

Matrix uses a dynamic publishing model rather than publishing content to a separate server for deployment.

Third party tool HTTrack (open source) can be used to create a separate, static version of the Matrix site.





Ability to dynamically produce and automatically update site navigation on output based on site structure.




Mandatory

Y/FC

Implemented via design templates.



Ability to provide dynamic site map generation.




Desirable

Y/FC

Site Map page template allows you to create a self generating site map that updates as the site structure updates.



Ability to provide search engine functionality that searches HTML and XML pages, Microsoft Office documents and Portable Document Format (PDF) files.




Mandatory

Y/FC

MySource Matrix may be extended with a powerful search engine module. Indexing includes Word/PDF documents as well as native HTML pages including metadata. The module is free to government, educational and not-for-profit organisations.

Search manual provided.






Deployment



The CMS supports secure deployment or publishing.

Please describe.

Mandatory

P/ALT

Matrix uses a dynamic publishing model rather than publishing content to a separate server for deployment.

Matrix does allow you to secure different areas of your site independently. You can set areas to be publicly accessible, others to require authentication and even set certain areas of your site to require SSL authentication.

At the MySource Matrix level, the access control mechanisms of the underlying operating system are utilised to ensure that only the webserver user has write access to the public data directory (which is needed for storing uploaded files and cached content) and write access is denied to the PHP source code. The access control mechanisms of the database restrict access to the MySource Matrix and the HIPO Server processes.

Additionally, it is important to ensure physical access to your web server is restricted, and the user accounts are strictly controlled.

External access to your server hosting the CMS should also be protected through a perimeter firewall, a firewall on the CMS server itself, and through the configuration of Apache directives, and the use of SSL.

Finally, your server could be configured so that the Apache web server is the only process listening to the network externally.





The CMS supports deployment to test and production servers.

Please describe.

Mandatory

P/ALT

As Matrix is open source it can be installed on as many servers as necessary and testing can be performed of new versions before upgrading the production environment.

In terms of content, Matrix allows you to host your live site and your test environment within a single system. You can create a test site with a test URL, and link the existing assets in whatever hierarchy you like.





The CMS must be capable of publishing content to multiple sites, or multiple locations on the same site, with presentation depending on the target site.

Please describe.

Highly desirable

Y/FC

There is no duplication - Each asset is a separate entity that may be easily re-used in many different places by creating a link to the original data source rather than duplicating it. When content is presented on multiple pages/sites, it inherits the destination page/sites design and style sheet applicable to each location.



The CMS supports scheduled deployment of content.

Please describe.

Desirable

Y/FC

Future status functionality.

User Authentication & Management




Authentication



Accessing CMS management and authoring functions will require authorised users and groups to authenticate.




Mandatory

Y/FC






Supports and integrates with Directory Services for user authentication, such as Active Directory / LDAP.

Please describe.

Mandatory

Y/FC

Matrix can be configured to interface to an LDAP directory for user and role information via the LDAP bridge.



All password related transactions must be via a secure encrypted channel, such as SSL. There must be no plain text password communications.

Please describe.

Mandatory

Y/FC

SSL is used for authentication and session security is handled through PHP sessions/cookies.

A login key is used for authentication to stop stolen requests or cookies. Client side PKI certificate authentication requires appropriate configuration of Apache.





Ability to integrate with an enterprise-wide single sign-on user authentication solution via the use of a plug-in or provision of an API.

Please describe.

Mandatory

Y/FC

MySource Matrix is an open source system to which the full API is available. Integration with other systems tends to be easier because the source code is open and based on open standards (e.g. PEAR)



Login should be simple and straight-forward, and kept to a minimum.




Mandatory

Y/FC

Login is only required once per browser window session.



The interface should clearly identify who has logged in.




Mandatory

Y/FC

Displayed in the top left corner of the browser window.




User Management



Supports tiered users i.e. super-users / site administrators / site developers / site contributors.

Please describe.

Mandatory

Y/FC

Allows you define the functions available to each user, and the assets to which they have access.

Matrix has the following types of user, each of which has varying access levels:



  • Normal user

  • Backend user

  • Administrator

  • Root User



Ability to use existing Directory Services groups or roles and apply them in the CMS.

Please describe.

Mandatory

Y/FC

MySource Matrix supports authentication from LDAP or Active directory and single sign on using Kerberos authentication.



Supports multiple groups.

Please describe.

Mandatory

Y/FC






Supports roles-based permissions with the ability to assign users and groups to particular roles.

Please describe.

Mandatory

Y/FC

Roles are a specialised form of user group – you can grant permissions for roles and include them in steps within a workflow schema. However, unlike user groups, the users who are assigned to roles are not fixed. Rather you can define which users and user groups are assigned to a role for individual assets.



Ability to add, modify, and delete directories and files based on user/ group/role permissions.

Please describe.

Mandatory

Y/FC

Allows you define the functions available to each user, and the assets to which they have access.



Ability to cascade / inherit permissions at specified tree levels rather than only site or page level.




Mandatory

Y/FC

Matrix gives you the option of cascading privileges to all assets beneath a specified page in the hierarchy.



Users and permissions must be easy to administer for super-users and site administrators.




Mandatory

Y/FC

System administrators can create and manage user accounts via an intuitive point-and-click interface.



Supports an unlimited number of content contributors.

What is this dependant on? Memory?

Mandatory

Y/FC

No system limitations on the number of content contributors. For optimum performance you will require adequate hardware.



Has no restrictions on the number of concurrent users of the CMS i.e. the number of users logged in at one time.

What is this dependant on? Memory?

Mandatory

Y/FC

No system limitations on the number of concurrent users. For optimum performance you will required adequate hardware.

Reporting & Review Tools



All activity in the CMS should be automatically logged including unauthorised attempts to access the CMS/database.

Please describe.

Mandatory

Y/FC

Comprehensive audit logs are generated for every change to every asset in the system log:

  • permission changes

  • attribute changes

  • links created

  • assets created

  • status changes

  • schema changes

  • login/logout

  • workflow changes



There should be tools that validate the metadata stored with resource.

Please describe options for validating metadata.

Mandatory

P/ALT

Metadata entry can be enforced, defaults specified and controlled vocabularies (select fields, thesaurus) used to ensure correct metadata entry.



Tools for analysis of the CMS logs should be included in the CMS management /administration and reporting should be provided including error and exception reporting.

Please describe.

Mandatory

Y/FC

Error message generated by the system are recorded. You can configure if errors are logged, the level of logging including whether to include the file line and number, and a stack trace.



The CMS should issue appropriate alerts whenever exception conditions occur so that prompt action may be taken to resolve the condition.

What options are there for issuing alerts – Email? SMS?

Mandatory

Y/FC

The system can be configured to automatically email an administrator when certain errors are encountered.

MySource Matrix uses standard email to deliver alerts. You could use a third-party email-to-SMS gateway to deliver those messages via SMS. Squiz monitor our servers using SNMP monitoring (outside MySource Matrix).





There should be reporting on when content is published to production, either manually or dynamically as part of a scheduled deploy.

Please describe.

Mandatory

Y/FC

Logs are generated for all status changes.



There should be review tools that can check internal and external links. These tools should provide reporting that also identifies permanent redirects and problem resources. It should be possible to conduct such checking on a specified section of the site and reports should be exportable in HTML format.




Highly desirable

Y/FC

Links report.

Version 3.14 of Matrix will have the ability to display Links Reports on the front-end and schedule them to be regenerated.

Currently Links reports don’t identify the text of the broken link i.e. the text within the tag. An enhancement request (via bug tracker) is required.




Online link management should provide an option to automatically update links upon moving a file or provide alerts regarding broken links as a result of a deleted document.

Please describe.

Mandatory

Y/FC

If a page or site is moved within MySource Matrix, any links to that asset on other pages are updated automatically and instantly. Attempts to remove an asset or group of assets will alert the use to potential link problems (e.g. broken links) and allow the user to take remedial action.



Tools for the analysis and management of web server logs should be included in the CMS management/administration for producing statistical reports on web usage. Reporting should provide comprehensive statistical analysis of usage to at least the depth of popular web server log analysis tools. It should also be able to map and display user pathways through the content.




Highly desirable

P/ALT

AWStats (open source)

Webalizer (open source)

WebTrends (commercial)

Neither AW Stats or Webalizer map user pathways through the site.





The CMS should contain an asset reporting providing comprehensive information on the assets stored in the CMS and operations on them, including:

Please identify all information provided per asset.

Mandatory

Y/FC






  • Date resource was created and last updated.

Please describe

Mandatory

Y/FC

System log reports on asset created, workflow and status changes.



  • Activity by user and group access levels.

Please describe

Mandatory

Y/FC






  • Expired resources and resources nearing expiry.




Highly desirable

Y/FC

Up For Review status indicates the Live version of an asset is due for review. If workflow is applied to the asset, each of the users in the first step of workflow receive a message notifying them it is time to review the asset.



  • Orphan resources.




Highly desirable

P/ALT

Matrix does not allow pages to become orphaned, since pages can only be created beneath a site or page.

To identify pages that have no NOTICE links to them you could perform a DB query.





Review tools that streamline quality assurance processes by validating the page output against technical standards.

Is this done by HTML Tidy? Any other mechanisms?

Desirable

Y/FC

Automatically corrects invalid tags via HTML Tidy.




Review tools that identify similar pages (i.e. via metadata) and reporting that provides a list of these pages which may be duplicates or partial duplicates of each other.




Desirable

P/ALT

The only way to achieve this would be to setup metadata search pages i.e. keywords. The results would list all pages with the same unique keyword.

Help Facilities, Error Messages and Documentation for Administrators




Help Facilities & Error Messages



Availability of context-sensitive help messages using language understandable by the novice user.

Please describe.

Highly desirable

Y

Contextual online help is available from within Matrix and the WYSIWYG editor, and tool tips are displayed. This is augmented by user documentation available online, written clearly in simple language and which includes workshops to help authors through the process of creating content.



Availability for all system failures to generate context-sensitive error messages using language understandable by the novice user.

Please describe.

Highly desirable

Y

Matrix employs many strategies to reduce the need for error messages to be generated at all, including sensible messages explaining the consequences of certain actions and the removal of functionality for users not trained in their operation. In the event these strategies fail, errors are recorded in a log file and also in the internal messaging system. The system can be configured to automatically email an administrator when certain errors are encountered.



Ability to locally customise help and error messages to express desired remediation and suggestions appropriate for separate user interfaces.




Highly desirable

P/MAJ

A custom translation for all error messages could be written and the translation system to install them. This would require a fair amount of work, but it is possible.
This requirement can vary depend on the amount of error messages etc and estimate this would take around 2 weeks (10 days @ $1,200 + GST per day of people time)



Ability to provide hyperlinks on any page to online help and references.

Please describe.

Desirable

P/ALT

There is no help within the MySource Matrix system.

Online help consists mainly of large PDF manuals that could be linked to, but would not be very efficient in locating specific information.

Links could be provided to useful threads/posts in the user forum.





Documentation for Administrators



Availability of comprehensive electronic documentation, with permission to excerpt and adapt this documentation for institutional use, including:

Please describe for all and/or link to where appropriate.

Mandatory

Y/FC

As below



  • functional descriptions of major components (e.g. interface configuration and navigation, workflow, versioning, metadata, user authentication, etc.)

Please describe.

Mandatory

Y/FC

System Administrator manual:
http://matrix.squiz.net/__data/assets/file/0016/11770/SysAdminManual_3.10.0b.pdf



  • help and error messages, including default message texts.

Please describe.

Highly desirable

P/ALT

The error messages describe the problem themselves; that is all the documentation currently available. Each has an error code that allows the Squiz Support team to debug any problems in code.



  • user authentication and access functionality.

Please describe.

Highly desirable

Y/FC

Fundamentals manual:
http://matrix.squiz.net/__data/assets/file/0003/12639/Fundamentals_3.10.0a.pdf

Also DAP package manual.





  • workflow customisation options.

Please describe.

Highly desirable

Y/FC

System Administrator manual:
http://matrix.squiz.net/__data/assets/file/0016/11770/SysAdminManual_3.10.0b.pdf



  • system level options for customising the application, including any tools for transferring local customisations to upgraded software.

Please describe.

Highly desirable

P/ALT

Customising the application:

System Administrator manual:


http://matrix.squiz.net/__data/assets/file/0016/11770/SysAdminManual_3.10.0b.pdf

There are no tools for transferring local customisations to upgraded software. If you change the source code, we can't automatically bring those changes across.





  • system level diagnostic and recovery tools.




Highly desirable

Y/FC

Server Administration manual, along with the MATR401 Server Administration course that covers system level issues.




Demonstrations



Availability of onsite or easily accessible demonstrations of the latest version of the CMS.




Highly desirable

Y/FC

Via VPN.

Compatibility with existing UWA hardware and software systems




Hardware and Software Requirements



Ability to host the application locally.




Mandatory

Y/FC






Ability to integrate into a diverse office environment and be accessed by Internet Explorer 5.5+ and Mozilla Firefox 1.3+ web browsers.

Please list all browsers that can be used to access Matrix.

Mandatory

P

Compatability testing performed for IE 6+ only.

Need to perform testing for IE 5.5.

Camino also supported for Windows, Mac and Linux.




The CMS should be accessible to web authors and end-users on any operating system supporting the browsers described in 99.




Mandatory

P

MySource Matrix is entirely browser based and therefore is compatible with a wide range of client standard operating systems. (Need to test IE 5.5).



Provision of a secure web-accessible administrator interface.




Mandatory

P/ALT

Admin interface is accessible via a web browser and requires authentication via login to access.

The admin interface of Matrix is itself not web accessible however it is possible to create templates that allow web accessible updating of content through the front-end ‘Simple Edit’ interface.





Provision for complete and robust recovery in case of operating system failure.

Please describe.

Mandatory

Y/FC

Matrix ships with a backup script that can create a full point-in-time backup of the Matrix system (which incorporates all websites contained within the system).



The CMS should integrate with and support deployment to Windows and/or Linux operating systems.




Mandatory

Y/FC

Redhat and Debian Linux are both supported.

Squiz does not currently support production versions of MySource Matrix on Microsoft Windows.





The CMS should integrate with Oracle DBMS.




Highly desirable

Y/FC

Matrix uses the PEAR database abstraction layer to provide greater database support including PostgreSQL and Oracle (9i or 10g).



Is extensible through an API and provides support for a standards based data exchange (e.g. XML) to facilitate integration with other systems and information sources within the University’s environment.

Please describe.

Mandatory

Y/FC

MySource Matrix is an open source system to which the full API is available. Integration with other systems tends to be easier because the source code is open and based on open standards (e.g. PEAR)

There are several ways to interface with external systems / data sources;



  1. DB Data Source

  2. RSS Data Source

  3. Remote Content

  4. Custom assets

  5. Asset bridge (LDAP)

Matrix also provides the DB Data Source to allow you to connect to a local or external database and execute a query. The DB data source asset contains a GUI interface to build simple queries. The results of the query will be displayed as shadow assets in the asset map, and you can display the query results using an Asset Listing.

Matrix fully supports outbound content syndication with the creation of RSS feeds with the RSS Feed asset which generates a valid RSS (1.0 or 2.0) or Atom (1.0) feed from an existing Asset Listing asset. Inbound information can be syndicated via the RSS Data Source which allows you to connect to any valid RSS feed and show external RSS items as shadow assets within your MySource Matrix system. You can then display the feed within your own site by using an Asset Listing to list the RSS items in the feed.

Inbound content can also be managed using a tool known as Remote Content – a screen scraper application. Irrelevant information can be stripped and formatting replaced on screen scraped content. URL info may also be replaced to allow users to surf through the remote content without leaving your Matrix site.

The system can be extended by adding new asset types (custom assets). For example an asset class could be developed to deal with output from an external application allowing simple and powerful integration.

Squiz can provide training so that you can create custom assets yourself. Pre-requisites for this training would be a basic knowledge of PHP and XML and would run for approx 2 days. Using the custom asset architecture of Matrix and the functions available with PHP, it is possible to build interfaces to other applications using WDSL, UDDI or SOAP.

Version 3.12 of Matrix includes a generic tool which allows the loading of WDSL files and configuring a web services interface to other applications using SOAP via a graphical user interface.

Matrix does not currently support interfacing with TRIM but are currently investigating this subject on behalf of a number of clients. Squiz propose to develop an interface with TRIM Context version 5.2.1 and to support newer versions as they are released. Squiz propose a pooled development approach to build a middleware application that will be installed on the same server as TRIM Context and will manage the interface between TRIM and MySource Matrix. The middleware application (which may be written in Java or PHP) will employ the COM protocol to communicate with the TRIM API. For the first stage of the project Squiz intend to create a one-way interface to TRIM allowing records stored in TRIM to be used in Matrix. The ability to input/update records in TRIM is likely to be added in the future but is unlikely to be included in the scope of this project.

The current proposal is to create a new asset type in MySource Matrix called a “TRIM record”. This asset may have several sub types denoting the type of file. This TRIM record asset will be used to store certain metadata required to manage the interface to TRIM such as the URI (TRIM’s term for Unique Row Identifier) and access restriction information. In this model the middleware application would implement the TRIMEventProcessor method of TRIM so that when changes are made to records within TRIM, the middleware application will notify MySource Matrix of the change and update the record in MySource Matrix accordingly.

Through this model, selected files (records) stored in TRIM would be in effect “synchronised” with MySource Matrix allowing those records to be treated as normal assets in MySource Matrix. In other words this content could be:


  • Included in pages (eg images).

  • Aggregated along with other content using templates such as the site map or asset listing templates.

  • Discovered by the MySource Matrix search engine.

  • Access restricted like other content in MySource Matrix.

  • Have designs, permissions, metadata, logging, versioning and workflow applied like all other assets.

However, content managed by TRIM will not be able to be updated from within MySource Matrix in this first stage project. Rather the content would need to be updated in TRIM which would then automatically update the content in MySource Matrix.

Content can be exported from Matrix in XHTML format, for use in third party document management systems (TRIM).





Ability to interoperate with an enterprise portal overlay (RSS/JSR168).

Please describe.

Mandatory

Y/FC

Matrix fully supports outbound content syndication with the creation of RSS feeds with the RSS Feed asset which generates a valid RSS (1.0 or 2.0) or Atom (1.0) feed from an existing Asset Listing asset.

MySource Matrix can produce a harvest control list as defined by the National Archives. This metadata list can be used by other appropriately configured systems to get a snap shot of the current state of information published by the CMS.

Customisation would be required to extend Matrix to acts as a producer in a WSRP, JSR or WebPart environment. Assets could be extended to act as portlets or WebParts, whilst Matrix itself could become a producer.




Ability to integrate enterprise portlets (JSR168).

Please describe

Highly desirable

Y/WM

Customisation would be required to extend Matrix to act as a consumer for remote portlets hosted on other producers.



Ability to support and interoperate with existing and future plug and play integrated web applications, such as:

Please describe for plug and play web apps in general.

Highly desirable









  • Client subscriptions to particular content / assets




Highly desirable

P/ALT

To do this in Matrix would require extensive development or an extremely convoluted and high maintenance setup:
The way to do it is to create a user group for membership and use triggers to sent to that group when something is updated. This is very easy, the issue is that if you want to individually pick out pages you would have to create a group and trigger for each page, then a way to manage the membership of groups. The common implementation is to create a group for each section of the site and use a what's new listing to list the latest stuff then trigger an email that links back to the what's new when something is updated in that section. This is easier to set up and maintain.

Matrix does allow you to include a link to a form containing a ‘Send to a friend’ field into the design of your page. MySource Matrix allows you to flexibly define the contents of the ‘Send to a friend’ email and allows you to include the URL, Subject, a message, the ‘From’ email address and additional ‘To’ email addresses. This could be nested in the footer or another part of your design.





  • Email subscriptions lists and newsletters.

Please describe.

Highly desirable

Y/FC

The Bulk Email Module provides online registration for and delivery of emails to selected User Groups. You can create a specific Page asset as the HTML email to send as the bulk mail, and include keyword replacements to personalise the content. You can also set up multiple Bulk Mail Post Offices for different delivery methods, as well as Bulk Mail Subscriber ages to allow users to subscribe to different lists.



  • ‘News & Events’ type applications.

Is an Asset Listing the best way to achieve this?

Highly desirable

Y/FC

RSS modules includes News Asset asset type:

http://matrix.squiz.net/__data/assets/file/0004/15367/MySource-Matrix-News-Manual_3.12.0a.pdf

Also Asset listings can be used.





  • Shopping cart template.

Please describe.

Mandatory

P/ALT

Matrix has its own E-commerce module that could be used in place of the shopping cart template.



Microsoft Office documents, Adobe Portable Document Format (PDF) documents and rich media objects such as graphics and shockwave flash files can be integrated and stored with the content in the CMS.




Highly desirable

Y/FC

Any type of file may be loaded and used by MySource Matrix, as long as the file does not exceed the size requirements nominated by the server.



The CMS can enforce naming conventions for files and directories.

Please describe.

Mandatory

P/ALT

MySource Matrix preserves the filenames of imported documents, and therefore supports any naming conventions that you already have in place. However, it does not enforce any conventions for files and directories created in MySource Matrix



The CMS can use persistent and human readable URLs.

Please describe.

Highly desirable

Y/FC

MySource Matrix publishes human readable URLs, rather than a complex GET string composed of question marks, ampersands and apparently meaningless strings of characters.




Application Administration



Support for role-based system administration.

Please describe.

Mandatory

Y/FC






The CMS should be extensible with the ability for UWA to add functionality as required locally.

Please describe.

Mandatory

Y/FC

MySource Matrix can be extended with modules (also known as custom assets) that allow appropriately authorised users to create interactive content without XML/HTML or any programming knowledge.

You can choose to purchase one of the currently available modules or to write your own, the complexity being the same as writing any application in PHP.





Provision of programmer tools for UWA to perform system customisation, system configuration, system monitoring, and reporting.

Please describe.

Highly desirable

Y/FC







Performance & Scalability



The CMS solution should be highly scalable with the ability to grow with the university.

Please describe for all below and in general terms regarding scalability.

Mandatory

Y/FC

The open source, license free nature of Matrix makes installation of the CMS across multiple servers a cost-effective means of serving large numbers of web objects providing a scalable solution for the future.

By incorporating server replication at the platform level, the architecture of MySource Matrix can provide both load balancing and disaster recovery because there is no single point of hardware failure. This can be achieved, for example, through the use of Redhat Cluster Suite with fibre channel storage and GFS.





  • No effective system limitations on the number of simultaneous active users and sessions.

Please describe.

Mandatory

Y/FC

There are no software specific limits. You will require adequate hardware.



  • The UWA MySource Classic installations currently host approximately 100,000 pages totaling almost 160Gb worth of storage space (with total server capacity of 2Tb). There should be no effective system limitations on the number of pages or hosted or storage capacity in the CMS.

Please describe.

Mandatory

Y/FC

There are no software specific limits. You will require adequate hardware.

The expected size of a database is difficult to predict for any project, however it should be noted that the overhead associated with pages is negligible. The main issue to consider when looking at the expected size of the database is the size of documents and how often they are updated if rollback is enabled. Additionally adding to the size of the database is the metadata defined for each document, the number of users in the system and the number of workflow assets.





  • Individual sites within an installation will exceed 5,000 pages without impact on performance.

Please describe.

Mandatory

Y/FC

There are no software specific limits. You will require adequate hardware.

Performance as above.





  • The number of individual sites and virtual domains within an installation will exceed 500 without impact on performance.

Please describe.

Mandatory

Y/FC

There are no software specific limits. You will require adequate hardware.

Performance as above.





  • The UWA web servers peak at 1,500,000 hits per day. The CMS would need to respond dynamically to such web requests to meet this expected load plus a reasonable safety margin.

Please describe.

Mandatory

Y/FC

As volume traffic increases on a site, the processing capacity of the server must be increased to cater for the load. A single commodity Intel server (dual CPU with 2+Gb RAM) running both the application and the database is generally adequate for a medium sized government agency. Larger groups may require a separate server for the database and the application while very large installations may require a server replicated environment.

Vendor Support



Availability of 24x7 support for problem resolution.




Highly desirable

P/ALT

24/7 availability of the system can be guaranteed through a SLA. This guarantee only covers MySource Matrix but does not cover failure of the hosting environment, hardware or third party applications with which the system interfaces.



Provision of appropriate communication mechanisms for problem resolution (e.g. email, telephone etc.).

Please list communication mechanisms that are available for support.

Mandatory

Y/FC

Phone, email and support web site.

Additionally there is the bug tracker web site.





Availability of maintenance contracts.

Please attach support options.

Mandatory

Y/FC

Documentation received.



Customer support options must be available to assist in resolving problems where software upgrades negatively impact local customisations.

Please describe.

Mandatory

P/ALT

Yes, however all time is chargeable and not covered by any SLA - all SLA guarantees are rendered invalid for any system with custom development installed.



Vendor supplied best practice advice for performing backups and maintenance of the CMS.

Please comment.

Highly desirable

P/ALT

Backup and maintenance should follow existing corporate web standards. Squiz recommend evaluating the business costs of an outage and determining the best backup strategy as a balance between cost of outage vs. cost of backup storage – this is not vendor advice.

Squiz time could be paid for to devise a strategy.





Provision of multiple customer references of the CMS.

Preference for customer references interoperating Matrix with a portal product.

Mandatory

Y/FC

We are not aware of any clients using a third party metadata tool or portal integrated with MySource Matrix.



Availability of user support groups.




Highly desirable

Y/FC

http://forums.matrix.squiz.net/


New Releases



Ability for UWA to perform the installation and upgrade of the CMS locally.




Mandatory

Y/FC






Provision of tools for transferring local customisations to upgraded software.

Please describe.

Highly desirable

N

If you change the source code, we can't automatically bring those changes across.



Clearly-defined procedures and response mechanisms for handling bug reports and enhancement requests.




Mandatory

Y/FC

Support tickets logged via email / extranet.

Bug tracker system available to subscribe to and use:



http://matrix.squiz.net/developer/bug-tracker

(Also takes enhancement requests.)





Share with your friends:
1   2   3   4   5   6   7   8




The database is protected by copyright ©essaydocs.org 2020
send message

    Main page