{"id":631,"date":"2009-06-22T19:16:39","date_gmt":"2009-06-22T19:16:39","guid":{"rendered":"http:\/\/software.sil.org\/wesay\/?p=631"},"modified":"2017-04-24T19:37:34","modified_gmt":"2017-04-24T19:37:34","slug":"more-control-over-missing-info-tasks","status":"publish","type":"post","link":"https:\/\/software.sil.org\/wesay\/more-control-over-missing-info-tasks\/","title":{"rendered":"More Control Over \u201cMissing Info\u201d Tasks"},"content":{"rendered":"<p>WeSay has always had Tasks which would show you just the words that needed some more information in a particular field.  However, the selection of which entries to show was pretty blunt:  if the field had an empty slot in any of its multiple writing systems, the task would show that entry.  This meant that you couldn\u2019t easily set up WeSay for a user who, for example, just wanted to add vernacular definitions where English ones had already been entered.<\/p>\n<p>In another case, we might want to set a user up to add voice recordings of example sentences. But the task should only show example sentences where someone had previously entered in the example text.<\/p>\n<p>The latest development release (0.5 build 2000) addresses this.  When you first create a project, tasks are configured to have the same behavior as before: an entry will be chosen if <em>any<\/em> of the writing systems assigned to that field are empty. <a href=\"\/wp-content\/uploads\/sites\/35\/2017\/04\/image-thumb-tasks.png\" rel=\"lightbox\"><br \/>\n<img decoding=\"async\" src=\"\/wp-content\/uploads\/sites\/35\/2017\/04\/image-thumb-tasks.png\" alt=\"Set up tasks for the user\" title=\"Set up tasks for the user\" \/><br \/>\n<\/a><\/p>\n<p>You can now limit the task to filling in the vernacular (<em>gaw<\/em>, in this example):  <a href=\"\/wp-content\/uploads\/sites\/35\/2017\/04\/20090619-142237250-thumb.png\" rel=\"lightbox\"><br \/>\n<img decoding=\"async\" src=\"\/wp-content\/uploads\/sites\/35\/2017\/04\/20090619-142237250-thumb.png\" alt=\"\" \/><br \/>\n<\/a><\/p>\n<p>In addition, we can limit the task to only those entries where some other writing system has already been filled in: <a href=\"\/wp-content\/uploads\/sites\/35\/2017\/04\/20090619-142111809-thumb.png\" rel=\"lightbox\"><br \/>\n<img decoding=\"async\" src=\"\/wp-content\/uploads\/sites\/35\/2017\/04\/20090619-142111809-thumb.png\" alt=\"\" \/><br \/>\n<\/a><\/p>\n<p>Thanks, <a href=\"http:\/\/www.ideophone.org\" title=\"\" class=\"external\" target=\"_blank\" rel=\"noopener\">Mark<\/a>, for taking the time to submit this request.  We would appreciate any feedback you can give us on this feature.  Does it work well for you?<\/p>\n<p>The obvious next step would be to add a way make duplicates of some tasks, so that you could have both an \u201cAdd Examples\u201d and an \u201cAdd Example Recordings\u201d task. This is now possible by editing the <em>.wesayconfig<\/em> file in a text editor. If you want to know how, <a href=\"..\/support#wpcf7-f420-o1\">set me an message<\/a>. That will tell me how much demand there is for it, and if there\u2019s enough, we\u2019ll make it easier.<\/p>\n<div class=\"top border\"><a href=\"#top\">top<\/a><\/div>\n","protected":false},"excerpt":{"rendered":"<p>WeSay has always had Tasks which would show you just the words that needed some more information in a particular field. However, the selection of which entries to show was pretty blunt: if the field had an empty slot in any of its multiple writing systems, the task would show that entry. This meant that [&hellip;]<\/p>\n","protected":false},"author":26,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[10],"tags":[],"class_list":["post-631","post","type-post","status-publish","format-standard","hentry","category-news"],"acf":[],"_links":{"self":[{"href":"https:\/\/software.sil.org\/wesay\/wp-json\/wp\/v2\/posts\/631","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/software.sil.org\/wesay\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/software.sil.org\/wesay\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/software.sil.org\/wesay\/wp-json\/wp\/v2\/users\/26"}],"replies":[{"embeddable":true,"href":"https:\/\/software.sil.org\/wesay\/wp-json\/wp\/v2\/comments?post=631"}],"version-history":[{"count":3,"href":"https:\/\/software.sil.org\/wesay\/wp-json\/wp\/v2\/posts\/631\/revisions"}],"predecessor-version":[{"id":634,"href":"https:\/\/software.sil.org\/wesay\/wp-json\/wp\/v2\/posts\/631\/revisions\/634"}],"wp:attachment":[{"href":"https:\/\/software.sil.org\/wesay\/wp-json\/wp\/v2\/media?parent=631"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/software.sil.org\/wesay\/wp-json\/wp\/v2\/categories?post=631"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/software.sil.org\/wesay\/wp-json\/wp\/v2\/tags?post=631"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}