“ For example: If we had a new portal about the United Kingdom's Royal Air Force, called Portal:Royal Air Force, the obvious class would be U for Military Science. Within U, we have subclass UGA for Air Forces. Therefore, this new portal would be clearly classified with the call number UGA. As such, the classification part of the portal header would be completed like this: | class = U | subclass1 = G | subclass2 = A Another example: If we had the new portal, Portal:Censorship, it might be more difficult to identify the correct class. ”
Summary
“Portal classification”, is a work by . It explores elements such as subclass, portal and classification.
Quotes from Portal classification ()
“ The subclass The second step in classifying a portal is to select the subclass. Each class has a different number of subclasses, using different combinations of letters. All call numbers require a subclass component. Portals should not be coded directly into a class without a subclass. The corresponding letters form the second and, sometimes, the third part of the call number. In the {{portal header}}, the first letter completes the subclass1 parameter and the second letter completes the subclass2 parameter. ”
“ The parent and midclass parameters are optional. The parent parameter will override the links to parent portals shown in the title bar of the header. Anything enteres in this parameter will be shown instead. The midclass parameter is for use with three-letter call numbers. ”
