Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Document Properties Marker
overridefalse


Short DescriptionShort introduction on using data tables or using views on data.
Doctypetopichide
NameFrom a Table to Views
Short Name
Parent
Parent Property
property-nameName
hide
Audience
Name List
doctyperole
render-no-hits-as-blanktrue
propertyAudience
empty-as-nonetrue

Subject
Name List
doctypesubject
propertySubject

Categories
Name List
doctypecategory
propertyCategories

Tags

Tag List
render-list-as-comma-separated-valuestrue
namesConfluence, projectdoc Toolbox, table, display table macro, single sourcing
propertyTags

hide
Flagshide
Iteration

Iteration
valuefilledfocused

hide
Type

Name List
doctypetopic-type
render-no-hits-as-blanktrue
namesTip
propertyType


Level of Experience

Name List
doctypeexperience-level
render-no-hits-as-blanktrue
namesAdvanced Beginner
propertyLevel of Experience


Expected Duration
Sponsors
Name List
doctypestakeholder
render-no-hits-as-blanktrue
propertySponsors

Sort Keyhide


...

Section
titleHandling these Requirements

So what are the options to handle these requirements with the tabular approach and what is an alternative?

Section
titleSelecting on Information

Selecting on information in a table can be done by filtering. Filters may reduce the amount of columns and the amount of lines.

Another way to solve the problem would be to create a page in the wiki dedicated to only one person.

Section


Column
width33%


Panel
titlePage for Tina


NameChristina Meyer
E-Mailchristina@example.com
Phone

098 321-123

Mobile+01 123 23451
skypetina.m



Section
titleFields of expertise
  • ...
  • ...
  • ...


Section
titleHistory of projects
  1. ...
  2. ...
  3. ...




Column
width33%


Panel
titlePage for Mike


NameMichael Suba
E-Mailmichael@example.com
Phone098 321-204
Mobile+01 123 23671
skypesuper.mickey



Section
titleFields of expertise
  • ...
  • ...
  • ...


Section
titleHistory of projects
  1. ...
  2. ...
  3. ...




Column
width33%


Panel
titlePage for John


NameJohn Doely
E-Mailjohn@example.com
Phone098 321-451
Mobile+01 123 24656
skypemycorporationme



Section
titleFields of expertise
  • ...
  • ...
  • ...


Section
titleHistory of projects
  1. ...
  2. ...
  3. ...




The page can be based on a blueprint to make it easier to add new members and provide the information that is most relevant to the team. Information that should only be visible to team members in certain roles could be added on separate pages. The access to these pages is restricted by the wikis access control and are transcluded on the public page. Therefore the transclusion will only happen if the user has sufficient access to the restricted information.

You can add information in different formats. For instance the telephone number in form of its extension and in full format. You may also define different type of team members where different types of information is relevant.

To automtically automatically render the information of all team members in tabular form, use the Display Table Macro. This macro allows you to query for team members with certain properties and select to show only the personal information that is relevant to your use case. That is you have the information of team members in one place and then have multiple views on this information by using the Display Table Macro.

Image Added


Section
titleReferencing Information

To reference a single member you would need to reference a single line in the table.

If you have each team member on a separate page, the URL to that page references the team member. Via this URL all information about the team member that is relevant to the team is accessible. This URL can be easily added to other documents to create a web of information.


Section
titleAdding more Information

In tabular form it is often unwieldly to have short information like a name in the same line as a list of special interestes or other multi-line notes.

If the information for a team member is on a separate page, any information can be added. The projectdoc Toolbox distinguishes between Document Properties, which are typical single line and used to filter on team members for a search result and Document Sections which comprise multiple blocks like paragraphs or tables. Since each view selects on information, the information can be rendered in the most appropriate layout.

Having defined fields of expertise on could also collect names of team members who are provicient in that field. That is by clicking on an expertise on a team member page, the user would have access to a list of team members that also have knowledge in that area.

If you document projects and link to the people who are part of the team, a history of projects can be automaticall rendered on the team member pages. The same is true for topics the team members are authors of if they are mentioned as as authors on the topic page.


...