The Guild Organizational KnowledgeBase is a collection of articles describing our organization’s position descriptions, responsibilities and processes, and procedural tasks.  We also list technical articles describing non-person aspects of the organization such as business information and technology specifications like for this website.

Please refer to the Data Model tab for a technical description of the documentation model built on this website.

Position DescriptionsProceduresKB CategoriesData Model
Position Descriptions
A subset of the many volunteer positions are described below as Position Descriptions.  Choose one to view its responsibilities and processes.

Position Description
Procedures
From the list below, you will find individual procedure articles that contain information and tasks necessary to complete the procedure.

Procedure
KnowledgeBase Categories
The list below shows all the sub-categories currently aligned under KnowledgeBase.
A Position Category will lead to a list of articles published for that position name.
A Procedure Category will lead to list of articles aligned to that name.  Explore.

  • Categories
  • Knowledge Base Data Model
    Multiple taxonomies (hierarchical structures) are listed in the table below.  The sets are intended to help article authors and readers better visualize the structural relationship of the various data entities and their meta data.

      Framework Information

    Volunteer Position
    is defined by a Position Description,
    which describes Responsibilities and Processes,
    with link(s) to Procedures and tasks.

    An open position is a Post object with the Category Volunteer Opening selected.

    A website Post is the document or web page that contains the textual narrative for Position Description and Procedure(s) with tasks.

    Position Description – Names the Position and contains a narrative description of Responsibilities and Processes.  A Category.
    Position – just a name for a role, assigned to a person. A Category bucket.  Subcategory instances name each position.
    Responsibilities – for each position, a narrative description.  Text data written in a Position Description.
    Process – a very short description of action(s), maybe presented in line with the responsibility. Text data written in a Position Description aligned to a Responsibility.
    Procedure – a set of tasks necessary to accomplish the procedure’s goal.  A Category bucket.  Subcategory instances name each procedure.
    Task(s) – specific actions, contact points, positions or people, and meta data, necessary to complete the procedures.  Text data written in a named Procedure subcategory document.
    Record – an article web page describing an important Guild document.

     

    A Category object is blue font face.  

     

    The construction starts with a website object called Post.  An author creates a new post, provides a title and narrative in the post body, and then assigns one or more categories then publishes it.  The Category provides a logical grouping factor or navigation or filtering.  Category can be used to relate one structure, such as Position, to another such as Procedure.  This way the Treasurer (a position) can easily identify any of the several Procedures needed to accomplish the responsibilities of the position.