APLAWS+ CMS features

Open source database integration

• APLAWS+ works with Oracle and now with PostgreSQL, the world's most advanced Open Source database software.  The option of which deployment to use will depend on your own business requirements.  Please see the PostgreSQL website for more information.
• A search API has been developed for both the Oracle Intermedia and the PostgreSQL Lucene search engines.

Default templates and improved template management system

• The APLAWS+ system is delivered with a set of default XSL Templates which serve as a starting point, i.e. they can be adapted rather than replaced.
• The templates have been developed to WAI AA standard and tested by the IBM Usability Labs.
• The templates are structured according to the proposed APLAWS Standard information architecture.
• As the system outputs XML, templating supports an unlimited number of custom content templates deployed using XSL Style Sheets with publishing to any channel (e.g. Web, WAP, Digital TV, etc).
• A Themes  Toolkit has been developed to allow for updating XSL templates in an FTP-style manner.  This is a consierable improvement to the way in which the first iteration of APLAWS worked.

Content creation

• Provides role-based permissions at multiple levels including content item granularity.
• A user-based and tested forms-based back-end interface for developing structured content consisting of text, images, and other binary assets.
• A WYSIWYG editor for custom content, including interaction with Cascading Style Sheet (CSS) classes.
• Provides a standard content contribution wizard for authors to follow with integrated role-based permissions
• Integrates with numerous file formats.
• Content is archived - previous versions of content allows users to rollback to earlier versions and view differences between versions.
• Use of UTF-8 to support and store multilingual content
• More authoring improvements in this release are described in the section below

Workflow

• Content moves through a series of steps during the creation process. Each step can be assigned to a customised role or user. Content is routed, e-mail notification sent and tasks assigned, documented by a full audit trail
• Provides a customizable, role-based workflow engine.
• Enables routing, e-mail notification, task assignments, and documents a full audit trail.
• Includes reporting capabilities to determine content state and user-assigned task status.

Lifecycles

• A flexible publishing model manages content lifecycles enabling scheduling of publishing and removing content items
• Automatic e-mail notifications for workflows and lifecycles when tasks are complete or content is about to expire.

Publishing

• Schedule content for publication and removal (manage content life cycle)
• Preview content items as they appear in all associated templates

Administration

• Provides security and permissions for users and groups
• Supports integration with LDAP and NTLM authentication
• Administrators specify groups, users and roles to perform specific actions, assigned by permissions.
• Administrators can delegate administrative privileges to others in a fully devolved model.

eGIF and Content syndication built into the system

• The system outputs and works with XML which is then styled by default templates - and therefore meets the baseline requirement for the UK Government Interoperability Framework.
• Supports RDF/RSS standards for syndicating content for external users. CMS can syndicate content and receive any RSS standard feed.
• Search and browse site content with advanced search across syndicated content.

Government Metadata Framework built into the authoring process

• The Government Metadata Standard fields are populated during the authoring process. Optional fields can be used for spatial data or records management.
• Supports Dublin Core metadata.

Categorisation

• Allows for many-to-many category lists to map together during the authoring process if needed.
• The Local Government Category List has been built into the system in this way, and maps to the Local Government Service list (ESD Toolkit PIDs).

Local Authority content types

• Content is organised into templates specifically developed for local government requirements.
• The basic Content Types are: Articles, Multi-part artciles, Press releases, News, and File Storage.
• Packaging tools allow for applications and Content Types to be easily installed into the system if developed by third parties

Subsites

• Several websites can be managed using the CMS with simple subsites with their own navigational categorisation.  This helps a local authority that wants to have, for example, a "youth" website to have a different look-and-feel to the main website, but still wants to keep the management of this content within the core set of skills and tools.

---

New APLAWS+ authoring improvements

The APLAWS+ code release has considerable improvements over its predecessor.  This part of the features overview highlights what these are in more detail.  

General Features

• User Home Page – all users are directed to this page on logon and will be returned to this page at the end of key tasks
• Home Folder – A Home folder can be set for each user to ensure that all content created will be placed within this folder. Each user can reset their home folder to another folder they have permission to access. Advanced users can opt to have no home folder set but to browse to a folder before creating content.
• New User Administration tab to allow administrators to set no home folder for advanced users. A shortcut from this tab goes directly to the administration application for setting up new users or groups
• Task List and Sections page are merged to form User Home Page 
• Users only see tabs which they have permission to access e.g. authors will not see categorisation tab unless they have permission to categorise items
• Task list is filtered by permission (can display owned tasks, locked tasks or all tasks) Can sort by item title, Due Date, Status and Locking User. Users selecting an item can select by task, which will take them to the authoring screens.
• Folder path is included in breadcrumb trail – truncating long breadcrumb trails
• Folder View – This can be sorted by Name, Title, Creation Date and Last Modified views
• User details are displayed on top navigation bar for audit compliance.
• Item Breadcrumb is displayed on top navigation bar.

Authoring

• New Summary Page available for each item – this includes Basic Properties information, Categorisation, a relative link, Workflow (with comments) and Lifecycle information.
• Authoring Steps Improved – 'Wizard Style' – Basic Properties/Body Text/Assign Categories/Set Lifecycle/Publish
• Items are automatically locked to users on creation or acceptance of a task.
• Summary page for published items displays a link to restart workflow
• Required metadata fields are filled in automatically – Creator, Date, Identifier, Publisher, Subject and Title are added during authoring or can be pre-populated.
• Recommended fields – Language is auto filled – Spatial/temporal coverage is also recommended – these can be added through the metadata screen, as can other advanced features.

HTML Editor

• HTML editor – New HTML editor that is compatible with IE 5.0 and above as well as Mozilla (Currently awaiting full release – only Beta available at present) Spellchecker functionality not available on Windows at present. Documentation will be available to assist set up and customisation.
• HTML editor can be customised for your instance – will allow add image, add links, bullets, aligning, add tables and spell checking
• Add link functionality calls CMS browser/search popup to insert relative links

Workflow 

• Workflow automatically started on item creation or edit
• Workflow automatically restarted when editing published item
• Rapid Workflow (1-stage) available for trusted users who have permission to publish directly

Alerts

• Workflow alerts are restricted to those users who have item permissions
• Lifecycle alerts are restricted to those users who have item permissions
• Documentation will be available to describe setting up and using alerts – Users should document alerts requirements to capture gaps that could be developed to enhance core functionality

Search

• Back end Search now allows search by author, date, folder and category

Content Types

• Input fields rationalised to ensure consistent naming of functional fields, e.g. description
• Redundant fields hidden to avoid confusion for users e.g. homepage field on News item, Launch Date on all content types. These can be re-instated by making changes to the config.init file
• Additional text fields HTML enabled to allow formatting of text
• Stable link displayed on summary page for all items to ensure usable link not dependent on folder path or content item location
• Content types review has identified future improvements to existing content types that could be funded jointly. APLAWS+ enhancements have enabled sharing of content types between instances so improved content types funded by individual authorities can be rolled back into the core system or shared via a library of potential resources.