MURDOCH     INDEX     SEARCH     PEOPLE  
Policies Index >>  Facilities & Services >>  Information Technology >> 

MurdochNet Policy

Section 1: PREAMBLE
Section 1.1: Purpose
Section 1.2: Scope
Section 1.3: Field of Application
Section 1.4: Policy Vocabulary
Section 1.5: Key Terms
Section 2: INTRODUCTION
Section 2.1: Goals
Section 2.2: Boundary of MurdochNet
Section 2.3: Environment of MurdochNet
Section 3: CODE OF CONDUCT
Section 3.1: Servers
Section 3.2: Content
Section 3.3: Links
Section 3.4: Misconduct
Section 4: SERVER MANAGEMENT
Section 4.1: Registration of Web Servers
Section 4.2: Murdoch Sub-domains
Section 4.3: Alternate Domain Names
Section 4.4: Naming Conventions for Web Servers
Section 4.5: Availability of Web Servers
Section 4.6: Security of Web Servers
Section 4.7: Backup (Hardware, Software, Data) of Web Servers
Section 4.8: Web Server Software
Section 4.9: Responsibility for Web Servers
Section 5: CONTENT MANAGEMENT
Section 5.1: Content Categories
Section 5.2: Content Management Procedures & Practices
Section 5.3: Standards & Guidelines for Content Preparation
Section 5.4: Murdoch Conventions for Content Preparation
Section 5.5: Murdoch Guidelines for Content Preparation
Section 5.6: Applications & Tools
Section 5.7: Responsibility for Content
Section 6: LINK MANAGEMENT
Section 6.1: Permissible Links
Section 6.2: Link Validation & Checking
Section 6.3: Link Revision & Relocation
Section 6.4: Responsibility for Registered Links
Section 7: Glossary of MurdochNet Terminology
: SCHEDULES
Schedule 1: Forms
Schedule 2: Contracts
Schedule 3: Guidelines
Schedule 4: Regulations
Schedule 5: Disclaimers
Schedule 6: Roles & Responsibilities

Section 5 CONTENT MANAGEMENT

Section 5.4 Murdoch Conventions for Content Preparation

Section 5.4.7 Dates Convention

The Murdoch Dates Convention to be practiced in the preparation of Content includes:

  • display of a date that reflects an event in the life cycle of an information resource (eg. when Content was created, when Content was last modified, when the information within Content shall no longer be valid).

Date Statements

The metadata that accompanies Content shall include date statements. The metadata shall be displayed in a manner that enables an end-user to make an informed decision about the currency of information within Content.

META Tags Used to Record Dates

The metadata that accompanies Content shall include:


  • The META tag ‘DC.Date.Available’ to indicate when a resource was first made available
  • The META tag ‘DC.Date.Created’ to indicate when a resource was created
  • The META tag ‘DC.Date.Modified’ to indicate when the HTML was last modified
  • The META tag ‘DC.Date.Valid’ to indicate when the information within Content expires.

Document Information Footers

The metadata that accompanies Content shall include the use of document information footers or metadata popups accessed by a link on a page titled Page Information. The footer or popup display shall include one or more date statements, depending on the Content Subcategory.

For example:

Document created: Sept 1st, 2001

HTML last modified: Sept 14th, 2002

Expiry date: August 31st, 2003

The format used for the display of dates should be readily understood by the end-user. It may include use of the ISO 8601 format, eg. 2003-12-31.

The minimum date statement required shall be the date the Content was last modified. In some cases this may be different to the date the information in the Content was edited, and an additional date statement, or an indicator within the body of the document may be required. An additional META tag ‘DC.Date.Issued’ may be used to clarify the date situation for editing information within Content as separate process from when the HTML was revised.

Use of other date statements such as creation date and expiry date, shall be determined by the Content Subcategory to which the Content has been assigned. For instance, official publications and public relations material should include expiry dates, implying that after that date the information within the Content may be presumed to be out of date and that alternative sources should be used to seek up to date information.

In any index page that precedes Foreign Content that is teaching and learning material, the index entry for an item should indicate the date up to which the Content is valid, implying that after that date access to the Content should be denied by the Server.

To determine what are the required date statements and their associated META tags for Content Subcategories, Content Providers preparing University Content should refer firstly to Section 5.4.12 Metadata Convention for an introduction, and then to the Guidelines for Metadata to Accompany MurdochNet Content.