Nine(9)=> Anatomy:

  
 

Nine(9)=> Making a group:

A group is a lot of responsibility in Nine(9) and you probably do not want it. A group_maintainer looks after 81 maps. If you find that you really want to request such a duty, then ask the server_maintainer to make you one. You can do this by following the instructions to make a map_entry at a point in Nine(9) where you know no group exists.

 

 

 

Nine(9)=> Making an archive:

An archive in Nine(9) is where you will put together nine related maps about one subject, (where you will make your first statement using Nine(9)). If you find that you want to request such a space then ask the your group_maintainer to make you one. You can do this by following the instructions to make a map_entry at a point in Nine(9)where you know no archive exists, yet you feel your subject fits.

 

 

 

Nine(9)=> Making a map:


1. Make sure you have a map_entry

2. Login to your knowledge map.

3. Getting your files organised:

4. Upload your map_images:

5. Link it all together:

6. link to other peoples knowledge_maps:

 

 

 

 

 

Nine(9)=> Server:

The Nine(9) server_maintainer sets up the initial structure of Nine(9) on the server.

This can be one or many persons. Only the server_maintainer can make a group and in turn nominate group_maintainers.

The server knows who is the server_maintainer by the use of a password.

That is: before Nine(9) lets you make a group, it first checks to see if the server_maintainer password associated with the Nine(9)_server corresponds to the one you entered.

Nine(9)_server map:

 

 

The server is arranged over a two dimentional grid 27 x 27. Each square represents a knowledge_map.

Nine(9)=> Groups:

 

Nine(9) divides up the top level of the server space it occupies by creating nine groups:

each is maintained by a group_maintainer.

The server knows who is the group_maintainer of 'group_1' by a name, password pair.

That is: Nine(9) checks to see if the group_name associated with a position on the matrix corresponds to a password associated with that position.

 

group_maintainer =

{

group_1_name = 'your_group_name'

group_1_password = 'your_group_password'

}

 

ONLY the group_maintainer can; make an archive_entry and therefore allow people to build archives in the group associated with 'your_group_name'.

 

 

Each group_maintainer can make a group:


open:(anyone can make an archive in this group)
or
closed: (the group maintainer decides who can make an archive in the group.)


This allows the host organisation of the Nine(9)_server to split topics between various groups and give responsibility of maintaining the groups to a number of people.

 

Each group contains nine archives.

*NOTE: When a new group is created then an email is automatically sent to the server_maintainer who looks after the Nine(9)_server.

 

 

Nine(9)=> Archives:

 

Nine(9)has 81 archives in nine groups:

each archive is maintained by an archive_maintainer.

The server knows who is the archive_maintainer of 'archive_1' by a name, password pair.

That is: Nine(9) checks to see if the archive_name associated with a position on the matrix corresponds to a password associated with that position.

 

archive_maintainer =
{
archive_1_name = 'your_archive_name'
archive_1_password = 'your_archive_password'
}

ONLY the archive_maintainer can make a map entry and therefore allow people to build knowledge_maps in the archive associated to 'your_archive_name'.

 

 

Archives are arranged over three rows and three columns, each archive_maintainer can make an archive:

open: (anyone can make a map in this archive)
or
closed: (the archive_maintainer decides who can make a map in the archive.)


This allows the group_maintainer to split topics between various archives and give responsibility to maintaining the archives to a number of people.
Each archive contains knowledge_maps.

*NOTE: When a new archive is created, an email is automatically sent to the group_maintainer who looks after the group containing the new archive.

 

 

 

Nine(9)=> knowledge_map anatomy:

 

 

Nine(9) Nine(9) has 729 knowledge_maps contained in 81 archives in nine groups: each knowledge_map is maintained by a map_maintainer. The server knows who is the map_maintainer of 'map_1' by a name, password pair. That is: Nine(9) checks to see if the map_name associated with a position on the matrix corresponds to a password associated with that position.

 

map_maintainer =
{
map_1_name = 'your_map_name'
map_1_password = 'your_map_password'
}

ONLY the map_maintainer can make: upload_files, delete_files, link_files and link_maps.

 

Knowledge_maps are arranged over three rows and three columns.

 

*NOTE:s

When a new knowledge_map is created then an email is automatically sent to the archive_maintainer who looks after the archive containing the new knowledge_map.

see also Knowledge_maps