Class Term

Major class of Taxonomy.

Inheritance
System.Object
BaseEntityInfo
Term
Implements
Inherited Members
Namespace: DotNetNuke.Entities.Content.Taxonomy
Assembly: DotNetNuke.dll
Syntax
public class Term : BaseEntityInfo, IHydratable
Remarks

Taxonomy is defined as “the practice and science of classification” – Wikipedia, while Folksonomy is defined as “collaborative tagging” – Wikipedia. Usually, taxonomy refers to the practice of using hierarchical categories applied to the content by a “content editor”, while folksonomy refers to the practice of free-form tagging of content by users. In DotNetNuke, while we expose both of these at the presentation layer, in the API and Data Layer they are implemented using a common data structure.

There are a number of advantages of using a special System Vocabulary for storing user entered tags. One is that both taxonomy terms and folksonomy tags are treated in the API and Data Layer in the same way. This means that we only have to manage one relationship between content and terms rather than two separate relationships. The second benefit of treating tags in this way is that an admin can “manage” the tags – ie remove any offensive or inappropriate tags, or correct spellings of tags, by using the Taxonomy Manager UI.

Examples
internal static List<Term> GetTerms(this Vocabulary voc, int vocabularyId)
{
    ITermController ctl = Util.GetTermController();
    return ctl.GetTermsByVocabulary(vocabularyId).ToList();
}

Constructors

| Improve this Doc View Source

Term()

Initializes a new instance of the Term class.

Declaration
public Term()
Remarks

Taxonomy is defined as “the practice and science of classification” – Wikipedia, while Folksonomy is defined as “collaborative tagging” – Wikipedia. Usually, taxonomy refers to the practice of using hierarchical categories applied to the content by a “content editor”, while folksonomy refers to the practice of free-form tagging of content by users. In DotNetNuke, while we expose both of these at the presentation layer, in the API and Data Layer they are implemented using a common data structure.

There are a number of advantages of using a special System Vocabulary for storing user entered tags. One is that both taxonomy terms and folksonomy tags are treated in the API and Data Layer in the same way. This means that we only have to manage one relationship between content and terms rather than two separate relationships. The second benefit of treating tags in this way is that an admin can “manage” the tags – ie remove any offensive or inappropriate tags, or correct spellings of tags, by using the Taxonomy Manager UI.

| Improve this Doc View Source

Term(Int32)

Initializes a new instance of the Term class.

Declaration
public Term(int vocabularyId)
Parameters
Type Name Description
System.Int32 vocabularyId
Remarks

Taxonomy is defined as “the practice and science of classification” – Wikipedia, while Folksonomy is defined as “collaborative tagging” – Wikipedia. Usually, taxonomy refers to the practice of using hierarchical categories applied to the content by a “content editor”, while folksonomy refers to the practice of free-form tagging of content by users. In DotNetNuke, while we expose both of these at the presentation layer, in the API and Data Layer they are implemented using a common data structure.

There are a number of advantages of using a special System Vocabulary for storing user entered tags. One is that both taxonomy terms and folksonomy tags are treated in the API and Data Layer in the same way. This means that we only have to manage one relationship between content and terms rather than two separate relationships. The second benefit of treating tags in this way is that an admin can “manage” the tags – ie remove any offensive or inappropriate tags, or correct spellings of tags, by using the Taxonomy Manager UI.

| Improve this Doc View Source

Term(String, String, Int32)

Initializes a new instance of the Term class.

Declaration
public Term(string name, string description, int vocabularyId)
Parameters
Type Name Description
System.String name
System.String description
System.Int32 vocabularyId
Remarks

Taxonomy is defined as “the practice and science of classification” – Wikipedia, while Folksonomy is defined as “collaborative tagging” – Wikipedia. Usually, taxonomy refers to the practice of using hierarchical categories applied to the content by a “content editor”, while folksonomy refers to the practice of free-form tagging of content by users. In DotNetNuke, while we expose both of these at the presentation layer, in the API and Data Layer they are implemented using a common data structure.

There are a number of advantages of using a special System Vocabulary for storing user entered tags. One is that both taxonomy terms and folksonomy tags are treated in the API and Data Layer in the same way. This means that we only have to manage one relationship between content and terms rather than two separate relationships. The second benefit of treating tags in this way is that an admin can “manage” the tags – ie remove any offensive or inappropriate tags, or correct spellings of tags, by using the Taxonomy Manager UI.

| Improve this Doc View Source

Term(String, String)

Initializes a new instance of the Term class.

Declaration
public Term(string name, string description)
Parameters
Type Name Description
System.String name
System.String description
Remarks

Taxonomy is defined as “the practice and science of classification” – Wikipedia, while Folksonomy is defined as “collaborative tagging” – Wikipedia. Usually, taxonomy refers to the practice of using hierarchical categories applied to the content by a “content editor”, while folksonomy refers to the practice of free-form tagging of content by users. In DotNetNuke, while we expose both of these at the presentation layer, in the API and Data Layer they are implemented using a common data structure.

There are a number of advantages of using a special System Vocabulary for storing user entered tags. One is that both taxonomy terms and folksonomy tags are treated in the API and Data Layer in the same way. This means that we only have to manage one relationship between content and terms rather than two separate relationships. The second benefit of treating tags in this way is that an admin can “manage” the tags – ie remove any offensive or inappropriate tags, or correct spellings of tags, by using the Taxonomy Manager UI.

| Improve this Doc View Source

Term(String)

Initializes a new instance of the Term class.

Declaration
public Term(string name)
Parameters
Type Name Description
System.String name
Remarks

Taxonomy is defined as “the practice and science of classification” – Wikipedia, while Folksonomy is defined as “collaborative tagging” – Wikipedia. Usually, taxonomy refers to the practice of using hierarchical categories applied to the content by a “content editor”, while folksonomy refers to the practice of free-form tagging of content by users. In DotNetNuke, while we expose both of these at the presentation layer, in the API and Data Layer they are implemented using a common data structure.

There are a number of advantages of using a special System Vocabulary for storing user entered tags. One is that both taxonomy terms and folksonomy tags are treated in the API and Data Layer in the same way. This means that we only have to manage one relationship between content and terms rather than two separate relationships. The second benefit of treating tags in this way is that an admin can “manage” the tags – ie remove any offensive or inappropriate tags, or correct spellings of tags, by using the Taxonomy Manager UI.

Properties

| Improve this Doc View Source

ChildTerms

Major class of Taxonomy.

Declaration
public List<Term> ChildTerms { get; }
Property Value
Type Description
List<Term>
Remarks

Taxonomy is defined as “the practice and science of classification” – Wikipedia, while Folksonomy is defined as “collaborative tagging” – Wikipedia. Usually, taxonomy refers to the practice of using hierarchical categories applied to the content by a “content editor”, while folksonomy refers to the practice of free-form tagging of content by users. In DotNetNuke, while we expose both of these at the presentation layer, in the API and Data Layer they are implemented using a common data structure.

There are a number of advantages of using a special System Vocabulary for storing user entered tags. One is that both taxonomy terms and folksonomy tags are treated in the API and Data Layer in the same way. This means that we only have to manage one relationship between content and terms rather than two separate relationships. The second benefit of treating tags in this way is that an admin can “manage” the tags – ie remove any offensive or inappropriate tags, or correct spellings of tags, by using the Taxonomy Manager UI.

Examples
internal static List<Term> GetTerms(this Vocabulary voc, int vocabularyId)
{
    ITermController ctl = Util.GetTermController();
    return ctl.GetTermsByVocabulary(vocabularyId).ToList();
}
| Improve this Doc View Source

Description

Major class of Taxonomy.

Declaration
public string Description { get; set; }
Property Value
Type Description
System.String
Remarks

Taxonomy is defined as “the practice and science of classification” – Wikipedia, while Folksonomy is defined as “collaborative tagging” – Wikipedia. Usually, taxonomy refers to the practice of using hierarchical categories applied to the content by a “content editor”, while folksonomy refers to the practice of free-form tagging of content by users. In DotNetNuke, while we expose both of these at the presentation layer, in the API and Data Layer they are implemented using a common data structure.

There are a number of advantages of using a special System Vocabulary for storing user entered tags. One is that both taxonomy terms and folksonomy tags are treated in the API and Data Layer in the same way. This means that we only have to manage one relationship between content and terms rather than two separate relationships. The second benefit of treating tags in this way is that an admin can “manage” the tags – ie remove any offensive or inappropriate tags, or correct spellings of tags, by using the Taxonomy Manager UI.

Examples
internal static List<Term> GetTerms(this Vocabulary voc, int vocabularyId)
{
    ITermController ctl = Util.GetTermController();
    return ctl.GetTermsByVocabulary(vocabularyId).ToList();
}
| Improve this Doc View Source

IsHeirarchical

Major class of Taxonomy.

Declaration
public bool IsHeirarchical { get; }
Property Value
Type Description
System.Boolean
Remarks

Taxonomy is defined as “the practice and science of classification” – Wikipedia, while Folksonomy is defined as “collaborative tagging” – Wikipedia. Usually, taxonomy refers to the practice of using hierarchical categories applied to the content by a “content editor”, while folksonomy refers to the practice of free-form tagging of content by users. In DotNetNuke, while we expose both of these at the presentation layer, in the API and Data Layer they are implemented using a common data structure.

There are a number of advantages of using a special System Vocabulary for storing user entered tags. One is that both taxonomy terms and folksonomy tags are treated in the API and Data Layer in the same way. This means that we only have to manage one relationship between content and terms rather than two separate relationships. The second benefit of treating tags in this way is that an admin can “manage” the tags – ie remove any offensive or inappropriate tags, or correct spellings of tags, by using the Taxonomy Manager UI.

Examples
internal static List<Term> GetTerms(this Vocabulary voc, int vocabularyId)
{
    ITermController ctl = Util.GetTermController();
    return ctl.GetTermsByVocabulary(vocabularyId).ToList();
}
| Improve this Doc View Source

KeyID

Major class of Taxonomy.

Declaration
public int KeyID { get; set; }
Property Value
Type Description
System.Int32
Remarks

Taxonomy is defined as “the practice and science of classification” – Wikipedia, while Folksonomy is defined as “collaborative tagging” – Wikipedia. Usually, taxonomy refers to the practice of using hierarchical categories applied to the content by a “content editor”, while folksonomy refers to the practice of free-form tagging of content by users. In DotNetNuke, while we expose both of these at the presentation layer, in the API and Data Layer they are implemented using a common data structure.

There are a number of advantages of using a special System Vocabulary for storing user entered tags. One is that both taxonomy terms and folksonomy tags are treated in the API and Data Layer in the same way. This means that we only have to manage one relationship between content and terms rather than two separate relationships. The second benefit of treating tags in this way is that an admin can “manage” the tags – ie remove any offensive or inappropriate tags, or correct spellings of tags, by using the Taxonomy Manager UI.

| Improve this Doc View Source

Left

Major class of Taxonomy.

Declaration
public int Left { get; }
Property Value
Type Description
System.Int32
Remarks

Taxonomy is defined as “the practice and science of classification” – Wikipedia, while Folksonomy is defined as “collaborative tagging” – Wikipedia. Usually, taxonomy refers to the practice of using hierarchical categories applied to the content by a “content editor”, while folksonomy refers to the practice of free-form tagging of content by users. In DotNetNuke, while we expose both of these at the presentation layer, in the API and Data Layer they are implemented using a common data structure.

There are a number of advantages of using a special System Vocabulary for storing user entered tags. One is that both taxonomy terms and folksonomy tags are treated in the API and Data Layer in the same way. This means that we only have to manage one relationship between content and terms rather than two separate relationships. The second benefit of treating tags in this way is that an admin can “manage” the tags – ie remove any offensive or inappropriate tags, or correct spellings of tags, by using the Taxonomy Manager UI.

Examples
internal static List<Term> GetTerms(this Vocabulary voc, int vocabularyId)
{
    ITermController ctl = Util.GetTermController();
    return ctl.GetTermsByVocabulary(vocabularyId).ToList();
}
| Improve this Doc View Source

Name

Major class of Taxonomy.

Declaration
public string Name { get; set; }
Property Value
Type Description
System.String
Remarks

Taxonomy is defined as “the practice and science of classification” – Wikipedia, while Folksonomy is defined as “collaborative tagging” – Wikipedia. Usually, taxonomy refers to the practice of using hierarchical categories applied to the content by a “content editor”, while folksonomy refers to the practice of free-form tagging of content by users. In DotNetNuke, while we expose both of these at the presentation layer, in the API and Data Layer they are implemented using a common data structure.

There are a number of advantages of using a special System Vocabulary for storing user entered tags. One is that both taxonomy terms and folksonomy tags are treated in the API and Data Layer in the same way. This means that we only have to manage one relationship between content and terms rather than two separate relationships. The second benefit of treating tags in this way is that an admin can “manage” the tags – ie remove any offensive or inappropriate tags, or correct spellings of tags, by using the Taxonomy Manager UI.

Examples
internal static List<Term> GetTerms(this Vocabulary voc, int vocabularyId)
{
    ITermController ctl = Util.GetTermController();
    return ctl.GetTermsByVocabulary(vocabularyId).ToList();
}
| Improve this Doc View Source

ParentTermId

Major class of Taxonomy.

Declaration
public int? ParentTermId { get; set; }
Property Value
Type Description
System.Nullable<System.Int32>
Remarks

Taxonomy is defined as “the practice and science of classification” – Wikipedia, while Folksonomy is defined as “collaborative tagging” – Wikipedia. Usually, taxonomy refers to the practice of using hierarchical categories applied to the content by a “content editor”, while folksonomy refers to the practice of free-form tagging of content by users. In DotNetNuke, while we expose both of these at the presentation layer, in the API and Data Layer they are implemented using a common data structure.

There are a number of advantages of using a special System Vocabulary for storing user entered tags. One is that both taxonomy terms and folksonomy tags are treated in the API and Data Layer in the same way. This means that we only have to manage one relationship between content and terms rather than two separate relationships. The second benefit of treating tags in this way is that an admin can “manage” the tags – ie remove any offensive or inappropriate tags, or correct spellings of tags, by using the Taxonomy Manager UI.

Examples
internal static List<Term> GetTerms(this Vocabulary voc, int vocabularyId)
{
    ITermController ctl = Util.GetTermController();
    return ctl.GetTermsByVocabulary(vocabularyId).ToList();
}
| Improve this Doc View Source

Right

Major class of Taxonomy.

Declaration
public int Right { get; }
Property Value
Type Description
System.Int32
Remarks

Taxonomy is defined as “the practice and science of classification” – Wikipedia, while Folksonomy is defined as “collaborative tagging” – Wikipedia. Usually, taxonomy refers to the practice of using hierarchical categories applied to the content by a “content editor”, while folksonomy refers to the practice of free-form tagging of content by users. In DotNetNuke, while we expose both of these at the presentation layer, in the API and Data Layer they are implemented using a common data structure.

There are a number of advantages of using a special System Vocabulary for storing user entered tags. One is that both taxonomy terms and folksonomy tags are treated in the API and Data Layer in the same way. This means that we only have to manage one relationship between content and terms rather than two separate relationships. The second benefit of treating tags in this way is that an admin can “manage” the tags – ie remove any offensive or inappropriate tags, or correct spellings of tags, by using the Taxonomy Manager UI.

Examples
internal static List<Term> GetTerms(this Vocabulary voc, int vocabularyId)
{
    ITermController ctl = Util.GetTermController();
    return ctl.GetTermsByVocabulary(vocabularyId).ToList();
}
| Improve this Doc View Source

Synonyms

Major class of Taxonomy.

Declaration
public List<string> Synonyms { get; }
Property Value
Type Description
List<System.String>
Remarks

Taxonomy is defined as “the practice and science of classification” – Wikipedia, while Folksonomy is defined as “collaborative tagging” – Wikipedia. Usually, taxonomy refers to the practice of using hierarchical categories applied to the content by a “content editor”, while folksonomy refers to the practice of free-form tagging of content by users. In DotNetNuke, while we expose both of these at the presentation layer, in the API and Data Layer they are implemented using a common data structure.

There are a number of advantages of using a special System Vocabulary for storing user entered tags. One is that both taxonomy terms and folksonomy tags are treated in the API and Data Layer in the same way. This means that we only have to manage one relationship between content and terms rather than two separate relationships. The second benefit of treating tags in this way is that an admin can “manage” the tags – ie remove any offensive or inappropriate tags, or correct spellings of tags, by using the Taxonomy Manager UI.

Examples
internal static List<Term> GetTerms(this Vocabulary voc, int vocabularyId)
{
    ITermController ctl = Util.GetTermController();
    return ctl.GetTermsByVocabulary(vocabularyId).ToList();
}
| Improve this Doc View Source

TermId

Major class of Taxonomy.

Declaration
public int TermId { get; set; }
Property Value
Type Description
System.Int32
Remarks

Taxonomy is defined as “the practice and science of classification” – Wikipedia, while Folksonomy is defined as “collaborative tagging” – Wikipedia. Usually, taxonomy refers to the practice of using hierarchical categories applied to the content by a “content editor”, while folksonomy refers to the practice of free-form tagging of content by users. In DotNetNuke, while we expose both of these at the presentation layer, in the API and Data Layer they are implemented using a common data structure.

There are a number of advantages of using a special System Vocabulary for storing user entered tags. One is that both taxonomy terms and folksonomy tags are treated in the API and Data Layer in the same way. This means that we only have to manage one relationship between content and terms rather than two separate relationships. The second benefit of treating tags in this way is that an admin can “manage” the tags – ie remove any offensive or inappropriate tags, or correct spellings of tags, by using the Taxonomy Manager UI.

Examples
internal static List<Term> GetTerms(this Vocabulary voc, int vocabularyId)
{
    ITermController ctl = Util.GetTermController();
    return ctl.GetTermsByVocabulary(vocabularyId).ToList();
}
| Improve this Doc View Source

Vocabulary

Major class of Taxonomy.

Declaration
public Vocabulary Vocabulary { get; }
Property Value
Type Description
Vocabulary
Remarks

Taxonomy is defined as “the practice and science of classification” – Wikipedia, while Folksonomy is defined as “collaborative tagging” – Wikipedia. Usually, taxonomy refers to the practice of using hierarchical categories applied to the content by a “content editor”, while folksonomy refers to the practice of free-form tagging of content by users. In DotNetNuke, while we expose both of these at the presentation layer, in the API and Data Layer they are implemented using a common data structure.

There are a number of advantages of using a special System Vocabulary for storing user entered tags. One is that both taxonomy terms and folksonomy tags are treated in the API and Data Layer in the same way. This means that we only have to manage one relationship between content and terms rather than two separate relationships. The second benefit of treating tags in this way is that an admin can “manage” the tags – ie remove any offensive or inappropriate tags, or correct spellings of tags, by using the Taxonomy Manager UI.

Examples
internal static List<Term> GetTerms(this Vocabulary voc, int vocabularyId)
{
    ITermController ctl = Util.GetTermController();
    return ctl.GetTermsByVocabulary(vocabularyId).ToList();
}
| Improve this Doc View Source

VocabularyId

Major class of Taxonomy.

Declaration
public int VocabularyId { get; }
Property Value
Type Description
System.Int32
Remarks

Taxonomy is defined as “the practice and science of classification” – Wikipedia, while Folksonomy is defined as “collaborative tagging” – Wikipedia. Usually, taxonomy refers to the practice of using hierarchical categories applied to the content by a “content editor”, while folksonomy refers to the practice of free-form tagging of content by users. In DotNetNuke, while we expose both of these at the presentation layer, in the API and Data Layer they are implemented using a common data structure.

There are a number of advantages of using a special System Vocabulary for storing user entered tags. One is that both taxonomy terms and folksonomy tags are treated in the API and Data Layer in the same way. This means that we only have to manage one relationship between content and terms rather than two separate relationships. The second benefit of treating tags in this way is that an admin can “manage” the tags – ie remove any offensive or inappropriate tags, or correct spellings of tags, by using the Taxonomy Manager UI.

Examples
internal static List<Term> GetTerms(this Vocabulary voc, int vocabularyId)
{
    ITermController ctl = Util.GetTermController();
    return ctl.GetTermsByVocabulary(vocabularyId).ToList();
}
| Improve this Doc View Source

Weight

Major class of Taxonomy.

Declaration
public int Weight { get; set; }
Property Value
Type Description
System.Int32
Remarks

Taxonomy is defined as “the practice and science of classification” – Wikipedia, while Folksonomy is defined as “collaborative tagging” – Wikipedia. Usually, taxonomy refers to the practice of using hierarchical categories applied to the content by a “content editor”, while folksonomy refers to the practice of free-form tagging of content by users. In DotNetNuke, while we expose both of these at the presentation layer, in the API and Data Layer they are implemented using a common data structure.

There are a number of advantages of using a special System Vocabulary for storing user entered tags. One is that both taxonomy terms and folksonomy tags are treated in the API and Data Layer in the same way. This means that we only have to manage one relationship between content and terms rather than two separate relationships. The second benefit of treating tags in this way is that an admin can “manage” the tags – ie remove any offensive or inappropriate tags, or correct spellings of tags, by using the Taxonomy Manager UI.

Examples
internal static List<Term> GetTerms(this Vocabulary voc, int vocabularyId)
{
    ITermController ctl = Util.GetTermController();
    return ctl.GetTermsByVocabulary(vocabularyId).ToList();
}

Methods

| Improve this Doc View Source

Fill(IDataReader)

Major class of Taxonomy.

Declaration
public virtual void Fill(IDataReader dr)
Parameters
Type Name Description
IDataReader dr
Remarks

Taxonomy is defined as “the practice and science of classification” – Wikipedia, while Folksonomy is defined as “collaborative tagging” – Wikipedia. Usually, taxonomy refers to the practice of using hierarchical categories applied to the content by a “content editor”, while folksonomy refers to the practice of free-form tagging of content by users. In DotNetNuke, while we expose both of these at the presentation layer, in the API and Data Layer they are implemented using a common data structure.

There are a number of advantages of using a special System Vocabulary for storing user entered tags. One is that both taxonomy terms and folksonomy tags are treated in the API and Data Layer in the same way. This means that we only have to manage one relationship between content and terms rather than two separate relationships. The second benefit of treating tags in this way is that an admin can “manage” the tags – ie remove any offensive or inappropriate tags, or correct spellings of tags, by using the Taxonomy Manager UI.

| Improve this Doc View Source

GetTermPath()

Major class of Taxonomy.

Declaration
public string GetTermPath()
Returns
Type Description
System.String
Remarks

Taxonomy is defined as “the practice and science of classification” – Wikipedia, while Folksonomy is defined as “collaborative tagging” – Wikipedia. Usually, taxonomy refers to the practice of using hierarchical categories applied to the content by a “content editor”, while folksonomy refers to the practice of free-form tagging of content by users. In DotNetNuke, while we expose both of these at the presentation layer, in the API and Data Layer they are implemented using a common data structure.

There are a number of advantages of using a special System Vocabulary for storing user entered tags. One is that both taxonomy terms and folksonomy tags are treated in the API and Data Layer in the same way. This means that we only have to manage one relationship between content and terms rather than two separate relationships. The second benefit of treating tags in this way is that an admin can “manage” the tags – ie remove any offensive or inappropriate tags, or correct spellings of tags, by using the Taxonomy Manager UI.

Examples
internal static List<Term> GetTerms(this Vocabulary voc, int vocabularyId)
{
    ITermController ctl = Util.GetTermController();
    return ctl.GetTermsByVocabulary(vocabularyId).ToList();
}

Implements

Extension Methods