Squiz Australia Pty. Ltd. A 92 Jarrett Street, Leichhardt NSW 2040
P +61 2 8507 9900 F +61 2 8507 9988 W www.squiz.net
APSC Website Redesign
Build Specification
Prepared for Australian Public Service Commission
CONFIDENTIAL – DO NOT DISTRIBUTE
© Squiz Pty Ltd 2011. This document is for use with Australian Public Service Commission only.
AUSTRALIA UNITED KINGDOM NEW ZEALAND EUROPE UNITED STATES
SYDNEY MELBOURNE CANBERRA HOBART BRISBANE
Contents Page
1 Version History
4
1.1
4
Reviewers
2 Introduction
5
2.1
Purpose
5
2.2
Scope
5
2.3
Out of Scope
5
2.4
Audience
5
2.5
Approach
5
2.6
Assumptions
5
2.7
Related Documentation
5
2.8
Glossary of terms
6
3 Global Header and Footer Elements
7
3.1
Wireframe
7
3.2
Functionality
7
3.3
Build Specification
8
4 Home page elements
10
4.1
Wireframe
10
4.2
Functionality
10
4.3
Build specification
11
5 Level 1 Landing Page
14
5.1
Wireframe
14
5.2
Functionality
14
5.3
Build specification
15
6 Sub-page L2 – L3 elements
16
6.1
Wireframe
16
6.2
Functionality
17
6.3
Build specification
17
7 Publications search and listing
19
7.1
Wireframe
19
7.2
Functionality
19
7.3
Build specification
20
8 Circulars and advices search and elements
22
8.1
22
Wireframe
Document1
CONFIDENTIAL – DO NOT DISTRIBUTE
> 2 of 35
8.2
Functionality
22
8.3
Build specification
23
9 Appendix A – Metadata Schemas
25
9.1
AGLS Global Schema
25
9.2
General Metadata Schema
26
9.3
APSC Metadata Schema
26
9.4
APSC Tagging Schema
27
10 Appendix B - Users & Groups
29
10.1 User Group Details
29
10.2 User Groups Asset Map Configuration
29
10.3 WYSIWYG Plugins Preferences
30
11 Permissions
32
11.1 Implementation Strategy
34
12 Appendix B – Accessibility and Browser Requirements
35
Document1
CONFIDENTIAL – DO NOT DISTRIBUTE
> 3 of 35
1
Version History
Version
Date
Author/Editor
Title
Organisation
Notes
0.1
14/12/2011
Libby Heasman
Technical
Business Analyst
Squiz
Initial Version
0.2
10/01/2012
Libby Heasman
Technical
Business Analyst
Squiz
Changes made
after receiving
mockups
0.3
30/01/92012
Libby Heasman
Technical
Business Analyst
Squiz
Changes from
meeting on
25/01/2012
0.4
15/2/2011
Libby Heasman
Technical
Business Analyst
Squiz
Changes from the
meeting on the
10/2/2012
1.1
Reviewers
Name
Title
Organisation
Bruce Hargrave
Project Manager
Squiz
Andrew Glenn
Internet Manager
Australian Public Service Commission
Document1
CONFIDENTIAL – DO NOT DISTRIBUTE
> 4 of 35
2
Introduction
2.1
Purpose
This document outlines the build specification for each functional component to be implemented for the APSC
website implementation to Squiz Matrix.
2.2
Scope
The scope of this document is confined to defining the APSC website requirements:

Functional components to be implemented

Underlying Squiz Matrix tools and features that will be used to provide the specified functionality
2.3
Out of Scope
The following items are deemed out of scope for this document

2.4
Audience
This document has been written for the Australian Public Service Commission and assumes readers are
familiar with basic Squiz Matrix concepts and tools.
2.5
Approach
The Build Specification was written following discussions of business requirements, website requirements
analysis workshops and the development of a functional specification; these have been the basis for the
specification.
2.6
Assumptions
The following assumptions were made by Squiz in preparing this document:
ID
Description
The business requirements have been defined and are correct as of the 12th December 2011
1.
2.7
Related Documentation
The below documents are complementary to this document and/or served as inputs:
ID
Description
Version
Creator
1
APSC Website Redesign Functional Specification
1
Libby Heasman
Document1
CONFIDENTIAL – DO NOT DISTRIBUTE
> 5 of 35
2.8
Glossary of terms
For more information see http://manuals.matrix.squizsuite.net/concepts
Term
Description
Asset
In Squiz Matrix, everything is an asset. Your websites, designs, pages, images and
files are assets within the system. There are many different types of assets in Squiz
Matrix; some common examples include Folder, Image, MS Excel Document, PDF
file, Standard Page, Asset listing
Backend
Generic term used to describe the administration interface
CMS
Content management system (Squiz Matrix)
Design area
Dynamically handled area of the design template, for example: Breadcrumbs, Menu,
Re-usable content and layouts, CSS.
Customisation
A Design Customisation allows you to configure the settings for the design areas,
without the need to create a separate Design asset. Customisations are essentially
variations on a theme
Static HTML
HTML (HyperText Markup Language) content that is not required to be generated
dynamically
Ajax
Asynchronous JavaScript and XML – Term given when JavaScript is used to
communicate with the server to retrieve information.
Nested content
Asset re-used by including it in the content of another asset.
Squiz
Previous branding name for Squiz Matrix. Some remnants of this naming still remain
in the system, particularly when referring to design area tags.
Markup
Short hand way of referring to HTML
CSS
Cascading Style Sheet – The technology used to define the look and feel of the HTML
Body copy
A dependent Matrix asset that holds HTML content
Hyperlink
Reference to a page, or asset that the browser can directly follow
RSS
Really Simple Syndication – a format of XML used to produce a web feed in a
standardised format.
Trigger
An asset type in Matrix that can respond to events occurring within the system and
perform actions.
CSS
CSS stands for Cascading Style Sheets. CSS is designed primarily to enable the
separation of document content from document presentation, including elements such
as the layout, colours, and fonts
Document1
CONFIDENTIAL – DO NOT DISTRIBUTE
> 6 of 35
3
Global Header and Footer Elements
3.1
Wireframe
3.2
Functionality
ID
Element
Description
G1
Australian
Government
Logo
Australian Government Logo positioned as per the Australian Government
requirements.
G2
Graphic and
mission
Welcoming graphic representative of the people of the Australian Public Service.
A short description of the APSC to summarise their mission.
G3
RSS
Subscribe using RSS. This RSS button will link to an RSS page to allow users to
either subscribe to RSS feeds they are interested in or subscribe to all feeds
from the site.
Document1
CONFIDENTIAL – DO NOT DISTRIBUTE
> 7 of 35
ID
Element
Description
G4
Talk with
us/collaborate
Talk with us link. This link navigates the user to a collaboration landing page. If
they are available, this page will contain further links to individual blogs and
surveys through an asset listing of child pages. The collaboration landing page
will use the L1 inside page design.
G5
Global header
links
Quick links to key pages. These links serve as a quick jump to the Home, Contact
Us and About Us page from anywhere in the site.
G6
Search
This search box will search the entire site by keywords entered.
G7
Global footer
links
Footer links. The footer will contain links to Privacy, Copyright, Freedom of
Information and the Information Publication Scheme and the Sitemap
(IDs match those referenced in the wireframe)
3.3
Build Specification
The global header and footer will be made up of the following Squiz Matrix Assets:
Squiz Matrix Asset
Functionality
Nested standard page asset 
To create global links, search form and RSS link, Talk to us link and footer
links
Section images

A selection of images that will display one randomly on page load
Search page

Single keyword search which will be used by the nested standard page
asset
3.3.1 Australian Government logo
Logo will to be included in the design parse file with a link to the site URL.
3.3.2 Graphic and mission
The graphic change will involve changing the banner on page load. The banner will be the width of the page
and will include the image of the APSC employee and the banner will be selected at random using JavaScript.
The rest of the text will be added through the design parse files except the employee’s role and section text.
The role and section text will be an empty span tag that will be populated using some JSON mapping that will
load the correct text for the banner that loads.
3.3.3 RSS/Talk with us links
These links will be built as a single nest content area in the design parse file. This will nest a standard page
asset that has a presentation and content type of raw HTML.
3.3.4 RSS subscription page
The RSS subscription page will allow interested users to subscribe to page changes for specific areas of the
site. The RSS Feed will be made up of the following asset:


Asset Listing Page – To create a list of all standard pages in the document site. This will created using a
structured root node selector for each topic area of the site.
RSS Feed – To list out the results of the Asset Listing Page.
Document1
CONFIDENTIAL – DO NOT DISTRIBUTE
> 8 of 35
3.3.5 Global header links
These links will be built as a single nest content area in the design parse file. This will nest a standard page
asset that has a presentation and content type of raw HTML.
3.3.6 Search
Search to be included as a nested design area, nesting a standard page asset with a content type and
presentation of raw HTML. A search page setup to perform a single keyword search will be referenced by the
search form.
3.3.7 Global footer links
These links will be built as a single nest content area in the design parse file. This will nest a standard page
asset that has a presentation and content type of raw HTML.
Document1
CONFIDENTIAL – DO NOT DISTRIBUTE
> 9 of 35
4
Home page elements
4.1
Wireframe
4.2
Functionality
ID
Element
Description
H1
Navigation menu
This will provide links to the top-level assets under the site asset.
H2
Latest news list
This box will display the last 5 latest news items released. The first item on the
list is the most recent news item and will be displayed in bold text. All
remaining news items in the list will be in normal text. All news items will
display

the release date by day and month

the title of the news item which is a link to the complete news article.
When a new news items is added it will become the first item in the list.
Document1
CONFIDENTIAL – DO NOT DISTRIBUTE
> 10 of 35
ID
Element
Description
H3
Current events list
This box will display the last 5 event news items. The first item on the list is the
most recent event news item and will be displayed in bold text. All remaining
event news items in the list will be in normal text. All event items will display

the release date

the title of the event news item

a short description of the event

a Read More link to be taken to the event page.
When a new event items is added it will become the first item in the list.
H4
Current Priorities
box
This box will display the current Prioritiess within the APS. The content of this
box will be updated as necessary.
H5
Navigate by topic
This box allows the user to navigate to a topic heading or key Level 1 or 2
pages.
Many of these topic headings will be type 2 links to L1 items such as the Merit
protection commission. Type 2 links do not appear in the main menu
H6
Navigate by
audience
This box allows the user to navigate to an area of interest based on their role or
objective in the site. Each of the topic headings links to a single Role page that
offers predetermined areas of interest for that role. Each of the sub headings
will link to Level 1 or Level 2 pages
Many of these topic headings will be type 2 links to L1 items. Type 2 links do
not appear in the main menu
(IDs match those referenced in the wireframe)
4.3
Build specification
Squiz Matrix Asset
Functionality
Asset Listings

To create the nested news, events, current Priorities information
Asset Listing

To created the Information about section
Search page

To enable the Information for section
Standard page

To nest the search page.
Standard page

To create the links for each information for area
4.3.1 Navigation menu
The menu will use the menu normal design area and display the top level only.
4.3.2 Latest news list
This will be built using an Asset Listing that with the following settings:




Root node – the News section of the site that will store all news items
Asset to list – news items
Asset Access to List – effective read
Assets per page – 3
Document1
CONFIDENTIAL – DO NOT DISTRIBUTE
> 11 of 35

Asset sorting – sort by Published date descending.
The results need to display as an unordered list.
Default format bodycopy will contain:

%asset_published^date_format:d-M% - %asset_name_linked%
CSS will be used to style the bullet image.
4.3.3 Current events list
This will be built using an Asset Listing that with the following settings:





Root node – the Events section of the site which will be a folder storing all events as standard pages
Asset to list – news items
Asset Access to List – effective read
Assets per page – 3
Asset sorting – sort by Published date descending.
The results need to display as an unordered list.
Default format bodycopy will contain:

%asset_published^date_format:d-M% - %asset_name_linked%
CSS will be used to style the bullet image.
4.3.4 Current Priorities box
This will be built as a standard page with 3 items in an unordered list and will be updated as necessary. This
will be included as a nested design area in the design parse file.
4.3.5 Navigate by topic
This will be built using an Asset Listing to list out the top-level pages of the site information architecture. The
Asset Listing will be setup:





Root node – site asset
Asset to list – standard pages
Asset Access to List – effective read
Direct children only - yes
Assets per page – 3
The Default Format Bodycopy will display the %asset_name_linked% keyword replacement.
Layout will be done using CSS and the asset listing will be nested into the design parse file using a nested
design area.
4.3.6 Navigate by audience
The will be built using the following assets and steps:
Search page
1.






Search page – details screen:
Root node – site asset
Assets to List – Standard Page
Search Statuses – select all
List Format – Custom Grouping
Search as Public User – No
Perform Roles Check – No
Document1
CONFIDENTIAL – DO NOT DISTRIBUTE
> 12 of 35

2.



3.


Perform Group Access Check – No
Search page – Search Fields
New field – audience
Data Type – metadata field and set the audience field in details
Word logic – all words
Search page – Details
Stored Query Locations – Search Field - audience
GET Variable Name - audience
Standard page asset to provide the search options
1.


o
o
Contents screen
Single nest content DIV and nest the Search page
Add additional GET variables of
Variable name – audience
Variable URL - %globals_get_audience%
Standard page asset for the Navigate by audience content will contain static links for each topic area. Append
the url of each link with ?audience=metadata value. See Appendix A – Metadata Schemas for more
information on the metadata values.
Document1
CONFIDENTIAL – DO NOT DISTRIBUTE
> 13 of 35
5
Level 1 Landing Page
5.1
Wireframe
(IDs match those referenced in the wireframe)
5.2
Functionality
ID
Element
Description
L1
L1 menu
This horizontal navigation bar displays all Level 1 pages. Hover over a menu item
to reveal a list of Level 2 content pages under that Level 1 parent
L2
L1 Heading
and content
This space displays a graphic and introduction text for this Level 1 page
L3
Section site
map
This is a self-generating site map displaying all Level 2 and Level 3 content
pages under the current Level 1 page
(IDs match those referenced in the wireframe)
Document1
CONFIDENTIAL – DO NOT DISTRIBUTE
> 14 of 35
5.3
Build specification
Squiz Matrix Asset
Functionality
Menu normal design area

To create the primary navigation
Standard page assets

To create the Landing page content
Sitemap

To create the links on the landing page
5.3.1 L1 menu
The menu will use the menu normal design area and display one sub level. The sub level elements will be
built using CSS to show sub items when hovering over the top-level menu item.
5.3.2 L1 Heading and content
The level 1 content will be a standard page asset with two DIVs. The top DIV will be a WYSIWYG
DIV
to display the graphic and heading information. The second DIV will be a nest content DIV to nest the sitemap
asset. See the next item Section site map for more information.
5.3.3 Section site map
This is a sitemap asset, with the following settings:


o
o


Static root node – site
Dynamic root node
Parameter - Replacement root nodes (must be child of static root node)
Source – Current asset / asset id
Map format – unordered list
Print stalks – no
CSS will be used to layout the sitemap in 3 columns.
Document1
CONFIDENTIAL – DO NOT DISTRIBUTE
> 15 of 35
6
Sub-page L2 – L3 elements
6.1
Wireframe
Document1
CONFIDENTIAL – DO NOT DISTRIBUTE
> 16 of 35
6.2
Functionality
ID
Element
Description
S1
L2 current
page
This menu area will display the title of the current page being viewed. This menu
item will be highlighted to show it is the current selection.
S2
L3 child pages
This horizontal menu displays all the children under the currently selected Level
2 page. When a Level 2 item is selected the menu option will show the children of
the current page.
S3
Breadcrumbs
This breadcrumb trail will show the user the path to the current page and provide
the ability to return to the parent pages by selecting it from the breadcrumb list.
S4
Body content
This is the content of the asset
S5
Related
information
This area will display any documentation or links related to the current content. If
no related documentation or links exist the box will not display.
Document links will display:

The document type icon

The title of the document as a hyperlink to download

The size of the document
The related topic links with display:

The title of the related page as link to that page
(IDs match those referenced in the wireframe)
6.3
Build specification
Squiz Matrix Asset
Functionality
Menu normal design area

To create the level 3 menu items
Asset lineage design area

To create the breadcrumbs
Asset listing

To create the related documents links
Metadata fields

To create the related documents and related topics links
6.3.1 L2 current page
This will be menu normal design area in the design parse file. CSS will be used to style the on current state.
The sub menu design area will be used print out the child assets of the current asset.
6.3.2 L3 child pages
CSS will be used to style the on current state of the current menu item.
6.3.3 Main content
The body design area will be used to display the contents of the asset.
Document1
CONFIDENTIAL – DO NOT DISTRIBUTE
> 17 of 35
6.3.4 Breadcrumbs
Breadcrumb area defined as an asset lineage design area showing the homepage as the first navigation item
and displaying current asset.
6.3.5 Related information
The will be built using the following assets:

o
o

o
o
o


o
Metadata sections called Functional. See Appendix A – Metadata Schemas for more information.
Metadata Text field – Related.Links
Metadata WYSIWYG field – Related.Topics.
Asset listing (related links)
Asset types to list – page (inherit), PDF document, MS Word Document, RTF File, powerpoint, excel
document
Root node – site
Dynamic Parameter
Parameter - Array of specific asset IDs or selection group (specified assets must be children of the static
related node)
Source – Set value of %globals_asset_metadata_Related.Links%
PDF Document, Word Document and RTF File, powerpoint, excel document type formats must be enabled
and all these file types will include a type icon %asset_attribute_title% linked to %asset_url% and display file
size as %asset_file_size_readable%.
The related links asset listing will then be included in the design parse file as nest content design area and
applied to all Level 2 and Level 3 assets.
This will work well if the related documents are stored in a central location in the site. Since the related links
are created by entering comma separated asset IDs in a text box.
Document1
CONFIDENTIAL – DO NOT DISTRIBUTE
> 18 of 35
7
Publications search and listing
7.1
Wireframe
7.2
Functionality
ID
Element
Description
P1
Publications
search
This search is restricted to publications and allows a search either by keyword or
topic or both. Search results will display in the same format as P3
P2
A-Z Navigation
Links
This A-Z displays a link for the first letter of each publication title. If there are no
publications beginning with a letter then that letter will be inactive. The user can
also select All to see a complete A-Z list of current publications
P3
A-Z List Items
Publications will be grouped alphabetically by the first letter of the publications
title. Each publication list item will display:

The title of the publication

A brief description of the publication
Document1
CONFIDENTIAL – DO NOT DISTRIBUTE
> 19 of 35
ID
P4
Element
Description

The tags used to categorise the publication. Each tag category item is a link to
allow a filter by tag search.

An icon to display the availability type e.g. download, online order, email order
and accompanying linked text.
Related
content
This box directs users to the option of searching for current circulars and links
through to that asset
(IDs match those referenced in the wireframe)
7.3
Build specification
Squiz Matrix Asset
Functionality
Search page

To create the search option
Asset listing

To create A – Z links and listing
It is recommended that publications be grouped in folders by year of publication. They can be children of the
Publications asset or in another location in the site.
7.3.1 Publications search
This is a search page with the following settings:




Root nodes – each year folder of the publications
Exclude root nodes - yes
Assets to display – Page (inherit), PDF and MS Word Document
Asset statuses to list – select all
Search fields:

o

o

o

o
Keyword
Data sources – include all
Topic
Data sources – Asset Metadata Field – Topic
General Tags
Data sources - Asset Metadata Field – APSC.GeneralTags
Policy and advice tags
Data sources – Asset Metadata Field – APSC.PolicyAdviceTags
Initial search page layout

Keyword: %keyword_query% %keyword_query_logic% Topic: %topic_query%
%submit_button%
Results page layout

%result_number% %asset_name_linked%
%asset_metadata_DC.Description%
7.3.2 A-Z Navigation links and publication list
This is created using a single asset listing with the following settings:


Asset types to list – Page (inherit), PDF and MS Word Document
Root node – Publication year folders
Document1
CONFIDENTIAL – DO NOT DISTRIBUTE
> 20 of 35


List format – A – Z Listing
A – Z Listing style – Single page
Page contents


o
Nest content DIV – nest the publications search page
WYSIWYG DIV
%page_list%
%asset_listing%
Default Format bodycopy

%asset_name_linked%
%asset_metadata_DC.Description%
Filed under: %asset_metadata_policy-advice-tags% | %asset_metadata_apsc-general-tags%
PDF and MS Word Format bodycopy

%asset_name_linked%
%asset_metadata_DC.Description%
Filed under: %asset_metadata_policy-advice-tags% | %asset_metadata_apsc-general-tags%
(%asset_file_size_readable%)
Note: The metadata key should link to %asset_url% to enable users to download the file.
JavaScript will be used to create an anchor from the list element that is linked to the publications search page
and appended with a query string of the list element text. If the user has JavaScript disabled then the tag text
will display but there will be no link.
7.3.3
Related content
This will be built in the same way as 6.3.5 Related information
Document1
CONFIDENTIAL – DO NOT DISTRIBUTE
> 21 of 35
8
Circulars and advices search and elements
8.1
Wireframe
8.2
Functionality
ID
Element
Description
C1
Circulars and
advices search
This search is restricted to circulars and advices and allows a search either by
keyword or topic or both. Search results will display in the same format as C3
Document1
CONFIDENTIAL – DO NOT DISTRIBUTE
> 22 of 35
ID
Element
Description
C2
Year
Navigation
The Year list displays a link for the current and past years since 1999 and then a
single link for all circulars and advices before 1999. The user can also select All
to see a complete list of circulars and advices on the same page.
C3
Chronologial
list
Circulars and advices will be displayed chronologically by most recent to least
recent. Grouped by year and then by type. Each circular and advice list item will
display:
C4

The title of the circular or advice that links to the circular or advice

A brief description of the circular or advice
Related
content
This box directs users to the option of searching for current publications and
links through to that asset
(IDs match those referenced in the wireframe)
8.3
Build specification
Squiz Matrix Asset
Functionality
Search page

To create the search option
Asset listing

To create A – Z links and listing
8.3.1 Circulars and advices search
This is a search page with the following settings:




Root nodes – each year folder of the circulars
Exclude root nodes - no
Assets to display – Page (inherit)
Asset statuses to list – select all
Search fields:

o

o
Keyword
Data sources – include all
Topic
Data sources – Asset Metadata Field – Topic
Initial search page layout

Keyword: %keyword_query% %keyword_query_logic% Topic: %topic_query%
%submit_button%
Results page layout

%result_number% %asset_name_linked%
%asset_metadata_DC.Description%
8.3.2 Year Navigation links and circular list
This is created using a single asset listing with the following settings:



Asset types to list – Page (inherit)
Root node – Circular year folders
Asset grouping – group by parent and restrict to folder
Document1
CONFIDENTIAL – DO NOT DISTRIBUTE
> 23 of 35


o
o

o
o
o
Sort – Descending
Dynamic Parameters
Parameter - Replacement Root node for the listing (must be a child of the static root node)
Get variable name – root_node_selection
Structured Root Selector Options
Name: root_node_selection
Root node: Circulars parent folder
Asset types: Folder
Page contents

o
o
Year links will need to be created manually and have the following structure
<a href="%asset_url%?root_node_selection=10895 1">All</a>&nbsp; <a
href="%asset_url%?root_node_selection=10896">2011</a>&nbsp; <a
href="%asset_url%?root_node_selection=10897">2010</a>&nbsp; <a
href="%asset_url%?root_node_selection=10898">2009</a> where root_node_selection id is the asset id of
the year folder.
%asset_listing%
Default Format bodycopy

%asset_name_linked%
%asset_metadata_DC.Description%
8.3.3
Related content
This will be built in the same way as 6.3.5 Related information
1 Asset IDs are included here as example only
Document1
CONFIDENTIAL – DO NOT DISTRIBUTE
> 24 of 35
9
Appendix A – Metadata Schemas
This section provides a snapshot view of the Metadata Schemas that will be created for this project and applied either globally or to specific areas of the site.
9.1
AGLS Global Schema
It is expected that we should be able to apply the existing AGLS schema in the matrix instance to this site.
ID
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
Field name
Friendly
name
Description
Field Type
Default Value
Scheme
DC.Identifier
Auto populated
Text – read only
%asset_url%
URI
DC.Title
Auto populated
Text – read only
%asset_name%
DC.Creator
The name of the document
creator
Text
Australian Public Service Commission
GOLD
Text
Australian Public Service Commission
GOLD
DC.Publisher
DC.Date.created
Auto populated
Date
Creation date keyword
ISO8601
DC.Date.modified
Auto populated
Date
Last updated keyword
ISO8601
AGLS.Function
Text – multiple
lines
DC.Rights
Text
Copyright Australian Government Public Service
Commission
Text
text/html
IMT
Text
en
RFC3066
AglsJuri
DC.Format
Auto populated
DC.Language
AGIFT
DC.Coverage.jurisdiction
Auto populated
Text
Commonwealth of Australia
AGLS.Audience
Auto populated
Text
ALL
Document1 - CONFIDENTIAL – DO NOT DISTRIBUTE
> 25 of 35
9.2
General Metadata Schema
ID
Field name
1.
DC.Description
2.
Keywords
3.
Audience
Friendly name
Description
Field Type
Default Value
Business Rules
Enter a brief
description for this
asset
Enter keywords for
this asset
Text
Select
Key/Value: APS Staff
Allow multiple:
Yes
Key/Value: Human Resources staff
Content tagged
with these labels
provide the
content of the
Information for
landing page
Text
Key/Value: SES
Key/Value: Job Seekers
Key/Value: Training Managers
9.3
ID
APSC Metadata Schema
Field name
Friendly name
Description
Field Type
Default Value
Business Rules
Section – Functional
1.
Related.Links
Separate each
asset ID with a
comma e.g.
1111,2222,3333
Text
2.
Related.Topics
Use the editor to
enter related links
each on a separate
line.
WYSIWYG
Select up to three
topics for this page
Select
Allow multiple:
yes
Select
Allow multiple:
no
Section – Publications
3.
Topic
4.
Order
Document1 - CONFIDENTIAL – DO NOT DISTRIBUTE
TBD
Key/Value: Download Only
Key/Value: <a
href="https://apsc.infoservices.com.au/colle
ctions/general-publications">Order
Online</a> / Order Online
> 26 of 35
9.4
ID
APSC Tagging Schema
Field name
Friendly name
Description
Field Type
Default Value
Business Rules
APSC Tags
1.
APSC.GeneralTa
gs
APSC General Tags
Select
2.
APSC.PolicyAdvi
ceTags
Policy and advice tags
Select
Document1 - CONFIDENTIAL – DO NOT DISTRIBUTE
Key/Value: APS | <li>APS</li>
Key/Value: APSC | <li>APSC</li>
Key/Value: APS Reform | <li>APS
Reform</li>
Key/Value: Career and career development
/ <li>Career and career development</li>
Key/Value: Forums - online | <li>Forums online</li>
Key/Value: Frameworks |
<li>Frameworks</li>
Key/Value: Governance |
<li>Governance</li>
Key/Value: International |
<li>International</li>
Key/Value: IPS | <li>IPS</li>
Key/Value: Leadership | <li>Leadership</li>
Key/Value: Networks | <li>Networks</li>
Key/Value: Statistical data – research and
evaluation | <li>Statistical data – research
and evaluation</li>
Key/Value: Training | <li>Training</li>
Key/Value: APS Values and Code of
Conduct | <li>APS Values and Code of
Conduct</li>
Key/Value: Disability | <li>Disability</li>
Key/Value: Employment framework |
<li>Employment framework</li>
Key/Value: Engagement |
<li>Engagement</li>
Key/Value: Ethics | <li>Ethics</li>
Key/Value: Indigenous | <li>Indigenous</li>
Key/Value: Legislation | legal and
government frameworks / <li> Legislation |
legal and government frameworks </li>
Key/Value: Merit | <li>Merit</li>
> 27 of 35
Key/Value: Movements |
<li>Movements</li>
Key/Value: Recruitment and selection |
<li>Recruitment and selection</li>
Key/Value: Performance |
<li>Performance</li>
Key/Value: Separation <li>Separation</li>
Key/Value: Workplace relations |
<li>Workplace relations</li>
Document1 - CONFIDENTIAL – DO NOT DISTRIBUTE
> 28 of 35
10
Appendix B - Users & Groups
10.1
User Group Details
The details below are suggested user groups for the APSC Squiz Matrix instance.
User Group
Squiz Matrix User
Type
System
Administrators2
System
Administrator
Site/Section
Administrator
Backend User
Content Author
Backend User
10.2
Comments
 Any modification to System Administrator user type can
only be made by the Root User.
 System Administrators are the only group that can
modify Site/Section Administrators.
The user will have admin permission on all or part of the
site. This allows the user to publish assets.

Users in this group will primarily use the Simple Edit
interface and therefore only be exposed to the features
of Matrix they need to interact with.
User Groups Asset Map Configuration
The following structure is representative of the recommended asset map configuration for the required APSC
user groups within the Squiz Matrix administration interface.
Figure 1 - Best Practice Structure of System Administrators within the Squiz Matrix Administration Interface
The System Administrator user accounts will be created within the System Administrator folder located at
under the System Management folder at the top of the asset tree.
Figure 2 - Best Practice Structure of Site/Section Specific User Groups within the Squiz Matrix Administration Interface
Site/Section Specific user accounts will be linked under the appropriate User Groups within the Users folder
specific to each Site or Section
This structure achieves:



Adherence to best practice standard asset map structure
Cascading of permissions from parent user groups to child user groups
A modular approach to granting permissions either site wide, to specific sections or to individual assets
2 User accounts of this type will be stored within Squiz Matrix along with all relevant account details. Management of these accounts will be
via the Squiz Matrix Administration Interface.
Document1 - CONFIDENTIAL – DO NOT DISTRIBUTE
10.3
WYSIWYG Plugins Preferences
The following table indicates the custom WYSIWYG editor preferences that will be made available to each
User Group. This will ensure a consistent user interface for User Groups throughout the Matrix Administration
Interface. Only System Administrators will have access to manage these settings within the APSC Squiz
Matrix instance. See the Squiz Matrix System Configuration Manual for a description of each plugin.
Content Author
Site/Section
Administrators
System
Administrators
X
X
X
X
X
X
X
X
X
About
Choose Language
Definition List
X
Format Font
Format Text
X
X
X
General
X
X
X
History
X
X
X
HTML Tidy
X
X
X
Indenting
X
X
X
Insert Image
X
X
X
Insert Link
X
X
X
Justify Text
X
X
X
X
X
Keyword Replace
Listing
X
X
X
Matrix Accessibility
X
X
X
Matrix Apply Style
X
X
X
Matrix Embed Movie
X
X
Matrix Embed YouTube
X
X
Matrix Expand Keywords
X
X
Document1 - CONFIDENTIAL – DO NOT DISTRIBUTE
Content Author
Site/Section
Administrators
System
Administrators
Matrix Insert Anchor
X
X
X
Matrix Insert Image
X
X
X
Matrix Insert Link
X
X
X
Matrix Insert Quick Link
X
X
X
Misc. Accessibility
X
X
X
Quotation
X
X
X
Replace Text
X
X
X
S Script
X
X
X
Select Colour
X
X
X
X
X
Snippet Keyword Replace
Special Chars
X
X
X
Spell Checker
X
X
X
Table Editing
X
X
X
Text Indicator
X
X
View Source
X
X
X
X
Visual Aid
Document1 - CONFIDENTIAL – DO NOT DISTRIBUTE
X
11
Permissions
The table below are suggested tasks that can be performed within Squiz Matrix and the permission which
groups can perform those tasks.
Task
Content Author
Adding/Managing Content Authors and Approvers
Site/Section
Administrators
System
Administrators
X
X
Apply new site designs and templates
X
Customise HTTP error messages
X
X
Override URLs generated by the system
X
X
Add and maintain RSS Feeds
X
X
Create new site
X
Add Image Maps
X
Control of WYSIWYG Plugins
X
X
Log History
X
X
Set Review or Expiry Dates on Content
X
X
X
Edit Content
X
X
X
Defined WYSIWYG Plugin for file naming, file size
X
and file type name
Specify Mandatory Fields in Forms
X
X
Restrict Export of Results from Polls/Forms
X
X
Create Metadata Schemas
X
Apply permissions to Content Assets
X
Assign Weighting To Search Results
X
X
Edit Metadata
X
X
X
Edit Title
X
X
X
Add Page
X
X
X
Document1 - CONFIDENTIAL – DO NOT DISTRIBUTE
Task
Content Author
Site/Section
Administrators
System
Administrators
X
X
X
X
Move Page within Site
X
X
Workflow Approve/Reject
X
X
Make Live (Publish)
X
X
Delete Page
Move Page within Section
Document1 - CONFIDENTIAL – DO NOT DISTRIBUTE
X
11.1
Implementation Strategy
This translates to the following permissions structure in Squiz Matrix:
User Group
Read
Write
Admin
Applied to which section(s)
System Administrators
X
System wide
Site/Section Administrator
X
Site/Section specific
X
Content Author
Public
X
Site/Section specific
For any content that is publically
accessible
Site/Section Administrators will grant permissions to certain User Groups for certain sections of the
site/section. For example the User Group labelled, “Section 1” will have access only to “Section 1” within the
site/section. This allows a more modular control of Users and their access.
Document1 - CONFIDENTIAL – DO NOT DISTRIBUTE
12 Appendix B – Accessibility and Browser
Requirements
Accessibility
The following are accessibility requirements of the system

Web Content Accessibility Guidelines (WCAG) 2.0

WCAG Priority AA
Web document validation
The design will pass the following validation method using the HTML 5 doctype:
http://validator.w3.org/
Browser support
The design will render correctly in the following browser types and versions:

IE 7

IE 8

Firefox 3.6 +

Safari 4+

Chrome
Document1 - CONFIDENTIAL – DO NOT DISTRIBUTE