-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create Turing-final-report.md #704
Conversation
test toc generation
add toc
@GeorgiaHCA are you happy with this report? Are there changes/additions you would like? |
@Arielle-Bennett @KirstieJane what do you think of the report? Does it cover our needs? |
Thanks @Davsarper! Do you have any more details about what the report requires? There's a whole lot I think could be included if appropriate, including words directly from autistic contributors - I'll compile some thoughts and share! Also in the impact section it says the impact is threefold but there are just 2 impacts listed |
@GeorgiaHCA I think we can make it as we want it to be for the most part, within this type of structure if there is more we want to say go for it (long is not an issue). There is not a rigid set of requirements for the report on Turing's side, I just did not want it to be a burden either |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good so far - a few comments to add!
...ct-documentation/communication/reports/turing-health-quartery-updates/Turing-final-report.md
Outdated
Show resolved
Hide resolved
...ct-documentation/communication/reports/turing-health-quartery-updates/Turing-final-report.md
Outdated
Show resolved
Hide resolved
...ct-documentation/communication/reports/turing-health-quartery-updates/Turing-final-report.md
Outdated
Show resolved
Hide resolved
...ct-documentation/communication/reports/turing-health-quartery-updates/Turing-final-report.md
Outdated
Show resolved
Hide resolved
|
||
The project had four goals: (1) Collect data to improve our understanding of sensory processing in people’s daily lives (2) Allow people to share their experiences and coping strategies to support others (3) Give non-autistic people a way to learn about the experiences of autistic people, allowing them to better understand the challenges and provide better support (4) Allow this data to be used by policy makers and creators of spaces and environments, to improve inclusion for autistic people. | ||
|
||
## Lessons learned |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Have we got any operational lessons learnt from the project management side? Apart from "build in project management time into grants"...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thinking in comment before writing into report:
- This approach ultimately made data management and ethics review processes much more straightforward to answer, nonetheless some of it can be a novelty to reviewers and clash with their usual best practives which made more assurances and explanations necessary
- The project changes in more unexpected ways after community input, which requires a more adaptative approach to managing it. With needs arising or changing along the project
- A project manager or similar figure is useful to convey to the community or collaborators, even researchers, hard lines or policies that must be followed and help them navigate those. This also helps researchers (I hope) focus on engagement and be receptive of their proposals
- Launch of a data collecting website platform: building the platform or research artefact can be somewhat independent of host institutions, but when it comes to going live this needs to be treated not as a research exercise but as a fully fledged platform. This means involving IT, following instutional policies and practices and considering cybersecurity aspects. In instances this could entail penetration testing or as in this project ensuring that is not needed via minimisation and anonymisation of collected data
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added into the report, left out bits and in particular the last item, it felt long enough and also focused on the most important bits
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should capture these internally in the doc hub for PMU though!
...ct-documentation/communication/reports/turing-health-quartery-updates/Turing-final-report.md
Outdated
Show resolved
Hide resolved
...ct-documentation/communication/reports/turing-health-quartery-updates/Turing-final-report.md
Outdated
Show resolved
Hide resolved
...ct-documentation/communication/reports/turing-health-quartery-updates/Turing-final-report.md
Outdated
Show resolved
Hide resolved
...ct-documentation/communication/reports/turing-health-quartery-updates/Turing-final-report.md
Outdated
Show resolved
Hide resolved
...ct-documentation/communication/reports/turing-health-quartery-updates/Turing-final-report.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Arielle-Bennett <[email protected]>
Co-authored-by: Arielle-Bennett <[email protected]>
...ct-documentation/communication/reports/turing-health-quartery-updates/Turing-final-report.md
Show resolved
Hide resolved
…uartery-updates/Turing-final-report.md Co-authored-by: Davsarper <[email protected]>
PR for preparing the final turing report, so far it has just a skeleton