Query check long transfer delay: Difference between revisions

mNo edit summary
Line 30: Line 30:
{{DT |  
{{DT |  
* Requiring notes to have content is really a very soft error check... do we need to consider something better?  
* Requiring notes to have content is really a very soft error check... do we need to consider something better?  
**maybe just a pop-up message to confirm if correct is enough? I will assume the date time entry has been confirmed to be correct. --[[User:JMojica|JMojica]] 15:16, 2022 February 16 (CST)  }}
**maybe just a pop-up message to confirm if correct is enough? I will assume the date time entry has been confirmed to be correct. --[[User:JMojica|JMojica]] 15:16, 2022 February 16 (CST)   
*** That would be an even softer error check, so might as well keep the notes field one and avoid ask-backs. [[User:Ttenbergen|Ttenbergen]] 08:24, 2022 June 9 (CDT)}}


* There was a suggestion to omit the error if the notes box has a comment. That makes me think: we use this method for other checks, but I don't actually know how powerful it is, since most collectors use notes for all sorts of things, and some will leave the content when they are ready to send. If we are serious about this we might want to require them to put an entry into the tmp field instead. Is it worth adding one more entry to that? Guess it depends partly on how common the scenario is. Thoughts? Ttenbergen 16:44, 2018 June 7 (CDT)
* There was a suggestion to omit the error if the notes box has a comment. That makes me think: we use this method for other checks, but I don't actually know how powerful it is, since most collectors use notes for all sorts of things, and some will leave the content when they are ready to send. If we are serious about this we might want to require them to put an entry into the tmp field instead. Is it worth adding one more entry to that? Guess it depends partly on how common the scenario is. Thoughts? Ttenbergen 16:44, 2018 June 7 (CDT)