Workspaces | |
Note:
A new feature called Workspace UI makes the creation of Workspaces easier since Tiki10
All the components are in place and are ready to be used, with or without UI. However, some consideration must be placed on how to assemble them for your particular use case if you don't use the Workspaces UI. For maximum control and for experienced powerusers/developers, you can create workpaces by hand (without an easy-to-use UI) following the indications below in this page |
Hand-made workspaces | |
The cycle to complete workspaces is in multiple steps:
Perspectives will modify certain aspects of the Tiki instance to make the workspace more visual. Below is a summary of the steps involved. For a more detailed tutorials, see: Tutorial: Manually creating a Workspace.
Play with it Switch to the perspective using the module. Because of the category jail, if you go to list pages, you won't see any pages. They are automatically filtered out so you can focus on your project. When you attempt to create a new wiki page, the category will automatically be selected. (This may require some permissions to assign categories to objects and add objects to a category) Switching out of the perspective will make everything visible again.
Create a dashboard The category jail affects how you view the content inside Tiki. The listing inside modules will be altered. Go a step further and change the home page of the perspective to a dashboard so members can quickly see what is going on when they begin working on the project.
|
Automation through Data Channels | |
Data channels allow to automate the process and convert workspace creation to a single step. However, some time must be invested to create the workspace template that will be used to initialize workspaces and serve as a starting point. The workspace can then be customized as needed using typical Tiki features. Data channels use the same syntax as profiles for their definition. Extensive reference documentation can be found on the profiles' site. They are stored in wiki pages, so complete history is provided to allow more collaboration. However, when executed, data channels have extensive rights, so limiting access to trusted users is a must. When starting out, it's better to test on a separate installation to avoid excessive amounts of test data from being generated. Organizing the workspace template Profile definitions can be cryptic. However, only the code blocks are evaluated and there can be multiple blocks in the page. Use the space in-between to describe what they do and what the objectives are.
Copy to clipboard
Copy to clipboard
Both names contain a strange structure: $profilerequest:workspace_name$Unknown$. This will be replaced by the name provided in the data channel form. If Test is entered as the workspace name, both the category and the perspective will be named Workspace Test. The perspective also contains the preferences that will be used. In this case, only the category_jail preference is set. The preference names are those used internally by Tiki. Some research may be required to find those. The value is set to $workspace_root, which is the name given to the category. It will be replaced by the ID of the freshly created category. Test it out Without the groups of the following section, you can run the data channel and generate perspectives and category. As an exercise, try the following:
Copy to clipboard
The groups section provides more information along with the privileges they grant. The autojoin flag indicates that the user triggering the data channel will automatically become a member of the group. Here, privileges are not granted globally. Instead, they are defined for the category and perspective.
Test it out With those groups, you create a minimal workspace with enough permissions to make it usable. Try to go further.
|
Distributing knowledge | |
About Profiles Profiles are Tiki's configuration distribution system. The configuration scripts are stored in a wiki, also running Tiki, referred to as the repository. The primary repository is profiles.tikiwiki.org, but any installation can be used by applying the Profile Repository Profile. Profiles can be applied from the admin panels.
A workspace profile is essentially a normal profile, but will require to copy the template verbatim and create the data channel. The repository will need to contain at least two pages: one for the profile definition and one containing the template. The template page can be an exact copy of the page currently used as a template. If the template uses external dependencies, those must also be provided by the profile. Copy to clipboard
The datachannel is then registered and granted to the Admins group. Additionally, you can add the perspective switching module automatically. Copy to clipboard
|
Historic notes | |
This permits to make smaller spaces within a Tiki instance, where Preferences can be overridden and permissions can be different. Workspaces will help with Social Networking, Project Management and Customer Relationship Management, which are use cases & profiles in addition to features. For more details, please see: Workspace
|
Simple explanation | |
and the following conversation |
FAQ-alike IRC conversation (helpful to understand) | |
mikebeary
nkoth
mikebeary
nkoth
mikebeary
nkoth
mikebeary
nkoth
mikebeary
nkoth
mikebeary
nkoth
mikebeary
nkoth
mikebeary
nkoth
mikebeary
nkoth
mikebeary
nkoth
mikebeary
mikebeary
nkoth
mikebeary
nkoth
nkoth
mikebeary
Related
|