Difference between revisions of "Template:Concept Table grouped by Collection 1"
m (refacoring: try to reduce template calls (dcterms:identifier vs. usage of template: Concept to imported URI during inline #ask); added dcterms:identifier) |
m (programmer note on property: terms-internal:summary (as table rows) of concept term) |
||
Line 61: | Line 61: | ||
Pages that have too much template calls can be found in this maintenance [[:category: Pages where template include size is exceeded]]. | Pages that have too much template calls can be found in this maintenance [[:category: Pages where template include size is exceeded]]. | ||
− | Technically this template relies on values generated by [[template: Concept Table grouped by Collection 2]] in [[template: Concept]] to be able to get quick display response time. [[Template: Concept Table grouped by Collection 2]] also produces the actual table layout. On a concept page it sets some thing like: | + | Technically this template relies on values generated by [[template: Concept Table grouped by Collection 2]] in [[template: Concept]] to be able to get a quick display response time. [[Template: Concept Table grouped by Collection 2]] also produces the actual table layout. On a concept page it sets some thing like: |
<pre> | <pre> | ||
Line 129: | Line 129: | ||
-->{{#ask: [[Category:Concept]] [[vann:termGroup::§]] [[vann:termGroup::{{{1|Audubon Core Attribution Vocabulary}}}]] | -->{{#ask: [[Category:Concept]] [[vann:termGroup::§]] [[vann:termGroup::{{{1|Audubon Core Attribution Vocabulary}}}]] | ||
− | | ?terms-internal:summary (as table rows) of concept term = | + | | ?terms-internal:summary (as table rows) of concept term =<!-- the property’s content is generated by template:Concept_Table_grouped_by_Collection_2 in template:Concept --> |
| link=none | | link=none | ||
| mainlabel=- | | mainlabel=- |
Revision as of 11:12, 28 January 2020
This template displays definitions of terms in a table layout grouped by concept collections. It can be and is usually invoked by a previous #ask query.
Contents
Technical Documentation
Parameters
- |1=
- concept collection name
- |limit concepts=
- the limit of concepts to
#ask
for subsequently (default: 500)
Note: that parameter 1 can also be provided by an #ask query wrapping this template (see use case 2).
Example/Usage
Use cases can be:
Use case 1 (to query just one collection)
Template:Concept Table grouped by Collection 1 └─ #ask (for concepts within the given collection) └─ template: Concept Table grouped by Collection 2 (generates table layout)
If you want to display concepts of just one collection (use case 1) use it as follows (here limited to just 2 concepts for this example):
{{Concept Table grouped by Collection 1|Audubon Core Attribution Vocabulary|limit concepts=2}}
… wich results in
Audubon Core Attribution Vocabulary
Concept Name: | ac:attributionLinkURL |
Normative URI | http://rs.tdwg.org/ac/terms/attributionLinkURL |
Label | Attribution Link URL |
Definition | The URL where information about ownership, attribution, etc. of the resource may be found. |
Defined By | http://terms.tdwg.org/wiki/Audubon_Core_Term_List#ac:attributionLinkURL |
Required: No — Repeatable: No | |
Notes: | Audubon Core: This URL may be used in creating a clickable logo. Providers should consider making this link as specific and useful to consumers as possible, e. g., linking to a metadata page of the specific image resource rather than to a generic page describing the owner or provider of a resource. |
Concept Name: | ac:attributionLogoURL |
Normative URI | http://rs.tdwg.org/ac/terms/attributionLogoURL |
Label | Attribution URL |
Definition | The URL of the icon or logo image to appear in source attribution. |
Defined By | http://terms.tdwg.org/wiki/Audubon_Core_Term_List#ac:attributionLogoURL |
Required: No — Repeatable: No | |
Notes: | Audubon Core: Entering this URL into a browser should only result in the icon (not in a webpage including the icon). |
Use case 2 (to query multiple concept collections)
#ask (for multiple concept collections) └─ Template:Concept Table grouped by Collection 1 └─ #ask (for concepts within previous results of concept collections) └─ template: Concept Table grouped by Collection 2 (generates table layout)
If you want to query for multiple concept collections (usecase 2: here in GGBN Data Standard) you can use it with an #ask
-query as follows:
{{#ask: [[Category:Concept collection]] [[skos:inScheme::GGBN Data Standard]] | ? #- | link=none | mainlabel=- | format=template | template=Concept Table grouped by Collection 1 | searchlabel=<i> … see also further results and collections</i> | limit=20 }}
Note that the parameter |limit=20
may be crucial here:
- depending on the concept scheme this means it queries for 20 collections and within those all (up to
|limit concepts=500
) concepts - if there are more results, then at the bottom a link will appear to see further results
- if the concept collection is too large (over 1000 concepts) this template may not be able to show all concepts and you can get a warning like:
Warning: Template include size is too large. Some templates will not be included.
Pages that have too much template calls can be found in this maintenance category: Pages where template include size is exceeded.
Technically this template relies on values generated by template: Concept Table grouped by Collection 2 in template: Concept to be able to get a quick display response time. Template: Concept Table grouped by Collection 2 also produces the actual table layout. On a concept page it sets some thing like:
{{#set: terms-internal:summary (as table rows) of concept term={{#ask: [[{{PAGENAME}}]] |format=template |template=Concept Table grouped by Collection 2 |mainlabel=- |? #- <!-- page name --> |?terms-internal:enLabel #- <!-- english label --> |?terms-internal:enDefinition #- <!-- english definition --> |?terms-internal:enExample #- <!-- english example --> |?terms-internal:enNote #- <!-- english notes --> |?rdfs:isDefinedBy #- <!-- the is definded by --> |?dcterms:identifier #- <!-- the URI --> }} }}