A user account is required in order to edit this wiki, but we've had to disable public user registrations due to spam.

To request an account, ask an autoconfirmed user on IRC (such as one of these permanent autoconfirmed members).

Difference between revisions of "AAFC Metadata Application Profile"

From WHATWG Wiki
Jump to: navigation, search
 
(23 intermediate revisions by the same user not shown)
Line 23: Line 23:
 
| Auto-pop & User
 
| Auto-pop & User
 
| Yes  
 
| Yes  
|}
 
  
 
|-valign="top"  
 
|-valign="top"  
Line 32: Line 31:
 
| Auto-pop & User
 
| Auto-pop & User
 
| Yes  
 
| Yes  
|}
 
  
 
|-valign="top"  
 
|-valign="top"  
Line 41: Line 39:
 
| Auto-pop & User
 
| Auto-pop & User
 
| Yes  
 
| Yes  
|}
 
 
  
 
|-valign="top"  
 
|-valign="top"  
Line 51: Line 47:
 
|  
 
|  
 
|  
 
|  
|}
 
  
  
Line 61: Line 56:
 
| User
 
| User
 
| No  
 
| No  
|}
 
  
  
Line 71: Line 65:
 
| User
 
| User
 
| No  
 
| No  
|}
 
 
  
 
|-valign="top"  
 
|-valign="top"  
Line 81: Line 73:
 
| User
 
| User
 
| No  
 
| No  
|}
 
  
 
|-valign="top"  
 
|-valign="top"  
Line 90: Line 81:
 
| User
 
| User
 
| No  
 
| No  
|}
 
  
  
Line 100: Line 90:
 
| User
 
| User
 
| No  
 
| No  
|}
 
 
  
 
|-valign="top"  
 
|-valign="top"  
Line 110: Line 98:
 
| User
 
| User
 
| No  
 
| No  
|}
 
  
 
|-valign="top"  
 
|-valign="top"  
Line 119: Line 106:
 
| User
 
| User
 
| No  
 
| No  
|}
 
 
  
 
|-valign="top"  
 
|-valign="top"  
Line 129: Line 114:
 
| User
 
| User
 
| No  
 
| No  
|}
 
  
  
Line 139: Line 123:
 
| User
 
| User
 
| No  
 
| No  
|}
 
  
  
Line 149: Line 132:
 
| Auto-pop & User
 
| Auto-pop & User
 
| Yes  
 
| Yes  
|}
 
 
 
  
 
|-valign="top"  
 
|-valign="top"  
Line 160: Line 140:
 
| User
 
| User
 
| Yes  
 
| Yes  
|}
 
  
 
|-valign="top"  
 
|-valign="top"  
Line 169: Line 148:
 
| Auto-pop  
 
| Auto-pop  
 
| Yes  
 
| Yes  
|}
 
 
  
 
|-valign="top"  
 
|-valign="top"  
Line 179: Line 156:
 
| Auto-pop  
 
| Auto-pop  
 
| Yes  
 
| Yes  
|}
 
 
  
 
|-valign="top"  
 
|-valign="top"  
Line 189: Line 164:
 
| Auto-pop & User
 
| Auto-pop & User
 
| Yes  
 
| Yes  
|}
 
 
  
 
|-valign="top"  
 
|-valign="top"  
Line 199: Line 172:
 
| User
 
| User
 
| Yes  
 
| Yes  
|}
 
 
  
 
|-valign="top"  
 
|-valign="top"  
Line 209: Line 180:
 
| Auto-pop
 
| Auto-pop
 
| Yes  
 
| Yes  
|}
 
 
  
 
|-valign="top"  
 
|-valign="top"  
Line 219: Line 188:
 
| Auto-pop  
 
| Auto-pop  
 
| Yes  
 
| Yes  
|}
 
  
+
|-valign="top"
TABLE OF CONTENTS
+
| 4.22
SUMMARY OF METADATA ATTRIBUTE SET 4
+
| Delegate of Responsibility Name
1.0 INTRODUCTION 8
+
| Administrative
1.1 Purpose of this Document 8
+
| Optional
1.2 Intended Audience 8
+
| User
1.3 Definition and Purpose of Metadata 8
+
| No
1.4 Purpose of an Application Profile 9
+
 
2.0 SCOPE 9
+
|-valign="top"
2.1 Categories of Metadata 9
+
| 4.23
2.2 Business rules 9
+
| Delegate of Responsibility Position
2.3 Key Referring Documents 9
+
| Administrative
3.0 ATTRIBUTES 10
+
| Optional
4.0 INTERNET METADATA ATTRIBUTE SET 11
+
| User
4.1 AAFC Collection 11
+
| No
4.2 AAFC Presentation Template Type 12
+
 
4.3 AAFC Primary Lane 13
+
|-valign="top"
4.4 Administrative Parent ID 14
+
| 4.24
4.5 Audience 15
+
| Delegate of Responsibility Team
4.6 Content Coordinator Name 16
+
| Administrative
4.7 Content Coordinator Position 17
+
| Optional
4.8 Content Coordinator Team 18
+
| User
4.9 Content Owner Name 19
+
| No
4.10 Content Owner Position/Title 20
+
 
4.11 Content Owner Team 21
+
|-valign="top"
4.12 Coverage (domestic) 22
+
| 4.25
4.13 Coverage (international) 23
+
| Description
4.14 Creator 24
+
| Descriptive
4.15 Date for Review 25
+
| Optional
4.16 Date Issued 26
+
| Auto-pop & User
4.17 Date Last Updated 27
+
| Yes
4.18 Date Modified 28
 
4.19 Date Reviewed 29
 
4.20 DCR Name 30
 
4.21 DCR Type 31
 
4.22 Delegate of Responsibility Name 32
 
4.23 Delegate of Responsibility Position 33
 
4.24 Delegate of Responsibility Team 34
 
4.25 Description 35
 
4.26 Destination Delivery 36
 
4.27 Filename 37
 
4.28 Format 38
 
4.29 Identifier 39
 
4.30 Keywords 40
 
4.31 Language 41
 
4.32 Next Review Period 42
 
4.33 Presentation 43
 
4.34 Subject (aafccore) 44
 
4.35 Subject (gccore) 45
 
4.36 Title 46
 
4.37 Type 47
 
4.38 Valid Date 48
 
4.39 vpath 49
 
4.40 vpathprod 50
 
APPENDIX A – REFERENCE 51
 
GLOSSARY 52
 
  
 +
|-valign="top"
 +
| 4.26
 +
| Destination Delivery
 +
| System
 +
| Mandatory
 +
| Auto-pop
 +
| Yes
  
  
 +
|-valign="top"
 +
| 4.27
 +
| Filename
 +
| System
 +
| Mandatory
 +
| Auto-pop
 +
| Yes
  
 +
|-valign="top"
 +
| 4.28
 +
| Format
 +
| Descriptive
 +
| Mandatory
 +
| Auto-pop
 +
| Yes
  
 +
|-valign="top"
 +
| 4.29
 +
| Identifier
 +
| Administrative
 +
| Mandatory
 +
| Auto-pop
 +
| Yes
  
 +
|-valign="top"
 +
| 4.30
 +
| Keywords
 +
| Descriptive
 +
| Optional
 +
| Auto-pop & User
 +
| Yes
  
 +
|-valign="top"
 +
| 4.31
 +
| Language
 +
| Administrative
 +
| Mandatory
 +
| Auto-pop
 +
| Yes
  
 +
|-valign="top"
 +
| 4.32
 +
| Next Review Period
 +
| Administrative
 +
| Mandatory
 +
| User
 +
| Yes
  
 +
|-valign="top"
 +
| 4.33
 +
| Presentation
 +
| System
 +
| Mandatory
 +
| Auto-pop
 +
| Yes
  
 +
|-valign="top"
 +
| 4.34
 +
| Subject (aafccore)
 +
| Descriptive
 +
| Mandatory
 +
| Auto-pop & User
 +
| Yes
  
  
 +
|-valign="top"
 +
| 4.35
 +
| Subject (gccore)
 +
| Descriptive
 +
| Mandatory
 +
| Auto-pop & User
 +
| Yes
  
  
 +
|-valign="top"
 +
| 4.36
 +
| Title
 +
| Administrative
 +
| Mandatory
 +
| Auto-pop & User
 +
| Yes
  
  
 +
|-valign="top"
 +
| 4.37
 +
| Type
 +
| Descriptive
 +
| Mandatory
 +
| Auto-pop & User
 +
| Yes
  
  
 +
|-valign="top"
 +
| 4.38
 +
| Valid Date
 +
| Administrative
 +
| Optional
 +
| User
 +
| No
  
  
 +
|-valign="top"
 +
| 4.39
 +
| vpath
 +
| System
 +
| Mandatory
 +
| Auto-pop
 +
| Yes
  
 +
|-valign="top"
 +
| 4.40
 +
| vpathprod
 +
| System
 +
| Mandatory
 +
| Auto-pop
 +
| Yes
 +
|}
  
  
 +
<font size = "5">AAFC Metadata Application Profile</font>
 +
----
  
  
 +
=='''Introduction'''==
  
 +
===Purpose of this Document===
  
1.0 Introduction
 
1.1 Purpose of this Document
 
 
The purpose of the AAFC Internet Metadata Application Profile is to fully describe how to apply metadata to information resources within the department’s internet, AAFC Online.  The intent is to offer working level details to comply with Government of Canada and departmental metadata and associated standards.
 
The purpose of the AAFC Internet Metadata Application Profile is to fully describe how to apply metadata to information resources within the department’s internet, AAFC Online.  The intent is to offer working level details to comply with Government of Canada and departmental metadata and associated standards.
  
 
The AAFC Internet Metadata Application Profile captures the business rules, type of entry and input, guidance and best practices for completing fields within the Content Management System (CMS). The CMS is responsible for streamlining and enhancing Web publishing processes and capabilities to support the electronic communication and service delivery needs of AAFC.  
 
The AAFC Internet Metadata Application Profile captures the business rules, type of entry and input, guidance and best practices for completing fields within the Content Management System (CMS). The CMS is responsible for streamlining and enhancing Web publishing processes and capabilities to support the electronic communication and service delivery needs of AAFC.  
  
1.2 Intended Audience
+
===Intended Audience===
 +
 
 
The intended audience for this document includes, but is not limited to:
 
The intended audience for this document includes, but is not limited to:
Information Architecture Services – Information Management Program (IMP)
+
* Information Architecture Services – Information Management Program (IMP)
E-Communications – Communications and Consultations Branch (CCB)
+
* E-Communications – Communications and Consultations Branch (CCB)
Portal and Content Services – Integrated Web Solutions
+
* Portal and Content Services – Integrated Web Solutions
Website Development Services – Integrated Web Solutions
+
* Website Development Services – Integrated Web Solutions
  
1.3 Definition and Purpose of Metadata  
+
===Definition and Purpose of Metadata===
The definition for metadata stated in the Standard on Metadata is:
+
 
 +
The definition for metadata stated in the [http://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=18909&section=text Standard on Metadata] is:
  
 
“Metadata defines and describes the structure and meaning of information resources, and the context and systems in which they exist. It is used to support efficient and effective management of these information resources over time.”  
 
“Metadata defines and describes the structure and meaning of information resources, and the context and systems in which they exist. It is used to support efficient and effective management of these information resources over time.”  
  
Metadata is used for description of resources, retrieval and management of information, identification of resource ownership, interoperability, e-commerce and other data properties.  Metadata summarizes the key qualities, properties, or attributes of a given resource.   
+
Metadata is used for description of resources, retrieval and management of information, identification of resource ownership, interoperability, e-commerce and other data properties.  Metadata summarizes the key qualities, properties, or attributes of a given resource.  It facilitates the discovery of resources and enables dynamic delivery of content to different sections within a web site or to different web sites so that content is written once but used many times (concept of reuse). As well, it enables the life cycle management of resources from creation to disposition.  Metadata can be used to trigger events in a life cycle so that content can be refreshed, removed or archived as appropriate and according to the Government of Canada’s record retention policies.
It facilitates the discovery of resources and enables dynamic delivery of content to different sections within a web site or to different web sites so that content is written once but used many times (concept of reuse). As well, it enables the life cycle management of resources from creation to disposition.  Metadata can be used to trigger events in a life cycle so that content can be refreshed, removed or archived as appropriate and according to the Government of Canada’s record retention policies.
 
  
 
In the context of this Internet Metadata Application Profile, metadata provides a description of the content on the web page. The fields in the CMS are separated into administrative, descriptive and system metadata. These fields may be auto-populated or applied by the user by selection of terms(s) or by free-text description.   
 
In the context of this Internet Metadata Application Profile, metadata provides a description of the content on the web page. The fields in the CMS are separated into administrative, descriptive and system metadata. These fields may be auto-populated or applied by the user by selection of terms(s) or by free-text description.   
1.4 Purpose of an Application Profile
 
An application profile is a set of attributes brought together from one or more namespace schemas for local application.  Application profiles describe how standard schemas are to be used.
 
 
2.0 Scope
 
The Internet Metadata Application Profile offers a complete description of the metadata attribute set for electronic content, as it applies to AAFC Online.
 
 
2.1 Categories of Metadata
 
This metadata attribute set is divided into three categories:
 
Administrative metadata – Information such as Date Issued and Next Review Date are necessary to effectively access, use and manage AAFC resources.
 
Descriptive metadata – Information describing the intellectual content of the object, like Description and Subject, used primarily as an aid to indexing and retrieving a resource.
 
System metadata – Information, such as File Name and DCR Name, which provide necessary identification and used to properly render the content onto AAFC Online.
 
2.2 Business Rules
 
The Internet Metadata Application Profile also outlines the specific AAFC business rules for completing each metadata attribute.
 
2.3 Key Referring Documents
 
Please refer to Appendix A for documentation.
 
 
 
 
 
  
 +
===Purpose of an Application Profile===
  
 +
An application profile is a set of attributes brought together from one or more namespace schemas for local application.  Application profiles describe how standard schemas are to be used.
  
 +
=='''Scope'''==
  
 +
The Internet Metadata Application Profile offers a complete description of the metadata attribute set for electronic content, as it applies to AAFC Online.
  
 +
===Categories of Metadata===
  
 +
This metadata attribute set is divided into three categories:
  
 +
'''Administrative metadata''' – Information such as Date Issued and Next Review Date are necessary to effectively access, use and manage AAFC resources.
  
 +
'''Descriptive metadata''' – Information describing the intellectual content of the object, like Description and Subject, used primarily as an aid to indexing and retrieving a resource.
  
 +
'''System metadata''' – Information, such as File Name and DCR Name, which provide necessary identification and used to properly render the content onto AAFC Online.
  
 +
===Business Rules===
  
 +
The Internet Metadata Application Profile also outlines the specific AAFC business rules for completing each metadata attribute.
  
 +
===Key Referring Documents===
  
 +
Please refer to Appendix A for documentation.
  
 +
=='''Attributes'''==
  
3.0 Attributes
 
 
Each attribute will be presented in the following format:  
 
Each attribute will be presented in the following format:  
  
 +
{| class="wikitable" style="width: 100%; height: 200px"
 +
|-
 +
! scope="col" width="225px" style="background:#FFBF00"| '''Attribute'''
 +
!style="background:#FFBF00"| '''Attribute Description'''
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Identification'''
 +
|-
 +
| Term Name || A unique token assigned to the term.
 +
|-
 +
| URI || A Uniform Resource Identifier used to identify the term.
 +
|-
 +
| Label || A human-readable label assigned to the term.
 +
|-
 +
| Defined by || An identifier of a namespace or a pointer to where the attribute is defined.
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Definition'''
 +
|-
 +
| Type of term || A property, class, vocabulary encoding scheme, or syntax encoding scheme.
 +
|-
 +
| Definition || A statement that represents the concept and essential nature of the term.
 +
|-
 +
| Comment || Additional information about the term or its application.
 +
|-
 +
| References || References to additional resources for further explanation and guidance for the application of the term.
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Relations'''
 +
|-
 +
| Encoding Scheme || The described term is qualified by the referenced scheme.
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Constraints'''
 +
|-
 +
| Obligation || Indicates whether the property is required to always or sometimes be present. The options are:
 +
* Mandatory – should always be present
 +
* Optional – may be present
 +
|-
 +
| Metadata Type || Indicates the type of data that can be represented in the value of the term. The options are:
 +
* Administrative
 +
* Descriptive
 +
* System
 +
|-
 +
| Entry Type || Indicates the method in which the value is selected. The options are:
 +
* Auto-populated
 +
* User entry – may be user selected or free-text description
 +
|-
 +
| Occurrence || Indicates any limit to the repeatability of the property.
 +
|-
 +
| Current Use || Indicates whether the property is currently applied in the system.
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Guidance'''
 +
|-
 +
| Explanation of Usage || Provides a description on why and how to use the property.
 +
|-
 +
| Example of HTML Syntax || Provides an example of the HTML syntax as it is provided at AAFC Online.
 +
|}
  
Attribute Attribute Description
+
=='''Internet Metadata Attribute Set'''==
Identification
 
Term Name A unique token assigned to the term.
 
URI A Uniform Resource Identifier used to identify the term.
 
Label A human-readable label assigned to the term.
 
Defined by An identifier of a namespace or a pointer to where the attribute is defined.
 
Definition
 
Type of term A property, class, vocabulary encoding scheme, or syntax encoding scheme.
 
Definition A statement that represents the concept and essential nature of the term.
 
Comment Additional information about the term or its application.
 
References References to additional resources for further explanation and guidance for the application of the term.
 
Relations
 
Encoding Scheme The described term is qualified by the referenced scheme.
 
Constraints
 
Obligation Indicates whether the property is required to always or sometimes be present. The options are:
 
• Mandatory – should always be present
 
• Optional – may be present
 
Metadata Type Indicates the type of data that can be represented in the value of the term. The options are:
 
• Administrative
 
• Descriptive
 
• System
 
Entry Type Indicates the method in which the value is selected. The options are:
 
• Auto-populated
 
• User entry – may be user selected or free-text description
 
Occurrence Indicates any limit to the repeatability of the property.
 
Current Use Indicates whether the property is currently applied in the system.
 
Guidance
 
Explanation of Usage Provides a description on why and how to use the property.
 
Example of HTML Syntax Provides an example of the HTML syntax as it is provided at AAFC Online.
 
  
 +
For ease of reference, the following attributes have been arranged in alphabetical order.
  
  
 +
===AAFC Collection===
  
 +
{| class="wikitable" style="width: 100%; height: 200px"
 +
|-
 +
! scope="col" width="225px" style="background:#FFBF00"| '''Attribute'''
 +
!style="background:#FFBF00"| '''Attribute Description'''
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Identification'''
 +
|-
 +
| Term Name || collection
 +
|-
 +
| URI ||
 +
|-
 +
| Label || AAFC Collection
 +
|-
 +
| Defined by || AAFC-AAC
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Definition'''
 +
|-
 +
| Type of term || Property
 +
|-
 +
| Definition || A group of content organized or owned by a specific business client or organized by theme or topic.
 +
|-
 +
| Comment || Identifies groups of content for which a left-hand navigation menu below a lane menu is required in the presentation layer.
 +
|-
 +
| References || AgriDoc: #384444
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Relations'''
 +
|-
 +
| Encoding Scheme || AAFC Collection Scheme (aafc.collection)
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Constraints'''
 +
|-
 +
| Obligation || Mandatory
 +
|-
 +
| Metadata Type || Descriptive
 +
|-
 +
| Entry Type || Auto-populated
 +
Exception: It is not auto-populated for Common-Commun, Rural Secretariat and Co-operatives Secretariat
 +
|-
 +
| Occurrence || Not repeatable
 +
|-
 +
| Current Use || In Use
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Guidance'''
 +
|-
 +
| Explanation of Usage || '''Why to Use'''
 +
The Collection Value is used to categorize web pages into specific topics and assist in navigation. The collection value will be provided in the left-hand menu under the appropriate lane. The breadcrumbs are set-up the following way: Home>Lane>Collection.
  
 +
'''How to Use'''
  
 +
In the ‘Descriptive’ tab of the CMS, the user must select the appropriate value in the drop down menu. There are two different AAFC Collection controlled vocabularies. All Primary Lane values, except Programs and Services, will use the same AAFC Collection controlled vocabulary. For Programs and Services, the collection value will be auto-populated.
 +
*Requests to add, modify or remove values must be sent to E-Communications, who will begin the change request process. The Information Architecture Services’ Metadata Specialists will verify the values, and ensure that the values in the CMS have been updated correctly.
 +
|-
 +
| Example of HTML Syntax || <meta name="aafc.collection" <font color="red">title</font>="aafcCollection" content="AgriInvest" />
 +
|}
  
  
 +
===AAFC Presentation Template Type===
  
4.0 Internet Metadata Attribute Set
+
{| class="wikitable" style="width: 100%; height: 200px"
For ease of reference, the following attributes have been arranged in alphabetical order.
+
|-
 
+
! scope="col" width="225px" style="background:#FFBF00"| '''Attribute'''
4.1 AAFC Collection
+
!style="background:#FFBF00"| '''Attribute Description'''
Attribute Attribute Description
+
|-
Identification
+
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Identification'''
Term Name collection
+
|-
URI
+
| Term Name || presentationTemplateType
Label AAFC Collection
+
|-
Defined by AAFC-AAC
+
| URI ||
Definition
+
|-
Type of term Property  
+
| Label || AAFC Presentation Template Type
Definition A group of content organized or owned by a specific business client or organized by theme or topic.
+
|-
Comment Identifies groups of content for which a left-hand navigation menu below a lane menu is required in the presentation layer.  
+
| Defined by || AAFC-AAC  
References AgriDoc: #384444
+
|-
Relations
+
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Definition'''
Encoding Scheme AAFC Collection Scheme (aafc.collection)
+
|-
Constraints
+
| Type of term || Property  
Obligation Mandatory
+
|-
Metadata Type Descriptive
+
| Definition || The attribute is used to select the content page presentation template.
Entry Type Auto-populated
+
|-
Exception: It is not auto-populated for Common-Commun, Rural Secretariat and Co-operatives Secretariat
+
| Comment || Used to indicate to the web presentation application, AAFC Online, which content page presentation template it should use to display the content record. Therefore, the attribute is used to match the TeamSite DCR to the presentation layer .jsp that is being rendered.
Occurrence Not repeatable
+
|-
Current Use In Use  
+
| References ||
Guidance
+
|-
Explanation of Usage Why to Use
+
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Relations'''
The Collection Value is used to categorize web pages into specific topics and assist in navigation. The collection value will be provided in the left-hand menu under the appropriate lane. The breadcrumbs are set-up the following way: Home>Lane>Collection.  
+
|-
 +
| Encoding Scheme || AAFC controlled vocabulary (aafc.presentationtemplatetype)
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Constraints'''
 +
|-
 +
| Obligation || Mandatory
 +
|-
 +
| Metadata Type || Descriptive
 +
|-
 +
| Entry Type || Auto-populated
 +
|-
 +
| Occurrence || Not repeatable  
 +
|-
 +
| Current Use || In Use  
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Guidance'''
 +
|-
 +
| Explanation of Usage || '''Why to Use'''
 +
Use this attribute to indicate to AAFC Online which content page presentation template should be used to display the content record.
  
How to Use
+
'''How to Use'''
In the ‘Descriptive’ tab of the CMS, the user must select the appropriate value in the drop down menu. There are two different AAFC Collection controlled vocabularies. All Primary Lane values, except Programs and Services, will use the same AAFC Collection controlled vocabulary. For Programs and Services, the collection value will be auto-populated.
 
*Requests to add, modify or remove values must be sent to E-Communications, who will begin the change request process. The Information Architecture Services’ Metadata Specialists will verify the values, and ensure that the values in the CMS have been updated correctly.
 
Example of HTML Syntax <meta name="aafc.collection" title="aafcCollection" content="AgriInvest" />
 
 
4.2 AAFC Presentation Template Type
 
Attribute Attribute Description
 
Identification
 
Term Name presentationTemplateType
 
URI
 
Label AAFC Presentation Template Type
 
Defined by AAFC-AAC
 
Definition
 
Type of term Property
 
Definition The attribute is used to select the content page presentation template.
 
Comment Used to indicate to the web presentation application, AAFC Online, which content page presentation template it should use to display the content record. Therefore, the attribute is used to match the TeamSite DCR to the presentation layer .jsp that is being rendered.
 
References
 
Relations
 
Encoding Scheme AAFC controlled vocabulary (aafc.presentationtemplatetype)
 
Constraints
 
Obligation Mandatory
 
  
Metadata Type Descriptive
 
Entry Type Auto-populated
 
Occurrence Not repeatable
 
Current Use In Use
 
Guidance
 
Explanation of Usage Why to Use
 
Use this attribute to indicate to AAFC Online which content page presentation template should be used to display the content record.
 
 
How to Use
 
 
The default value is 2 columns. The user would need to manually change the value using the drop down menu if a different value was required.  
 
The default value is 2 columns. The user would need to manually change the value using the drop down menu if a different value was required.  
Example of HTML Syntax Not applicable
+
|-
 
+
| Example of HTML Syntax || Not applicable.
 
+
|}
 
 
 
 
  
  
 +
===AAFC Primary Lane===
  
 
+
{| class="wikitable" style="width: 100%; height: 200px"
 
+
|-
 
+
! scope="col" width="225px" style="background:#FFBF00"| '''Attribute'''
 
+
!style="background:#FFBF00"| '''Attribute Description'''
4.3 AAFC Primary Lane
+
|-
Attribute Attribute Description
+
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Identification'''
Identification
+
|-
Term Name primaryLane
+
| Term Name || primaryLane
URI
+
|-
Label Primary Lane
+
| URI ||
Defined by AAFC-AAC  
+
|-
Definition
+
| Label || Primary Lane
Type of term Property
+
|-
Definition The Primary Lane groups together web pages of similar interests or themes in order to dynamically generate the presentation layer requirements (style sheets, banners, navigation menus, etc).
+
| Defined by || AAFC-AAC  
Comment
+
|-
References
+
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Definition'''
Relations
+
|-
Encoding Scheme AAFC Primary  Lane Scheme (aafc.primaryLane)
+
| Type of term || Property  
Constraints
+
|-
Obligation Mandatory  
+
| Definition || The Primary Lane groups together web pages of similar interests or themes in order to dynamically generate the presentation layer requirements (style sheets, banners, navigation menus, etc).
 
+
|-
Metadata Type Descriptive
+
| Comment ||
Entry Type Auto-populated
+
|-
Exception: It is not auto-populated for Common-Commun, Rural Secretariat and Co-operatives Secretariat
+
| References ||
Occurrence Not repeatable
+
|-
Current Use In Use  
+
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Relations'''
Guidance
+
|-
Explanation of Usage Why to Use
+
| Encoding Scheme || AAFC Primary  Lane Scheme (aafc.primaryLane)
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Constraints'''
 +
|-
 +
| Obligation || Mandatory
 +
|-
 +
| Metadata Type || Descriptive
 +
|-
 +
| Entry Type || Auto-populated
 +
Exception: It is not auto-populated for Common-Commun, Rural Secretariat and Co-operatives  
 +
|-
 +
| Occurrence || Not repeatable  
 +
|-
 +
| Current Use || In Use  
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Guidance'''
 +
|-
 +
| Explanation of Usage || '''Why to Use'''
 
The Primary Lane is used to denote the first level of content below the Home page, into general subject/thematic areas. This attribute is driven by the business/content areas.
 
The Primary Lane is used to denote the first level of content below the Home page, into general subject/thematic areas. This attribute is driven by the business/content areas.
 
It divides content into major sections that share a common top left navigation menu (Lane menu) and other presentation attributes (Lane banner graphic, style sheets, etc). The Primary Lane determines the location and presentation of the content by loading the appropriate presentation layer requirements (style sheets, banners, navigation menus, etc). The breadcrumbs are set-up the following way: Home>Lane>Collection
 
It divides content into major sections that share a common top left navigation menu (Lane menu) and other presentation attributes (Lane banner graphic, style sheets, etc). The Primary Lane determines the location and presentation of the content by loading the appropriate presentation layer requirements (style sheets, banners, navigation menus, etc). The breadcrumbs are set-up the following way: Home>Lane>Collection
  
How to Use
+
'''How to Use'''
 +
 
 
In the ‘Descriptive’ tab of the CMS, the user must select the appropriate value in the drop down menu. For all branches, except Common-Commun, Rural Secretariat and Co-operatives Secretariat, the value is auto-populated.  
 
In the ‘Descriptive’ tab of the CMS, the user must select the appropriate value in the drop down menu. For all branches, except Common-Commun, Rural Secretariat and Co-operatives Secretariat, the value is auto-populated.  
 
*Requests to add, modify or remove values must be sent to E-Communications, who will begin the change request process. The Information Architecture Services’ Metadata Specialists will verify the values, and ensure that the values in the CMS have been updated correctly. E-Communications is involved in the process for how the Primary Lane is assigned to resources.
 
*Requests to add, modify or remove values must be sent to E-Communications, who will begin the change request process. The Information Architecture Services’ Metadata Specialists will verify the values, and ensure that the values in the CMS have been updated correctly. E-Communications is involved in the process for how the Primary Lane is assigned to resources.
Example of HTML Syntax <meta name="aafc.primaryLane" title="aafcPrimaryLane" content="Producers" />
+
|-
 
+
| Example of HTML Syntax || <meta name="aafc.primaryLane" <font color="red">title</font>="aafcPrimaryLane" content="Producers" />
 
+
|}
 
 
4.4 Administrative Parent ID
 
Attribute Attribute Description
 
Identification
 
Term Name administrativeParentID
 
URI
 
Label Administrative Parent ID
 
Defined by AAFC-AAC
 
Definition
 
Type of term Property
 
Definition An identification number relating to the parent (original) web page.
 
Comment
 
References
 
Relations
 
Encoding Scheme
 
Constraints
 
Obligation Optional
 
Metadata Type Administrative
 
Entry Type Property is not operational
 
Occurrence Not repeatable
 
Current Use Not in use
 
Guidance
 
Explanation of Usage Property is not operational
 
Example of HTML Syntax Property is not operational
 
 
 
 
 
 
 
 
 
 
 
  
  
 +
===Administrative Parent ID===
  
 +
{| class="wikitable" style="width: 100%; height: 200px"
 +
|-
 +
! scope="col" width="225px" style="background:#FFBF00"| '''Attribute'''
 +
!style="background:#FFBF00"| '''Attribute Description'''
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Identification'''
 +
|-
 +
| Term Name || administrativeParentID
 +
|-
 +
| URI ||
 +
|-
 +
| Label || Administrative Parent ID
 +
|-
 +
| Defined by || AAFC-AAC
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Definition'''
 +
|-
 +
| Type of term || Property
 +
|-
 +
| Definition || An identification number relating to the parent (original) web page.
 +
|-
 +
| Comment ||
 +
|-
 +
| References ||
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Relations'''
 +
|-
 +
| Encoding Scheme ||
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Constraints'''
 +
|-
 +
| Obligation || Optional
 +
|-
 +
| Metadata Type || Administrative
 +
|-
 +
| Entry Type || Property is not operational
 +
|-
 +
| Occurrence || Not repeatable
 +
|-
 +
| Current Use || Not in use
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Guidance'''
 +
|-
 +
| Explanation of Usage || Property is not operational
 +
|-
 +
| Example of HTML Syntax || Property is not operational
 +
|}
  
  
 +
===Audience===
  
 +
{| class="wikitable" style="width: 100%; height: 200px"
 +
|-
 +
! scope="col" width="225px" style="background:#FFBF00"| '''Attribute'''
 +
!style="background:#FFBF00"| '''Attribute Description'''
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Identification'''
 +
|-
 +
| Term Name || audience
 +
|-
 +
| URI || http://purl.org/dc/terms/audience
 +
|-
 +
| Label || Audience
 +
|-
 +
| Defined by || DCMI Metadata Terms
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Definition'''
 +
|-
 +
| Type of term || Property
 +
|-
 +
| Definition || A class of entity for whom the resource is intended or useful.
 +
|-
 +
| Comment || To identify this resource as being of interest to a specific demographic.
 +
|-
 +
| References ||
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Relations'''
 +
|-
 +
| Encoding Scheme || Government of Canada Audience Scheme (gcaudience)
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Constraints'''
 +
|-
 +
| Obligation || Optional
 +
|-
 +
| Metadata Type || Descriptive
 +
|-
 +
| Entry Type || User entry (user selected)
 +
|-
 +
| Occurrence || Not repeatable
 +
|-
 +
| Current Use || Not in use
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Guidance'''
 +
|-
 +
| Explanation of Usage || '''Why to Use'''
 +
Use the attribute to identify the group(s) for whom the information and services are intended.
  
 +
'''How to Use'''
  
 
 
 
 
4.5 Audience
 
Attribute Attribute Description
 
Identification
 
Term Name audience
 
URI http://purl.org/dc/terms/audience
 
 
Label Audience
 
Defined by DCMI Metadata Terms
 
Definition
 
Type of term Property
 
Definition A class of entity for whom the resource is intended or useful.
 
Comment To identify this resource as being of interest to a specific demographic.
 
References
 
Relations
 
Encoding Scheme Government of Canada Audience Scheme (gcaudience)
 
 
Constraints
 
Obligation Optional
 
Metadata Type Descriptive
 
Entry Type User entry (user selected)
 
Occurrence Not repeatable
 
Current Use Not in use
 
Guidance
 
Explanation of Usage Why to Use
 
Use the attribute to identify the group(s) for whom the information and services are intended.
 
 
How to Use
 
 
This attribute is not currently in use at AAFC.  
 
This attribute is not currently in use at AAFC.  
Example of HTML Syntax <meta name="dcterms.audience" title="gcaudience" content="business" />
+
|-
 
+
| Example of HTML Syntax || <meta name="<font color="red">dcterms.audience</font>" <font color="red">title</font>="gcaudience" content="business" />
 
+
|}
 
 
 
 
 
 
 
 
 
 
 
 
  
  
 +
===Content Coordinator Name===
  
 +
{| class="wikitable" style="width: 100%; height: 200px"
 +
|-
 +
! scope="col" width="225px" style="background:#FFBF00"| '''Attribute'''
 +
!style="background:#FFBF00"| '''Attribute Description'''
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Identification'''
 +
|-
 +
| Term Name || contentCoordinatorName
 +
|-
 +
| URI ||
 +
|-
 +
| Label || Content Coordinator Name
 +
|-
 +
| Defined by || AAFC-AAC
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Definition'''
 +
|-
 +
| Type of term || Property
 +
|-
 +
| Definition || The names of the person(s) who have the authority to edit the content.
 +
|-
 +
| Comment || To reflect the ownership structure per page according to the approved web governance framework.
 +
|-
 +
| References ||
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Relations'''
 +
|-
 +
| Encoding Scheme ||
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Constraints'''
 +
|-
 +
| Obligation || Optional
 +
|-
 +
| Metadata Type || Administrative
 +
|-
 +
| Entry Type || User entry (free-text description)
 +
|-
 +
| Occurrence || Repeatable
 +
|-
 +
| Current Use || Not in use
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Guidance'''
 +
|-
 +
| Explanation of Usage || '''Why to Use'''
 +
It is used to state the person(s) who is allowed to edit the content.
  
 +
'''How to Use'''
  
4.6 Content Coordinator Name
 
Attribute Attribute Description
 
Identification
 
Term Name contentCoordinatorName
 
URI
 
Label Content Coordinator Name
 
Defined by AAFC-AAC
 
Definition
 
Type of term Property
 
Definition The names of the person(s) who have the authority to edit the content.
 
Comment To reflect the ownership structure per page according to the approved web governance framework.
 
References
 
Relations
 
Encoding Scheme
 
Constraints
 
Obligation Optional
 
Metadata Type Administrative
 
 
Entry Type User entry (free-text description)
 
Occurrence Repeatable
 
Current Use Not in use
 
Guidance
 
Explanation of Usage Why to Use
 
It is used to state the person(s) who is allowed to edit the content.
 
 
How to Use
 
 
This attribute is not currently in use at AAFC. However, if a user wants to provide a name, the field is limited to 100 characters.  
 
This attribute is not currently in use at AAFC. However, if a user wants to provide a name, the field is limited to 100 characters.  
Example of HTML Syntax Not applicable
+
|-
 
+
| Example of HTML Syntax || Not applicable
 
+
|}
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
  
  
 +
===Content Coordinator Position===
  
 +
{| class="wikitable" style="width: 100%; height: 200px"
 +
|-
 +
! scope="col" width="225px" style="background:#FFBF00"| '''Attribute'''
 +
!style="background:#FFBF00"| '''Attribute Description'''
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Identification'''
 +
|-
 +
| Term Name || contentCoordinatorPosition
 +
|-
 +
| URI ||
 +
|-
 +
| Label || Content Coordinator Position
 +
|-
 +
| Defined by || AAFC-AAC
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Definition'''
 +
|-
 +
| Type of term || Property
 +
|-
 +
| Definition || The role of the person(s) who have the authority to edit the content.
 +
|-
 +
| Comment || To reflect the ownership structure per page according to the approved web governance framework.
 +
|-
 +
| References ||
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Relations'''
 +
|-
 +
| Encoding Scheme ||
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Constraints'''
 +
|-
 +
| Obligation || Optional
 +
|-
 +
| Metadata Type || Administrative
 +
|-
 +
| Entry Type || User entry (free-text description)
 +
|-
 +
| Occurrence || Repeatable
 +
|-
 +
| Current Use || Not in use
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Guidance'''
 +
|-
 +
| Explanation of Usage || '''Why to Use'''
 +
It is used to state the role of the person(s) who are allowed to edit the content.
  
4.7 Content Coordinator Position
+
'''How to Use'''
Attribute Attribute Description
 
Identification
 
Term Name contentCoordinatorPosition
 
URI
 
Label Content Coordinator Position
 
Defined by AAFC-AAC
 
Definition
 
Type of term Property
 
Definition The role of the person(s) who have the authority to edit the content.
 
Comment To reflect the ownership structure per page according to the approved web governance framework.
 
References
 
Relations
 
Encoding Scheme
 
Constraints
 
Obligation Optional
 
Metadata Type Administrative
 
Entry Type User entry (free-text description)
 
Occurrence Repeatable
 
Current Use Not in use
 
Guidance
 
Explanation of Usage Why to Use
 
It is used to state the role of the person(s) who are allowed to edit the content.
 
  
How to Use
 
 
This attribute is not currently in use at AAFC. However, if a user wants to provide a position title, the field is limited to 200 characters.
 
This attribute is not currently in use at AAFC. However, if a user wants to provide a position title, the field is limited to 200 characters.
Example of HTML Syntax Not applicable
+
|-
 
+
| Example of HTML Syntax || Not applicable
 
+
|}
 
 
 
 
 
 
 
 
  
  
 +
===Content Coordinator Team===
  
 +
{| class="wikitable" style="width: 100%; height: 200px"
 +
|-
 +
! scope="col" width="225px" style="background:#FFBF00"| '''Attribute'''
 +
!style="background:#FFBF00"| '''Attribute Description'''
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Identification'''
 +
|-
 +
| Term Name || contentCoordinatorTeam
 +
|-
 +
| URI ||
 +
|-
 +
| Label || Content Coordinator Team
 +
|-
 +
| Defined by || AAFC-AAC
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Definition'''
 +
|-
 +
| Type of term || Property
 +
|-
 +
| Definition || The team name of the person(s) who has the authority to edit the content.
 +
|-
 +
| Comment || To reflect the ownership structure per page according to the approved web governance framework.
 +
|-
 +
| References ||
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Relations'''
 +
|-
 +
| Encoding Scheme ||
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Constraints'''
 +
|-
 +
| Obligation || Optional
 +
|-
 +
| Metadata Type || Administrative
 +
|-
 +
| Entry Type || User entry (free-text description)
 +
|-
 +
| Occurrence || Repeatable
 +
|-
 +
| Current Use || Not in use
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Guidance'''
 +
|-
 +
| Explanation of Usage || '''Why to Use'''
 +
It is used to state the team name of the person(s) who are allowed to edit the content.
  
 +
'''How to Use'''
  
 
 
 
 
 
4.8 Content Coordinator Team
 
Attribute Attribute Description
 
Identification
 
Term Name contentCoordinatorTeam 
 
URI
 
Label Content Coordinator Team
 
Defined by AAFC-AAC
 
Definition
 
Type of term Property
 
Definition The team name of the person(s) who has the authority to edit the content.
 
Comment To reflect the ownership structure per page according to the approved web governance framework.
 
References
 
Relations
 
Encoding Scheme
 
Constraints
 
Obligation Optional
 
Metadata Type Administrative
 
Entry Type User entry (free-text description)
 
Occurrence Repeatable
 
Current Use Not in use
 
Guidance
 
Explanation of Usage Why to Use
 
It is used to state the team name of the person(s) who are allowed to edit the content.
 
 
How to Use
 
 
This attribute is not currently in use at AAFC. However, if a user wants to provide a team name, the field is limited to 200 characters.
 
This attribute is not currently in use at AAFC. However, if a user wants to provide a team name, the field is limited to 200 characters.
Example of HTML Syntax Not applicable
+
|-
 
+
| Example of HTML Syntax || Not applicable
 
+
|}
 
 
 
 
 
 
 
 
 
 
 
 
 
 
  
  
 +
===Content Owner Name===
  
 +
{| class="wikitable" style="width: 100%; height: 200px"
 +
|-
 +
! scope="col" width="225px" style="background:#FFBF00"| '''Attribute'''
 +
!style="background:#FFBF00"| '''Attribute Description'''
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Identification'''
 +
|-
 +
| Term Name || contentOwnerName
 +
|-
 +
| URI ||
 +
|-
 +
| Label || Content Owner Name
 +
|-
 +
| Defined by || AAFC-AAC
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Definition'''
 +
|-
 +
| Type of term || Property
 +
|-
 +
| Definition || The name of the person with the highest level of accountability in creation of the content.
 +
|-
 +
| Comment || To reflect the ownership structure per page according to the approved web governance framework.
 +
|-
 +
| References ||
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Relations'''
 +
|-
 +
| Encoding Scheme ||
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Constraints'''
 +
|-
 +
| Obligation || Optional
 +
|-
 +
| Metadata Type || Administrative
 +
|-
 +
| Entry Type || User entry (free-text description)
 +
|-
 +
| Occurrence || Not repeatable
 +
|-
 +
| Current Use || Not in use
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Guidance'''
 +
|-
 +
| Explanation of Usage || '''Why to Use'''
 +
It is used to state the person with the highest level of accountability in creation of the content. It is always the Assistant Deputy Minister (ADM).
  
 +
'''How to Use'''
  
 
 
 
4.9 Content Owner Name
 
Attribute Attribute Description
 
Identification
 
Term Name contentOwnerName
 
URI
 
Label Content Owner Name
 
Defined by AAFC-AAC
 
Definition
 
Type of term Property
 
Definition The name of the person with the highest level of accountability in creation of the content.
 
Comment To reflect the ownership structure per page according to the approved web governance framework.
 
References
 
Relations
 
Encoding Scheme
 
Constraints
 
Obligation Optional
 
Metadata Type Administrative
 
Entry Type User entry (free-text description)
 
Occurrence Not repeatable
 
Current Use Not in use
 
Guidance
 
Explanation of Usage Why to Use
 
It is used to state the person with the highest level of accountability in creation of the content. It is always the Assistant Deputy Minister (ADM).
 
 
How to Use
 
 
This attribute is not currently in use at AAFC. However, if a user wants to provide a name, the field is limited to 200 characters. The field is not repeatable and if a user provides more than one name in the field it will treat it as one entry.  
 
This attribute is not currently in use at AAFC. However, if a user wants to provide a name, the field is limited to 200 characters. The field is not repeatable and if a user provides more than one name in the field it will treat it as one entry.  
Example of HTML Syntax Not applicable
+
|-
 
+
| Example of HTML Syntax || Not applicable
 
+
|}
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
  
  
 +
===Content Owner Position/Title===
  
 
+
{| class="wikitable" style="width: 100%; height: 200px"
4.10 Content Owner Position/Title
+
|-
Attribute Attribute Description
+
! scope="col" width="225px" style="background:#FFBF00"| '''Attribute'''
Identification
+
!style="background:#FFBF00"| '''Attribute Description'''
Term Name contentOwnerPositionTitle  
+
|-
URI
+
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Identification'''
Label Content Owner Position/Title  
+
|-
Defined by AAFC-AAC  
+
| Term Name || contentOwnerPositionTitle
Definition
+
|-
Type of term Property
+
| URI ||
Definition The title of the person with the highest level of accountability in creation of the content.
+
|-
Comment To reflect the ownership structure per page according to the approved web governance framework.
+
| Label || Content Owner Position/Title  
References
+
|-
Relations
+
| Defined by || AAFC-AAC
Encoding Scheme
+
|-
Constraints
+
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Definition'''
Obligation Optional  
+
|-
Metadata Type Administrative
+
| Type of term || Property  
 
+
|-
Entry Type User entry (free-text description)
+
| Definition || The title of the person with the highest level of accountability in creation of the content.
Occurrence Not repeatable
+
|-
Current Use Not in use  
+
| Comment || To reflect the ownership structure per page according to the approved web governance framework.
Guidance
+
|-
Explanation of Usage Why to Use
+
| References ||
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Relations'''
 +
|-
 +
| Encoding Scheme ||
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Constraints'''
 +
|-
 +
| Obligation || Optional
 +
|-
 +
| Metadata Type || Administrative
 +
|-
 +
| Entry Type || User entry (free-text description)
 +
|-
 +
| Occurrence || Not repeatable
 +
|-
 +
| Current Use || Not in use
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Guidance'''
 +
|-
 +
| Explanation of Usage || '''Why to Use'''
 
It is used to state the title of the person with the highest level of accountability in creation of the content. It is always the Assistant Deputy Minister (ADM).
 
It is used to state the title of the person with the highest level of accountability in creation of the content. It is always the Assistant Deputy Minister (ADM).
  
How to Use
+
'''How to Use'''
This attribute is not currently in use at AAFC. However, if a user wants to provide a position title, the field is limited to 200 characters. The field is not repeatable and if a user provides more than one position title in the field it will treat it as one entry.
 
Example of HTML Syntax Not applicable
 
  
 +
This attribute is not currently in use at AAFC. However, if a user wants to provide a position title, the field is limited to 200 characters. The field is not repeatable and if a user provides more than one position title in the field it will treat it as one entry.
 +
|-
 +
| Example of HTML Syntax || Not applicable
 +
|}
  
  
 +
===Content Owner Team===
  
 +
{| class="wikitable" style="width: 100%; height: 200px"
 +
|-
 +
! scope="col" width="225px" style="background:#FFBF00"| '''Attribute'''
 +
!style="background:#FFBF00"| '''Attribute Description'''
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Identification'''
 +
|-
 +
| Term Name || contentOwnerTeam
 +
|-
 +
| URI ||
 +
|-
 +
| Label || Content Owner Team
 +
|-
 +
| Defined by || AAFC-AAC
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Definition'''
 +
|-
 +
| Type of term || Property
 +
|-
 +
| Definition || The team name the person with the highest level of accountability in creation of the content.
 +
|-
 +
| Comment || To reflect the ownership structure per page according to the approved web governance framework.
 +
|-
 +
| References ||
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Relations'''
 +
|-
 +
| Encoding Scheme ||
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Constraints'''
 +
|-
 +
| Obligation || Optional
 +
|-
 +
| Metadata Type || Administrative
 +
|-
 +
| Entry Type || User entry (free-text description)
 +
|-
 +
| Occurrence || Not repeatable
 +
|-
 +
| Current Use || Not in use
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Guidance'''
 +
|-
 +
| Explanation of Usage || '''Why to Use'''
 +
It is used to state the team name of the person with the highest level of accountability in creation of the content. The person with the highest level of accountability is the Assistant Deputy Minister (ADM).
  
 +
'''How to Use'''
  
 
 
 
 
 
 
 
 
 
 
4.11 Content Owner Team
 
Attribute Attribute Description
 
Identification
 
Term Name contentOwnerTeam
 
URI
 
Label Content Owner Team
 
Defined by AAFC-AAC
 
Definition
 
Type of term Property
 
Definition The team name the person with the highest level of accountability in creation of the content.
 
Comment To reflect the ownership structure per page according to the approved web governance framework.
 
References
 
Relations
 
Encoding Scheme
 
Constraints
 
Obligation Optional
 
Metadata Type Administrative
 
 
Entry Type User entry (free-text description)
 
Occurrence Not repeatable
 
Current Use Not in use
 
Guidance
 
Explanation of Usage Why to Use
 
It is used to state the team name of the person with the highest level of accountability in creation of the content. The person with the highest level of accountability is the Assistant Deputy Minister (ADM).
 
 
How to Use
 
 
This attribute is not currently in use at AAFC. However, if a user wants to provide a team name, the field is limited to 200 characters. The field is not repeatable and if a user provides more than one team name in the field it will treat it as one entry.
 
This attribute is not currently in use at AAFC. However, if a user wants to provide a team name, the field is limited to 200 characters. The field is not repeatable and if a user provides more than one team name in the field it will treat it as one entry.
Example of HTML Syntax Not applicable
+
|-
 
+
| Example of HTML Syntax || Not applicable
 
+
|}
 
 
 
 
 
 
 
 
 
 
 
 
  
  
 +
===Coverage (domestic)===
  
 
+
{| class="wikitable" style="width: 100%; height: 200px"
 
+
|-
 
+
! scope="col" width="225px" style="background:#FFBF00"| '''Attribute'''
 
+
!style="background:#FFBF00"| '''Attribute Description'''
4.12 Coverage (domestic)
+
|-
Attribute Attribute Description
+
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Identification'''
Identification
+
|-
Term Name coverage
+
| Term Name || coverage  
URI http://purl.org/dc/terms/coverage  
+
|-
 
+
| URI || http://purl.org/dc/terms/coverage  
Label Coverage (domestic)
+
|-
Defined by DCMI Metadata Terms
+
| Label || Coverage (domestic)
Definition
+
|-
Type of term Property
+
| Defined by || DCMI Metadata Terms
Definition The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant.
+
|-
Comment Spatial topic and spatial applicability may be a named place or a location specified by its geographic coordinates.
+
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Definition'''
References
+
|-
Relations
+
| Type of term || Property  
Encoding Scheme Regions of Canada (gcregions)
+
|-
 +
| Definition || The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant.
 +
|-
 +
| Comment || Spatial topic and spatial applicability may be a named place or a location specified by its geographic coordinates.
 +
|-
 +
| References ||
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Relations'''
 +
|-
 +
| Encoding Scheme || Regions of Canada (gcregions)
 
http://geogratis.gc.ca/STATS/XML/CanadaProvRegions.jsp.xml
 
http://geogratis.gc.ca/STATS/XML/CanadaProvRegions.jsp.xml
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Constraints'''
 +
|-
 +
| Obligation || Optional
 +
|-
 +
| Metadata Type || Descriptive
 +
|-
 +
| Entry Type || User entry (user selected)
 +
|-
 +
| Occurrence || Not repeatable
 +
|-
 +
| Current Use || Not in use
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Guidance'''
 +
|-
 +
| Explanation of Usage || '''Why to Use'''
 +
To identify the geographic scope of the content of this resource for resource discovery and research purposes.
  
Constraints
+
'''How to Use'''
Obligation Optional
 
Metadata Type Descriptive
 
Entry Type User entry (user selected)
 
Occurrence Not repeatable
 
Current Use Not in use
 
Guidance
 
Explanation of Usage Why to Use
 
To identify the geographic scope of the content of this resource for resource discovery and research purposes.
 
  
How to Use
 
 
This attribute is not currently in use at AAFC.
 
This attribute is not currently in use at AAFC.
Example of HTML Syntax <meta name=”dcterms.spatial” title=”gcregions” content=”Canada”/>
+
|-
 
+
| Example of HTML Syntax || <meta name=”<font color="red">dcterms.spatial</font>” <font color="red">title</font>=”<font color="red">gcregions</font>” content=”Canada”/>
 
+
|}
 
 
  
  
 +
===Coverage (international)===
  
 
+
{| class="wikitable" style="width: 100%; height: 200px"
 
+
|-
 
+
! scope="col" width="225px" style="background:#FFBF00"| '''Attribute'''
 
+
!style="background:#FFBF00"| '''Attribute Description'''
 
+
|-
4.13 Coverage (international)
+
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Identification'''
Attribute Attribute Description
+
|-
Identification
+
| Term Name || coverage  
Term Name coverage
+
|-
URI http://purl.org/dc/terms/coverage
+
| URI || http://purl.org/dc/terms/coverage  
 
+
|-
Label Coverage (international)
+
| Label || Coverage (international)
Defined by DCMI Metadata Terms
+
|-
Definition
+
| Defined by || DCMI Metadata Terms
Type of term Property
+
|-
Definition The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant.
+
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Definition'''
Comment Spatial topic and spatial applicability may be a named place or a location specified by its geographic coordinates.
+
|-
References
+
| Type of term || Property  
Relations
+
|-
Encoding Scheme ISO 3166-1:2006
+
| Definition || The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant.
 +
|-
 +
| Comment || Spatial topic and spatial applicability may be a named place or a location specified by its geographic coordinates.
 +
|-
 +
| References ||
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Relations'''
 +
|-
 +
| Encoding Scheme || ISO 3166-1:2006
 
http://www.iso.org/iso/home/standards/country_codes/iso-3166-1_decoding_table.htm  
 
http://www.iso.org/iso/home/standards/country_codes/iso-3166-1_decoding_table.htm  
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Constraints'''
 +
|-
 +
| Obligation || Optional
 +
|-
 +
| Metadata Type || Descriptive
 +
|-
 +
| Entry Type || User entry (user selected)
 +
|-
 +
| Occurrence || Not repeatable
 +
|-
 +
| Current Use || Not in use
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Guidance'''
 +
|-
 +
| Explanation of Usage || '''Why to Use'''
 +
To identify the geographic scope of the content of this resource for resource discovery and research purposes.
  
Constraints
+
'''How to Use'''
Obligation Optional
 
Metadata Type Descriptive
 
Entry Type User entry (user selected)
 
Occurrence Not repeatable
 
Current Use Not in use
 
Guidance
 
Explanation of Usage Why to Use
 
To identify the geographic scope of the content of this resource for resource discovery and research purposes.
 
  
How to Use
 
 
This attribute is not currently in use at AAFC.
 
This attribute is not currently in use at AAFC.
Example of HTML Syntax Not applicable  
+
|-
 +
| Example of HTML Syntax || <font color="red">Not applicable
 +
</font>
 +
|}
  
  
 +
===Creator===
  
 
+
{| class="wikitable" style="width: 100%; height: 200px"
 
+
|-
 
+
! scope="col" width="225px" style="background:#FFBF00"| '''Attribute'''
 
+
!style="background:#FFBF00"| '''Attribute Description'''
 
+
|-
 
+
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Identification'''
 
+
|-
 
+
| Term Name || creator
4.14 Creator
+
|-
Attribute Attribute Description
+
| URI || http://purl.org/dc/elements/1.1/creator
Identification
+
|-
Term Name creator
+
| Label || Creator
URI http://purl.org/dc/elements/1.1/creator
+
|-
 
+
| Defined by || DCMI Metadata Terms
Label Creator
+
|-
Defined by DCMI Metadata Terms
+
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Definition'''
Definition
+
|-
Type of term Property
+
| Type of term || Property  
Definition An entity primarily responsible for making the content of the resource.
+
|-
Comment To identify the entity responsible for the intellectual content of this resource.
+
| Definition || An entity primarily responsible for making the content of the resource.
References
+
|-
Relations
+
| Comment || To identify the entity responsible for the intellectual content of this resource.
Encoding Scheme For titles of federal institutions
+
|-
 +
| References ||
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Relations'''
 +
|-
 +
| Encoding Scheme || '''For titles of federal institutions'''
 
Registry of Applied Titles
 
Registry of Applied Titles
 
http://www.tbs-sct.gc.ca/fip-pcim/reg-eng.asp
 
http://www.tbs-sct.gc.ca/fip-pcim/reg-eng.asp
  
For Government of Canada organizational divisions and subdivisions
+
'''For Government of Canada organizational divisions and subdivisions'''
 +
 
 
Government Electronic Directory Service (GEDS)  
 
Government Electronic Directory Service (GEDS)  
 
http://sage-geds.tpsgc-pwgsc.gc.ca/
 
http://sage-geds.tpsgc-pwgsc.gc.ca/
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Constraints'''
 +
|-
 +
| Obligation || Mandatory
 +
|-
 +
| Metadata Type || Administrative
 +
|-
 +
| Entry Type || Auto-populated/User entry
 +
|-
 +
| Occurrence || Not repeatable
 +
|-
 +
| Current Use || In Use
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Guidance'''
 +
|-
 +
| Explanation of Usage || '''Why to Use'''
 +
This attribute is important for a number of reasons including rights management, assisting in the determination of archival value and other lifecycle processes. This attribute must be expressed in the HTML <Header> to comply with the [http://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=18909&section=text Standard on Metadata].
  
Constraints
+
'''How to Use'''
Obligation Mandatory
 
Metadata Type Administrative
 
 
 
Entry Type Auto-populated/User entry
 
Occurrence Not repeatable
 
Current Use In Use
 
Guidance
 
Explanation of Usage Why to Use
 
This attribute is important for a number of reasons including rights management, assisting in the determination of archival value and other lifecycle processes. This attribute must be expressed in the HTML <Header> to comply with the Standard on Metadata.
 
  
How to Use
 
 
The Government of Canada (creator 1) and Agriculture and Agri-Food Canada (creator 2) are auto-populated. A third creator can be added using GEDS as a reference. The field allows for free-text. Each portion of the Creator attribute is entered separately in the CMS so there is no need to separate each unit with a period. For the Creator field, up to 200 characters are allowed.
 
The Government of Canada (creator 1) and Agriculture and Agri-Food Canada (creator 2) are auto-populated. A third creator can be added using GEDS as a reference. The field allows for free-text. Each portion of the Creator attribute is entered separately in the CMS so there is no need to separate each unit with a period. For the Creator field, up to 200 characters are allowed.
 
In the HTML syntax, each bureaucratic units and sub-divisions is separated with using a semi-colon (“ ; “).  
 
In the HTML syntax, each bureaucratic units and sub-divisions is separated with using a semi-colon (“ ; “).  
Example of HTML Syntax <meta name="dcterms.creator" content="Government of Canada;Agriculture and Agri-Food Canada;Research Branch" />  
+
|-
 +
| Example of HTML Syntax || <meta name="<font color="red">dcterms.creator</font> " content="Government of Canada;Agriculture and Agri-Food Canada;Research Branch" />  
 +
|}
  
  
 +
===Date for Review===
  
 
+
{| class="wikitable" style="width: 100%; height: 200px"
 
+
|-
 
+
! scope="col" width="225px" style="background:#FFBF00"| '''Attribute'''
 
+
!style="background:#FFBF00"| '''Attribute Description'''
4.15 Date for Review
+
|-
Attribute Attribute Description
+
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Identification'''
Identification
+
|-
Term Name dateForReview  
+
| Term Name || dateForReview
URI
+
|-
Label Date For Review  
+
| URI ||
Defined by Government of Canada Web Content Management System - Metadata Element Set
+
|-
Definition
+
| Label || Date For Review
Type of term Property
+
|-
Definition Date on which the issued resource will be revisited for evaluation of relevance or timeliness.
+
| Defined by || Government of Canada Web Content Management System - Metadata Element Set
Comment
+
|-
References
+
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Definition'''
Relations
+
|-
Encoding Scheme W3CDTF   
+
| Type of term || Property  
 +
|-
 +
| Definition || Date on which the issued resource will be revisited for evaluation of relevance or timeliness.
 +
|-
 +
| Comment ||
 +
|-
 +
| References ||
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Relations'''
 +
|-
 +
| Encoding Scheme ||W3CDTF   
 
http://www.w3.org/TR/NOTE-datetime
 
http://www.w3.org/TR/NOTE-datetime
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Constraints'''
 +
|-
 +
| Obligation || Mandatory
 +
|-
 +
| Metadata Type || Administrative
 +
|-
 +
| Entry Type || Auto-populated
 +
|-
 +
| Occurrence || Not repeatable
 +
|-
 +
| Current Use || In Use
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Guidance'''
 +
|-
 +
| Explanation of Usage || '''Why to Use'''
 +
This attribute is to be used to ensure the accuracy, relevance and timeliness of information on a web site.  This attribute can serve to provide the author, editor and publisher with a reminder that the content should be reviewed for its accuracy, relevance and timeliness.  This date must occur after Date Issued or Date Modified and ideally, before Valid Date. Though this attribute was not intended for publication to the web, it does appear in the HTML <Header>. 
  
Constraints
+
'''How to Use'''
Obligation Mandatory
 
Metadata Type Administrative
 
Entry Type Auto-populated
 
Occurrence Not repeatable
 
Current Use In Use
 
Guidance
 
Explanation of Usage Why to Use
 
This attribute is to be used to ensure the accuracy, relevance and timeliness of information on a web site.  This attribute can serve to provide the author, editor and publisher with a reminder that the content should be reviewed for its accuracy, relevance and timeliness.  This date must occur after Date Issued or Date Modified and ideally, before Valid Date. Though this attribute was not intended for publication to the web, it does appear in the HTML <Header>. 
 
  
How to Use
 
 
Date For Review is system generated by adding Date Reviewed to Next Review Period (selected number of months).  
 
Date For Review is system generated by adding Date Reviewed to Next Review Period (selected number of months).  
 
All dates will be entered in the form YYYY-MM-DD, as specified by the ISO 8601.  
 
All dates will be entered in the form YYYY-MM-DD, as specified by the ISO 8601.  
 
At this time, there is no trigger within the workflow system to notify the author or editor with a reminder that the content should be reviewed and/or updated.
 
At this time, there is no trigger within the workflow system to notify the author or editor with a reminder that the content should be reviewed and/or updated.
Example of HTML Syntax <meta name="gcterms.dateForReview" title="W3CDTF" content="2011-05-28" />
+
|-
 
+
| Example of HTML Syntax || <meta name="gcterms.dateForReview"<font color="red">title</font>="W3CDTF" content="2011-05-28" />
 +
|}
  
  
 +
===Date Issued===
  
 
+
{| class="wikitable" style="width: 100%; height: 200px"
 
+
|-
4.16 Date Issued
+
! scope="col" width="225px" style="background:#FFBF00"| '''Attribute'''
Attribute Attribute Description
+
!style="background:#FFBF00"| '''Attribute Description'''
Identification
+
|-
Term Name issued
+
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Identification'''
URI http://purl.org/dc/terms/issued
+
|-
 
+
| Term Name || issued
Label Date Issued
+
|-
Defined by DCMI Metadata Terms
+
| URI || http://purl.org/dc/terms/issued
Definition
+
|-
Type of term Property
+
| Label || Date Issued
Definition Date of formal issuance (e.g., publication) of the resource onto the web.  
+
|-
Comment
+
| Defined by || DCMI Metadata Terms
References
+
|-
Relations
+
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Definition'''
Encoding Scheme W3CDTF   
+
|-
 +
| Type of term || Property  
 +
|-
 +
| Definition || Date of formal issuance (e.g., publication) of the resource onto the web.
 +
|-
 +
| Comment ||
 +
|-
 +
| References ||
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Relations'''
 +
|-
 +
| Encoding Scheme ||W3CDTF   
 
http://www.w3.org/TR/NOTE-datetime
 
http://www.w3.org/TR/NOTE-datetime
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Constraints'''
 +
|-
 +
| Obligation || Mandatory
 +
|-
 +
| Metadata Type || Administrative
 +
|-
 +
| Entry Type || Auto-populated
 +
|-
 +
| Occurrence || Not repeatable
 +
|-
 +
| Current Use || In Use
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Guidance'''
 +
|-
 +
| Explanation of Usage || '''Why to Use'''
 +
The Date Issued attribute is used to capture the date the resource was first made available to the public on an Internet site. For legal purposes, this is an important date if users make decisions based on information provided by government departments. As well, it is useful for maintenance, resource discovery and evidentiary purposes. This attribute must be expressed in the HTML <Header> to comply with the [http://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=18909&section=text Standard on Metadata].
  
Constraints
+
'''How to Use'''
Obligation Mandatory
 
Metadata Type Administrative
 
Entry Type Auto-populated
 
Occurrence Not repeatable
 
Current Use In Use
 
Guidance
 
Explanation of Usage Why to Use
 
The Date Issued attribute is used to capture the date the resource was first made available to the public on an Internet site. For legal purposes, this is an important date if users make decisions based on information provided by government departments. As well, it is useful for maintenance, resource discovery and evidentiary purposes. This attribute must be expressed in the HTML <Header> to comply with the Standard on Metadata.
 
  
How to Use
 
 
The Date Issued is auto-populated. All dates will be entered in the form YYYY-MM-DD, as specified by ISO 8601.
 
The Date Issued is auto-populated. All dates will be entered in the form YYYY-MM-DD, as specified by ISO 8601.
Example of HTML Syntax <meta name="dcterms.issued" title="W3CDTF" content="2009-03-10" />
+
|-
 
+
| Example of HTML Syntax ||<meta name="dcterms.issued"<font color="red">title</font>="W3CDTF" content="2009-03-10" />
 
+
|}
 
 
 
 
 
 
  
  
 +
===Date Last Updated===
  
 
+
{| class="wikitable" style="width: 100%; height: 200px"
 
+
|-
 
+
! scope="col" width="225px" style="background:#FFBF00"| '''Attribute'''
 
+
!style="background:#FFBF00"| '''Attribute Description'''
 
+
|-
4.17 Date Last Updated
+
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Identification'''
Attribute Attribute Description
+
|-
Identification
+
| Term Name || dateLastUpdated
Term Name dateLastUpdated
+
|-
URI
+
| URI ||
Label Date Last Updated
+
|-
Defined by Government of Canada Web Content Management System - Metadata Element Set
+
| Label || Date Last Updated
Definition
+
|-
Type of term Property
+
| Defined by || Government of Canada Web Content Management System - Metadata Element Set
Definition Date on which the content resource was last changed within the CMS.
+
|-
Comment To document the last date on which a change (major or minor) has been made to this resource for maintenance, evidentiary, and system and workflow purposes.
+
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Definition'''
References
+
|-
Relations
+
| Type of term || Property  
Encoding Scheme W3CDTF  
+
|-
 +
| Definition || Date on which the content resource was last changed within the CMS.
 +
|-
 +
| Comment || To document the last date on which a change (major or minor) has been made to this resource for maintenance, evidentiary, and system and workflow purposes.
 +
|-
 +
| References ||
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Relations'''
 +
|-
 +
| Encoding Scheme ||W3CDTF
 
http://www.w3.org/TR/NOTE-datetime
 
http://www.w3.org/TR/NOTE-datetime
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Constraints'''
 +
|-
 +
| Obligation || Mandatory
 +
|-
 +
| Metadata Type || Administrative
 +
|-
 +
| Entry Type || Auto-populated
 +
|-
 +
| Occurrence || Not repeatable
 +
|-
 +
| Current Use || In Use
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Guidance'''
 +
|-
 +
| Explanation of Usage || '''Why to Use'''
 +
Date Last Updated identifies when any change has been made to the resource and the resource is saved in the CMS. 
  
Constraints
+
'''How to Use'''
Obligation Mandatory
 
Metadata Type Administrative
 
Entry Type Auto-populated
 
Occurrence Not repeatable
 
Current Use In Use
 
Guidance
 
Explanation of Usage Why to Use
 
Date Last Updated identifies when any change has been made to the resource and the resource is saved in the CMS. 
 
  
How to Use
 
 
Date Last Updated is system generated and is pre-populated from system date on Teamsite DCR creation and subsequently changed when the resource is re-saved in the CMS.  Date Last Updated cannot be manually changed. All dates will be entered in the form YYYY-MM-DD, as specified by ISO 8601.
 
Date Last Updated is system generated and is pre-populated from system date on Teamsite DCR creation and subsequently changed when the resource is re-saved in the CMS.  Date Last Updated cannot be manually changed. All dates will be entered in the form YYYY-MM-DD, as specified by ISO 8601.
 
+
|-
Example of HTML Syntax <meta name="gcterms.dateLastUpdated" title="W3CDTF" content="2011-09-30" />
+
| Example of HTML Syntax || <meta name="gcterms.dateLastUpdated" <font color="red">title</font>="W3CDTF" content="2011-09-30" />
 
+
|}
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
  
  
 +
===Date Modified===
  
4.18 Date Modified
+
{| class="wikitable" style="width: 100%; height: 200px"
Attribute Attribute Description
+
|-
Identification
+
! scope="col" width="225px" style="background:#FFBF00"| '''Attribute'''
Term Name modified
+
!style="background:#FFBF00"| '''Attribute Description'''
URI http://purl.org/dc/terms/modified
+
|-
 
+
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Identification'''
Label Date Modified
+
|-
Defined by DCMI Metadata Terms
+
| Term Name || modified
Definition
+
|-
Type of term Property
+
| URI || http://purl.org/dc/terms/modified
Definition The date when a substantial revision is done to the resource and is then re-published to the web.
+
|-
Comment To document when a significant change has been made to this resource to assist users in determining the currency of the content and for life-cycle management of the resource.
+
| Label || Date Modified
References
+
|-
Relations
+
| Defined by || DCMI Metadata Terms
Encoding Scheme W3CDTF  
+
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Definition'''
 +
|-
 +
| Type of term || Property  
 +
|-
 +
| Definition || The date when a <font color="red">substantial</font> revision is done to the resource and is then re-published to the web.
 +
|-
 +
| Comment || To document when a <font color="red">significant</font> change has been made to this resource to assist users in determining the currency of the content and for life-cycle management of the resource.
 +
|-
 +
| References ||
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Relations'''
 +
|-
 +
| Encoding Scheme ||W3CDTF
 
http://www.w3.org/TR/NOTE-datetime
 
http://www.w3.org/TR/NOTE-datetime
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Constraints'''
 +
|-
 +
| Obligation || Mandatory
 +
|-
 +
| Metadata Type || Administrative
 +
|-
 +
| Entry Type || auto-populated when the page is first issued/published. It will be user entry after that initial population.
 +
|-
 +
| Occurrence || Not repeatable
 +
|-
 +
| Current Use || In Use
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Guidance'''
 +
|-
 +
| Explanation of Usage || '''Why to Use'''
 +
This attribute is used to document the date on which a significant change to the content of the resource was made.  For formatting changes or small grammatical changes, the value of this attribute should not change; instead the Date Last Updated attribute will be used. This attribute must be expressed in the HTML <Header> to comply with the [http://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=18909&section=text Standard on Metadata].
  
Constraints
+
'''How to Use'''
Obligation Mandatory
 
Metadata Type Administrative
 
Entry Type auto-populated when the page is first issued/published. It will be user entry after that initial population.
 
Occurrence Not repeatable
 
Current Use In Use
 
Guidance
 
Explanation of Usage Why to Use
 
This attribute is used to document the date on which a significant change to the content of the resource was made.  For formatting changes or small grammatical changes, the value of this attribute should not change; instead the Date Last Updated attribute will be used. This attribute must be expressed in the HTML <Header> to comply with the Standard on Metadata.
 
  
How to Use
 
 
This attribute must always have a value in the CMS.  When a page is first published the Date Modified will be auto-populated with the date of publication. Date Modified is manually edited and replaces Date Issued in the footer of the page when a DCR is revised with substantial changes. All dates must be entered in the form YYYY-MM-DD, as specified by ISO 8601. There is a calendar option available to use when entering the date. Date modified cannot be a date that is earlier than Date Issued.  
 
This attribute must always have a value in the CMS.  When a page is first published the Date Modified will be auto-populated with the date of publication. Date Modified is manually edited and replaces Date Issued in the footer of the page when a DCR is revised with substantial changes. All dates must be entered in the form YYYY-MM-DD, as specified by ISO 8601. There is a calendar option available to use when entering the date. Date modified cannot be a date that is earlier than Date Issued.  
Example of HTML Syntax <meta name="dcterms.modified" title="W3CDTF" content="2010-04-09" />
+
|-
+
| Example of HTML Syntax || <meta name="dcterms.modified" <font color="red">title</font>="W3CDTF" content="2010-04-09" />
 +
|}
  
  
 +
===Date Reviewed===
  
 
+
{| class="wikitable" style="width: 100%; height: 200px"
 
+
|-
 
+
! scope="col" width="225px" style="background:#FFBF00"| '''Attribute'''
4.19 Date Reviewed
+
!style="background:#FFBF00"| '''Attribute Description'''
Attribute Attribute Description
+
|-
Identification
+
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Identification'''
Term Name dateReviewed
+
|-
URI
+
| Term Name || dateReviewed
Label Date Reviewed
+
|-
Defined by Government of Canada Web Content Management System – Metadata Element Set
+
| URI || http://purl.org/dc/terms/modified
Definition
+
|-
Type of term Property
+
| Label || Date Reviewed
Definition The last date on which the issued resource was revisited for evaluation of relevance or timeliness.
+
|-
Comment To indicate that this resource was reviewed and is current.
+
| Defined by || Government of Canada Web Content Management System – Metadata Element Set
References
+
|-
Relations
+
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Definition'''
Encoding Scheme W3CDTF  
+
|-
 +
| Type of term || Property  
 +
|-
 +
| Definition || The last date on which the issued resource was revisited for evaluation of relevance or timeliness.
 +
|-
 +
| Comment || To indicate that this resource was reviewed and is current.
 +
|-
 +
| References ||
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Relations'''
 +
|-
 +
| Encoding Scheme ||W3CDTF
 
http://www.w3.org/TR/NOTE-datetime
 
http://www.w3.org/TR/NOTE-datetime
 
+
|-
Constraints
+
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Constraints'''
Obligation Optional  
+
|-
Metadata Type Administrative
+
| Obligation || Optional  
Entry Type User entry  
+
|-
 +
| Metadata Type || Administrative
 +
|-
 +
| Entry Type || User entry  
 
Note: If a date is not selected by the user, it will auto-populate with the date it was published.  
 
Note: If a date is not selected by the user, it will auto-populate with the date it was published.  
Occurrence Not repeatable
+
|-
Current Use In Use  
+
| Occurrence || Not repeatable
Guidance
+
|-
Explanation of Usage Why to Use
+
| Current Use || In Use  
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Guidance'''
 +
|-
 +
| Explanation of Usage || '''Why to Use'''
 
Use this attribute to ensure the accuracy, relevance and timeliness of information on a web site. The attribute indicates to the author, editor, publisher or end-user that the content was accurate as of a specific date.
 
Use this attribute to ensure the accuracy, relevance and timeliness of information on a web site. The attribute indicates to the author, editor, publisher or end-user that the content was accurate as of a specific date.
  
How to Use
+
'''How to Use'''
 +
 
 
Date Reviewed is manually edited, though if left blank by the user the field will be populated with the date it was published. This date would remain until manually updated. All dates must be entered in the form YYYY-MM-DD, as specified by ISO 8601. There is a calendar option available to use when entering the date.
 
Date Reviewed is manually edited, though if left blank by the user the field will be populated with the date it was published. This date would remain until manually updated. All dates must be entered in the form YYYY-MM-DD, as specified by ISO 8601. There is a calendar option available to use when entering the date.
Example of HTML Syntax <meta name="gcterms.dateReviewed" title="W3CDTF" content="2010-05-28" />
+
|-
 
+
| Example of HTML Syntax || <meta name="gcterms.dateReviewed" <font color="red">title</font>="W3CDTF" content="2010-05-28" />
 
+
|}
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
  
  
 +
===DCR Name===
  
 
+
{| class="wikitable" style="width: 100%; height: 200px"
4.20 DCR Name
+
|-
Attribute Attribute Description
+
! scope="col" width="225px" style="background:#FFBF00"| '''Attribute'''
Identification
+
!style="background:#FFBF00"| '''Attribute Description'''
Term Name dcrName
+
|-
URI
+
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Identification'''
Label DCR Name
+
|-
Defined by AAFC-AAC  
+
| Term Name || dcrName
Definition
+
|-
Type of term Property
+
| URI ||
Definition An identifier linking resources that belong to a collection of resources.  
+
|-
Comment
+
| Label || DCR Name
References
+
|-
Relations
+
| Defined by || AAFC-AAC  
Encoding Scheme
+
|-
Constraints
+
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Definition'''
Obligation Mandatory  
+
|-
Metadata Type System
+
| Type of term || Property  
Entry Type Auto-populated
+
|-
Occurrence Not repeatable
+
| Definition || An identifier linking resources that belong to a collection of resources.  
Current Use In Use  
+
|-
Guidance
+
| Comment ||
Explanation of Usage Why to Use
+
|-
 +
| References ||
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Relations'''
 +
|-
 +
| Encoding Scheme ||
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Constraints'''
 +
|-
 +
| Obligation || Mandatory
 +
|-
 +
| Metadata Type || System
 +
|-
 +
| Entry Type || Auto-populated
 +
|-
 +
| Occurrence || Not repeatable
 +
|-
 +
| Current Use || In Use  
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Guidance'''
 +
|-
 +
| Explanation of Usage || '''Why to Use'''
 
The DCR Name is important for system-related issues, identification and navigation.  
 
The DCR Name is important for system-related issues, identification and navigation.  
  
How to Use
+
'''How to Use'''
The field is auto-populated. It cannot be modified by the user.
 
Example of HTML Syntax Not applicable
 
  
 +
The field is auto-populated. It cannot be modified by the user.
 +
|-
 +
| Example of HTML Syntax || Not applicable
 +
|}
  
  
 +
===DCR Type===
  
 
+
{| class="wikitable" style="width: 100%; height: 200px"
4.21 DCR Type
+
|-
Attribute Attribute Description
+
! scope="col" width="225px" style="background:#FFBF00"| '''Attribute'''
Identification
+
!style="background:#FFBF00"| '''Attribute Description'''
Term Name dcrType
+
|-
URI
+
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Identification'''
Label DCR Type
+
|-
Defined by AAFC-AAC  
+
| Term Name || dcrType
Definition
+
|-
Type of term Property
+
| URI ||
Definition A reference to a group of related resources by an identifier assigned within the CMS providing a pathway to a specific record.  
+
|-
Comment
+
| Label || DCR Type
References
+
|-
Relations
+
| Defined by || AAFC-AAC  
Encoding Scheme
+
|-
Constraints
+
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Definition'''
Obligation Mandatory  
+
|-
Metadata Type System
+
| Type of term || Property  
Entry Type Auto-populated
+
|-
Occurrence Not repeatable
+
| Definition || A reference to a group of related resources by an identifier assigned within the CMS providing a pathway to a specific record.  
Current Use In Use  
+
|-
Guidance
+
| Comment ||
Explanation of Usage Why to Use
+
|-
 +
| References ||
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Relations'''
 +
|-
 +
| Encoding Scheme ||
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Constraints'''
 +
|-
 +
| Obligation || Mandatory  
 +
|-
 +
| Metadata Type || System
 +
|-
 +
| Entry Type || Auto-populated
 +
|-
 +
| Occurrence || Not repeatable
 +
|-
 +
| Current Use || In Use  
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Guidance'''
 +
|-
 +
| Explanation of Usage || '''Why to Use'''
 
The DCR Type is important for system-related issues, identification and navigation.  
 
The DCR Type is important for system-related issues, identification and navigation.  
  
How to Use
+
'''How to Use'''
This field is auto-populated. It cannot be modified by the user.
 
Example of HTML Syntax Not applicable
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
  
 +
The field is auto-populated. It cannot be modified by the user.
 +
|-
 +
| Example of HTML Syntax || Not applicable
 +
|}
  
  
 +
===Delegate of Responsibility Name===
  
 +
{| class="wikitable" style="width: 100%; height: 200px"
 +
|-
 +
! scope="col" width="225px" style="background:#FFBF00"| '''Attribute'''
 +
!style="background:#FFBF00"| '''Attribute Description'''
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Identification'''
 +
|-
 +
| Term Name || delegateOfResponsiblitiyName
 +
|-
 +
| URI ||
 +
|-
 +
| Label || Delegate of Responsibility Name
 +
|-
 +
| Defined by || AAFC-AAC
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Definition'''
 +
|-
 +
| Type of term || Property
 +
|-
 +
| Definition || The name of the person who has the Delegate of Responsibility. They have been delegated responsibility for content by the Content Owner.
 +
|-
 +
| Comment || To reflect the ownership structure per page according to the approved web governance framework.
 +
|-
 +
| References ||
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Relations'''
 +
|-
 +
| Encoding Scheme ||
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Constraints'''
 +
|-
 +
| Obligation || Optional 
 +
|-
 +
| Metadata Type || Administrative
 +
|-
 +
| Entry Type || User entry (free-text description)
 +
|-
 +
| Occurrence || Not repeatable
 +
|-
 +
| Current Use || Not in use
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Guidance'''
 +
|-
 +
| Explanation of Usage || '''Why to Use'''
 +
It is used to state the name of the person appointed by the Content Owner who approves content to be published to the web.
  
4.22 Delegate of Responsibility Name
+
'''How to Use'''
Attribute Attribute Description
 
Identification
 
Term Name delegateOfResponsiblitiyName
 
URI
 
Label Delegate of Responsibility Name
 
Defined by AAFC-AAC
 
Definition
 
Type of term Property
 
Definition The name of the person who has the Delegate of Responsibility. They have been delegated responsibility for content by the Content Owner.
 
Comment To reflect the ownership structure per page according to the approved web governance framework.
 
References
 
Relations
 
Encoding Scheme
 
Constraints
 
Obligation Optional
 
Metadata Type Administrative
 
Entry Type User entry (free-text description)
 
Occurrence Not repeatable
 
Current Use Not in use
 
Guidance
 
Explanation of Usage Why to Use
 
It is used to state the name of the person appointed by the Content Owner who approves content to be published to the web.
 
  
How to Use
 
 
This attribute is not currently in use at AAFC. However, if a user wants to provide a name, the field is limited to 200 characters. The field is not repeatable and if a user provides more than one name in the field it will treat it as one entry.
 
This attribute is not currently in use at AAFC. However, if a user wants to provide a name, the field is limited to 200 characters. The field is not repeatable and if a user provides more than one name in the field it will treat it as one entry.
Example of HTML Syntax Not applicable
+
|-
 
+
| Example of HTML Syntax || Not applicable
 
+
|}
 
 
 
 
 
 
 
 
 
 
  
  
 +
===Delegate of Responsibility Position===
  
 +
{| class="wikitable" style="width: 100%; height: 200px"
 +
|-
 +
! scope="col" width="225px" style="background:#FFBF00"| '''Attribute'''
 +
!style="background:#FFBF00"| '''Attribute Description'''
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Identification'''
 +
|-
 +
| Term Name || delegateOfResponsibilityPosition
 +
|-
 +
| URI ||
 +
|-
 +
| Label || Delegate of Responsibility Position
 +
|-
 +
| Defined by || AAFC-AAC
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Definition'''
 +
|-
 +
| Type of term || Property
 +
|-
 +
| Definition || The position of the person with the Delegate of Responsibility.
 +
|-
 +
| Comment || To reflect the ownership structure per page according to the approved web governance framework.
 +
|-
 +
| References ||
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Relations'''
 +
|-
 +
| Encoding Scheme ||
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Constraints'''
 +
|-
 +
| Obligation || Optional 
 +
|-
 +
| Metadata Type || Administrative
 +
|-
 +
| Entry Type || User entry (free-text description)
 +
|-
 +
| Occurrence || Not repeatable
 +
|-
 +
| Current Use || Not in use
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Guidance'''
 +
|-
 +
| Explanation of Usage || '''Why to Use'''
 +
It is used to state the position title of the person appointed by the Content Owner who approves content to be published to the web.
  
 +
'''How to Use'''
  
 
4.23 Delegate of Responsibility Position
 
Attribute Attribute Description
 
Identification
 
Term Name delegateOfResponsibilityPosition
 
URI
 
Label Delegate of Responsibility Position
 
Defined by AAFC-AAC
 
Definition
 
Type of term Property
 
Definition The position of the person with the Delegate of Responsibility.
 
Comment To reflect the ownership structure per page according to the approved web governance framework.
 
References
 
Relations
 
Encoding Scheme
 
Constraints
 
Obligation Optional
 
Metadata Type Administrative
 
Entry Type User entry (free-text description)
 
Occurrence Not repeatable
 
Current Use Not in use
 
Guidance
 
Explanation of Usage Why to Use
 
It is used to state the position title of the person appointed by the Content Owner who approves content to be published to the web.
 
 
How to Use
 
 
This attribute is not currently in use at AAFC. However, if a user wants to provide a position title, the field is limited to 200 characters. The field is not repeatable and if a user provides more than one position title in the field it will treat it as one entry.
 
This attribute is not currently in use at AAFC. However, if a user wants to provide a position title, the field is limited to 200 characters. The field is not repeatable and if a user provides more than one position title in the field it will treat it as one entry.
Example of HTML Syntax Not applicable
+
|-
 
+
| Example of HTML Syntax || Not applicable
 
+
|}
 
 
 
 
  
  
 +
===Delegate of Responsibility Team===
  
 +
{| class="wikitable" style="width: 100%; height: 200px"
 +
|-
 +
! scope="col" width="225px" style="background:#FFBF00"| '''Attribute'''
 +
!style="background:#FFBF00"| '''Attribute Description'''
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Identification'''
 +
|-
 +
| Term Name || delegateOfResponsibilityTeam
 +
|-
 +
| URI ||
 +
|-
 +
| Label || Delegate of Responsibility Team
 +
|-
 +
| Defined by || AAFC-AAC
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Definition'''
 +
|-
 +
| Type of term || Property
 +
|-
 +
| Definition || The name of the team or branch of the Delegate of Responsibility.
 +
|-
 +
| Comment || To reflect the ownership structure per page according to the approved web governance framework.
 +
|-
 +
| References ||
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Relations'''
 +
|-
 +
| Encoding Scheme ||
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Constraints'''
 +
|-
 +
| Obligation || Optional 
 +
|-
 +
| Metadata Type || Administrative
 +
|-
 +
| Entry Type || User entry (free-text description)
 +
|-
 +
| Occurrence || Not repeatable
 +
|-
 +
| Current Use || Not in use
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Guidance'''
 +
|-
 +
| Explanation of Usage || '''Why to Use'''
 +
It is used to state the team name of the manager appointed by the Delegate of Responsibility who approves content to be published to the web.
  
 +
'''How to Use'''
  
 
 
 
 
 
4.24 Delegate of Responsibility Team
 
Attribute Attribute Description
 
Identification
 
Term Name delegateOfResponsibilityTeam
 
URI
 
Label Delegate of Responsibility Team
 
Defined by AAFC-AAC
 
Definition
 
Type of term Property
 
Definition The name of the team or branch of the Delegate of Responsibility.
 
Comment To reflect the ownership structure per page according to the approved web governance framework.
 
References
 
Relations
 
Encoding Scheme
 
Constraints
 
Obligation Optional
 
Metadata Type Administrative
 
Entry Type User entry (free-text description)
 
Occurrence Not repeatable
 
Current Use Not in use
 
Guidance
 
Explanation of Usage Why to Use
 
It is used to state the team name of the manager appointed by the Delegate of Responsibility who approves content to be published to the web.
 
 
How to Use
 
 
This attribute is not currently in use at AAFC. However, if a user wants to provide a team name, the field is limited to 200 characters. The field is not repeatable and if a user provides more than one team name in the field it will treat it as one entry.
 
This attribute is not currently in use at AAFC. However, if a user wants to provide a team name, the field is limited to 200 characters. The field is not repeatable and if a user provides more than one team name in the field it will treat it as one entry.
Example of HTML Syntax Not applicable
+
|-
 +
| Example of HTML Syntax || Not applicable
 +
|}
  
  
 +
===Description===
  
 +
{| class="wikitable" style="width: 100%; height: 200px"
 +
|-
 +
! scope="col" width="225px" style="background:#FFBF00"| '''Attribute'''
 +
!style="background:#FFBF00"| '''Attribute Description'''
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Identification'''
 +
|-
 +
| Term Name || description
 +
|-
 +
| URI || http://purl.org/dc/elements/1.1/description
 +
|-
 +
| Label || Description
 +
|-
 +
| Defined by || DCMI Metadata Terms
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Definition'''
 +
|-
 +
| Type of term || Property
 +
|-
 +
| Definition || A narrative account of the content of the resource.
 +
|-
 +
| Comment || Limited to 2000 characters.
 +
|-
 +
| References ||
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Relations'''
 +
|-
 +
| Encoding Scheme ||
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Constraints'''
 +
|-
 +
| Obligation || Optional
 +
|-
 +
| Metadata Type || Descriptive
 +
|-
 +
| Entry Type || <font color="red">Auto-populated
 +
Note: The field is initially populated by Metatagger, then verified by the Metadata Analysts.</font>
 +
|-
 +
| Occurrence || Not repeatable
 +
|-
 +
| Current Use || In Use
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Guidance'''
 +
|-
 +
| Explanation of Usage || '''Why to Use'''
 +
This attribute is used to assist the user in determining the relevance of the resources on a search results page or on a links page without having to navigate to each resource.
  
 +
'''How to Use'''
  
 
 
 
 
4.25 Description
 
Attribute Attribute Description
 
Identification
 
Term Name description
 
URI http://purl.org/dc/elements/1.1/description
 
 
Label Description
 
Defined by DCMI Metadata Terms
 
Definition
 
Type of term Property
 
Definition A narrative account of the content of the resource.
 
Comment Limited to 2000 characters.
 
References
 
Relations
 
Encoding Scheme
 
Constraints
 
Obligation Optional
 
Metadata Type Descriptive
 
Entry Type Auto-populated
 
Note: The field is initially populated by Metatagger, then verified by the Metadata Analysts.
 
Occurrence Not repeatable
 
Current Use In Use
 
Guidance
 
Explanation of Usage Why to Use
 
This attribute is used to assist the user in determining the relevance of the resources on a search results page or on a links page without having to navigate to each resource.
 
 
How to Use
 
 
The system limits data entry to 2000 characters. The description should be written in the language of the resource. For bilingual introductory (or splash) pages repeat the attribute for each language. The field can be auto-populated, but also allows user entry.  
 
The system limits data entry to 2000 characters. The description should be written in the language of the resource. For bilingual introductory (or splash) pages repeat the attribute for each language. The field can be auto-populated, but also allows user entry.  
 
+
|-
Example of HTML Syntax <meta name="dcterms.description" content="Agriculture and Agri-Food Canada provides information and programs for those who raise animals or who grow plants for food, feed or industrial use. Agricultural producers will find information about economic forecasts and statistics, policies and acts, incentive programs and other services" />
+
| Example of HTML Syntax || <meta name="<font color="red">dcterms.description</font>" content="Agriculture and Agri-Food Canada provides information and programs for those who raise animals or who grow plants for food, feed or industrial use. Agricultural producers will find information about economic forecasts and statistics, policies and acts, incentive programs and other services" />
 +
|}
  
  
 +
===Destination Delivery===
  
 
+
{| class="wikitable" style="width: 100%; height: 200px"
 
+
|-
 
+
! scope="col" width="225px" style="background:#FFBF00"| '''Attribute'''
 
+
!style="background:#FFBF00"| '''Attribute Description'''
4.26 Destination Delivery
+
|-
Attribute Attribute Description
+
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Identification'''
Identification
+
|-
Term Name destinationDelivery
+
| Term Name || destinationDelivery
URI
+
|-
Label Destination Delivery
+
| URI ||
Defined by Government of Canada Web Content Management System – Metadata Attribute Set
+
|-
Definition
+
| Label || Destination Delivery
Type of term Property
+
|-
Definition The destination(s) to which a piece of content is to be published (e.g., Internet, Extranet, Intranet, etc).
+
| Defined by || Government of Canada Web Content Management System – Metadata Attribute Set
Comment To identify the delivery output destinations to support publishing and dynamic display purposes.
+
|-
References
+
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Definition'''
Relations
+
|-
Encoding Scheme
+
| Type of term || Property  
Constraints
+
|-
Obligation Mandatory  
+
| Definition || The destination(s) to which a piece of content is to be published (e.g., Internet, Extranet, Intranet, etc).
Metadata Type System
+
|-
Entry Type Auto-populated
+
| Comment || To identify the delivery output destinations to support publishing and dynamic display purposes.
Occurrence Not repeatable
+
|-
Current Use In use
+
| References ||
Guidance
+
|-
Explanation of Usage Why to Use
+
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Relations'''
 +
|-
 +
| Encoding Scheme ||
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Constraints'''
 +
|-
 +
| Obligation || Mandatory  
 +
|-
 +
| Metadata Type || System
 +
|-
 +
| Entry Type || Auto-populated  
 +
|-
 +
| Occurrence || Not repeatable
 +
|-
 +
| Current Use || In Use
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Guidance'''
 +
|-
 +
| Explanation of Usage || '''Why to Use'''
 
Use this attribute to indicate where a record will be published (Internet, Extranet, Intranet, channels, or particular sections of web sites, etc). This attribute is used by the CMS in order to render the content to the correct online destinations.
 
Use this attribute to indicate where a record will be published (Internet, Extranet, Intranet, channels, or particular sections of web sites, etc). This attribute is used by the CMS in order to render the content to the correct online destinations.
  
How to Use
+
'''How to Use'''
The field is auto-populated. It cannot be modified once the record is created.
 
Example of HTML Syntax Not applicable
 
 
 
 
 
  
 +
The field is auto-populated. It cannot be modified once the record is created.
 +
|-
 +
| Example of HTML Syntax || Not applicable
 +
|}
  
  
 +
===Filename===
  
 +
{| class="wikitable" style="width: 100%; height: 200px"
 +
|-
 +
! scope="col" width="225px" style="background:#FFBF00"| '''Attribute'''
 +
!style="background:#FFBF00"| '''Attribute Description'''
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Identification'''
 +
|-
 +
| Term Name || filename
 +
|-
 +
| URI ||
 +
|-
 +
| Label || Filename
 +
|-
 +
| Defined by || AAFC-AAC
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Definition'''
 +
|-
 +
| Type of term || Property
 +
|-
 +
| Definition || The file name is the specific file or folder where the record resides.
 +
|-
 +
| Comment ||
 +
|-
 +
| References ||
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Relations'''
 +
|-
 +
| Encoding Scheme ||
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Constraints'''
 +
|-
 +
| Obligation || Mandatory
 +
|-
 +
| Metadata Type || System
 +
|-
 +
| Entry Type || Auto-populated
 +
|-
 +
| Occurrence || Not repeatable
 +
|-
 +
| Current Use || In Use
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Guidance'''
 +
|-
 +
| Explanation of Usage || '''Why to Use'''
 +
The Filename is important for system-related issues, identification and navigation.
  
 +
'''How to Use'''
  
 
 
 
4.27 Filename
 
Attribute Attribute Description
 
Identification
 
Term Name filename
 
URI
 
Label Filename
 
Defined by AAFC-AAC
 
Definition
 
Type of term Property
 
Definition The file name is the specific file or folder where the record resides.
 
Comment
 
References
 
Relations
 
Encoding Scheme
 
Constraints
 
Obligation Mandatory
 
Metadata Type System
 
Entry Type Auto-populated
 
 
Occurrence Not repeatable
 
Current Use In Use
 
Guidance
 
Explanation of Usage Why to Use
 
The Filename is important for system-related issues, identification and navigation.
 
 
How to Use
 
 
The field is auto-populated. It cannot be modified once the record is created.
 
The field is auto-populated. It cannot be modified once the record is created.
Example of HTML Syntax Not applicable
+
|-
 
+
| Example of HTML Syntax || Not applicable
 
+
|}
  
  
 +
===Format===
  
 +
{| class="wikitable" style="width: 100%; height: 200px"
 +
|-
 +
! scope="col" width="225px" style="background:#FFBF00"| '''Attribute'''
 +
!style="background:#FFBF00"| '''Attribute Description'''
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Identification'''
 +
|-
 +
| Term Name || format
 +
|-
 +
| URI || http://purl.org/dc/elements/1.1/format
 +
|-
 +
| Label || Format
 +
|-
 +
| Defined by || DCMI Metadata Terms
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Definition'''
 +
|-
 +
| Type of term || Property
 +
|-
 +
| Definition || The physical or digital manifestation of the resource.
 +
|-
 +
| Comment ||
 +
|-
 +
| References ||
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Relations'''
 +
|-
 +
| Encoding Scheme || Government of Canada Format Scheme (gcformat) http://www.collectionscanada.gc.ca/webarchives/20071120030246/www.tbs-sct.gc.ca/im-gi/mwg-gtm/fmt-fmt/docs/2003/schem_e.asp
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Constraints'''
 +
|-
 +
| Obligation || Mandatory
 +
|-
 +
| Metadata Type || Descriptive
 +
|-
 +
| Entry Type || Auto-populated
 +
|-
 +
| Occurrence || Not repeatable
 +
|-
 +
| Current Use || In Use
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Guidance'''
 +
|-
 +
| Explanation of Usage || '''Why to Use'''
 +
This attribute is used to describe the media-type to determine software, hardware or other equipment needed to display or operate the resource.  Examples of dimensions include size and duration.
  
 +
'''How to Use'''
  
 
 
 
 
 
 
 
 
 
4.28 Format
 
Attribute Attribute Description
 
Identification
 
Term Name format
 
URI http://purl.org/dc/elements/1.1/format
 
 
Label Format
 
Defined by DCMI Metadata Terms
 
Definition
 
Type of term Property
 
Definition The physical or digital manifestation of the resource. 
 
Comment
 
References
 
Relations
 
Encoding Scheme Government of Canada Format Scheme (gcformat) http://www.collectionscanada.gc.ca/webarchives/20071120030246/www.tbs-sct.gc.ca/im-gi/mwg-gtm/fmt-fmt/docs/2003/schem_e.asp
 
 
Constraints
 
Obligation Mandatory
 
Metadata Type Descriptive
 
Entry Type Auto-populated
 
Occurrence Not repeatable
 
Current Use In use
 
Guidance
 
Explanation of Usage Why to Use
 
This attribute is used to describe the media-type to determine software, hardware or other equipment needed to display or operate the resource.  Examples of dimensions include size and duration.
 
 
How to Use
 
 
The field is auto-populated. It cannot be modified once the record is created. All resources should be described using a “type/sub-type” designation. Terms must be selected from a registered controlled vocabulary. If you require additional Internet Media Types (MIME) types, you can add them to your list of terms but it is recommend that you notify the authority for the gcformat scheme as identified in the IMRC – dc.format Guidelines in order that terms can be added to the formal GC scheme if they represent common needs.
 
The field is auto-populated. It cannot be modified once the record is created. All resources should be described using a “type/sub-type” designation. Terms must be selected from a registered controlled vocabulary. If you require additional Internet Media Types (MIME) types, you can add them to your list of terms but it is recommend that you notify the authority for the gcformat scheme as identified in the IMRC – dc.format Guidelines in order that terms can be added to the formal GC scheme if they represent common needs.
Example of HTML Syntax <meta name="dcterms.format" title="gcformat" content="text/html" />
+
|-
 +
| Example of HTML Syntax || <meta name="<font color="red">dcterms.format</font>" <font color="red">title</font>="gcformat" content="text/html" />
 +
|}
  
  
 +
===Identifier===
  
 +
{| class="wikitable" style="width: 100%; height: 200px"
 +
|-
 +
! scope="col" width="225px" style="background:#FFBF00"| '''Attribute'''
 +
!style="background:#FFBF00"| '''Attribute Description'''
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Identification'''
 +
|-
 +
| Term Name || identifier
 +
|-
 +
| URI ||
 +
|-
 +
| Label || Identifier
 +
|-
 +
| Defined by || AAFC-AAC
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Definition'''
 +
|-
 +
| Type of term || Property
 +
|-
 +
| Definition || An unambiguous reference to the resource within a given context.
 +
|-
 +
| Comment || Represented as a series of numbers.
 +
|-
 +
| References ||
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Relations'''
 +
|-
 +
| Encoding Scheme ||
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Constraints'''
 +
|-
 +
| Obligation || Mandatory
 +
|-
 +
| Metadata Type || Administrative
 +
|-
 +
| Entry Type || Auto-populated
 +
|-
 +
| Occurrence || Not repeatable
 +
|-
 +
| Current Use || In Use 
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Guidance'''
 +
|-
 +
| Explanation of Usage || '''Why to Use'''
 +
The identifier is used for identification purposes. It appears as part of the URL for the record’s web page.
  
 +
'''How to Use'''
  
4.29 Identifier
 
Attribute Attribute Description
 
Identification
 
Term Name identifier
 
URI
 
Label Identifier
 
Defined by AAFC-AAC
 
Definition
 
Type of term Property
 
Definition An unambiguous reference to the resource within a given context.
 
Comment Represented as a series of numbers.
 
References
 
Relations
 
Encoding Scheme
 
Constraints
 
Obligation Mandatory
 
Metadata Type Administrative
 
Entry Type Auto-populated
 
Occurrence Not repeatable
 
Current Use In Use
 
Guidance
 
Explanation of Usage Why to Use
 
The identifier is used for identification purposes. It appears as part of the URL for the record’s web page.
 
 
How to Use
 
 
The field is auto-populated.  
 
The field is auto-populated.  
Example of HTML Syntax Not applicable
+
|-
 
+
| Example of HTML Syntax || Not applicable
 
+
|}
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
  
  
 +
===Keywords===
  
 
+
{| class="wikitable" style="width: 100%; height: 200px"
4.30 Keywords
+
|-
Attribute Attribute Description
+
! scope="col" width="225px" style="background:#FFBF00"| '''Attribute'''
Identification
+
!style="background:#FFBF00"| '''Attribute Description'''
Term Name keywords
+
|-
URI
+
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Identification'''
Label Keywords
+
|-
Defined by
+
| Term Name || keywords
Definition
+
|-
Type of term Property
+
| URI ||
Definition A word or phrase describing the content of the resource and not found in one of the subject controlled vocabularies.
+
|-
Comment To provide content owners the opportunity to include free text information that is not represented in the controlled vocabulary.  
+
| Label || Keywords
References
+
|-
Relations
+
| Defined by || AAFC-AAC
Encoding Scheme
+
|-
Constraints
+
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Definition'''
Obligation Optional  
+
|-
Metadata Type Descriptive
+
| Type of term || Property  
Entry Type Auto-populated
+
|-
 +
| Definition || A word or phrase describing the content of the resource and not found in one of the subject controlled vocabularies.
 +
|-
 +
| Comment || To provide content owners the opportunity to include free text information that is not represented in the controlled vocabulary.
 +
|-
 +
| References ||
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Relations'''
 +
|-
 +
| Encoding Scheme ||
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Constraints'''
 +
|-
 +
| Obligation || Optional  
 +
|-
 +
| Metadata Type || Descriptive
 +
|-
 +
| Entry Type || <font color="red">Auto-populated  
 
Note: The field is autopopulated by Metatagger, and then verified by the Metadata Analysts
 
Note: The field is autopopulated by Metatagger, and then verified by the Metadata Analysts
Occurrence Not repeatable
+
</font>
Current Use In Use  
+
|-
Guidance
+
| Occurrence || Not repeatable
Explanation of Usage Why to Use
+
|-
 +
| Current Use || In Use  
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Guidance'''
 +
|-
 +
| Explanation of Usage || '''Why to Use'''
 
Keywords are useful for providing additional terms for the user. It may serve as another access point for search engines.  
 
Keywords are useful for providing additional terms for the user. It may serve as another access point for search engines.  
  
How to Use
+
'''How to Use'''
 +
 
 
Add acronyms, publication numbers, cataloguing or report numbers, phrases and frequently used words or terms by which users commonly access the resource. Between each word provide a comma (,) and then a space. For the Keywords field, up to 2000 characters is allowed. The field can be auto-populated, but also allows user entry.
 
Add acronyms, publication numbers, cataloguing or report numbers, phrases and frequently used words or terms by which users commonly access the resource. Between each word provide a comma (,) and then a space. For the Keywords field, up to 2000 characters is allowed. The field can be auto-populated, but also allows user entry.
  
 
Tips for selecting keywords
 
Tips for selecting keywords
  
Add common words to scientific terms or vice versa when not in a controlled vocabulary.  
+
* Add common words to scientific terms or vice versa when not in a controlled vocabulary.  
Use keywords only if no terms adequately describe the resource from the list of the subjects  
+
* Use keywords only if no terms adequately describe the resource from the list of the subjects  
Select keywords that capture the most unique characteristics of the resource.
+
* Select keywords that capture the most unique characteristics of the resource.
Example of HTML Syntax <meta name=”keywords” content =”mad cow disease”>
+
|-
 +
| Example of HTML Syntax || <meta name=”keywords” content =”mad cow disease”>
 +
|}
  
  
 +
===Language===
  
 +
{| class="wikitable" style="width: 100%; height: 200px"
 +
|-
 +
! scope="col" width="225px" style="background:#FFBF00"| '''Attribute'''
 +
!style="background:#FFBF00"| '''Attribute Description'''
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Identification'''
 +
|-
 +
| Term Name || language
 +
|-
 +
| URI || http://purl.org/dc/elements/1.1/language
 +
|-
 +
| Label || Language
 +
|-
 +
| Defined by || DCMI Metadata Terms
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Definition'''
 +
|-
 +
| Type of term || Property
 +
|-
 +
| Definition || The language of the intellectual content of the resource.
 +
|-
 +
| Comment || To identify the language(s) of this resource for the purpose of application processing (accessibility, search, workflow, etc.).
 +
|-
 +
| References ||
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Relations'''
 +
|-
 +
| Encoding Scheme || ISO 639.2/T Codes for the Representation of Names of Languages http://lcweb.loc.gov/standards/iso639-2/langhome.html
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Constraints'''
 +
|-
 +
| Obligation || Mandatory 
 +
|-
 +
| Metadata Type || Administrative
 +
|-
 +
| Entry Type || Auto-populated
 +
Note: The field is autopopulated by Metatagger, and then verified by the Metadata Analysts
 +
|-
 +
| Occurrence || Not repeatable
 +
|-
 +
| Current Use || In Use
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Guidance'''
 +
|-
 +
| Explanation of Usage || '''Why to Use'''
 +
It is used to identify the language of the intellectual content of a resource. This attribute must be expressed in the HTML <Header> to comply with the Standard on Metadata.
  
 +
'''How to Use'''
  
4.31 Language
 
Attribute Attribute Description
 
Identification
 
Term Name language
 
URI http://purl.org/dc/elements/1.1/language
 
 
Label Language
 
Defined by DCMI Metadata Terms
 
Definition
 
Type of term Property
 
Definition The language of the intellectual content of the resource.
 
Comment To identify the language(s) of this resource for the purpose of application processing (accessibility, search, workflow, etc.).
 
References
 
Relations
 
Encoding Scheme ISO 639.2/T Codes for the Representation of Names of Languages http://lcweb.loc.gov/standards/iso639-2/langhome.html
 
 
Constraints
 
Obligation Mandatory
 
Metadata Type Administrative
 
Entry Type Auto-populated
 
Occurrence Not repeatable
 
Current Use In Use
 
Guidance
 
Explanation of Usage Why to Use
 
It is used to identify the language of the intellectual content of a resource. This attribute must be expressed in the HTML <Header> to comply with the Standard on Metadata.
 
 
How to Use
 
 
The field is auto-populated. It cannot be modified once the record is created.
 
The field is auto-populated. It cannot be modified once the record is created.
Example of HTML Syntax <meta name="dcterms.language" title ="ISO639-2" content="eng">
+
|-
<meta name=”dcterms.language” title =”ISO639-2” content=”fra”>
+
| Example of HTML Syntax || <<meta name="<font color="red">dcterms.language</font>" <font color="red">title</font> ="ISO639-2" content="eng">
 
+
<meta name="<font color="red">dcterms.language</font>" <font color="red">title</font> ="ISO639-2" content="fra">
 +
|}
  
  
 +
===Next Review Period===
  
 
+
{| class="wikitable" style="width: 100%; height: 200px"
 
+
|-
 
+
! scope="col" width="225px" style="background:#FFBF00"| '''Attribute'''
 
+
!style="background:#FFBF00"| '''Attribute Description'''
 
+
|-
 
+
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Identification'''
 
+
|-
4.32 Next Review Period
+
| Term Name || nextReviewPeriod
Attribute Attribute Description
+
|-
Identification
+
| URI ||
Term Name nextReviewPeriod
+
|-
URI
+
| Label || Next Review Period
Label Next Review Period
+
|-
Defined by AAFC-AAC
+
| Defined by || AAFC-AAC
Definition
+
|-
Type of term Property
+
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Definition'''
Definition The period representing the end at which time the content must be reviewed for accuracy, relevance, correctness, intellectual applicability, etc. Relates to the life-cycle management of content.
+
|-
Comment To indicate the period for which content has relevance.
+
| Type of term || Property  
References
+
|-
Relations
+
| Definition || The period representing the end at which time the content must be reviewed for accuracy, relevance, correctness, intellectual applicability, etc. Relates to the life-cycle management of content.
Encoding Scheme W3CDTF   
+
|-
 +
| Comment || To indicate the period for which content has relevance.
 +
|-
 +
| References ||
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Relations'''
 +
|-
 +
| Encoding Scheme || W3CDTF   
 
http://www.w3.org/TR/NOTE-datetime  
 
http://www.w3.org/TR/NOTE-datetime  
 
+
|-
Constraints
+
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Constraints'''
Obligation Mandatory  
+
|-
Metadata Type Administrative
+
| Obligation || Mandatory
Entry Type User entry  
+
|-
Note: The user may select from a drop down list the number of months until the next review period. If the user does not choose, the default is ‘12’ months.  
+
| Metadata Type || Administrative
Occurrence Not repeatable
+
|-
Current Use In Use  
+
| Entry Type || User entry  
Guidance
+
Note: The user may select from a drop down list the number of months until the next review period. If the user does not choose, the default is ‘12’ months.
Explanation of Usage Why to Use
+
|-
 +
| Occurrence || Not repeatable
 +
|-
 +
| Current Use || In Use  
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Guidance'''
 +
|-
 +
| Explanation of Usage || '''Why to Use'''
 
This attribute is used to identify the period of time when a resource should be reviewed for relevance from a legal, service delivery perspective, or intellectual content perspective (e.g., a policy, program or service is applicable).   
 
This attribute is used to identify the period of time when a resource should be reviewed for relevance from a legal, service delivery perspective, or intellectual content perspective (e.g., a policy, program or service is applicable).   
  
How to Use
+
'''How to Use'''
The user may select the appropriate time frame for the resource up to 36 months. If they do not choose a value, then the default value, 12 months, will be provided. 
 
Example of HTML Syntax Not applicable
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
4.33 Presentation
 
Attribute Attribute Description
 
Identification
 
Term Name presentation
 
URI
 
Label Presentation
 
Defined by AAFC-AAC
 
Definition
 
Type of term Property
 
Definition The presentation layer value indicates how the page is rendered at the front end.
 
Comment
 
References
 
Relations
 
Encoding Scheme
 
Constraints
 
Obligation Mandatory
 
Metadata Type System
 
Entry Type Auto-populated
 
Occurrence Not repeatable
 
Current Use In Use
 
Guidance
 
Explanation of Usage Why to Use
 
This attribute is used by the presentation layer when rendering pages.
 
 
 
How to Use
 
The field is auto-populated. When the DCR is first created, the value 1 or 0 will be chosen.
 
Example of HTML Syntax Not applicable
 
 
 
 
 
 
 
  
 +
The user may select the appropriate time frame for the resource up to 36 months. If they do not choose a value, then the default value, 12 months, will be provided.
 +
|-
 +
| Example of HTML Syntax || Not applicable
 +
|}
  
  
 +
===Presentation===
  
 +
{| class="wikitable" style="width: 100%; height: 200px"
 +
|-
 +
! scope="col" width="225px" style="background:#FFBF00"| '''Attribute'''
 +
!style="background:#FFBF00"| '''Attribute Description'''
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Identification'''
 +
|-
 +
| Term Name || presentation
 +
|-
 +
| URI ||
 +
|-
 +
| Label || Presentation
 +
|-
 +
| Defined by || AAFC-AAC
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Definition'''
 +
|-
 +
| Type of term || Property
 +
|-
 +
| Definition || The presentation layer value indicates how the page is rendered at the front end.
 +
|-
 +
| Comment ||
 +
|-
 +
| References ||
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Relations'''
 +
|-
 +
| Encoding Scheme ||
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Constraints'''
 +
|-
 +
| Obligation || Mandatory 
 +
|-
 +
| Metadata Type || System
 +
|-
 +
| Entry Type || Auto-populated
 +
|-
 +
| Occurrence || Not repeatable
 +
|-
 +
| Current Use || In Use
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Guidance'''
 +
|-
 +
| Explanation of Usage || '''Why to Use'''
 +
This attribute is used by the presentation layer when rendering pages. 
  
 +
'''How to Use'''
  
 +
The field is auto-populated. When the DCR is first created, the value 1 or 0 will be chosen.
 +
|-
 +
| Example of HTML Syntax || Not applicable
 +
|}
  
  
 +
===Subject (aafccore)===
  
 +
{| class="wikitable" style="width: 100%; height: 200px"
 +
|-
 +
! scope="col" width="225px" style="background:#FFBF00"| '''Attribute'''
 +
!style="background:#FFBF00"| '''Attribute Description'''
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Identification'''
 +
|-
 +
| Term Name || aafcSubject
 +
|-
 +
| URI || http://purl.org/dc/elements/1.1/subject
 +
|-
 +
| Label || Subject (aafccore)
 +
|-
 +
| Defined by || DCMI Metadata Terms
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Definition'''
 +
|-
 +
| Type of term || Property
 +
|-
 +
| Definition || The topic of the resource.
 +
|-
 +
| Comment ||
 +
|-
 +
| References || AgriDoc #384444
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Relations'''
 +
|-
 +
| Encoding Scheme || Agriculture and Agri-Food Canada Subject Taxonomy (aafcsubject)
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Constraints'''
 +
|-
 +
| Obligation || Mandatory 
 +
|-
 +
| Metadata Type || Descriptive
 +
|-
 +
| Entry Type || Auto-populated
 +
Note: The field is populated by Metatagger, and then verified.
 +
|-
 +
| Occurrence || Not repeatable
 +
|-
 +
| Current Use || In Use
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Guidance'''
 +
|-
 +
| Explanation of Usage || '''Why to Use'''
 +
It is used to describe what the content of this resource is about through the use of controlled terms. The AAFC subject values (aafcsubject) provide more granular, precise description of AAFC’s business and operational activities than the Government of Canada Core Subject Thesaurus (gccore). This attribute must be expressed in the HTML <Header> to comply with the [http://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=18909&section=text Standard on Metadata].
  
 +
'''How to Use'''
  
 
 
4.34 Subject (aafccore)
 
Attribute Attribute Description
 
Identification
 
Term Name aafcSubject
 
URI http://purl.org/dc/elements/1.1/subject
 
 
Label Subject (aafccore)
 
Defined by DCMI Metadata Terms
 
Definition
 
Type of term Property
 
Definition The topic of the resource.
 
Comment
 
References AgriDoc #384444
 
Relations
 
Encoding Scheme Agriculture and Agri-Food Canada Subject Taxonomy (aafcsubject)
 
 
Constraints
 
Obligation Mandatory
 
Metadata Type Descriptive
 
Entry Type Auto-populated
 
Note: The field is populated by Metatagger, and then verified.
 
Occurrence Not repeatable
 
Current Use In Use
 
Guidance
 
Explanation of Usage Why to Use
 
It is used to describe what the content of this resource is about through the use of controlled terms. The AAFC subject values (aafcsubject) provide more granular, precise description of AAFC’s business and operational activities than the Government of Canada Core Subject Thesaurus (gccore). This attribute must be expressed in the HTML <Header> to comply with the Standard on Metadata.
 
 
How to Use
 
 
Select terms that represent the concept of the web page. The field can be auto-populated, but also allows user entry.
 
Select terms that represent the concept of the web page. The field can be auto-populated, but also allows user entry.
 
+
|-
Example of HTML Syntax <meta name="aafc.subject" title="aafcsubject" content="rural development;agricultural economics" />
+
| Example of HTML Syntax || <meta name="aafc.subject" <font color="red">title</font>="aafcsubject" content="rural development;agricultural economics" />
 
+
|}
 
 
  
  
 +
===Subject (gccore)===
  
 
+
{| class="wikitable" style="width: 100%; height: 200px"
 
+
|-
 
+
! scope="col" width="225px" style="background:#FFBF00"| '''Attribute'''
 
+
!style="background:#FFBF00"| '''Attribute Description'''
4.35 Subject (gccore)
+
|-
Attribute Attribute Description
+
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Identification'''
Identification
+
|-
Term Name subject
+
| Term Name || subject
URI http://purl.org/dc/elements/1.1/subject  
+
|-
 
+
| URI || http://purl.org/dc/elements/1.1/subject  
Label Subject (gccore)
+
|-
Defined by DCMI Metadata Terms
+
| Label || Subject (gccore)
 
+
|-
Definition
+
| Defined by || DCMI Metadata Terms
Type of term Property
+
|-
Definition The topic of the resource.  
+
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Definition'''
Comment This attribute is meant to standardize subject values across government departments and will enhance GC Canada site search.
+
|-
References
+
| Type of term || Property  
Relations
+
|-
Encoding Scheme Government of Canada Core Subject Thesaurus (gccore)
+
| Definition || The topic of the resource.
 +
|-
 +
| Comment || This attribute is meant to standardize subject values across government departments and will enhance GC Canada site search.
 +
|-
 +
| References ||
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Relations'''
 +
|-
 +
| Encoding Scheme || Government of Canada Core Subject Thesaurus (gccore)
 
http://www.thesaurus.gc.ca/recherche-search/thes-eng.html
 
http://www.thesaurus.gc.ca/recherche-search/thes-eng.html
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Constraints'''
 +
|-
 +
| Obligation || Mandatory 
 +
|-
 +
| Metadata Type || Descriptive
 +
|-
 +
| Entry Type || Auto-populated
 +
Note: The field is populated by Metatagger, and then verified.
 +
|-
 +
| Occurrence || Not repeatable
 +
|-
 +
| Current Use || In Use
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Guidance'''
 +
|-
 +
| Explanation of Usage || '''Why to Use'''
 +
It is used to describe what the content of this resource is about through the use of controlled terms. Gccore values represent subjects at a higher level than values selected from aafccore. This attribute must be expressed in the HTML <Header> to comply with the [http://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=18909&section=text Standard on Metadata].
  
Constraints
+
'''How to Use'''
Obligation Mandatory
 
Metadata Type Descriptive
 
Entry Type Auto-populated
 
Note: The field is populated by Metatagger, and then verified.
 
Occurrence Not repeatable
 
Current Use In Use
 
Guidance
 
Explanation of Usage Why to Use
 
It is used to describe what the content of this resource is about through the use of controlled terms. Gccore values represent subjects at a higher level than values selected from aafccore. This attribute must be expressed in the HTML <Header> to comply with the Standard on Metadata.
 
  
How to Use
 
 
Select terms that represent the concept of the web page. The field can be auto-populated, but also allows user entry.
 
Select terms that represent the concept of the web page. The field can be auto-populated, but also allows user entry.
 +
|-
 +
| Example of HTML Syntax || <meta name= “<font color="red">dcterms.subject</font>” <font color="red">title</font>= “gccore” content= “agriculture”>
 +
|}
  
Example of HTML Syntax <meta name= “dcterms.subject” title= “gccore” content= “agriculture”>
 
 
 
 
 
 
 
 
 
4.36 Title
 
Attribute Attribute Description
 
Identification
 
Term Name title
 
URI http://purl.org/dc/elements/1.1/title
 
  
Label Title
+
===Title===
Defined by DCMI Metadata Terms
 
Definition
 
Type of term Property
 
Definition A name given to the resource.
 
Comment
 
References
 
Relations
 
Encoding Scheme
 
  
Constraints
+
{| class="wikitable" style="width: 100%; height: 200px"
Obligation Mandatory  
+
|-
Metadata Type Administrative
+
! scope="col" width="225px" style="background:#FFBF00"| '''Attribute'''
 +
!style="background:#FFBF00"| '''Attribute Description'''
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Identification'''
 +
|-
 +
| Term Name || title
 +
|-
 +
| URI || http://purl.org/dc/elements/1.1/title
 +
|-
 +
| Label || Title
 +
|-
 +
| Defined by || DCMI Metadata Terms
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Definition'''
 +
|-
 +
| Type of term || Property
 +
|-
 +
| Definition || A name given to the resource.
 +
|-
 +
| Comment ||
 +
|-
 +
| References ||
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Relations'''
 +
|-
 +
| Encoding Scheme ||
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Constraints'''
 +
|-
 +
| Obligation || Mandatory
 +
|-
 +
| Metadata Type || Administrative
 +
|-
 +
| Entry Type || Auto-populated (for CMI) and User entry (for all other users)
 +
|-
 +
| Occurrence || Not repeatable
 +
|-
 +
| Current Use || In Use
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Guidance'''
 +
|-
 +
| Explanation of Usage || '''Why to Use'''
 +
The Title is the official name of the resource and is used to help distinguish one resource from another. Meaningful titles should be assigned for accessibility, speed of identification, and to facilitate control. This attribute must be expressed in the HTML <Header> to comply with the [http://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=18909&section=text Standard on Metadata].
 +
.
  
Entry Type Auto-populated (for CMI) and User entry (for all other users)
+
'''How to Use'''
Occurrence Not repeatable
 
Current Use In Use
 
Guidance
 
Explanation of Usage Why to Use
 
The Title is the official name of the resource and is used to help distinguish one resource from another. Meaningful titles should be assigned for accessibility, speed of identification, and to facilitate control. This attribute must be expressed in the HTML <Header> to comply with the Standard on Metadata.
 
  
How to Use
 
 
For CMI (Programs and Services), the title is the Program Name, and it is auto-populated. For all other users, the title is manually entered. For the Title field, up to 2000 characters are allowed. Use a hyphen [–] preceded and followed by space as the separator when adding additional contextual information to a resource title unless this will cause confusion for persons reading the title. Spell out acronyms and abbreviations.  
 
For CMI (Programs and Services), the title is the Program Name, and it is auto-populated. For all other users, the title is manually entered. For the Title field, up to 2000 characters are allowed. Use a hyphen [–] preceded and followed by space as the separator when adding additional contextual information to a resource title unless this will cause confusion for persons reading the title. Spell out acronyms and abbreviations.  
Example of HTML Syntax <meta name="dcterms.title" content="Pulses and Special Crops" />
+
|-
 +
| Example of HTML Syntax || <meta name="<font color="red">dcterms.title</font>" <font color="red">content</font>="Pulses and Special Crops" />
 +
|}
  
  
 +
===Type===
  
 +
{| class="wikitable" style="width: 100%; height: 200px"
 +
|-
 +
! scope="col" width="225px" style="background:#FFBF00"| '''Attribute'''
 +
!style="background:#FFBF00"| '''Attribute Description'''
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Identification'''
 +
|-
 +
| Term Name || type
 +
|-
 +
| URI || http://purl.org/dc/elements/1.1/type
 +
|-
 +
| Label || Type
 +
|-
 +
| Defined by || DCMI Metadata Terms
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Definition'''
 +
|-
 +
| Type of term || Property
 +
|-
 +
| Definition || The nature or genre of the content of the resource.
 +
|-
 +
| Comment || To provide additional information about the purpose of this resource to assist with information management and resource discovery.
 +
To assist users in interpreting information contained in this resource by indentifying its internal structure.
 +
|-
 +
| References || AgriDoc #384444
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Relations'''
 +
|-
 +
| Encoding Scheme || <font color="red">AAFC Type Scheme (aafc.type)</font>
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Constraints'''
 +
|-
 +
| Obligation || Mandatory 
 +
|-
 +
| Metadata Type || Descriptive
 +
|-
 +
| Entry Type || Auto-populated
 +
Note: The field is populated by Metatagger, and then verified.
 +
|-
 +
| Occurrence || Not repeatable
 +
|-
 +
| Current Use || In Use
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Guidance'''
 +
|-
 +
| Explanation of Usage || '''Why to Use'''
 +
This attribute is useful in understanding the purpose or function of the record and it provides indications as to the internal structure of a resource's content. It is used for categorizing content by type, e.g. policy, abstract, presentation.
  
 +
'''How to Use'''
  
 
 
 
4.37 Type
 
Attribute Attribute Description
 
Identification
 
Term Name type
 
URI http://purl.org/dc/elements/1.1/type
 
 
Label Type
 
Defined by DCMI Metadata Terms
 
Definition
 
Type of term Property
 
Definition The nature or genre of the content of the resource.
 
Comment To provide additional information about the purpose of this resource to assist with information management and resource discovery.
 
To assist users in interpreting information contained in this resource by identifying its internal structure.
 
References AgriDoc #384444
 
Relations
 
Encoding Scheme AAFC Type Scheme (aafc.type)
 
Constraints
 
Obligation Mandatory
 
Metadata Type Descriptive
 
 
Entry Type Auto-populated
 
Note: The field is populated by Metatagger, and then verified.
 
Occurrence Not repeatable
 
Current Use In Use
 
Guidance
 
Explanation of Usage Why to Use
 
This attribute is useful in understanding the purpose or function of the record and it provides indications as to the internal structure of a resource's content. It is used for categorizing content by type, e.g. policy, abstract, presentation.
 
 
How to Use
 
 
Select a term that represents the concept of the web page. There can only be one type selected. The field can be auto-populated, but also allows user entry.
 
Select a term that represents the concept of the web page. There can only be one type selected. The field can be auto-populated, but also allows user entry.
 +
|-
 +
| Example of HTML Syntax || <meta name="<font color="red">dcterms.type</font>" <font color="red">title</font>="<font color="red">aafctype</font>" content="contact information" />
 +
|}
  
Example of HTML Syntax <meta name="dcterms.type" title="aafctype" content="contact information" />
 
  
 +
===Valid Date===
  
 
+
{| class="wikitable" style="width: 100%; height: 200px"
 
+
|-
 
+
! scope="col" width="225px" style="background:#FFBF00"| '''Attribute'''
 
+
!style="background:#FFBF00"| '''Attribute Description'''
 
+
|-
4.38 Valid Date
+
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Identification'''
Attribute Attribute Description
+
|-
Identification
+
| Term Name || dateValid
Term Name dateValid
+
|-
URI
+
| URI ||
Label Valid Date
+
|-
Defined by Government of Canada Web Content Management System – Metadata Element Set
+
| Label || Valid Date
Definition
+
|-
Type of term Property
+
| Defined by || Government of Canada Web Content Management System – Metadata Element Set
Definition The end date of the date range representing the applicability for intellectual or legal relevance e.g., the end date on which a policy, program or service is applicable.
+
|-
Comment To indicate the last date on which this resource has relevance.
+
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Definition'''
References
+
|-
Relations
+
| Type of term || Property  
Encoding Scheme W3CDTF   
+
|-
 +
| Definition || The end date of the date range representing the applicability for intellectual or legal relevance e.g., the end date on which a policy, program or service is applicable.
 +
|-
 +
| Comment || To indicate the last date on which this resource has relevance.
 +
|-
 +
| References ||
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Relations'''
 +
|-
 +
| Encoding Scheme || W3CDTF   
 
http://www.w3.org/TR/NOTE-datetime
 
http://www.w3.org/TR/NOTE-datetime
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Constraints'''
 +
|-
 +
| Obligation || Optional 
 +
|-
 +
| Metadata Type || Administrative
 +
|-
 +
| Entry Type || User entry
 +
|-
 +
| Occurrence || Not repeatable
 +
|-
 +
| Current Use || Not in use
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Guidance'''
 +
|-
 +
| Explanation of Usage || '''Why to Use'''
 +
Use this attribute to identify when a resource will stop being relevant from a legal or service delivery perspective (e.g. a policy or service is applicable). The resources are still made available on the web site even though the content of the resource is no longer valid (e.g., for “sun-setting” programs and services, resources might still be available to the public as information that such a program or service was available but the program no longer is).
  
Constraints
+
'''How to Use'''
Obligation Optional
 
Metadata Type Administrative
 
Entry Type User entry
 
Occurrence Not repeatable
 
Current Use Not in use
 
Guidance
 
Explanation of Usage Why to Use
 
Use this attribute to identify when a resource will stop being relevant from a legal or service delivery perspective (e.g. a policy or service is applicable). The resources are still made available on the web site even though the content of the resource is no longer valid (e.g., for “sun-setting” programs and services, resources might still be available to the public as information that such a program or service was available but the program no longer is).
 
  
How to Use
 
 
Valid Date is manually edited. All dates must be entered in the form YYYY-MM-DD, as specified by ISO 8601. There is a calendar option available to use when entering the date.
 
Valid Date is manually edited. All dates must be entered in the form YYYY-MM-DD, as specified by ISO 8601. There is a calendar option available to use when entering the date.
Example of HTML Syntax Not applicable  
+
|-
 +
| Example of HTML Syntax || Not applicable  
 +
|}
  
  
 +
===vpath===
  
 +
{| class="wikitable" style="width: 100%; height: 200px"
 +
|-
 +
! scope="col" width="225px" style="background:#FFBF00"| '''Attribute'''
 +
!style="background:#FFBF00"| '''Attribute Description'''
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Identification'''
 +
|-
 +
| Term Name || vpath
 +
|-
 +
| URI ||
 +
|-
 +
| Label || Valid Date
 +
|-
 +
| Defined by || AAFC-AAC
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Definition'''
 +
|-
 +
| Type of term || Property
 +
|-
 +
| Definition || A reference to a group of related resources by an identifier assigned within the CMS providing a pathway to a specific record.
 +
|-
 +
| Comment ||
 +
|-
 +
| References ||
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Relations'''
 +
|-
 +
| Encoding Scheme ||
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Constraints'''
 +
|-
 +
| Obligation || Mandatory 
 +
|-
 +
| Metadata Type || System
 +
|-
 +
| Entry Type || Auto-populated
 +
|-
 +
| Occurrence || Not repeatable
 +
|-
 +
| Current Use || In Use
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Guidance'''
 +
|-
 +
| Explanation of Usage || '''Why to Use'''
 +
The vpath is important for system-related issues and identification.
  
 +
'''How to Use'''
  
 
 
 
 
 
 
 
 
4.39 vpath
 
Attribute Attribute Description
 
Identification
 
Term Name vpath
 
URI
 
Label vpath
 
Defined by AAFC-AAC
 
Definition
 
Type of term Property
 
Definition A reference to a group of related resources by an identifier assigned within the CMS providing a pathway to a specific record.
 
Comment
 
References
 
Relations
 
Encoding Scheme
 
Constraints
 
Obligation Mandatory
 
Metadata Type System
 
Entry Type Auto-populated
 
Occurrence Not repeatable
 
Current Use In Use
 
Guidance
 
Explanation of Usage Why to Use
 
The vpath is important for system-related issues and identification.
 
 
How to Use
 
 
The field is auto-populated. It cannot be modified by the user.
 
The field is auto-populated. It cannot be modified by the user.
Example of HTML Syntax Not applicable
+
|-
 
+
| Example of HTML Syntax || Not applicable  
 
+
|}
 
 
 
 
 
 
 
 
  
  
 +
===vpathprod===
  
 +
{| class="wikitable" style="width: 100%; height: 200px"
 +
|-
 +
! scope="col" width="225px" style="background:#FFBF00"| '''Attribute'''
 +
!style="background:#FFBF00"| '''Attribute Description'''
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Identification'''
 +
|-
 +
| Term Name || vpathprod
 +
|-
 +
| URI ||
 +
|-
 +
| Label || vpathprod
 +
|-
 +
| Defined by || AAFC-AAC
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Definition'''
 +
|-
 +
| Type of term || Property
 +
|-
 +
| Definition || A reference to a group of related resources providing the pathway to a specific record.
 +
|-
 +
| Comment ||
 +
|-
 +
| References ||
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Relations'''
 +
|-
 +
| Encoding Scheme ||
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Constraints'''
 +
|-
 +
| Obligation || Mandatory 
 +
|-
 +
| Metadata Type || System
 +
|-
 +
| Entry Type || Auto-populated
 +
|-
 +
| Occurrence || Not repeatable
 +
|-
 +
| Current Use || In Use
 +
|-
 +
| colspan="2" style="text-align: center; background: #BEBEBE" | '''Guidance'''
 +
|-
 +
| Explanation of Usage || '''Why to Use'''
 +
The vpathprod is important for system-related issues and identification.
  
 +
'''How to Use'''
  
 
 
 
 
 
 
4.40 vpathprod
 
Attribute Attribute Description
 
Identification
 
Term Name vpathprod
 
URI
 
Label vpathprod
 
Defined by AAFC-AAC
 
Definition
 
Type of term Property
 
Definition A reference to a group of related resources providing the pathway to a specific record.
 
Comment
 
References
 
Relations
 
Encoding Scheme
 
Constraints
 
Obligation Mandatory
 
Metadata Type System
 
Entry Type Auto-populated
 
Occurrence Not repeatable
 
Current Use In Use
 
Guidance
 
Explanation of Usage Why to Use
 
The vpathprod is important for system-related issues and identification.
 
 
How to Use
 
 
The field is auto-populated. It cannot be modified by the user.
 
The field is auto-populated. It cannot be modified by the user.
Example of HTML Syntax Not applicable  
+
|-
 
+
| Example of HTML Syntax || Not applicable  
 
+
|}
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
  
  
Appendix A – Reference
+
=='''Appendix A – Reference'''==
  
Metadata specifications
+
'''Metadata specifications'''
  
List of Controlled Vocabulary
+
''List of Controlled Vocabulary''<br />Agriculture and Agri-Food Canada (2007) – AgriDOC # 384444
Agriculture and Agri-Food Canada (2007) – AgriDOC # 384444
 
  
Content Management System specifications
+
'''Content Management System specifications'''
  
Web Content Management Solution (CMS) Project Charter
+
''Web Content Management Solution (CMS) Project Charter''<br />Agriculture and Agri-Food Canada (2006) – AgriDOC # 481534
Agriculture and Agri-Food Canada (2006) – AgriDOC # 481534
 
  
AAFC Web Renovation Information Architecture Principles
+
''AAFC Web Renovation Information Architecture Principles''<br />Agriculture and Agri-Food Canada, E-Communications Unit, CCT (2006) – AgriDOC #1790807
Agriculture and Agri-Food Canada, E-Communications Unit, CCT (2006) – AgriDOC #1790807
 
 
   
 
   
Other Metadata References
+
'''Other Metadata References'''
  
Government of Canada. (2007). Web Content Management System Metadata Element Set. http://www.gcpedia.gc.ca/gcwiki/images/9/9e/Web_Content_Management_System_Metadata_Element_Set.doc  
+
Government of Canada. (2007). ''Web Content Management System Metadata Element Set''<br />http://www.gcpedia.gc.ca/gcwiki/images/9/9e/Web_Content_Management_System_Metadata_Element_Set.doc  
  
Government of Canada. (2007). Web Content Management System Metadata Application Profile.
+
Government of Canada. (2007). ''Web Content Management System Metadata Application Profile''.<br />http://www.gcpedia.gc.ca/gcwiki/images/c/c7/Web_Content_Management_System_Metadata_Application_Profile.doc  
http://www.gcpedia.gc.ca/gcwiki/images/c/c7/Web_Content_Management_System_Metadata_Application_Profile.doc  
 
  
Treasury Board of Canada Secretariat. (2011). Government of Canada Metadata Implementation Guideline for Web Resource Discovery, 6th edition (Draft). http://www.gcpedia.gc.ca/gcwiki/images/2/23/MIG_6th_ed.doc
+
Treasury Board of Canada Secretariat. (2011). ''Government of Canada Metadata Implementation Guideline for Web Resource Discovery, 6th edition'' (Draft).<br />http://www.gcpedia.gc.ca/gcwiki/images/2/23/MIG_6th_ed.doc
  
Treasury Board of Canada Secretariat. (2010). Standard on Metadata. http://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=18909
+
Treasury Board of Canada Secretariat. (2010). ''Standard on Metadata''.<br />http://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=18909

Latest revision as of 13:09, 17 June 2013

Department of Agriculture and Agri-Food Editor: Patricia Redmond Patricia.Redmond@agr.gc.ca

Summary of Metadata Attribute Set

For these attributes, the entry type may be auto-populated for Programs and Services (CMI) and some groups, but user entry for other groups. The fields affected will have further specifications stated in 4.0.


Section Attribute Metadata Type Obligation Entry Type In Use
4.1 AAFC Collection Descriptive Mandatory Auto-pop & User Yes
4.2 AAFC Presentation Template Type Descriptive Mandatory Auto-pop & User Yes
4.3 AAFC Primary Lane Descriptive Mandatory Auto-pop & User Yes
4.4 Administrative Parent ID Administrative Optional


4.5 Audience Descriptive Optional User No


4.6 Content Coordinator Name Administrative Optional User No
4.7 Content Coordinator Name Administrative Optional User No
4.8 Content Coordinator Team Administrative Optional User No


4.9 Content Owner Name Administrative Optional User No
4.10 Content Owner Position / Title Administrative Optional User No
4.11 Content Owner Team Administrative Optional User No
4.12 Coverage (domestic) Descriptive Optional User No


4.13 Coverage (international) Descriptive Optional User No


4.14 Creator Administrator Mandatory Auto-pop & User Yes
4.15 Date for Review Administrative Mandatory User Yes
4.16 Date Issued Admistrative Mandatory Auto-pop Yes
4.17 Date Last Updated Admistrative Mandatory Auto-pop Yes
4.18 Date Modified Administrative Mandatory Auto-pop & User Yes
4.19 Date Reviewed Admistrative Optional User Yes
4.20 DCR Name System Mandatory Auto-pop Yes
4.21 DCR Type System Mandatory Auto-pop Yes
4.22 Delegate of Responsibility Name Administrative Optional User No
4.23 Delegate of Responsibility Position Administrative Optional User No
4.24 Delegate of Responsibility Team Administrative Optional User No
4.25 Description Descriptive Optional Auto-pop & User Yes
4.26 Destination Delivery System Mandatory Auto-pop Yes


4.27 Filename System Mandatory Auto-pop Yes
4.28 Format Descriptive Mandatory Auto-pop Yes
4.29 Identifier Administrative Mandatory Auto-pop Yes
4.30 Keywords Descriptive Optional Auto-pop & User Yes
4.31 Language Administrative Mandatory Auto-pop Yes
4.32 Next Review Period Administrative Mandatory User Yes
4.33 Presentation System Mandatory Auto-pop Yes
4.34 Subject (aafccore) Descriptive Mandatory Auto-pop & User Yes


4.35 Subject (gccore) Descriptive Mandatory Auto-pop & User Yes


4.36 Title Administrative Mandatory Auto-pop & User Yes


4.37 Type Descriptive Mandatory Auto-pop & User Yes


4.38 Valid Date Administrative Optional User No


4.39 vpath System Mandatory Auto-pop Yes
4.40 vpathprod System Mandatory Auto-pop Yes


AAFC Metadata Application Profile



Introduction

Purpose of this Document

The purpose of the AAFC Internet Metadata Application Profile is to fully describe how to apply metadata to information resources within the department’s internet, AAFC Online. The intent is to offer working level details to comply with Government of Canada and departmental metadata and associated standards.

The AAFC Internet Metadata Application Profile captures the business rules, type of entry and input, guidance and best practices for completing fields within the Content Management System (CMS). The CMS is responsible for streamlining and enhancing Web publishing processes and capabilities to support the electronic communication and service delivery needs of AAFC.

Intended Audience

The intended audience for this document includes, but is not limited to:

  • Information Architecture Services – Information Management Program (IMP)
  • E-Communications – Communications and Consultations Branch (CCB)
  • Portal and Content Services – Integrated Web Solutions
  • Website Development Services – Integrated Web Solutions

Definition and Purpose of Metadata

The definition for metadata stated in the Standard on Metadata is:

“Metadata defines and describes the structure and meaning of information resources, and the context and systems in which they exist. It is used to support efficient and effective management of these information resources over time.”

Metadata is used for description of resources, retrieval and management of information, identification of resource ownership, interoperability, e-commerce and other data properties. Metadata summarizes the key qualities, properties, or attributes of a given resource. It facilitates the discovery of resources and enables dynamic delivery of content to different sections within a web site or to different web sites so that content is written once but used many times (concept of reuse). As well, it enables the life cycle management of resources from creation to disposition. Metadata can be used to trigger events in a life cycle so that content can be refreshed, removed or archived as appropriate and according to the Government of Canada’s record retention policies.

In the context of this Internet Metadata Application Profile, metadata provides a description of the content on the web page. The fields in the CMS are separated into administrative, descriptive and system metadata. These fields may be auto-populated or applied by the user by selection of terms(s) or by free-text description.

Purpose of an Application Profile

An application profile is a set of attributes brought together from one or more namespace schemas for local application. Application profiles describe how standard schemas are to be used.

Scope

The Internet Metadata Application Profile offers a complete description of the metadata attribute set for electronic content, as it applies to AAFC Online.

Categories of Metadata

This metadata attribute set is divided into three categories:

Administrative metadata – Information such as Date Issued and Next Review Date are necessary to effectively access, use and manage AAFC resources.

Descriptive metadata – Information describing the intellectual content of the object, like Description and Subject, used primarily as an aid to indexing and retrieving a resource.

System metadata – Information, such as File Name and DCR Name, which provide necessary identification and used to properly render the content onto AAFC Online.

Business Rules

The Internet Metadata Application Profile also outlines the specific AAFC business rules for completing each metadata attribute.

Key Referring Documents

Please refer to Appendix A for documentation.

Attributes

Each attribute will be presented in the following format:

Attribute Attribute Description
Identification
Term Name A unique token assigned to the term.
URI A Uniform Resource Identifier used to identify the term.
Label A human-readable label assigned to the term.
Defined by An identifier of a namespace or a pointer to where the attribute is defined.
Definition
Type of term A property, class, vocabulary encoding scheme, or syntax encoding scheme.
Definition A statement that represents the concept and essential nature of the term.
Comment Additional information about the term or its application.
References References to additional resources for further explanation and guidance for the application of the term.
Relations
Encoding Scheme The described term is qualified by the referenced scheme.
Constraints
Obligation Indicates whether the property is required to always or sometimes be present. The options are:
  • Mandatory – should always be present
  • Optional – may be present
Metadata Type Indicates the type of data that can be represented in the value of the term. The options are:
  • Administrative
  • Descriptive
  • System
Entry Type Indicates the method in which the value is selected. The options are:
  • Auto-populated
  • User entry – may be user selected or free-text description
Occurrence Indicates any limit to the repeatability of the property.
Current Use Indicates whether the property is currently applied in the system.
Guidance
Explanation of Usage Provides a description on why and how to use the property.
Example of HTML Syntax Provides an example of the HTML syntax as it is provided at AAFC Online.

Internet Metadata Attribute Set

For ease of reference, the following attributes have been arranged in alphabetical order.


AAFC Collection

Attribute Attribute Description
Identification
Term Name collection
URI
Label AAFC Collection
Defined by AAFC-AAC
Definition
Type of term Property
Definition A group of content organized or owned by a specific business client or organized by theme or topic.
Comment Identifies groups of content for which a left-hand navigation menu below a lane menu is required in the presentation layer.
References AgriDoc: #384444
Relations
Encoding Scheme AAFC Collection Scheme (aafc.collection)
Constraints
Obligation Mandatory
Metadata Type Descriptive
Entry Type Auto-populated

Exception: It is not auto-populated for Common-Commun, Rural Secretariat and Co-operatives Secretariat

Occurrence Not repeatable
Current Use In Use
Guidance
Explanation of Usage Why to Use

The Collection Value is used to categorize web pages into specific topics and assist in navigation. The collection value will be provided in the left-hand menu under the appropriate lane. The breadcrumbs are set-up the following way: Home>Lane>Collection.

How to Use

In the ‘Descriptive’ tab of the CMS, the user must select the appropriate value in the drop down menu. There are two different AAFC Collection controlled vocabularies. All Primary Lane values, except Programs and Services, will use the same AAFC Collection controlled vocabulary. For Programs and Services, the collection value will be auto-populated.

  • Requests to add, modify or remove values must be sent to E-Communications, who will begin the change request process. The Information Architecture Services’ Metadata Specialists will verify the values, and ensure that the values in the CMS have been updated correctly.
Example of HTML Syntax <meta name="aafc.collection" title="aafcCollection" content="AgriInvest" />


AAFC Presentation Template Type

Attribute Attribute Description
Identification
Term Name presentationTemplateType
URI
Label AAFC Presentation Template Type
Defined by AAFC-AAC
Definition
Type of term Property
Definition The attribute is used to select the content page presentation template.
Comment Used to indicate to the web presentation application, AAFC Online, which content page presentation template it should use to display the content record. Therefore, the attribute is used to match the TeamSite DCR to the presentation layer .jsp that is being rendered.
References
Relations
Encoding Scheme AAFC controlled vocabulary (aafc.presentationtemplatetype)
Constraints
Obligation Mandatory
Metadata Type Descriptive
Entry Type Auto-populated
Occurrence Not repeatable
Current Use In Use
Guidance
Explanation of Usage Why to Use

Use this attribute to indicate to AAFC Online which content page presentation template should be used to display the content record.

How to Use

The default value is 2 columns. The user would need to manually change the value using the drop down menu if a different value was required.

Example of HTML Syntax Not applicable.


AAFC Primary Lane

Attribute Attribute Description
Identification
Term Name primaryLane
URI
Label Primary Lane
Defined by AAFC-AAC
Definition
Type of term Property
Definition The Primary Lane groups together web pages of similar interests or themes in order to dynamically generate the presentation layer requirements (style sheets, banners, navigation menus, etc).
Comment
References
Relations
Encoding Scheme AAFC Primary Lane Scheme (aafc.primaryLane)
Constraints
Obligation Mandatory
Metadata Type Descriptive
Entry Type Auto-populated

Exception: It is not auto-populated for Common-Commun, Rural Secretariat and Co-operatives

Occurrence Not repeatable
Current Use In Use
Guidance
Explanation of Usage Why to Use

The Primary Lane is used to denote the first level of content below the Home page, into general subject/thematic areas. This attribute is driven by the business/content areas. It divides content into major sections that share a common top left navigation menu (Lane menu) and other presentation attributes (Lane banner graphic, style sheets, etc). The Primary Lane determines the location and presentation of the content by loading the appropriate presentation layer requirements (style sheets, banners, navigation menus, etc). The breadcrumbs are set-up the following way: Home>Lane>Collection

How to Use

In the ‘Descriptive’ tab of the CMS, the user must select the appropriate value in the drop down menu. For all branches, except Common-Commun, Rural Secretariat and Co-operatives Secretariat, the value is auto-populated.

  • Requests to add, modify or remove values must be sent to E-Communications, who will begin the change request process. The Information Architecture Services’ Metadata Specialists will verify the values, and ensure that the values in the CMS have been updated correctly. E-Communications is involved in the process for how the Primary Lane is assigned to resources.
Example of HTML Syntax <meta name="aafc.primaryLane" title="aafcPrimaryLane" content="Producers" />


Administrative Parent ID

Attribute Attribute Description
Identification
Term Name administrativeParentID
URI
Label Administrative Parent ID
Defined by AAFC-AAC
Definition
Type of term Property
Definition An identification number relating to the parent (original) web page.
Comment
References
Relations
Encoding Scheme
Constraints
Obligation Optional
Metadata Type Administrative
Entry Type Property is not operational
Occurrence Not repeatable
Current Use Not in use
Guidance
Explanation of Usage Property is not operational
Example of HTML Syntax Property is not operational


Audience

Attribute Attribute Description
Identification
Term Name audience
URI http://purl.org/dc/terms/audience
Label Audience
Defined by DCMI Metadata Terms
Definition
Type of term Property
Definition A class of entity for whom the resource is intended or useful.
Comment To identify this resource as being of interest to a specific demographic.
References
Relations
Encoding Scheme Government of Canada Audience Scheme (gcaudience)
Constraints
Obligation Optional
Metadata Type Descriptive
Entry Type User entry (user selected)
Occurrence Not repeatable
Current Use Not in use
Guidance
Explanation of Usage Why to Use

Use the attribute to identify the group(s) for whom the information and services are intended.

How to Use

This attribute is not currently in use at AAFC.

Example of HTML Syntax <meta name="dcterms.audience" title="gcaudience" content="business" />


Content Coordinator Name

Attribute Attribute Description
Identification
Term Name contentCoordinatorName
URI
Label Content Coordinator Name
Defined by AAFC-AAC
Definition
Type of term Property
Definition The names of the person(s) who have the authority to edit the content.
Comment To reflect the ownership structure per page according to the approved web governance framework.
References
Relations
Encoding Scheme
Constraints
Obligation Optional
Metadata Type Administrative
Entry Type User entry (free-text description)
Occurrence Repeatable
Current Use Not in use
Guidance
Explanation of Usage Why to Use

It is used to state the person(s) who is allowed to edit the content.

How to Use

This attribute is not currently in use at AAFC. However, if a user wants to provide a name, the field is limited to 100 characters.

Example of HTML Syntax Not applicable


Content Coordinator Position

Attribute Attribute Description
Identification
Term Name contentCoordinatorPosition
URI
Label Content Coordinator Position
Defined by AAFC-AAC
Definition
Type of term Property
Definition The role of the person(s) who have the authority to edit the content.
Comment To reflect the ownership structure per page according to the approved web governance framework.
References
Relations
Encoding Scheme
Constraints
Obligation Optional
Metadata Type Administrative
Entry Type User entry (free-text description)
Occurrence Repeatable
Current Use Not in use
Guidance
Explanation of Usage Why to Use

It is used to state the role of the person(s) who are allowed to edit the content.

How to Use

This attribute is not currently in use at AAFC. However, if a user wants to provide a position title, the field is limited to 200 characters.

Example of HTML Syntax Not applicable


Content Coordinator Team

Attribute Attribute Description
Identification
Term Name contentCoordinatorTeam
URI
Label Content Coordinator Team
Defined by AAFC-AAC
Definition
Type of term Property
Definition The team name of the person(s) who has the authority to edit the content.
Comment To reflect the ownership structure per page according to the approved web governance framework.
References
Relations
Encoding Scheme
Constraints
Obligation Optional
Metadata Type Administrative
Entry Type User entry (free-text description)
Occurrence Repeatable
Current Use Not in use
Guidance
Explanation of Usage Why to Use

It is used to state the team name of the person(s) who are allowed to edit the content.

How to Use

This attribute is not currently in use at AAFC. However, if a user wants to provide a team name, the field is limited to 200 characters.

Example of HTML Syntax Not applicable


Content Owner Name

Attribute Attribute Description
Identification
Term Name contentOwnerName
URI
Label Content Owner Name
Defined by AAFC-AAC
Definition
Type of term Property
Definition The name of the person with the highest level of accountability in creation of the content.
Comment To reflect the ownership structure per page according to the approved web governance framework.
References
Relations
Encoding Scheme
Constraints
Obligation Optional
Metadata Type Administrative
Entry Type User entry (free-text description)
Occurrence Not repeatable
Current Use Not in use
Guidance
Explanation of Usage Why to Use

It is used to state the person with the highest level of accountability in creation of the content. It is always the Assistant Deputy Minister (ADM).

How to Use

This attribute is not currently in use at AAFC. However, if a user wants to provide a name, the field is limited to 200 characters. The field is not repeatable and if a user provides more than one name in the field it will treat it as one entry.

Example of HTML Syntax Not applicable


Content Owner Position/Title

Attribute Attribute Description
Identification
Term Name contentOwnerPositionTitle
URI
Label Content Owner Position/Title
Defined by AAFC-AAC
Definition
Type of term Property
Definition The title of the person with the highest level of accountability in creation of the content.
Comment To reflect the ownership structure per page according to the approved web governance framework.
References
Relations
Encoding Scheme
Constraints
Obligation Optional
Metadata Type Administrative
Entry Type User entry (free-text description)
Occurrence Not repeatable
Current Use Not in use
Guidance
Explanation of Usage Why to Use

It is used to state the title of the person with the highest level of accountability in creation of the content. It is always the Assistant Deputy Minister (ADM).

How to Use

This attribute is not currently in use at AAFC. However, if a user wants to provide a position title, the field is limited to 200 characters. The field is not repeatable and if a user provides more than one position title in the field it will treat it as one entry.

Example of HTML Syntax Not applicable


Content Owner Team

Attribute Attribute Description
Identification
Term Name contentOwnerTeam
URI
Label Content Owner Team
Defined by AAFC-AAC
Definition
Type of term Property
Definition The team name the person with the highest level of accountability in creation of the content.
Comment To reflect the ownership structure per page according to the approved web governance framework.
References
Relations
Encoding Scheme
Constraints
Obligation Optional
Metadata Type Administrative
Entry Type User entry (free-text description)
Occurrence Not repeatable
Current Use Not in use
Guidance
Explanation of Usage Why to Use

It is used to state the team name of the person with the highest level of accountability in creation of the content. The person with the highest level of accountability is the Assistant Deputy Minister (ADM).

How to Use

This attribute is not currently in use at AAFC. However, if a user wants to provide a team name, the field is limited to 200 characters. The field is not repeatable and if a user provides more than one team name in the field it will treat it as one entry.

Example of HTML Syntax Not applicable


Coverage (domestic)

Attribute Attribute Description
Identification
Term Name coverage
URI http://purl.org/dc/terms/coverage
Label Coverage (domestic)
Defined by DCMI Metadata Terms
Definition
Type of term Property
Definition The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant.
Comment Spatial topic and spatial applicability may be a named place or a location specified by its geographic coordinates.
References
Relations
Encoding Scheme Regions of Canada (gcregions)

http://geogratis.gc.ca/STATS/XML/CanadaProvRegions.jsp.xml

Constraints
Obligation Optional
Metadata Type Descriptive
Entry Type User entry (user selected)
Occurrence Not repeatable
Current Use Not in use
Guidance
Explanation of Usage Why to Use

To identify the geographic scope of the content of this resource for resource discovery and research purposes.

How to Use

This attribute is not currently in use at AAFC.

Example of HTML Syntax <meta name=”dcterms.spatialtitle=”gcregions” content=”Canada”/>


Coverage (international)

Attribute Attribute Description
Identification
Term Name coverage
URI http://purl.org/dc/terms/coverage
Label Coverage (international)
Defined by DCMI Metadata Terms
Definition
Type of term Property
Definition The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant.
Comment Spatial topic and spatial applicability may be a named place or a location specified by its geographic coordinates.
References
Relations
Encoding Scheme ISO 3166-1:2006

http://www.iso.org/iso/home/standards/country_codes/iso-3166-1_decoding_table.htm

Constraints
Obligation Optional
Metadata Type Descriptive
Entry Type User entry (user selected)
Occurrence Not repeatable
Current Use Not in use
Guidance
Explanation of Usage Why to Use

To identify the geographic scope of the content of this resource for resource discovery and research purposes.

How to Use

This attribute is not currently in use at AAFC.

Example of HTML Syntax Not applicable


Creator

Attribute Attribute Description
Identification
Term Name creator
URI http://purl.org/dc/elements/1.1/creator
Label Creator
Defined by DCMI Metadata Terms
Definition
Type of term Property
Definition An entity primarily responsible for making the content of the resource.
Comment To identify the entity responsible for the intellectual content of this resource.
References
Relations
Encoding Scheme For titles of federal institutions

Registry of Applied Titles http://www.tbs-sct.gc.ca/fip-pcim/reg-eng.asp

For Government of Canada organizational divisions and subdivisions

Government Electronic Directory Service (GEDS) http://sage-geds.tpsgc-pwgsc.gc.ca/

Constraints
Obligation Mandatory
Metadata Type Administrative
Entry Type Auto-populated/User entry
Occurrence Not repeatable
Current Use In Use
Guidance
Explanation of Usage Why to Use

This attribute is important for a number of reasons including rights management, assisting in the determination of archival value and other lifecycle processes. This attribute must be expressed in the HTML <Header> to comply with the Standard on Metadata.

How to Use

The Government of Canada (creator 1) and Agriculture and Agri-Food Canada (creator 2) are auto-populated. A third creator can be added using GEDS as a reference. The field allows for free-text. Each portion of the Creator attribute is entered separately in the CMS so there is no need to separate each unit with a period. For the Creator field, up to 200 characters are allowed. In the HTML syntax, each bureaucratic units and sub-divisions is separated with using a semi-colon (“ ; “).

Example of HTML Syntax <meta name="dcterms.creator " content="Government of Canada;Agriculture and Agri-Food Canada;Research Branch" />


Date for Review

Attribute Attribute Description
Identification
Term Name dateForReview
URI
Label Date For Review
Defined by Government of Canada Web Content Management System - Metadata Element Set
Definition
Type of term Property
Definition Date on which the issued resource will be revisited for evaluation of relevance or timeliness.
Comment
References
Relations
Encoding Scheme W3CDTF

http://www.w3.org/TR/NOTE-datetime

Constraints
Obligation Mandatory
Metadata Type Administrative
Entry Type Auto-populated
Occurrence Not repeatable
Current Use In Use
Guidance
Explanation of Usage Why to Use

This attribute is to be used to ensure the accuracy, relevance and timeliness of information on a web site. This attribute can serve to provide the author, editor and publisher with a reminder that the content should be reviewed for its accuracy, relevance and timeliness. This date must occur after Date Issued or Date Modified and ideally, before Valid Date. Though this attribute was not intended for publication to the web, it does appear in the HTML <Header>.

How to Use

Date For Review is system generated by adding Date Reviewed to Next Review Period (selected number of months). All dates will be entered in the form YYYY-MM-DD, as specified by the ISO 8601. At this time, there is no trigger within the workflow system to notify the author or editor with a reminder that the content should be reviewed and/or updated.

Example of HTML Syntax <meta name="gcterms.dateForReview"title="W3CDTF" content="2011-05-28" />


Date Issued

Attribute Attribute Description
Identification
Term Name issued
URI http://purl.org/dc/terms/issued
Label Date Issued
Defined by DCMI Metadata Terms
Definition
Type of term Property
Definition Date of formal issuance (e.g., publication) of the resource onto the web.
Comment
References
Relations
Encoding Scheme W3CDTF

http://www.w3.org/TR/NOTE-datetime

Constraints
Obligation Mandatory
Metadata Type Administrative
Entry Type Auto-populated
Occurrence Not repeatable
Current Use In Use
Guidance
Explanation of Usage Why to Use

The Date Issued attribute is used to capture the date the resource was first made available to the public on an Internet site. For legal purposes, this is an important date if users make decisions based on information provided by government departments. As well, it is useful for maintenance, resource discovery and evidentiary purposes. This attribute must be expressed in the HTML <Header> to comply with the Standard on Metadata.

How to Use

The Date Issued is auto-populated. All dates will be entered in the form YYYY-MM-DD, as specified by ISO 8601.

Example of HTML Syntax <meta name="dcterms.issued"title="W3CDTF" content="2009-03-10" />


Date Last Updated

Attribute Attribute Description
Identification
Term Name dateLastUpdated
URI
Label Date Last Updated
Defined by Government of Canada Web Content Management System - Metadata Element Set
Definition
Type of term Property
Definition Date on which the content resource was last changed within the CMS.
Comment To document the last date on which a change (major or minor) has been made to this resource for maintenance, evidentiary, and system and workflow purposes.
References
Relations
Encoding Scheme W3CDTF

http://www.w3.org/TR/NOTE-datetime

Constraints
Obligation Mandatory
Metadata Type Administrative
Entry Type Auto-populated
Occurrence Not repeatable
Current Use In Use
Guidance
Explanation of Usage Why to Use

Date Last Updated identifies when any change has been made to the resource and the resource is saved in the CMS.

How to Use

Date Last Updated is system generated and is pre-populated from system date on Teamsite DCR creation and subsequently changed when the resource is re-saved in the CMS. Date Last Updated cannot be manually changed. All dates will be entered in the form YYYY-MM-DD, as specified by ISO 8601.

Example of HTML Syntax <meta name="gcterms.dateLastUpdated" title="W3CDTF" content="2011-09-30" />


Date Modified

Attribute Attribute Description
Identification
Term Name modified
URI http://purl.org/dc/terms/modified
Label Date Modified
Defined by DCMI Metadata Terms
Definition
Type of term Property
Definition The date when a substantial revision is done to the resource and is then re-published to the web.
Comment To document when a significant change has been made to this resource to assist users in determining the currency of the content and for life-cycle management of the resource.
References
Relations
Encoding Scheme W3CDTF

http://www.w3.org/TR/NOTE-datetime

Constraints
Obligation Mandatory
Metadata Type Administrative
Entry Type auto-populated when the page is first issued/published. It will be user entry after that initial population.
Occurrence Not repeatable
Current Use In Use
Guidance
Explanation of Usage Why to Use

This attribute is used to document the date on which a significant change to the content of the resource was made. For formatting changes or small grammatical changes, the value of this attribute should not change; instead the Date Last Updated attribute will be used. This attribute must be expressed in the HTML <Header> to comply with the Standard on Metadata.

How to Use

This attribute must always have a value in the CMS. When a page is first published the Date Modified will be auto-populated with the date of publication. Date Modified is manually edited and replaces Date Issued in the footer of the page when a DCR is revised with substantial changes. All dates must be entered in the form YYYY-MM-DD, as specified by ISO 8601. There is a calendar option available to use when entering the date. Date modified cannot be a date that is earlier than Date Issued.

Example of HTML Syntax <meta name="dcterms.modified" title="W3CDTF" content="2010-04-09" />


Date Reviewed

Attribute Attribute Description
Identification
Term Name dateReviewed
URI http://purl.org/dc/terms/modified
Label Date Reviewed
Defined by Government of Canada Web Content Management System – Metadata Element Set
Definition
Type of term Property
Definition The last date on which the issued resource was revisited for evaluation of relevance or timeliness.
Comment To indicate that this resource was reviewed and is current.
References
Relations
Encoding Scheme W3CDTF

http://www.w3.org/TR/NOTE-datetime

Constraints
Obligation Optional
Metadata Type Administrative
Entry Type User entry

Note: If a date is not selected by the user, it will auto-populate with the date it was published.

Occurrence Not repeatable
Current Use In Use
Guidance
Explanation of Usage Why to Use

Use this attribute to ensure the accuracy, relevance and timeliness of information on a web site. The attribute indicates to the author, editor, publisher or end-user that the content was accurate as of a specific date.

How to Use

Date Reviewed is manually edited, though if left blank by the user the field will be populated with the date it was published. This date would remain until manually updated. All dates must be entered in the form YYYY-MM-DD, as specified by ISO 8601. There is a calendar option available to use when entering the date.

Example of HTML Syntax <meta name="gcterms.dateReviewed" title="W3CDTF" content="2010-05-28" />


DCR Name

Attribute Attribute Description
Identification
Term Name dcrName
URI
Label DCR Name
Defined by AAFC-AAC
Definition
Type of term Property
Definition An identifier linking resources that belong to a collection of resources.
Comment
References
Relations
Encoding Scheme
Constraints
Obligation Mandatory
Metadata Type System
Entry Type Auto-populated
Occurrence Not repeatable
Current Use In Use
Guidance
Explanation of Usage Why to Use

The DCR Name is important for system-related issues, identification and navigation.

How to Use

The field is auto-populated. It cannot be modified by the user.

Example of HTML Syntax Not applicable


DCR Type

Attribute Attribute Description
Identification
Term Name dcrType
URI
Label DCR Type
Defined by AAFC-AAC
Definition
Type of term Property
Definition A reference to a group of related resources by an identifier assigned within the CMS providing a pathway to a specific record.
Comment
References
Relations
Encoding Scheme
Constraints
Obligation Mandatory
Metadata Type System
Entry Type Auto-populated
Occurrence Not repeatable
Current Use In Use
Guidance
Explanation of Usage Why to Use

The DCR Type is important for system-related issues, identification and navigation.

How to Use

The field is auto-populated. It cannot be modified by the user.

Example of HTML Syntax Not applicable


Delegate of Responsibility Name

Attribute Attribute Description
Identification
Term Name delegateOfResponsiblitiyName
URI
Label Delegate of Responsibility Name
Defined by AAFC-AAC
Definition
Type of term Property
Definition The name of the person who has the Delegate of Responsibility. They have been delegated responsibility for content by the Content Owner.
Comment To reflect the ownership structure per page according to the approved web governance framework.
References
Relations
Encoding Scheme
Constraints
Obligation Optional
Metadata Type Administrative
Entry Type User entry (free-text description)
Occurrence Not repeatable
Current Use Not in use
Guidance
Explanation of Usage Why to Use

It is used to state the name of the person appointed by the Content Owner who approves content to be published to the web.

How to Use

This attribute is not currently in use at AAFC. However, if a user wants to provide a name, the field is limited to 200 characters. The field is not repeatable and if a user provides more than one name in the field it will treat it as one entry.

Example of HTML Syntax Not applicable


Delegate of Responsibility Position

Attribute Attribute Description
Identification
Term Name delegateOfResponsibilityPosition
URI
Label Delegate of Responsibility Position
Defined by AAFC-AAC
Definition
Type of term Property
Definition The position of the person with the Delegate of Responsibility.
Comment To reflect the ownership structure per page according to the approved web governance framework.
References
Relations
Encoding Scheme
Constraints
Obligation Optional
Metadata Type Administrative
Entry Type User entry (free-text description)
Occurrence Not repeatable
Current Use Not in use
Guidance
Explanation of Usage Why to Use

It is used to state the position title of the person appointed by the Content Owner who approves content to be published to the web.

How to Use

This attribute is not currently in use at AAFC. However, if a user wants to provide a position title, the field is limited to 200 characters. The field is not repeatable and if a user provides more than one position title in the field it will treat it as one entry.

Example of HTML Syntax Not applicable


Delegate of Responsibility Team

Attribute Attribute Description
Identification
Term Name delegateOfResponsibilityTeam
URI
Label Delegate of Responsibility Team
Defined by AAFC-AAC
Definition
Type of term Property
Definition The name of the team or branch of the Delegate of Responsibility.
Comment To reflect the ownership structure per page according to the approved web governance framework.
References
Relations
Encoding Scheme
Constraints
Obligation Optional
Metadata Type Administrative
Entry Type User entry (free-text description)
Occurrence Not repeatable
Current Use Not in use
Guidance
Explanation of Usage Why to Use

It is used to state the team name of the manager appointed by the Delegate of Responsibility who approves content to be published to the web.

How to Use

This attribute is not currently in use at AAFC. However, if a user wants to provide a team name, the field is limited to 200 characters. The field is not repeatable and if a user provides more than one team name in the field it will treat it as one entry.

Example of HTML Syntax Not applicable


Description

Attribute Attribute Description
Identification
Term Name description
URI http://purl.org/dc/elements/1.1/description
Label Description
Defined by DCMI Metadata Terms
Definition
Type of term Property
Definition A narrative account of the content of the resource.
Comment Limited to 2000 characters.
References
Relations
Encoding Scheme
Constraints
Obligation Optional
Metadata Type Descriptive
Entry Type Auto-populated

Note: The field is initially populated by Metatagger, then verified by the Metadata Analysts.

Occurrence Not repeatable
Current Use In Use
Guidance
Explanation of Usage Why to Use

This attribute is used to assist the user in determining the relevance of the resources on a search results page or on a links page without having to navigate to each resource.

How to Use

The system limits data entry to 2000 characters. The description should be written in the language of the resource. For bilingual introductory (or splash) pages repeat the attribute for each language. The field can be auto-populated, but also allows user entry.

Example of HTML Syntax <meta name="dcterms.description" content="Agriculture and Agri-Food Canada provides information and programs for those who raise animals or who grow plants for food, feed or industrial use. Agricultural producers will find information about economic forecasts and statistics, policies and acts, incentive programs and other services" />


Destination Delivery

Attribute Attribute Description
Identification
Term Name destinationDelivery
URI
Label Destination Delivery
Defined by Government of Canada Web Content Management System – Metadata Attribute Set
Definition
Type of term Property
Definition The destination(s) to which a piece of content is to be published (e.g., Internet, Extranet, Intranet, etc).
Comment To identify the delivery output destinations to support publishing and dynamic display purposes.
References
Relations
Encoding Scheme
Constraints
Obligation Mandatory
Metadata Type System
Entry Type Auto-populated
Occurrence Not repeatable
Current Use In Use
Guidance
Explanation of Usage Why to Use

Use this attribute to indicate where a record will be published (Internet, Extranet, Intranet, channels, or particular sections of web sites, etc). This attribute is used by the CMS in order to render the content to the correct online destinations.

How to Use

The field is auto-populated. It cannot be modified once the record is created.

Example of HTML Syntax Not applicable


Filename

Attribute Attribute Description
Identification
Term Name filename
URI
Label Filename
Defined by AAFC-AAC
Definition
Type of term Property
Definition The file name is the specific file or folder where the record resides.
Comment
References
Relations
Encoding Scheme
Constraints
Obligation Mandatory
Metadata Type System
Entry Type Auto-populated
Occurrence Not repeatable
Current Use In Use
Guidance
Explanation of Usage Why to Use

The Filename is important for system-related issues, identification and navigation.

How to Use

The field is auto-populated. It cannot be modified once the record is created.

Example of HTML Syntax Not applicable


Format

Attribute Attribute Description
Identification
Term Name format
URI http://purl.org/dc/elements/1.1/format
Label Format
Defined by DCMI Metadata Terms
Definition
Type of term Property
Definition The physical or digital manifestation of the resource.
Comment
References
Relations
Encoding Scheme Government of Canada Format Scheme (gcformat) http://www.collectionscanada.gc.ca/webarchives/20071120030246/www.tbs-sct.gc.ca/im-gi/mwg-gtm/fmt-fmt/docs/2003/schem_e.asp
Constraints
Obligation Mandatory
Metadata Type Descriptive
Entry Type Auto-populated
Occurrence Not repeatable
Current Use In Use
Guidance
Explanation of Usage Why to Use

This attribute is used to describe the media-type to determine software, hardware or other equipment needed to display or operate the resource. Examples of dimensions include size and duration.

How to Use

The field is auto-populated. It cannot be modified once the record is created. All resources should be described using a “type/sub-type” designation. Terms must be selected from a registered controlled vocabulary. If you require additional Internet Media Types (MIME) types, you can add them to your list of terms but it is recommend that you notify the authority for the gcformat scheme as identified in the IMRC – dc.format Guidelines in order that terms can be added to the formal GC scheme if they represent common needs.

Example of HTML Syntax <meta name="dcterms.format" title="gcformat" content="text/html" />


Identifier

Attribute Attribute Description
Identification
Term Name identifier
URI
Label Identifier
Defined by AAFC-AAC
Definition
Type of term Property
Definition An unambiguous reference to the resource within a given context.
Comment Represented as a series of numbers.
References
Relations
Encoding Scheme
Constraints
Obligation Mandatory
Metadata Type Administrative
Entry Type Auto-populated
Occurrence Not repeatable
Current Use In Use
Guidance
Explanation of Usage Why to Use

The identifier is used for identification purposes. It appears as part of the URL for the record’s web page.

How to Use

The field is auto-populated.

Example of HTML Syntax Not applicable


Keywords

Attribute Attribute Description
Identification
Term Name keywords
URI
Label Keywords
Defined by AAFC-AAC
Definition
Type of term Property
Definition A word or phrase describing the content of the resource and not found in one of the subject controlled vocabularies.
Comment To provide content owners the opportunity to include free text information that is not represented in the controlled vocabulary.
References
Relations
Encoding Scheme
Constraints
Obligation Optional
Metadata Type Descriptive
Entry Type Auto-populated

Note: The field is autopopulated by Metatagger, and then verified by the Metadata Analysts

Occurrence Not repeatable
Current Use In Use
Guidance
Explanation of Usage Why to Use

Keywords are useful for providing additional terms for the user. It may serve as another access point for search engines.

How to Use

Add acronyms, publication numbers, cataloguing or report numbers, phrases and frequently used words or terms by which users commonly access the resource. Between each word provide a comma (,) and then a space. For the Keywords field, up to 2000 characters is allowed. The field can be auto-populated, but also allows user entry.

Tips for selecting keywords

  • Add common words to scientific terms or vice versa when not in a controlled vocabulary.
  • Use keywords only if no terms adequately describe the resource from the list of the subjects
  • Select keywords that capture the most unique characteristics of the resource.
Example of HTML Syntax <meta name=”keywords” content =”mad cow disease”>


Language

Attribute Attribute Description
Identification
Term Name language
URI http://purl.org/dc/elements/1.1/language
Label Language
Defined by DCMI Metadata Terms
Definition
Type of term Property
Definition The language of the intellectual content of the resource.
Comment To identify the language(s) of this resource for the purpose of application processing (accessibility, search, workflow, etc.).
References
Relations
Encoding Scheme ISO 639.2/T Codes for the Representation of Names of Languages http://lcweb.loc.gov/standards/iso639-2/langhome.html
Constraints
Obligation Mandatory
Metadata Type Administrative
Entry Type Auto-populated

Note: The field is autopopulated by Metatagger, and then verified by the Metadata Analysts

Occurrence Not repeatable
Current Use In Use
Guidance
Explanation of Usage Why to Use

It is used to identify the language of the intellectual content of a resource. This attribute must be expressed in the HTML <Header> to comply with the Standard on Metadata.

How to Use

The field is auto-populated. It cannot be modified once the record is created.

Example of HTML Syntax <<meta name="dcterms.language" title ="ISO639-2" content="eng">

<meta name="dcterms.language" title ="ISO639-2" content="fra">


Next Review Period

Attribute Attribute Description
Identification
Term Name nextReviewPeriod
URI
Label Next Review Period
Defined by AAFC-AAC
Definition
Type of term Property
Definition The period representing the end at which time the content must be reviewed for accuracy, relevance, correctness, intellectual applicability, etc. Relates to the life-cycle management of content.
Comment To indicate the period for which content has relevance.
References
Relations
Encoding Scheme W3CDTF

http://www.w3.org/TR/NOTE-datetime

Constraints
Obligation Mandatory
Metadata Type Administrative
Entry Type User entry

Note: The user may select from a drop down list the number of months until the next review period. If the user does not choose, the default is ‘12’ months.

Occurrence Not repeatable
Current Use In Use
Guidance
Explanation of Usage Why to Use

This attribute is used to identify the period of time when a resource should be reviewed for relevance from a legal, service delivery perspective, or intellectual content perspective (e.g., a policy, program or service is applicable).

How to Use

The user may select the appropriate time frame for the resource up to 36 months. If they do not choose a value, then the default value, 12 months, will be provided.

Example of HTML Syntax Not applicable


Presentation

Attribute Attribute Description
Identification
Term Name presentation
URI
Label Presentation
Defined by AAFC-AAC
Definition
Type of term Property
Definition The presentation layer value indicates how the page is rendered at the front end.
Comment
References
Relations
Encoding Scheme
Constraints
Obligation Mandatory
Metadata Type System
Entry Type Auto-populated
Occurrence Not repeatable
Current Use In Use
Guidance
Explanation of Usage Why to Use

This attribute is used by the presentation layer when rendering pages.

How to Use

The field is auto-populated. When the DCR is first created, the value 1 or 0 will be chosen.

Example of HTML Syntax Not applicable


Subject (aafccore)

Attribute Attribute Description
Identification
Term Name aafcSubject
URI http://purl.org/dc/elements/1.1/subject
Label Subject (aafccore)
Defined by DCMI Metadata Terms
Definition
Type of term Property
Definition The topic of the resource.
Comment
References AgriDoc #384444
Relations
Encoding Scheme Agriculture and Agri-Food Canada Subject Taxonomy (aafcsubject)
Constraints
Obligation Mandatory
Metadata Type Descriptive
Entry Type Auto-populated

Note: The field is populated by Metatagger, and then verified.

Occurrence Not repeatable
Current Use In Use
Guidance
Explanation of Usage Why to Use

It is used to describe what the content of this resource is about through the use of controlled terms. The AAFC subject values (aafcsubject) provide more granular, precise description of AAFC’s business and operational activities than the Government of Canada Core Subject Thesaurus (gccore). This attribute must be expressed in the HTML <Header> to comply with the Standard on Metadata.

How to Use

Select terms that represent the concept of the web page. The field can be auto-populated, but also allows user entry.

Example of HTML Syntax <meta name="aafc.subject" title="aafcsubject" content="rural development;agricultural economics" />


Subject (gccore)

Attribute Attribute Description
Identification
Term Name subject
URI http://purl.org/dc/elements/1.1/subject
Label Subject (gccore)
Defined by DCMI Metadata Terms
Definition
Type of term Property
Definition The topic of the resource.
Comment This attribute is meant to standardize subject values across government departments and will enhance GC Canada site search.
References
Relations
Encoding Scheme Government of Canada Core Subject Thesaurus (gccore)

http://www.thesaurus.gc.ca/recherche-search/thes-eng.html

Constraints
Obligation Mandatory
Metadata Type Descriptive
Entry Type Auto-populated

Note: The field is populated by Metatagger, and then verified.

Occurrence Not repeatable
Current Use In Use
Guidance
Explanation of Usage Why to Use

It is used to describe what the content of this resource is about through the use of controlled terms. Gccore values represent subjects at a higher level than values selected from aafccore. This attribute must be expressed in the HTML <Header> to comply with the Standard on Metadata.

How to Use

Select terms that represent the concept of the web page. The field can be auto-populated, but also allows user entry.

Example of HTML Syntax <meta name= “dcterms.subjecttitle= “gccore” content= “agriculture”>


Title

Attribute Attribute Description
Identification
Term Name title
URI http://purl.org/dc/elements/1.1/title
Label Title
Defined by DCMI Metadata Terms
Definition
Type of term Property
Definition A name given to the resource.
Comment
References
Relations
Encoding Scheme
Constraints
Obligation Mandatory
Metadata Type Administrative
Entry Type Auto-populated (for CMI) and User entry (for all other users)
Occurrence Not repeatable
Current Use In Use
Guidance
Explanation of Usage Why to Use

The Title is the official name of the resource and is used to help distinguish one resource from another. Meaningful titles should be assigned for accessibility, speed of identification, and to facilitate control. This attribute must be expressed in the HTML <Header> to comply with the Standard on Metadata. .

How to Use

For CMI (Programs and Services), the title is the Program Name, and it is auto-populated. For all other users, the title is manually entered. For the Title field, up to 2000 characters are allowed. Use a hyphen [–] preceded and followed by space as the separator when adding additional contextual information to a resource title unless this will cause confusion for persons reading the title. Spell out acronyms and abbreviations.

Example of HTML Syntax <meta name="dcterms.title" content="Pulses and Special Crops" />


Type

Attribute Attribute Description
Identification
Term Name type
URI http://purl.org/dc/elements/1.1/type
Label Type
Defined by DCMI Metadata Terms
Definition
Type of term Property
Definition The nature or genre of the content of the resource.
Comment To provide additional information about the purpose of this resource to assist with information management and resource discovery.

To assist users in interpreting information contained in this resource by indentifying its internal structure.

References AgriDoc #384444
Relations
Encoding Scheme AAFC Type Scheme (aafc.type)
Constraints
Obligation Mandatory
Metadata Type Descriptive
Entry Type Auto-populated

Note: The field is populated by Metatagger, and then verified.

Occurrence Not repeatable
Current Use In Use
Guidance
Explanation of Usage Why to Use

This attribute is useful in understanding the purpose or function of the record and it provides indications as to the internal structure of a resource's content. It is used for categorizing content by type, e.g. policy, abstract, presentation.

How to Use

Select a term that represents the concept of the web page. There can only be one type selected. The field can be auto-populated, but also allows user entry.

Example of HTML Syntax <meta name="dcterms.type" title="aafctype" content="contact information" />


Valid Date

Attribute Attribute Description
Identification
Term Name dateValid
URI
Label Valid Date
Defined by Government of Canada Web Content Management System – Metadata Element Set
Definition
Type of term Property
Definition The end date of the date range representing the applicability for intellectual or legal relevance e.g., the end date on which a policy, program or service is applicable.
Comment To indicate the last date on which this resource has relevance.
References
Relations
Encoding Scheme W3CDTF

http://www.w3.org/TR/NOTE-datetime

Constraints
Obligation Optional
Metadata Type Administrative
Entry Type User entry
Occurrence Not repeatable
Current Use Not in use
Guidance
Explanation of Usage Why to Use

Use this attribute to identify when a resource will stop being relevant from a legal or service delivery perspective (e.g. a policy or service is applicable). The resources are still made available on the web site even though the content of the resource is no longer valid (e.g., for “sun-setting” programs and services, resources might still be available to the public as information that such a program or service was available but the program no longer is).

How to Use

Valid Date is manually edited. All dates must be entered in the form YYYY-MM-DD, as specified by ISO 8601. There is a calendar option available to use when entering the date.

Example of HTML Syntax Not applicable


vpath

Attribute Attribute Description
Identification
Term Name vpath
URI
Label Valid Date
Defined by AAFC-AAC
Definition
Type of term Property
Definition A reference to a group of related resources by an identifier assigned within the CMS providing a pathway to a specific record.
Comment
References
Relations
Encoding Scheme
Constraints
Obligation Mandatory
Metadata Type System
Entry Type Auto-populated
Occurrence Not repeatable
Current Use In Use
Guidance
Explanation of Usage Why to Use

The vpath is important for system-related issues and identification.

How to Use

The field is auto-populated. It cannot be modified by the user.

Example of HTML Syntax Not applicable


vpathprod

Attribute Attribute Description
Identification
Term Name vpathprod
URI
Label vpathprod
Defined by AAFC-AAC
Definition
Type of term Property
Definition A reference to a group of related resources providing the pathway to a specific record.
Comment
References
Relations
Encoding Scheme
Constraints
Obligation Mandatory
Metadata Type System
Entry Type Auto-populated
Occurrence Not repeatable
Current Use In Use
Guidance
Explanation of Usage Why to Use

The vpathprod is important for system-related issues and identification.

How to Use

The field is auto-populated. It cannot be modified by the user.

Example of HTML Syntax Not applicable


Appendix A – Reference

Metadata specifications

List of Controlled Vocabulary
Agriculture and Agri-Food Canada (2007) – AgriDOC # 384444

Content Management System specifications

Web Content Management Solution (CMS) Project Charter
Agriculture and Agri-Food Canada (2006) – AgriDOC # 481534

AAFC Web Renovation Information Architecture Principles
Agriculture and Agri-Food Canada, E-Communications Unit, CCT (2006) – AgriDOC #1790807

Other Metadata References

Government of Canada. (2007). Web Content Management System Metadata Element Set
http://www.gcpedia.gc.ca/gcwiki/images/9/9e/Web_Content_Management_System_Metadata_Element_Set.doc

Government of Canada. (2007). Web Content Management System Metadata Application Profile.
http://www.gcpedia.gc.ca/gcwiki/images/c/c7/Web_Content_Management_System_Metadata_Application_Profile.doc

Treasury Board of Canada Secretariat. (2011). Government of Canada Metadata Implementation Guideline for Web Resource Discovery, 6th edition (Draft).
http://www.gcpedia.gc.ca/gcwiki/images/2/23/MIG_6th_ed.doc

Treasury Board of Canada Secretariat. (2010). Standard on Metadata.
http://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=18909