Difference between revisions of "Template talk:Property setting"
Dag Endresen (Talk | contribs) (→Parameter “title”, “label”) |
|||
(3 intermediate revisions by 3 users not shown) | |||
Line 7: | Line 7: | ||
: I added parameter “categories” --[[User:Andreas Plank|Andreas Plank]] 11:05, 28 September 2012 (CEST) | : I added parameter “categories” --[[User:Andreas Plank|Andreas Plank]] 11:05, 28 September 2012 (CEST) | ||
− | == Parameter “title”, “label” == | + | == Parameter == |
+ | |||
+ | === “title”, “label” === | ||
Technically I use “title” to pass it on to ''all'' other formlink titles in the tool box. It is meant to be a general title, not like label. On page [[Property:dwc:year]] the title can be “Darwin Core Term” or “Darwin Core Vocabulary” but should not have a title “Year”, the Wiki title is already “dwc:year”. Does it make sense or do I use parameter “title” in a wrong sense? --[[User:Andreas Plank|Andreas Plank]] 12:33, 28 September 2012 (CEST) | Technically I use “title” to pass it on to ''all'' other formlink titles in the tool box. It is meant to be a general title, not like label. On page [[Property:dwc:year]] the title can be “Darwin Core Term” or “Darwin Core Vocabulary” but should not have a title “Year”, the Wiki title is already “dwc:year”. Does it make sense or do I use parameter “title” in a wrong sense? --[[User:Andreas Plank|Andreas Plank]] 12:33, 28 September 2012 (CEST) | ||
− | When I see the input for Title on the "Property:dwc:year" page, I think of the title for that individual resource and not a general category such as "Darwin Core term". I am not sure what is meant by pass it on to other formlink titles...? --[[User:Dag Endresen|Dag Endresen]] 14:16, 28 September 2012 (CEST) | + | : When I see the input for Title on the "Property:dwc:year" page, I think of the title for that individual resource and not a general category such as "Darwin Core term". I am not sure what is meant by pass it on to other formlink titles...? --[[User:Dag Endresen|Dag Endresen]] 14:16, 28 September 2012 (CEST) |
+ | :: Maybe "heading" would be more appropriate instead of "title" --[[User:Andreas Plank|Andreas Plank]] 15:10, 9 October 2012 (CEST) | ||
+ | |||
+ | ::: I believe much of the requirement, i.e. to provide context to a property, can best be fullfilled by retrieving the concepts schemes as defined in the concept template associated with the current property in the article namespace. The same applies to the label. I find it useful to retrieve this information and display it on the property page, but I would rather like not to duplicate any user-entered information in article versus property namespace. I would find it useful if this information (label, schemes) is shown BOTH in in template and form, and in the latter there is an edit-pencil symbol placed behind it, which automatically links to or creates the associated concept page in article namespace. [[User:Gregor Hagedorn|Gregor Hagedorn]] 15:37, 11 October 2012 (CEST) | ||
+ | |||
+ | === Simplify parameter === | ||
+ | |||
+ | Some questions/proposals: | ||
+ | |has type= → mandatory (one of {{abbr|SMW}} [[Special:Types]]) | ||
+ | : Can text be made the default if missing? --[[User:Gregor Hagedorn|Gregor Hagedorn]] 21:08, 6 October 2012 (CEST) | ||
+ | :: Form-default is "String", so should it be "has type=String" with some automated checking category?<br/>Done (assumes "String" if not given). --[[User:Andreas Plank|Andreas Plank]] 10:08, 8 October 2012 (CEST) | ||
+ | |display units= → used when “has type” is “Quantities” (, separated) | ||
+ | |corresponds to= → used when “has type” is “Quantities” (; separated) | ||
+ | : why comma versus semicolon separated? Perhaps provide a link to the smw documentation to help readers understand the functionality. --[[User:Gregor Hagedorn|Gregor Hagedorn]] 21:08, 6 October 2012 (CEST) | ||
+ | :: "corresponds to" can be e.g. "1 W, Watt, Watts; 0.001 kW" so ";" is needed --[[User:Andreas Plank|Andreas Plank]] 10:08, 8 October 2012 (CEST) | ||
+ | |title= → optional (title, e.g. “Darwin Core term”) | ||
+ | : Remove to reduce potential duplication with [[Template:Concept]] in the main article space? --[[User:Gregor Hagedorn|Gregor Hagedorn]] 21:08, 6 October 2012 (CEST) | ||
+ | :: Yes could be removed to avoid confusion, but it would be nice to have some section to what a property page, e.g "Property:germplasm:BreedingEvent" or any other property belongs to. Really remove? <br />Or should it be called "heading"? --[[User:Andreas Plank|Andreas Plank]] 10:08, 8 October 2012 (CEST) | ||
+ | |label= → optional (maps to [[property: rdfs:label]]) | ||
+ | : Remove to reduce potential duplication with [[Template:Concept]] in the main article space? Can label be automatically be obtained from there? --[[User:Gregor Hagedorn|Gregor Hagedorn]] 21:08, 6 October 2012 (CEST) | ||
+ | :: ''Can label be automatically be obtained from there?'' With #ask maybe. If it works, I remove parameter label.<br/>Works with: <nowiki>{{#ask: [[{{PAGENAME}}]] |mainlabel=-|link=none|?skos:prefLabel#prefLabel= |+index=1 |format=list}}</nowiki> --[[User:Andreas Plank|Andreas Plank]] 10:08, 8 October 2012 (CEST) | ||
+ | ::: If any label, shouldn’t it map to [[property: skos:prefLabel |skos:prefLabel]]? --[[User:Andreas Plank|Andreas Plank]] 10:46, 8 October 2012 (CEST) | ||
+ | |imported from= → optional (uses imported page by MediaWiki:Smw_import_''local-ns-prefix'', details see [http://semantic-mediawiki.org/wiki/Help:Import_vocabulary Help {{abbr|SMW}} import vocabulary]) | ||
+ | : Can we have a default here, that if nothing is said it is assumed that the page title is imported? --[[User:Gregor Hagedorn|Gregor Hagedorn]] 21:08, 6 October 2012 (CEST) | ||
+ | :: We could assume an import if <nowiki>{{PAGENAME}}</nowiki> has a ":", e.g. "germplasm<span style="background-color:#fcaf3e;padding:0px 0.2em">:</span>BreedingEvent".<br/>Done. --[[User:Andreas Plank|Andreas Plank]] 10:08, 8 October 2012 (CEST) | ||
+ | |categories= → optional management categories (, separated list) | ||
+ | : Remove to reduce potential duplication with [[Template:Concept]] in the main article space? --[[User:Gregor Hagedorn|Gregor Hagedorn]] 21:08, 6 October 2012 (CEST) | ||
+ | :: So how can we collect then concepts together or separated? Do I have to create an #ask query for getting e.g. all dcterms? I vote against it. You can also use categories to categorize ordinary properties, not used as "concepts" for our terms Wiki. --[[User:Andreas Plank|Andreas Plank]] 10:08, 8 October 2012 (CEST) | ||
+ | ::: a) It is always possible to add a manual category at the bottom of a page, i.e. outside of the template. This is good for internal/rare purposes. b) For normal purposes, adding categories to property-namespace bears a high managemnt cost of checking that they are ALL set correctly. I propose a similar solution to the label and scheme: a lookup of the scheme from the Concept template (article namespace) and assign any associated property to this category as well. --[[User:Gregor Hagedorn|Gregor Hagedorn]] 16:35, 11 October 2012 (CEST) | ||
+ | |||
+ | === Subproperty of=== | ||
+ | |||
+ | Remove from template, retrieve from concept template page (concept relation) using ask query to set the smw-property on the Property: page. --[[User:Gregor Hagedorn|Gregor Hagedorn]] 16:35, 11 October 2012 (CEST) | ||
+ | |||
+ | === As floating box === | ||
+ | |||
+ | I propose to make the entire table box floating top right like an infobox and trying to make it appear less technical. | ||
+ | * Add the schemes (retrieved by ask query) first, scheme labels in bold. | ||
+ | * Reduce "Has type (SMW) : Text [Show] Hints for this type …" to "Has type : Text [more...]" with "Hints for this type …" and the SMW and type link from left as part of the expansion on more. | ||
+ | change the | ||
+ | * Change the left (non-floating) text from "Value has type: Text. This page defines basic settings needed for SMW. Page Special:Properties lists all available properties in this wiki." to "This page lists all occurrences of the property RETRIEVED LABEL IN BOLD within this platform." | ||
+ | * Move "Page Special:Properties lists all available properties in this wiki." to the editor tools. | ||
+ | --[[User:Gregor Hagedorn|Gregor Hagedorn]] 16:35, 11 October 2012 (CEST) |
Latest revision as of 15:35, 11 October 2012
To gather pages automatically there are many possibilities. What possibility is most suitable?
- set «Class:Imported vocabulary “prefix”»
- set «Class:Use title as class»
- additional parameter in the template,
|categories=cat1
(may have multiple categories) - additional parameter in the template,
|category=cat
(can have only one category)
--Andreas Plank 11:38, 25 September 2012 (CEST)
- I added parameter “categories” --Andreas Plank 11:05, 28 September 2012 (CEST)
Contents
Parameter
“title”, “label”
Technically I use “title” to pass it on to all other formlink titles in the tool box. It is meant to be a general title, not like label. On page Property:dwc:year the title can be “Darwin Core Term” or “Darwin Core Vocabulary” but should not have a title “Year”, the Wiki title is already “dwc:year”. Does it make sense or do I use parameter “title” in a wrong sense? --Andreas Plank 12:33, 28 September 2012 (CEST)
- When I see the input for Title on the "Property:dwc:year" page, I think of the title for that individual resource and not a general category such as "Darwin Core term". I am not sure what is meant by pass it on to other formlink titles...? --Dag Endresen 14:16, 28 September 2012 (CEST)
- Maybe "heading" would be more appropriate instead of "title" --Andreas Plank 15:10, 9 October 2012 (CEST)
- I believe much of the requirement, i.e. to provide context to a property, can best be fullfilled by retrieving the concepts schemes as defined in the concept template associated with the current property in the article namespace. The same applies to the label. I find it useful to retrieve this information and display it on the property page, but I would rather like not to duplicate any user-entered information in article versus property namespace. I would find it useful if this information (label, schemes) is shown BOTH in in template and form, and in the latter there is an edit-pencil symbol placed behind it, which automatically links to or creates the associated concept page in article namespace. Gregor Hagedorn 15:37, 11 October 2012 (CEST)
Simplify parameter
Some questions/proposals:
|has type= → mandatory (one of SMW Special:Types)
- Can text be made the default if missing? --Gregor Hagedorn 21:08, 6 October 2012 (CEST)
- Form-default is "String", so should it be "has type=String" with some automated checking category?
Done (assumes "String" if not given). --Andreas Plank 10:08, 8 October 2012 (CEST)
- Form-default is "String", so should it be "has type=String" with some automated checking category?
|display units= → used when “has type” is “Quantities” (, separated) |corresponds to= → used when “has type” is “Quantities” (; separated)
- why comma versus semicolon separated? Perhaps provide a link to the smw documentation to help readers understand the functionality. --Gregor Hagedorn 21:08, 6 October 2012 (CEST)
- "corresponds to" can be e.g. "1 W, Watt, Watts; 0.001 kW" so ";" is needed --Andreas Plank 10:08, 8 October 2012 (CEST)
|title= → optional (title, e.g. “Darwin Core term”)
- Remove to reduce potential duplication with Template:Concept in the main article space? --Gregor Hagedorn 21:08, 6 October 2012 (CEST)
- Yes could be removed to avoid confusion, but it would be nice to have some section to what a property page, e.g "Property:germplasm:BreedingEvent" or any other property belongs to. Really remove?
Or should it be called "heading"? --Andreas Plank 10:08, 8 October 2012 (CEST)
- Yes could be removed to avoid confusion, but it would be nice to have some section to what a property page, e.g "Property:germplasm:BreedingEvent" or any other property belongs to. Really remove?
|label= → optional (maps to property: rdfs:label)
- Remove to reduce potential duplication with Template:Concept in the main article space? Can label be automatically be obtained from there? --Gregor Hagedorn 21:08, 6 October 2012 (CEST)
- Can label be automatically be obtained from there? With #ask maybe. If it works, I remove parameter label.
Works with: {{#ask: [[{{PAGENAME}}]] |mainlabel=-|link=none|?skos:prefLabel#prefLabel= |+index=1 |format=list}} --Andreas Plank 10:08, 8 October 2012 (CEST)- If any label, shouldn’t it map to skos:prefLabel? --Andreas Plank 10:46, 8 October 2012 (CEST)
- Can label be automatically be obtained from there? With #ask maybe. If it works, I remove parameter label.
|imported from= → optional (uses imported page by MediaWiki:Smw_import_local-ns-prefix, details see Help SMW import vocabulary)
- Can we have a default here, that if nothing is said it is assumed that the page title is imported? --Gregor Hagedorn 21:08, 6 October 2012 (CEST)
- We could assume an import if {{PAGENAME}} has a ":", e.g. "germplasm:BreedingEvent".
Done. --Andreas Plank 10:08, 8 October 2012 (CEST)
- We could assume an import if {{PAGENAME}} has a ":", e.g. "germplasm:BreedingEvent".
|categories= → optional management categories (, separated list)
- Remove to reduce potential duplication with Template:Concept in the main article space? --Gregor Hagedorn 21:08, 6 October 2012 (CEST)
- So how can we collect then concepts together or separated? Do I have to create an #ask query for getting e.g. all dcterms? I vote against it. You can also use categories to categorize ordinary properties, not used as "concepts" for our terms Wiki. --Andreas Plank 10:08, 8 October 2012 (CEST)
- a) It is always possible to add a manual category at the bottom of a page, i.e. outside of the template. This is good for internal/rare purposes. b) For normal purposes, adding categories to property-namespace bears a high managemnt cost of checking that they are ALL set correctly. I propose a similar solution to the label and scheme: a lookup of the scheme from the Concept template (article namespace) and assign any associated property to this category as well. --Gregor Hagedorn 16:35, 11 October 2012 (CEST)
- So how can we collect then concepts together or separated? Do I have to create an #ask query for getting e.g. all dcterms? I vote against it. You can also use categories to categorize ordinary properties, not used as "concepts" for our terms Wiki. --Andreas Plank 10:08, 8 October 2012 (CEST)
Subproperty of
Remove from template, retrieve from concept template page (concept relation) using ask query to set the smw-property on the Property: page. --Gregor Hagedorn 16:35, 11 October 2012 (CEST)
As floating box
I propose to make the entire table box floating top right like an infobox and trying to make it appear less technical.
- Add the schemes (retrieved by ask query) first, scheme labels in bold.
- Reduce "Has type (SMW) : Text [Show] Hints for this type …" to "Has type : Text [more...]" with "Hints for this type …" and the SMW and type link from left as part of the expansion on more.
change the
- Change the left (non-floating) text from "Value has type: Text. This page defines basic settings needed for SMW. Page Special:Properties lists all available properties in this wiki." to "This page lists all occurrences of the property RETRIEVED LABEL IN BOLD within this platform."
- Move "Page Special:Properties lists all available properties in this wiki." to the editor tools.
--Gregor Hagedorn 16:35, 11 October 2012 (CEST)