Help talk:Automating the work list on composer pages: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 4: | Line 4: | ||
:There is no limit to the number of categories that can be included (i.e., the limit is extremely large with respect to any practical usage). | :There is no limit to the number of categories that can be included (i.e., the limit is extremely large with respect to any practical usage). | ||
:The SortWorks function was originally conceived for composer pages that are simple enough, and that represent the large majority of the composer pages on ChoralWiki. With respect to DPL or other forms of work list automation, SortWorks has the advantage that it is less demanding in terms of server resources. This does not imply that SortWorks must be mandatorily used on all composer pages: if a small fraction of composer pages is automated using DPL or other forms of automation, the overall impact in terms of usage of server resources is small, and therefore the overall system efficiency remains good. Nevertheless, if you think that extending SortWorks with the possibility to exclude specific categories is best from a usability perspective, this can be certainly done. Max a.k.a. [[User:Choralia|Choralia]] ([[User talk:Choralia|talk]]) 06:01, 22 April 2016 (UTC) | :The SortWorks function was originally conceived for composer pages that are simple enough, and that represent the large majority of the composer pages on ChoralWiki. With respect to DPL or other forms of work list automation, SortWorks has the advantage that it is less demanding in terms of server resources. This does not imply that SortWorks must be mandatorily used on all composer pages: if a small fraction of composer pages is automated using DPL or other forms of automation, the overall impact in terms of usage of server resources is small, and therefore the overall system efficiency remains good. Nevertheless, if you think that extending SortWorks with the possibility to exclude specific categories is best from a usability perspective, this can be certainly done. Max a.k.a. [[User:Choralia|Choralia]] ([[User talk:Choralia|talk]]) 06:01, 22 April 2016 (UTC) | ||
:Max, I've been using the new version on several of the bigger composer pages and it works very well, giving a much tidier feel to the page and, I suspect, making the page much less daunting to those new to the site. There have been one or two occasions where having the ability to exclude would have been useful, as Barry suggests, so if it can be done without a great effort, it would be a useful addition.[[User:Jamesgibb|Jamesgibb]] ([[User talk:Jamesgibb|talk]]) 10:14, 22 April 2016 (UTC) | |||
Revision as of 10:14, 22 April 2016
Improvements to SortWorks function
Thank you for allowing multiple categories to be included. Is there a limit to how many categories can be included? Also, is there a way to exclude a category (for example, if I want to include Sacred music, but not Contrafacta)?
I have built several Composer pages using a dpl script that shows the year of publication (for example, William Billings, Daniel Read, Oliver Holden, Jacob French). Are you going to ask me to use SortWorks instead? If so, I would like to rearrange these pages by year. Thanks again — Barry Johnston (talk) 19:28, 21 April 2016 (UTC)
- There is no limit to the number of categories that can be included (i.e., the limit is extremely large with respect to any practical usage).
- The SortWorks function was originally conceived for composer pages that are simple enough, and that represent the large majority of the composer pages on ChoralWiki. With respect to DPL or other forms of work list automation, SortWorks has the advantage that it is less demanding in terms of server resources. This does not imply that SortWorks must be mandatorily used on all composer pages: if a small fraction of composer pages is automated using DPL or other forms of automation, the overall impact in terms of usage of server resources is small, and therefore the overall system efficiency remains good. Nevertheless, if you think that extending SortWorks with the possibility to exclude specific categories is best from a usability perspective, this can be certainly done. Max a.k.a. Choralia (talk) 06:01, 22 April 2016 (UTC)
- Max, I've been using the new version on several of the bigger composer pages and it works very well, giving a much tidier feel to the page and, I suspect, making the page much less daunting to those new to the site. There have been one or two occasions where having the ability to exclude would have been useful, as Barry suggests, so if it can be done without a great effort, it would be a useful addition.Jamesgibb (talk) 10:14, 22 April 2016 (UTC)