Content Category (Node Type): Difference between revisions
m Randallkinard moved page Content Category to Content Category (Object): new naming convention |
No edit summary |
||
| Line 1: | Line 1: | ||
{{AutoVersion}} | |||
{{stubs}} | {{stubs}} | ||
<blockquote> | <blockquote>{{#lst:Glossary|Content Category}}</blockquote> | ||
</blockquote> | |||
A more complicated set of documents may exist, where some '''Document Types''' are a sub-category of a larger '''Document Type'''. This could just be useful for logically organizing '''Document Types''' into categories. Furthermore, this is part of creating a hierarchical structure in a '''Content Model'''. The '''Content Category''', as a child of the parent '''Content Model''', will inherit the '''Content Model's''' '''Data Model''' and its '''Data Elements'''. '''Document Types''', as children of the '''Content Category''', will inherit the parent '''Content Category's''' '''Data Model''' (including the '''Content Model's''' '''Data Model''' that it inherited). | A more complicated set of documents may exist, where some '''Document Types''' are a sub-category of a larger '''Document Type'''. This could just be useful for logically organizing '''Document Types''' into categories. Furthermore, this is part of creating a hierarchical structure in a '''Content Model'''. The '''Content Category''', as a child of the parent '''Content Model''', will inherit the '''Content Model's''' '''Data Model''' and its '''Data Elements'''. '''Document Types''', as children of the '''Content Category''', will inherit the parent '''Content Category's''' '''Data Model''' (including the '''Content Model's''' '''Data Model''' that it inherited). | ||
For example, if a set of documents contains Invoices, Checks, Receipts and Purchase Orders, they might fit into a '''Content Category''' of "Payments" and other '''Document Types''' might be placed under other '''Content Categories'''. All of the '''Document Types''' in the "Payments" '''Content Category''' would inherit from both the '''Content Category''' and the '''Content Model''' itself. | For example, if a set of documents contains Invoices, Checks, Receipts and Purchase Orders, they might fit into a '''Content Category''' of "Payments" and other '''Document Types''' might be placed under other '''Content Categories'''. All of the '''Document Types''' in the "Payments" '''Content Category''' would inherit from both the '''Content Category''' and the '''Content Model''' itself. | ||
Revision as of 14:52, 26 April 2024
|
This article is about the current version of Grooper. Note that some content may still need to be updated. |
| 2025 |
|
STUB |
This article is a stub. It contains minimal information on the topic and should be expanded. |
collections_bookmark A Content Category is a container for other Content Category or description Document Type nodes in a stacks Content Model. Content Categories are often used simply as organizational buckets for Content Models with large numbers of Document Types. However, Content Categories are also necessary to create branches in a Content Model's classification taxonomy, allowing for more complex Data Element inheritance and Behavior inheritance.
A more complicated set of documents may exist, where some Document Types are a sub-category of a larger Document Type. This could just be useful for logically organizing Document Types into categories. Furthermore, this is part of creating a hierarchical structure in a Content Model. The Content Category, as a child of the parent Content Model, will inherit the Content Model's Data Model and its Data Elements. Document Types, as children of the Content Category, will inherit the parent Content Category's Data Model (including the Content Model's Data Model that it inherited).
For example, if a set of documents contains Invoices, Checks, Receipts and Purchase Orders, they might fit into a Content Category of "Payments" and other Document Types might be placed under other Content Categories. All of the Document Types in the "Payments" Content Category would inherit from both the Content Category and the Content Model itself.