W3C home > Mailing lists > Public > public-silver@w3.org > January 2017

Re: Researcher Follow-up Survey design feedback

From: Sarah Horton <shorton@paciellogroup.com>
Date: Thu, 12 Jan 2017 11:14:49 +0000
Message-Id: <2EFD86DC-E5A0-4577-923D-4BB603E8B000@paciellogroup.com>
To: David Sloan <Dsloan@paciellogroup.com>, Silver Task Force <public-silver@w3.org>
Thanks, Dave. If we can get these changes in place today (Thursday) we can do the outreach to research partners by the end of the week.

I don’t have editing access to the survey document. Would whoever does that has time to make updates please respond to the list with an “I got it!” :) and let us know when it’s ready to share?

Thanks!

Best,
Sarah

> On Jan 11, 2017, at 4:24 PM, David Sloan <Dsloan@paciellogroup.com> wrote:
> 
> Hi all
> 
> Jeanne asked me earlier this week for feedback on the initial draft of the Researcher follow-up survey, which I provided, but I’m aware she’s had limited availability to respond in the last couple of days. So I’m sharing my response here in order to speed up for discussion and action.
> 
> General observations
> * We’re not collecting publication data at this stage, just establish willingness to contribute in specific ways, so we don’t need to ask for too much detail on specific projects.
> * People completing this are unlikely to have a W3C account. Will the survey be open to all, or will respondents need to have a W3C account to complete it? It’s possible that registration may place a sufficiently high barrier that may lose us some responses.
> 
> 
> Comments on specific questions
> 
> Q3. is just a Y/N. Suggest we add text to the question:
> We’ll work with you to gather details of your publications at a later stage.
> 
> Q4. Suggested question text:
> Have you produced research data that might be of relevance to Silver's research activity?
> 
> Suggested comment field label:
> Conditions/license for access and reuse
> 
> Q5 Suggested comment field label:
> Comments on publication schedule and topic
> 
> Q6: Remove comment field. Add a “Maybe” option to the current set of answers.
> 
> Q7: I’m assuming branching isn’t supported by this survey tool, hence why we have to expose it to all respondents.
> 
> Suggested question text:
> If you are willing to use Silver research questions or activities as a basis for student projects, please indicate the type of project you would be willing to run:
> 
> Suggested comment field label:
> Please provide details of other types of student project
> 
> Q10 Might need to define “secondary research” or find a better phrase. I wasn’t too sure of it myself in the original research description document.
> 
> Suggested wording of last answer option (rephrase so it’s not a question):
> Other user research projects you think Silver should undertake as part of its research?
> 
> Q11: Hyperlink needs fixed
> 
> Suggested comment field label (using text that currently appears before the Yes/No options):
> If yes, please give details of your difficulties, including alternative conditions under which you’d be prepared to contribute work not already in the public domain.
> 
> 
> Dave
> 
> David Sloan
> 
> UX Research Lead
> The Paciello Group
> dsloan@paciellogroup.com
> 
> CONFIDENTIALITY NOTICE: The information contained in this message may be privileged, confidential and protected from disclosure. If you are not the intended recipient, any use, disclosure, dissemination, distribution or copying of any portion of this message or any attachment is strictly prohibited. If you think you have received this message in error, please notify the sender at the above e-mail address, and delete this e-mail along with any attachments. Thank you.
> 
> 

Sarah Horton
UX Strategy Lead
The Paciello Group
603 252-6052 mobile

This message is intended to be confidential and may be legally privileged. It is intended solely for the addressee. If you are not the intended recipient, please delete this message from your system and notify us immediately. Any disclosure, copying, distribution or action taken or omitted to be taken by an unintended recipient in reliance on this message is prohibited and may be unlawful.
Received on Thursday, 12 January 2017 11:15:19 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:23:49 UTC