Extension talk:Semantic Organization/Flow

The Invoice Overview Template example is missing something. Although there are four Invoices, the all, open, and due filters find no entries so far. The template filter lists one in square brackets but does not pick up field values.

should be fixed now

Page 1 prints correctly including Header, Intro, Contents and initial Agenda content up to the calculated page break. The page break calculation shifts correctly if you increase the Intro content.

But on page 2 - the top file name, and bottom page 2/2 prints but not the Agenda content.

Any thoughts on this?

I'm not sure if I understand your description correctly. If you post an issue at github you can easily add screenshots, so it's clear, how it looks.

Some hints:

• Top file name and page 2/2 comes from the browser (and should be configurable in the browser)
• What browser are you using?
• Does the problem also occur if you try to print this page?
• Do you use any custom styles or is it a vanilla Semantic Organization installation?

Page two does resolve in Microsoft Edge.

Page 2 doesn't resolve in Firefox or Windows Explorer.

I haven't seen this used anywhere?

It's used on the not yet documented page SemanticOrganization that can be used to create overview pages (i.e. enable features). This is only experimental so far...

How do you add the ? link as exampled on the Projects page?

You have to create the message MediaWiki:semorg-<feature>-help-page-name (e.g. MediaWiki:semorg-project-help-page-name) and set it's content to the title of the help page you would like to link to.

What does the Group permanent check box do?

It's just a way to mark a group as “permanent” in contrast to “temporary” groups. It's one way to classify groups. The property can be used in semantic queries. We used it to display only permanent (i.e. the most important) groups in the navigation...

A direct copy of Template:Semorg-manual gives Error: #autoedit cannot be called on pages in the "Help" namespace on this wiki.

This is strange as [NS_HELP] is marked = true by default. (In fact the SMW configuration file shows "12": true,) Adding $smwgNamespacesWithSemanticLinks[NS_HELP] = true; has no effect either.

Any suggestions?

#autoedit is a parser function provided by the Page Forms extension, it's documentation can be found here: Extension:Page_Forms/Linking_to_forms#auto-edit

The necessary configuration setting should be:

$wgPageFormsAutoeditNamespaces[] = NS_HELP;

If you extract the latest SO zip (with Custom.css 4.53), and cut and paste semorg.kollabor's Features Page, the Boostrap 4 "cards card-columns" div does not work.

Tweeki skin is based on Bootstrap (v3.4.1 or v4.4.1 via opt-in).

Must LocalSettings be amended to enable SO to opt in?

SemanticOrganizationHooks looks for the following $wgTweekiSkinUseBootstrap4 = true; $wgTweekiSkinUseExternallinkStyles = false; $wgSemorgUseCustomTweekiFiles == false;

No, there is no explicit opt-in necessary. SO does it for you as it depends on Bootstrap 4 features. I can't reproduce your issue with a fresh install of SO and Tweeki. Are there any customizations from your side that could be responsible? Is your wiki publicly available?

After much fiddling I resolved all by going back to

MediaWiki 1.31.1

Semantic MediaWiki 2.5.8.

{{semorg-doc-description|invoice}}

Renders as

Invoices

⧼doc-description⧽

Invoices

Invoices: all · open · open (Summary) · due

Filter

no entries so far…

no entries so far…

{{semorg-doc-description}} and Mediawiki:doc-description are part of the documentation and not of the extension itself. If you want to create an overview page for invoices, use {{semorg-invoice-overview}}.

• Accepting that add attribute equals add property, you start by adding properties per step.
• You then add two MediaWiki: messages per Property.(MYSTEP-process-step-title and MYSTEP-process-step-text). Can these be added via en.json and SOproperties.php?
• You then add these properties as hidden fields {{field|MYSTEP|hidden}} to Form:semorg-process.
• You then Add calls to {{semorg-process-step}} to the template (it must have the same name as the form). How do you do this? Which template?

Does this mean that you can only have one process?

Could you please add an example to Example Data. It would help enormously.

I'm sorry, processes in the current state are more a placeholder than a fully implemented feature. I didn't find the time so far to do it and it probably will take some time till I get back to it...

A verification of how it works.

SMW Embed template has 3 steps

1. Add a tag like "{{{field|Skills|holds template}}}" within the "Person" template part of the form definition
2. Add "{{{Skills|}}}" somewhere inside the page Template:Person, so that it gets displayed in pages
3. Add "|embed in field=Person[Skills]" to the "{{{for template|Skill|multiple" part of the form definition

In SMW SO using, embedded Files as an example, the generator embed appears to work like this:

A) In en.json, using meeting as an example, you add

      "semorg-field-meeting-files-name": "Files",

    "semorg-field-meeting-files-parameters": "holds template",

ie {{{field|meeting-files|holds template}}} This solves 1. above.

B) The next thing I find on the generated page is

als embedded

{{semorg-form-template-embed|meeting|}}

And is inserted in Form:<feature>.

C) This manages steps 2 and 3 above. It does so by calling Template:Semorg-form-template-embed which expects and has the following paramaters.

|{{int:semorg-{{{1|}}}-template}}

|multiple

|embed in field={{{2|}}}

|add button text={{int:semorg-form-{{{1|}}}-add-button-text}}

|displayed fields when minimized={{int:semorg-form-{{{1|}}}-displayed-fields-when-minimized}}

From the B) and C) above it becomes apparent that embed als {{semorg-form-template-embed|meeting|}}leaves out the {{{2|}}} paramater which you must add. In this case "Files".

But that makes the <feature> multiple and not files. So you must also change "meeting" to "file".

So we now have

i) paramater |file| supplying Template:Semorg-file.

ii) paramater |files supplying "embed in field".

and this correctly opens the File template dialogue. (If you leave {{{2|}}}out the button does not appear.)

And saves to the page.

Thanks for helping to make this more clear. I added some explanatory text on the generated page. At B) you would have to look at the generated page for file since that's the feature you want to embed. The second parameter of the semorg-form-template-embed call should be the target field as you correctly pointed out. To be on the safe side it should be referenced in the form <feature>[<field>], e.g. meeting-group[files].