Difference between revisions of "Portal"

From Organic Design wiki
m
m (typos, punct)
 
(8 intermediate revisions by 2 users not shown)
Line 1: Line 1:
[[Category:Glossary]][[Category:Nodal Applications]][[Category:Nodal Concepts]]
+
<noinclude>{{glossary}}</noinclude>We use the term [[portal]] to refer to an easily-accessible repository of information that's associated with a key concept or structural element of an [[organisation]] or [[trust group]]. Any concept, no matter how abstract, could have an associated portal, but the most important are the elements that form the organisation's structure, such as departments and projects.
{{stub}}''This is the meaning of the word in the nodal context. For [[XmlWiki]] workspaces, see [[:Category:Workspaces]]''
 
*'''See also: &rarr; [[Interface]]'''
 
  
A workspace is a [[Node]] containing a collection of concepts and tools relating to a particular user or group. It exhibits layout and graphics properties based on the fundamental [[Geometry]] and higher-level [[Box Model]]. Workspaces may be static and used as templates or classes, but in normal operation a workspace is a dynamic user-interface structure undergoing change from interaction with its user or group members.
+
The actual form that the portals have depends on the technological context the organisation operates within and could range from physical noticeboards in outback villages to electronic desktop widgets in a PDA. The most important aspects of the portal are that:
 +
*they are used in a consistent way throughout the organisation,
 +
*that access be restricted to the members of the group that the portal is associated with,
 +
*that they can serve as an easily accessible catalogue for current relevant documentation and procedures,
 +
*and that they exhibit a scheduling aspect so that activity (such as work done for that context) can be logged and meetings or resources can be booked.<noinclude>
  
== [[Wiki Organisation]] Portal ==
+
== Using a CMS for implementing portals ==
We are setting up a range of portals now in order to add the functionality to wiki organisation that is referred to here: [[w:Enterprise Portal]]. Portals form entry points to various aspects of the organisation. They have the name space "Portal" reserved for them. There are some common features we are adding to our portals, which include:
+
We have implemented a prototype of our portal system in [[W:MediaWiki|MediaWiki]] in the form of our [[Wiki Organisation]] system, and we're now working on a more complete implementation in [[Drupal]]. In the context of a CMS, a portal is like a "home page" for a particular department, role, user or other high-level concept, such as procedures or projects. Many of our portals in the Wiki Organisation system are actually category pages with the standard items hidden and replaced with a more specifically structured list of member items. In general, we have a portal for the top level nodes in the organisation's [[Ontology]] that contain the following kinds of information:
 +
*Creation (of new member records)
 +
*Searches
 +
*Queries (of associated records, e.g. Orders associated with a Person)
 +
*Calendar: interface to member records
 +
*Activity: Most recently used member records
 +
*Procedures: related to this type (e.g. procedures associated with a Wiki, Computer or Person)
 +
*Reports: Creation of dynamic PDF reports of all category items listed in portal
  
*Easy creation of new articles (using preloads)
+
== See also ==
*Listing category articles (ideally in section 0 dpl report style)
+
*[[Software architecture]]
*Calendar interface for creating new articles and accessing historic ones (in some cases, like [[Portal:Meetings]]
+
*[[Wikipedia:Enterprise Portal]]
*Creation of dynamic PDF reports of all category items listed in portal
+
</noinclude>

Latest revision as of 23:14, 24 July 2011

Glossary.svg This page describes a concept which is part of our glossary

We use the term portal to refer to an easily-accessible repository of information that's associated with a key concept or structural element of an organisation or trust group. Any concept, no matter how abstract, could have an associated portal, but the most important are the elements that form the organisation's structure, such as departments and projects.

The actual form that the portals have depends on the technological context the organisation operates within and could range from physical noticeboards in outback villages to electronic desktop widgets in a PDA. The most important aspects of the portal are that:

  • they are used in a consistent way throughout the organisation,
  • that access be restricted to the members of the group that the portal is associated with,
  • that they can serve as an easily accessible catalogue for current relevant documentation and procedures,
  • and that they exhibit a scheduling aspect so that activity (such as work done for that context) can be logged and meetings or resources can be booked.

Using a CMS for implementing portals

We have implemented a prototype of our portal system in MediaWiki in the form of our Wiki Organisation system, and we're now working on a more complete implementation in Drupal. In the context of a CMS, a portal is like a "home page" for a particular department, role, user or other high-level concept, such as procedures or projects. Many of our portals in the Wiki Organisation system are actually category pages with the standard items hidden and replaced with a more specifically structured list of member items. In general, we have a portal for the top level nodes in the organisation's Ontology that contain the following kinds of information:

  • Creation (of new member records)
  • Searches
  • Queries (of associated records, e.g. Orders associated with a Person)
  • Calendar: interface to member records
  • Activity: Most recently used member records
  • Procedures: related to this type (e.g. procedures associated with a Wiki, Computer or Person)
  • Reports: Creation of dynamic PDF reports of all category items listed in portal

See also