# data[].attributes.body
I have currently never pre-registered a project. I actually am not sure why, like many people involved in research I have a few ideas that have been circulating in the background that would be perfect for pre-registration.

In the next few hours I could pre-register one of my upcoming research projects. Ultimately this would set my project up for success by thinking about the potential openness of the final project/research. It would help with the creation of a planning template for this project and potentially future projects (which is something that I struggle with).

Mostly there is no reason why I haven't pre-registered a project, it just has ultimately never crossed my mind.

# data[].attributes.body
In my research career I have not taken any steps towards Open Research. The reason behind this is a complete lack of awareness around Open Research principles, concepts and the impact on replicability. In my time in research these ideas have never come up, which in hindsight is shocking. So, rather then thinking about how to apply this to my research right now, I am more focused on bringing some of these concepts in to my lab courses. In the short term, I need to explore more tools (such as protocols.io) and think about how I can implement these in my courses. Furthermore, this will afford an opportunity to teach students about Open Research ideas (even if only at a surface level), tools, and how they can relate to improved transparency and the replication crisis.

# data[].attributes.body
1. I will deposit data in a trusted institutional repository ex: UBC Dataverse.

2. I will ensure ethical compliance before sharing by reviewing participant consent forms to confirm that data sharing is permitted. If needed, I will anonymize or de-identify the data to protect participants’ privacy. I will consult UBC's office of research ethics if needed.

3. I will create and publish a data documentation file describing variables, collection methods, coding schemes and transformations, if any.

# data[].attributes.body
Since I'm just writing my dissertation now, I am not really in the mindset of pre-registering projects or figuring out what should or should not be open. I really just want to get this degree done! Also, like another paddle it post, it never really crossed my mind that the research process itself would be open. I've always thought about it in terms of the output, or educational materials. So this is giving me a lot of things to think about as I move forward, and start my research career with open processes in mind, rather than trying to retrofit it on something that I am already quite familiar with.

# data[].attributes.body
I'm not a researcher specifically but this unit has made me consider how I can adopt open research principles into how I communicate and share the different components of my work in the future. Even if this work isn't currently public, I will also think about ways that closed work might be more easily repurposed to be more open and therefore useful to others.

Some example steps:

Re-consider default reliance on proprietary software at the beginning of each project; think of the 'lifecycle' of the materials I will be producing over the course of the project, and what labour would be required to liberate it from a locked environment.

Create a data management plan for project to account for what kinds of files will be produced, how they will be used, who will have access to them, and what the stages of the information's lifecycle will be once 'archived' and/or published.

Apart from project files themselves, create a metadata/read-me file/codebook that outlines terminology, legends, and codes that someone else would need to first understand or contribute to the project.

# data[].attributes.body
I have never pre-registered a study that I've done, and was honestly unaware that it was a thing you could do. Now that I am aware that it is a possibility, I am going to learn more about this and keep it in mind when I begin to work on a new project. This undoubtedly help my project succeed and will also be another way to keep on track, as well as brainstorm ways that the project could contribute to the open research field.

# data[].attributes.body
So far, I have not engageed in Open Research. I took this course to learn principles to be able to apply this knowledge to future projects. One thing that I would do now to prepare for having a more open research process is rethinking my organization practices. For example, I have a study with many folders and study files, and there is no naming convention. So if anyone else wanted to navigate these files it would be challenging. I would start by giving the study a code and integrating a naming structure. From there, the next step would be to start an @ReadMe file so that anyone who is trying to navigate the folder can find the relevant files easily.

# data[].attributes.body
I am not a researcher, but this unit has made me reflect on the open access tools I have used in the past and the ones I have missed out on! I would have loved to use terracotta when I was a TA and building canvas courses from a very early stage. Now I am more focused on open workflow practices to ensure institutional knowledge is passed down in a way that makes the work reproducible and replicable. I will be integrating README files and considering how files are stored to ensure long-term accessibility and retention.

# data[].attributes.body
I would like to start making my research protocols more open, to allow for others to reproduce my work. The protocols.io platform seems like a great tool for this. To get started I could:

Review protocols in my discipline on protocols.io to get familiar with style and formatting

Identify my own protocols that could be included in this database as a supplement to our own published methods sections

# data[].attributes.headline
Bridging the Gap Between IT Practice and Research

# data[].attributes.subject
Bridging the Gap Between IT Practice and Research

# data[].attributes.body
I’m not a researcher, but in my dual role as a Systems Analyst and Quality Assurance professional, I see I can use several OSF tools that could support different aspects of my daily work—such as organizing project documentation, maintaining versioned specifications and test cases, sharing with stakeholders, integrating with GitHub, and creating traceability.

However, I took this course because I’m exploring the possibility of transitioning into a research role—particularly in fields like information systems, human-computer interaction (HCI), or educational technology. This unit has provided valuable information and made me reflect on the importance of open research and its potential to drive collaboration and transparency in the field.

# data[].attributes.body
At my current job, I create documents such as guidelines and policies. I’ve never considered making them openly available, but I realize they could be useful for others in similar roles. To move forward, I would take the following steps: 1) review Creative Commons license options, 2) explore platforms for hosting the documents, and 3) consult with unit management for review and feedback.

# data[].attributes.body
I was new to learning about Open Workflows. In my previous research, our data is Open Access, but each stage of our process and the tools used is not shared beyond the Methods section. I now know that having an Open Workflow helps with reproducibility, which is a key goal of my work. In my research, although we used R, which is nonproprietary, our R code was not shared, hindering reproducibility. Now that I know about README files, I would like to use them in the future. Moving forward, I'll look more at how my work can be Open, reproducible, and replicable. One action would be to look further into Workflow best practices.

# data[].attributes.body
I haven’t shared any of my thematic analysis codebooks or coding decisions publicly.

If I took a few hours I could likely do the following to change that:

Upload an anonymized version of one focus group coding framework (e.g., initial codes + definitions) to the OSF project I created as part of this course.

Write a brief overview of my coding process, including how codes were developed, discussed, and refined.

Take a look through existing OSF projects in qualitative research to see how others are documenting and sharing their analytic processes and see if there is anything I can take away to improve my processes.

# data[].attributes.body
Languages, literacies and education are the realms for which I really hope to delve into learning, teaching, and research in order to contribute my expertise. While studying and teaching at Simon Fraser University, it was really rewarding and valuable to join our research team and work for the Faculty of Education and Centre for English Language Learning, Teaching and Research to embark upon research to provide the best programs, services and supports. My favourite are the programs, services and supports offered by the Student Learning Commons, Research Commons ("SLC Support", 2014) and Centre for Educational Excellence, which I really hope to introduce for promoting inclusive supports, and academic, career and educational excellence.

Reference List

SLC Support for EAL Students - Updated Sept. 2014. (2014, October 7). Retrieved August 31, 2025, from https://canvas.sfu.ca/courses/13718/files/1854554?module_item_id=244352

Christine Pan

# data[].attributes.body
Having worked on several papers in the past, the most "preregistration" adjacent task I had done was REB applications. Knowing about tools like OSF now, I will be preregistering my protocols more.