Help:Налаштування
From semantic-mediawiki.org
Семантична МедіаВікі пропонує ряд налаштувань, що адміністратори сайтів можуть змінювати згідно певних потреб. Ця сторінка показує всі варіантти налаштувань версії 1.7.0 і вище. Всі доступні варіанти налаштувань можуть бути знайдені у файлі SMW_Settings.php, що відповідає певній версії. Для зміни налаштувань, слід скопіювати відповідні значення у LocalSettings.php, як показано у іструкції з встановлення. Не змінюйте SMW_Settings.php прямо, оскільки ваші зміни можуть бути затерті оновленнями програмного забезпечення.
Налаштування при встановленні[edit]
The following settings relate to the basic installation of SMW.
| Parameter | Description |
|---|---|
| $smwgNamespaceIndex | If you already have custom namespaces on your site, insert
$smwgNamespaceIndex = ???; into your LocalSettings.php before including SemanticMediaWiki.php (formerly SMW_Settings.php). The number ??? must be the smallest even namespace number that is not in use yet. However, it must not be smaller than 100. Default: 100 |
| $smwgEnableUpdateJobs | SMW defers some tasks until after a page was edited by using the MediaWiki job queueing system (see the manual on job queues). For example, when the type of a property is changed, all affected pages will be scheduled for (later) update. If a wiki generates too many jobs in this way, the following setting can be used to disable jobs. Note that this will cause some parts of the semantic data to get out of date, so that manual modifications or the use of SMW_refreshData.php might be needed.
Default: true |
| $smwgLinksInValues | Should SMW accept inputs like [[property::Some [[link]] in value]]? If enabled, this may lead to PHP crashes (!) when very long texts are used as values. This is due to limitations in the library PCRE that PHP uses for pattern matching. The provoked PHP crashes will prevent requests from being completed – usually clients will receive server errors ("invalid response") or be offered to download "index.php". It might be okay to enable this if such problems are not observed in your wiki.
Default: false |
| $smwgUseCategoryHierarchy | Should SMW consider MediaWiki's subcategory hierarchy in querying? If set to true, subcategories will always be interpreted like subclasses. For example, if A is a subcategory of B then a query for all elements of B will also yield all elements of A. If this setting is disabled, then subclass relationships can still be given explicitly by using the property Property:Subcategory of on some category page. Only if the setting is false will such annotations be shown in the Factbox (if enabled).
Default: true |
| $smwgCategoriesAsInstances | Should category pages that use some [[Category:Foo]] statement be treated as elements of the category Foo? If disabled, then it is not possible to make category pages elements of other categories. See also the above setting $smwgUseCategoryHierarchy.
Default: true |
| $smwgNamespacesWithSemanticLinks | Overwriting the following array, you can define for which namespaces the semantic links and annotations are to be evaluated. On other pages, annotations can be given but are silently ignored. This is useful since, e.g., talk pages usually do not have attributes and the like. In fact, is is not obvious what a meaningful attribute of a talk page could be. Pages without annotations will also be ignored during full OWL/RDF export, unless they are referred to from another article.
Default: $smwgNamespacesWithSemanticLinks = array( NS_MAIN => true, NS_TALK => false, NS_USER => true, NS_USER_TALK => false, NS_PROJECT => true, NS_PROJECT_TALK => false, NS_IMAGE => true, NS_IMAGE_TALK => false, NS_MEDIAWIKI => false, NS_MEDIAWIKI_TALK => false, NS_TEMPLATE => false, NS_TEMPLATE_TALK => false, NS_HELP => true, NS_HELP_TALK => false, NS_CATEGORY => true, NS_CATEGORY_TALK => false, SMW_NS_PROPERTY => true, SMW_NS_PROPERTY_TALK => false, SMW_NS_TYPE => true, SMW_NS_TYPE_TALK => false, SMW_NS_CONCEPT => true, SMW_NS_CONCEPT_TALK => false, ); |
| $smwgDefaultNumRecurringEvents | This is a setting for recurring events, created with the #set_recurring_event parser function. This setting defines the default number of instances defined by this parser function, if no end date is set.
Default: 100 |
| $smwgMaxNumRecurringEvents | This is a setting for recurring events, created with the #set_recurring_event parser function. This setting defines the maximum number that can be defined by this parser function, regardless of an end date.
Default: 500 |
| $smwgPageSpecialProperties | List of enabled page-related special properties. The setting was introduced in Semantic MediaWiki 1.7.0. Other possible settings are:
See the help page on $smwgPageSpecialProperties for detailed information to set this parameter. Default: array( '_MDAT' ) (corresponds to special property Modification date) |
Налаштування інтерфейсу[edit]
The following settings are relevant for the general appearance of various wiki pages in SMW, as well as for browsing interfaces such as Special:Browse.
| Parameter | Description |
|---|---|
| $smwgShowFactbox | This setting allows you to select in which cases you want to have a factbox appear below an article. Note that the Magic Words __SHOWFACTBOX__ and __NOFACTBOX__ can be used to control Factbox display for individual pages. Other options for this setting include:
Default: SMW_FACTBOX_HIDDEN |
| $smwgShowFactboxEdit | Same as $smwgShowFactbox but for edit mode and same possible values.
Default: SMW_FACTBOX_NONEMPTY |
| $smwgToolboxBrowseLink | Should the toolbox of each content page show a link to browse the properties of that page using Special:Browse? This is a useful way to access properties and it is somewhat more subtle than showing a Factbox on every page.
Default: true |
| $smwgInlineErrors | Should warnings be displayed in wikitexts right after the problematic input? This affects only semantic annotations, not warnings that are displayed by inline queries or other features.
Default: true |
| $smwgSearchByPropertyFuzzy | Should the search by property special page display nearby results when there are only few results with the exact value? Switch this off if this page has performance problems.
Default: true |
| $smwgTypePagingLimit | Number of results shown in the listings on pages in the namespace Type.
Default: 200 |
| $smwgConceptPagingLimit | Number of results shown in the listings on pages in the namespace Concept.
Default: 200 |
| $smwgPropertyPagingLimit | Number of results shown in the listings on pages in the namespace Property. Uses a smaller value since these lists need more space.
Default: 25 |
| $smwgMaxPropertyValues | Number of values that are shown for each page in the listing on property pages. If increased to higher values, it might be useful to reduce $smwgPropertyPagingLimit to avoid performance impacts when showing property pages.
Default: 3 |
| $smwgMaxNonExpNumber | The maximal number that SMW will normally display without using scientific exp notation. The default is rather large since some users have problems understanding exponents. Scientific applications may prefer a smaller value for concise display.
Default: 1000000000000000 |
Налаштування запитів[edit]
Settings for inline queries and for semantic queries in general. This can especially be used to prevent overly high server-load by complex queries. The following settings affect all queries, wherever they occur. ... further results
| Parameter | Description |
|---|---|
| $smwgQSubpropertyDepth | Restrict level of sub-property inclusion (steps within property hierarchy). Use 0 to disable hierarchy-inferencing in queries.
Default: 10 |
| $smwgQSortingSupport | Should sorting of query results be possible?
Default: true |
| $smwgQRandSortingSupport | Enables or disables the random sorting of query results.
Default: true |
| $smwgQDefaultNamespaces | Which namespaces should be searched by default? A value of NULL switches off default restrictions on searching, which is faster. An example value with namespaces would be array(NS_MAIN, NS_IMAGE).
Default: NULL |
| $smwgQComparators | List of comparator characters supported by queries, separated by '|'. Possible entries for this list are
If unsupported comparators are used, they are treated as part of the queried value. The behaviour of the comparators < and > varies depending on the setting for $smwStrictComparators. Default: '<|>|!~|!|~|≤|≥|<<|>>' |
| $smwStrictComparators | Enables or disables strict treatment of comparator symbols.
Default: false |
| $smwgIgnoreQueryErrors | Should queries be executed even if some errors were detected? A hint that points out errors is shown in any case.
Default: true |
Налаштування вбудованих запитів та Special:Ask[edit]
The following settings affect inline queries and querying special pages, in particular Special:Ask. Essentially they should mirror the kind of queries that should immediately be answered by the wiki, using whatever computations are needed.
Налаштування запитів-понять[edit]
Further settings for queries. The following settings affect queries that are part of concept pages. These are usually chosen to be less restricted than inline queries, since there are two other means for controlling their use:
- Concept queries that would not be allowed as normal queries will not be executed directly, but can use pre-computed results instead. This is the default. See Concept caching for details on how to exploit this.
- The whole Concept: namespace can be restricted (using some suitable MediaWiki extension) to an experienced user group that may create more complex queries resonably. Other users can employ thus defined concepts in their queries.
| Parameter | Description |
|---|---|
| $smwgQConceptCaching | Which concepts should be displayed only if available from cache? Possible values are:
In any case, caches will always be used if available (but see $smwgQConceptCacheLifetime). Default: CONCEPT_CACHE_HARD |
| $smwgQConceptMaxSize | Same as $smwgQMaxSize but for concepts.
Default: 20 |
| $smwgQConceptMaxDepth | Same as $smwgQMaxDepth but for concepts.
Default: 8 |
| $smwgQConceptFeatures | Same as $smwgQFeatures but for concepts. Note that using concepts in concepts is currently not supported – do not enable it!
Default: SMW_PROPERTY_QUERY | SMW_CATEGORY_QUERY | SMW_NAMESPACE_QUERY | SMW_CONJUNCTION_QUERY | SMW_DISJUNCTION_QUERY |
| $smwgQConceptCacheLifetime | This setting defines the cache life time in minutes. If a concept cache exists but is older than this, SMW tries to recompute it, and will only use the cache if this is not allowed due to settings above.
Default: 24 * 60 (= 1 day) |
Налаштування для запитів formatting/display[edit]
| Parameter | Description |
|---|---|
| $smwgQDefaultLinking | Which result columns in an inline query should be linked if not specified otherwise. Possible values are 'none', 'subject' (links only in first column), 'all'.
Default: 'all' |
| $smwgQDefaultLimit | Default number of rows returned in a query. Can be increased with limit=... in #ask.
Default: 50 |
| $smwgResultFormats | This setting contains an array of all query result formats that the wiki supports. It is normally extended automatically by extensions that supply additional formats. However, it is also possible to set this array manually, e.g. to disable some formats. To disable a format, do unset($smwgResultFormats['template']); Disabled formats will be treated like if the format parameter had been omitted. The formats 'table' and 'list' are defaults that cannot be disabled. The format 'broadtable' should not be disabled either in order not to break Special:Ask.
Default: array( 'table' => 'SMWTableResultPrinter', 'list' => 'SMWListResultPrinter', 'ol' => 'SMWListResultPrinter', 'ul' => 'SMWListResultPrinter', 'broadtable' => 'SMWTableResultPrinter', 'category' => 'SMWCategoryResultPrinter', 'embedded' => 'SMWEmbeddedResultPrinter', 'template' => 'SMWListResultPrinter', 'count' => 'SMWListResultPrinter', 'debug' => 'SMWListResultPrinter', 'rss' => 'SMWRSSResultPrinter', 'csv' => 'SMWCsvResultPrinter', 'dsv' => 'SMWDSVResultPrinter', 'json' => 'SMWJSONResultPrinter', 'rdf' => 'SMWRDFResultPrinter' ); |
Налаштування експорту[edit]
RSS експорт[edit]
OWL/RDF експорт[edit]
| Parameter | Description |
|---|---|
| $smwgAllowRecursiveExport | Can normal users request recursive export, i.e. an OWL/RDF export that includes a full export of all mentioned pages, and of all pages they mention, and so on. Recommended only for very small wikis.
Default: false |
| $smwgExportBacklinks | Should incoming properties be part of OWL/RDF export?
Default: true |
| $smwgNamespace | The URI-namespace of exported URIs. Will be set automatically if nothing is given, using the base URL provided to enableSemantics(). But in order to make pretty URIs you will need to set this to something nice and adapt your Apache configuration appropriately. This is done, e.g., on semanticweb.org, where URIs are of the form http://semanticweb.org/wiki/FOAF. An example setting would be
$smwgNamespace = 'http://example.org/id/'; Default: unset |
Other settings[edit]
The following settings usually need no modification.
SPARQL та RDF налаштування[edit]
See also the help page on configuring SWM for use with SPARQL and RDF stores.
| Parameter | Description |
|---|---|
| $smwgSparqlDatabase | Configure SPARQL database connection for Semantic MediaWiki. This is used when SPARQL-based features are enabled, e.g. when using 'SMWSparqlStore' as the $smwgDefaultStore. The default setting uses a generic SPARQL connector that is based on recent SPARQL documents. However there are settings available for use with specific connectors:
Default: 'SMWSparqlDatabase' |
| $smwgSparqlQueryEndpoint | Configure SPARQL database connection for Semantic MediaWiki. This is used when SPARQL-based features are enabled. Endpoint (service URL) for queries (reading queries like SELECT). This endpoint is neccessary.
Default: 'http://localhost:8080/sparql/' |
| $smwgSparqlUpdateEndpoint | Configure SPARQL database connection for Semantic MediaWiki. This is used when SPARQL-based features are enabled. Endpoint (service URL) for updates (SPARQL Update queries). Can be omitted if not supported.
Default: 'http://localhost:8080/update/' |
| $smwgSparqlDataEndpoint | Configure SPARQL database connection for Semantic MediaWiki. This is used when SPARQL-based features are enabled. Endpoint (service URL) for data (SPARQL HTTP Protocol for Graph Management) Can be omitted if not supported.
Default: 'http://localhost:8080/data/' |
| $smwgSparqlDefaultGraph | The default graph is similar to a database name in relational databases. It can be set to any URI (e.g. the main page URI of your wiki with "#graph" appended). Leaving the default graph URI empty only works if the store is configured to use some default graph or if it generally supports this. Different wikis should normally use different default graphs unless there is a good reason to share one graph.
Default: '' |
Інші налаштування[edit]
| Parameter | Description |
|---|---|
| $smwgPDefaultType | Default property type. Undefined properties (those without pages or whose pages have no "has type" statement) will be assumed to be of this type. This is an internal type id. See the file languages/SMW_LanguageXX.php to find what IDs to use for datatpyes in your language. The default corresponds to "Type:Page". The English ids are as follows:
Default: '_wpg' (corresponds to datatype Page) |
| $smwgTranslate | Setting this to true allows to translate all the labels within Special:Browse given that they have interwiki links. This feature is currently disabled and cannot be activated with this setting.
Default: false |
| $smwgAdminRefreshStore | If the following is set to true, the wiki data can be repaired using the interface on the page Special:SMWAdmin. Setting this option to false does not stop ongoing repair processes.
Default: true |
| $smwgHistoricTypeNamespace | If the following is set to true, you can still access the old namespaces Type (104) and Type_talk (105) which have been replaced by Special:Types and are thus obsolete starting with SMW 1.6.0.
Default: false |
Ця сторінка стосується усіх версій Семантичної МедіаВікі, починаючи з 1.7.0 і до останньої версії.
Інші мови : fr
