Difference between revisions of "Template talk:PropertyUseTable"
Jump to navigation
Jump to search
m (clarify) |
m (t) |
||
| Line 1: | Line 1: | ||
==Identifying already used 'wanted' subjects== | ==Identifying already used 'wanted' subjects== | ||
| − | At present the list displayed on property pages is in a system format sorted by Subject page and showing just 25 results with a 'more results' link. This makes it tedious to find subjects that are already defined, whether their pages exist or not and risks making | + | At present the list displayed on property pages is in a system format sorted by Subject page and showing just 25 results with a 'more results' link. This makes it tedious to find subjects that are already defined, whether their pages exist or not and risks making many 'wanted' subject pages for the SAME subject idea/page if not made simpler. A sortable table would help solve the problem. This template was intended for use on property pages themselves. The idea being to provide a link to display a table view. The query works fine. However, it appears a separate page for each property needing a table view will be required, so, re-thinking. Ideas? --[[User:Peter|Peter P]] ([[User talk:Peter|talk]]) 11:00, 22 December 2013 (GMT) |
Revision as of 11:13, 22 December 2013
Identifying already used 'wanted' subjects
At present the list displayed on property pages is in a system format sorted by Subject page and showing just 25 results with a 'more results' link. This makes it tedious to find subjects that are already defined, whether their pages exist or not and risks making many 'wanted' subject pages for the SAME subject idea/page if not made simpler. A sortable table would help solve the problem. This template was intended for use on property pages themselves. The idea being to provide a link to display a table view. The query works fine. However, it appears a separate page for each property needing a table view will be required, so, re-thinking. Ideas? --Peter P (talk) 11:00, 22 December 2013 (GMT)
