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 Chat (such as one of these permanent autoconfirmed members).
AAFC Metadata Application Profile
Department of Agriculture and Agri-Food Editor: Patricia Redmond [email protected]
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:
|
| Metadata Type | Indicates the type of data that can be represented in the value of the term. The options are:
|
| Entry Type | Indicates the method in which the value is selected. The options are:
|
| 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.
|
| 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.
|
| 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) |
| 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.spatial” title=”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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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
|
| 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 |
| 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) |
| 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.subject” title= “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 |
| 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