Open WIN Community issueshttps://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues2024-02-18T13:45:55+00:00https://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/1Add documentation on open access publishing2024-02-18T13:45:55+00:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.ukAdd documentation on open access publishingYing-Qiu ZhengYing-Qiu Zhenghttps://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/2rename "Open Neuroimaging Working Group" to "Open WIN Steering Group"2022-03-14T22:43:47+00:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.ukrename "Open Neuroimaging Working Group" to "Open WIN Steering Group"https://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/3add all-contributors bot2022-10-11T19:45:54+01:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.ukadd all-contributors bothttps://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/4transfer open data wiki pages from redmine to github2022-01-21T19:34:20+00:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.uktransfer open data wiki pages from redmine to githubhttps://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/5Port GitHub Pages to GitLab2021-07-15T16:18:06+01:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.ukPort GitHub Pages to GitLabhttps://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/6Readability - action findings of accessibility report2023-02-27T10:15:43+00:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.ukReadability - action findings of accessibility reportJuju FarsJuju Farshttps://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/7[documentation] emojis2022-03-14T22:44:14+00:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.uk[documentation] emojishttps://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/8Creating an open-science news tab2021-08-18T11:13:56+01:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.ukCreating an open-science news tabhttps://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/9Quick guides for different use cases2021-10-21T11:12:12+01:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.ukQuick guides for different use caseshttps://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/10[documentation] Fix typos2022-01-21T19:34:05+00:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.uk[documentation] Fix typoshttps://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/11[documentation] Benefits of Open Research2022-07-06T11:11:19+01:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.uk[documentation] Benefits of Open Researchhttps://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/12Aim and principles of the community2021-07-15T16:18:26+01:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.ukAim and principles of the communityhttps://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/13Are the personas and pathways representative?2021-07-15T16:18:38+01:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.ukAre the personas and pathways representative?https://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/14Site as an effective advert for the community2021-07-15T16:18:44+01:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.ukSite as an effective advert for the communityhttps://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/15[documentation] Add info about open source licensing of software2021-09-29T10:22:47+01:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.uk[documentation] Add info about open source licensing of softwareThe official line on open source licensing your software is here: https://researchsupport.admin.ox.ac.uk/reporting/openaccess#collapse393821
I’ve spoken with OUI about this recently, and they say that in practical terms if you think you...The official line on open source licensing your software is here: https://researchsupport.admin.ox.ac.uk/reporting/openaccess#collapse393821
I’ve spoken with OUI about this recently, and they say that in practical terms if you think your code might have commercial value then you should get approval from your HoD. I’d like to get in place some blanket approval from WIN HoDs which means we don’t have to go to them for approval in every instance, especially if it's lilt chances of code for analysis cf. whole software packages.
The “safest” option (in terms of protecting University IP) would be to use a CC-BY-NC-SA-2.0, so it cannot be used for commercial purposes, with a “share alike” to stop anyone else passing it on for commercial use. You could add a note at the top of the license requesting that anyone interested in commercial use should contact you.
For the Copyright notice, you should include:
“Copyright, 2021, University of Oxford. All rights reserved"
As per the examples here: https://innovation.ox.ac.uk/university-members/commercialising-technology/ip-patents-licenses/software-copyright/.https://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/16add join link to win-open-data mailing list2021-07-16T11:06:58+01:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.ukadd join link to win-open-data mailing listSubmitted a request to create win-open-data@maillist.ox.ac.uk for external users to subscribe to updates (15/07/21).
> Logged: Support Call# 11111087 - List "win-open-data@maillist.ox.ac.uk" creation request from cassandra.gouldvanpraag...Submitted a request to create win-open-data@maillist.ox.ac.uk for external users to subscribe to updates (15/07/21).
> Logged: Support Call# 11111087 - List "win-open-data@maillist.ox.ac.uk" creation request from cassandra.gouldvanpraag@psych.ox.ac.uk
Also expect mailing list subscribe to be included in data availability statements for papers currently being prepared for submission.
When request has been approved update the following:
* [ ] link for joining
* [ ] add suggested data availability statement wordingCassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.ukCassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.ukhttps://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/17[documentation] Creating a doi with zenodo2022-01-28T10:00:36+00:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.uk[documentation] Creating a doi with zenodoWrite section about how to create a doi for a gitlab repository using zenodo. Basic stages below.
First time creating a doi for this project:
- [x] 1. Have the repository exist on GitLab (and/or DigitalBrainBank)
- [x] 2. In [zenodo](h...Write section about how to create a doi for a gitlab repository using zenodo. Basic stages below.
First time creating a doi for this project:
- [x] 1. Have the repository exist on GitLab (and/or DigitalBrainBank)
- [x] 2. In [zenodo](https://zenodo.org), log in or create an account. Go to "[new upload](https://zenodo.org/deposit/new)" and add details about your material. Click the "resave doi" button to get the doi which will be issued by zenodo.
- [x] 3. Copy this doi into your README for your project on GitLab, or other documentation. Include this in a section entitled "How to cite this material".
- [x] 4. Make a “[release](https://stackoverflow.com/questions/29520905/how-to-create-releases-in-gitlab)” of the repository. Add a note to mark this as the initial release.
- [x] 5. Download the repository from GitLab (download icon on the repository home page) as a .zip or other compressed file type.
- [x] 6. Upload the compressed file collection to zenodo.
- [x] 7. Finalise the zenodo entry will all contributors including their ORDIC IDs. Include a link to the GitLab repository.
- [x] 8. Set an embargo period for the material if it is not yet publicly available on GitLab.https://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/18[documentation] Record gifs for gitlab tutorials2024-02-16T15:19:51+00:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.uk[documentation] Record gifs for gitlab tutorialsrecord and incorporate gifs into gitlab tutorialsrecord and incorporate gifs into gitlab tutorialsCassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.ukCassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.ukhttps://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/19[documentation] How to access gitlab once left Oxford2024-02-18T13:47:00+00:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.uk[documentation] How to access gitlab once left OxfordGuide for people to access their existing repositories once they have left Oxford, and create new repositories for work remaining.
Proposed process (to be confirmed):
1. Ask IT to create a guest (external) account
2. List the existing r...Guide for people to access their existing repositories once they have left Oxford, and create new repositories for work remaining.
Proposed process (to be confirmed):
1. Ask IT to create a guest (external) account
2. List the existing repositories which you would like to be added too
3. Provide the proposed name of any new repositories which you would like created
4. IT adds new guest account as owner/maintainer on repost listed in 2 and 3.
To do:
- [x] Confirm process with IT
- [ ] Add this to community pages https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/tools/gitlab/Ying-Qiu ZhengYing-Qiu Zhenghttps://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/20[documentation] Make gitlab guides more prominent2022-10-11T19:51:43+01:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.uk[documentation] Make gitlab guides more prominentThink about where the gitlab tutorials should be. They are a bit hidden at the bottom of tools now. Perhaps "git and gitlab" should be their own section so they are really easy to find when people are on-boarding. Could also nest all the...Think about where the gitlab tutorials should be. They are a bit hidden at the bottom of tools now. Perhaps "git and gitlab" should be their own section so they are really easy to find when people are on-boarding. Could also nest all the pages under "tutorials" then... :)
To Do:
- [x] Move gitlab etc tutorials to its own section (alongside tools)
- [x] Add a gitlab sticker on how page
- [x] Think about whether stuff like "what to include in your repo" should be in the gitlab section rather than analysis. All gitlab mentions in other section should then link back to the main gitlab area.https://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/21[task] Get blanket approval for open source licensing of software2021-09-06T21:32:05+01:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.uk[task] Get blanket approval for open source licensing of software[University recommendations on open source licensing](https://researchsupport.admin.ox.ac.uk/reporting/openaccess#collapse393821) requires permission from HoD to apply open source license to software.
If we can shift responsibility from...[University recommendations on open source licensing](https://researchsupport.admin.ox.ac.uk/reporting/openaccess#collapse393821) requires permission from HoD to apply open source license to software.
If we can shift responsibility from HoD to Heidi for approval, then we can get a blanket approval statement around "we approve in principle open source licensing (suggest MIT), if you are reasonably confident that your resources have limited immediate commercial potential. If you are unsure of the commercial potential of your resources, please speak with OUI at one of their drop-ins" **Speak to Heidi about this, and OUI to shift responsibility to Heidi from HoD.
- [ ] Establish with Oxford University Innovation that Head of WIN can act as Head Of Department in granting permission for research software to be given an open source license.
- [ ] Request from Head of WIN that they grant a blanket approval of open source licensing, with the assumption that the PI has explored commercial applications. This negates the need for hypothetical requests for each new material.
- [ ] This about how to incorporate the above in practice. Where is the approval communicated? How is it applied? Do we need to host a signed letter?https://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/22[website] Update CONTIBUTING.md for gitlab and where milestones are hosted.2021-09-08T11:18:14+01:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.uk[website] Update CONTIBUTING.md for gitlab and where milestones are hosted.CONTIBUTING.md needs to be updated for move of repo to gitlab.
Also an opportunity to revisit milestones, roadmap, what we're working on etc.CONTIBUTING.md needs to be updated for move of repo to gitlab.
Also an opportunity to revisit milestones, roadmap, what we're working on etc.https://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/23[website] Make it clear that communication channels (inc gitlab issues) are i...2022-05-06T15:07:02+01:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.uk[website] Make it clear that communication channels (inc gitlab issues) are internal only- [x] slack, mailing list and gitlab issues are internal only. Make this clear.
Thank about a channel for external users to stay up to date or contribute.
- [x] update CONTRIBUTING.md with a route for external users- [x] slack, mailing list and gitlab issues are internal only. Make this clear.
Thank about a channel for external users to stay up to date or contribute.
- [x] update CONTRIBUTING.md with a route for external usershttps://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/24[task] Launch Ambassador program2021-10-21T08:48:31+01:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.uk[task] Launch Ambassador programThings to prep to get the Ambassadors program ready to launch!
- [x] Review and edit existing material about Ambassadors on the website
- [x] Review Jono Bacon material
- [x] Review CSCCE material on [Champions programs](https://zenodo...Things to prep to get the Ambassadors program ready to launch!
- [x] Review and edit existing material about Ambassadors on the website
- [x] Review Jono Bacon material
- [x] Review CSCCE material on [Champions programs](https://zenodo.org/record/5275270#.YUsXOC2ZNBw)
- [x] Review Ambassadors strategy docs make with Carinne. Incorporated into [goals.md](https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/ambassadors/goals/)Launch Ambassadors ProgramCassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.ukCassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.ukhttps://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/25[documentation] What to think about when writing documentation for Open WIN t...2022-03-02T13:10:57+00:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.uk[documentation] What to think about when writing documentation for Open WIN toolsWhen writing documentation for the Open WIN tools, it may be useful to consider and explicitly document the following:
- [ ] Use cases and scenarios
- [ ] How to use the tool, with video and written tutorials
- [ ] How will we users fir...When writing documentation for the Open WIN tools, it may be useful to consider and explicitly document the following:
- [ ] Use cases and scenarios
- [ ] How to use the tool, with video and written tutorials
- [ ] How will we users first encounter the tool (for example will a radiographer recommend it)? Do we need to create materials to support the first encounter?
- [ ] What ongoing attention should a user give to their output once it has been shared? How can they reference it and encourage re-use?
- [ ] What incentives would be particularly valuable to users to encourage uptake of this tool?https://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/26Add "neurodiversity" to participation guidelines2022-01-21T19:44:24+00:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.ukAdd "neurodiversity" to participation guidelinesThe [participation guidelines](https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/community/CODE_OF_CONDUCT/#guiding-principles) do not explicitly mention neurodiversity. This should be added toothed list.The [participation guidelines](https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/community/CODE_OF_CONDUCT/#guiding-principles) do not explicitly mention neurodiversity. This should be added toothed list.https://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/27gitlab tutorials - add how to create an account2021-11-03T11:35:30+00:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.ukgitlab tutorials - add how to create an accountThis [tutorial page](https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/gitlab/2-1-starting-gitlab-account/) starts from "use your WIN IT account", but doesn't tell you how to get an account. Add a link to the...This [tutorial page](https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/gitlab/2-1-starting-gitlab-account/) starts from "use your WIN IT account", but doesn't tell you how to get an account. Add a link to the IT Sharepoint page describing how to register for an account.https://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/28Update ambassadors pages to show program selection closed and ambassadors cho...2022-06-15T09:57:13+01:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.ukUpdate ambassadors pages to show program selection closed and ambassadors chosen!- [x] Update pages to close off application process
- [x] Add page about who are ambassadors are, with profile for each.
- [x] Finalise profiles- [x] Update pages to close off application process
- [x] Add page about who are ambassadors are, with profile for each.
- [x] Finalise profileshttps://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/29[documentation] links in gitlab guide are broken2022-01-21T19:33:16+00:00Bernd Taschler[documentation] links in gitlab guide are brokenRelated to #20.
Problem file: [gitlab-tutorials.md](https://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/blob/master/docs/gitlab/gitlab-tutorials.md)
Error message for all main links on https://open.win.ox.ac.uk/page...Related to #20.
Problem file: [gitlab-tutorials.md](https://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/blob/master/docs/gitlab/gitlab-tutorials.md)
Error message for all main links on https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/gitlab/gitlab-tutorials/
(Interestingly, Table-of-contents links at the bottom of the site do work.)https://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/30Create issue templates2022-02-17T12:59:01+00:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.ukCreate issue templatesWe should have some nice issue templates for this project. Have a look through the sort of issues we are creating already and create some templates using [this guide](https://docs.gitlab.com/ee/user/project/description_templates.html)
-...We should have some nice issue templates for this project. Have a look through the sort of issues we are creating already and create some templates using [this guide](https://docs.gitlab.com/ee/user/project/description_templates.html)
- [x] Range of templates defined - one "default" issue felt more manageable for users
- [x] Templates created - see .gitlab/issue_templates/default.mdhttps://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/31Fix broken image paths2022-01-21T19:32:21+00:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.ukFix broken image pathsRelative image paths were broken in a gitlab update... Broken paths need to be moved up one (add "..") to fix. Known broken paths below. Note the "Edit this page on GitLab" link at the bottom of each to be taken directly to it.
- [x] [G...Relative image paths were broken in a gitlab update... Broken paths need to be moved up one (add "..") to fix. Known broken paths below. Note the "Edit this page on GitLab" link at the bottom of each to be taken directly to it.
- [x] [Guiding principles](https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/open-leadership/)
- [x] [Using this repo](https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/using-this-repo/)
- [x] [Open Acquisition](https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/tools/acquisition/)
- [x] [Open Tasks](https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/tools/tasks/)
- [x] [Open Analysis](https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/tools/analysis/)
- [x] [Open Data](https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/tools/data/)
- [x] [External events](https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/events/external/)
- [x] [Atom tutorial](https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/gitlab/1-3-tools-atom/)
- [x] [Basic git commands](https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/gitlab/2-4-starting-git-basics/)
- [x] [Collaborating with a stranger (pull requests)](https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/gitlab/3-2-collaborating-fork-their-repo/)
- [x] [Make a repository](https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/gitlab/4-1-you-make-your-repo/)
- [x] [Make a gitlab pages site](https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/gitlab/4-3-you-make-your-pages-site/)https://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/32Improve instructions for creating SSH key2022-02-04T20:13:43+00:00Verena SarrazinImprove instructions for creating SSH keyThe page https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/gitlab/2-1-starting-gitlab-account/ contains a description for obtaining the SSH key for setting up a Gitlab repository. In the description, there i...The page https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/gitlab/2-1-starting-gitlab-account/ contains a description for obtaining the SSH key for setting up a Gitlab repository. In the description, there is a link to an IT website that contains a list of steps to follow. In our case, only one of the steps is needed, which is confusing for users.
When creating an SSH key for the local computer (as indicated in the “Creating a key” section in this link https://sharepoint.nexus.ox.ac.uk/sites/NDCN/FMRIB/IT/User Guides/SSH.aspx#title11), only need to run $ ssh-keygen -t rsa. Ignore the instructions after “To transfer the public key, use scp…”
Proposed solution:
- [x] Update the instructions to include only the relevant line that needs to be run in the command window ($ ssh-keygen -t rsa),
- [x] link to the IT webpage by saying that more information can be found there (https://sharepoint.nexus.ox.ac.uk/sites/NDCN/FMRIB/IT/User%20Guides/Git.aspx).
- [x] review the instructions for adding the SSH key to the profile settingshttps://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/33Rename "acquisition" to "mr protocols database"2022-03-02T13:09:35+00:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.ukRename "acquisition" to "mr protocols database"Decided name for the acquisition tool is "mr protocols". Make sure this is updated in the community pages.Decided name for the acquisition tool is "mr protocols". Make sure this is updated in the community pages.https://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/34Test issue - OPDC link2022-02-09T12:07:51+00:00Ludovica GriffantiTest issue - OPDC linkCopy-pasting what I wrote in email to Cass, to test the quick link added to the pages
I remember this is something I worked on at the open science hackathon, and I *think* might be about pointing at one of these snippets: • https://git.f...Copy-pasting what I wrote in email to Cass, to test the quick link added to the pages
I remember this is something I worked on at the open science hackathon, and I *think* might be about pointing at one of these snippets: • https://git.fmrib.ox.ac.uk/-/snippets/32 • https://git.fmrib.ox.ac.uk/-/snippets/31they are both set as private so might be the reason why the link is broken. I think I can make them public, but might need a bit of context on how to use them. Matt South helped me out with them, so he might be able to make this case example usefulhttps://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/35Replace ACKNOWLEDGEMENTS.md with CITATION.cff on gitlab "what to include" page2022-04-13T15:09:33+01:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.ukReplace ACKNOWLEDGEMENTS.md with CITATION.cff on gitlab "what to include" page## I'm submitting a ...
> Put an x in the appropriate square brackets
- [ ] bug/error report
- [x] feature request
## What is the current behaviour?
> Please describe the problem you have encountered or the feature/content you would l...## I'm submitting a ...
> Put an x in the appropriate square brackets
- [ ] bug/error report
- [x] feature request
## What is the current behaviour?
> Please describe the problem you have encountered or the feature/content you would like to extend. Please include links to the affected page(s).
The ["What to include on your repo" page](https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/gitlab/repo-include/) currently suggests providing a text descriptor for how you would like this resource to be cited. An evolving standard of best practice is to use the [citation file format (.cff)](https://the-turing-way.netlify.app/communication/citable/citable-cff.html?highlight=cff)
## What is the expected/preferred behaviour?
> Please describe how the problem could be fixed or what additional feature/content could be included.
> If you are able to, you are welcome to submit new content directly via a merge request. This will ensure you are attributed for your suggestion. See this guide on submitting a merge request via GitLab: https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/gitlab/3-2-collaborating-fork-their-repo/
- [x] Replace ACKNOWLEDGEMENTS.md with [CITATION.cff](https://the-turing-way.netlify.app/communication/citable/citable-cff.html?highlight=cff) to the list of items to include in your repository.
- [x] Add an Acknowledgements section to README.md and link to CITATION.cff
## What is the motivation / use case for changing the behaviour?
> Why should we make this fix or include this content?
## Other information
> Please give any additional detail which may be relevant or useful, for example detailed explanation, stacktraces, related issues, links for us to have context.https://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/36[GitLab Pages] basic template2022-02-22T19:53:20+00:00Bernd Taschler[GitLab Pages] basic templateHi,
I've been trying to create a basic template repo that includes the necessary files to publish a repo with GitLab Pages (maybe to be included in future in addition to the existing guide for GitHub pages).
I couldn't find any documen...Hi,
I've been trying to create a basic template repo that includes the necessary files to publish a repo with GitLab Pages (maybe to be included in future in addition to the existing guide for GitHub pages).
I couldn't find any documentation on the intranet, so I tried to reverse-engineer the existing setup for the 'Open WIN Community' repo.
Because the WIN/FMRIB gitlab instance is managed differently than the (main) gitlab.com, there are additional install requirements and dependencies to be sorted out. After some trial and error I got the CI/CD runner compiling everything successfully. However can't get the pages to display at the designated location, i.e. when trying to view the GitLab pages in a browser I get an error saying 'This page can't be reached.'
Checking with the 'Open WIN Community' repo, I noticed that the given URL where the pages are supposed to be served also doesn't work. I.e. accessing from within the repo --> 'Settings' --> 'Pages' --> "Your pages are served under:" https://open-science.pages.fmrib.ox.ac.uk/community/Open-WIN-Community" ... this link doesn't work. In fact, the repo is served at: https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/ instead.
So, I don't understand how the pages are served at a different URL than what the repo thinks it should be:
- Why does the first link above not work?
- How have the existing Community pages been set up?
- What is necessary to serve a different repo with GitLab Pages from within the fmrib/WIN gitlab instance?Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.ukCassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.ukhttps://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/37[documentation] protocols db - format for user guides on gitlab pages2022-03-02T13:05:38+00:00Bernd Taschler[documentation] protocols db - format for user guides on gitlab pagesThe `just-the-docs` theme for jekyll gitlab pages allows only for a maximum of 3 levels in the section hierarchy. For the MR protocols database, the first and second level are already taken by *Open WIN Tools* > *Open MR Protocols*.
Th...The `just-the-docs` theme for jekyll gitlab pages allows only for a maximum of 3 levels in the section hierarchy. For the MR protocols database, the first and second level are already taken by *Open WIN Tools* > *Open MR Protocols*.
This means that the user guides live on the third level (e.g. *Open WIN Tools* > *Open MR Protocols* > *Guide for WIN Users*) and can't have any further subsections.
So I was thinking about a couple of possible options:
1. Publish each guide as a one long, self-contained page.
2. Split off the step-by-step db access guides from other thematically distinct topics (e.g. why make protocols public, how to create a DOI, etc.) and indicate on each page whether this applies to all users or internal users only.
3. Create a pseudo-hierarchy by adding numbered sections in the title of individual pages. For example:
- *Open WIN Tools*
- *Open MR Protocols*
- *1. Guide for WIN Users*
- *1.1 Why make your protocol public*
- *1.2 How to add a DOI*
- *1.3 How to access the database*
- *...*
- *2. Guide for External Users*
- *2.1 How to access the database*
I'm leaning towards option 3 but it might look a bit messy / clumsy. Any preferences or other suggestions?Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.ukCassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.ukhttps://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/38[documentation] Add link to GitLab Pages template2022-05-06T13:50:51+01:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.uk[documentation] Add link to GitLab Pages template## I'm submitting a ...
- [ ] bug/error report
- [x] feature request
## What is the current behaviour?
There are some Jekyll templates for creating GitLab Pages sites, but they are only accessible if you know to look for them.
## Wh...## I'm submitting a ...
- [ ] bug/error report
- [x] feature request
## What is the current behaviour?
There are some Jekyll templates for creating GitLab Pages sites, but they are only accessible if you know to look for them.
## What is the expected/preferred behaviour?
Link the [beautiful Jekyll](https://git.fmrib.ox.ac.uk/open-science/community/beautiful-jekyll) [just-the-docs](https://git.fmrib.ox.ac.uk/open-science/community/just-the-docs) and [basic Jekyll](https://git.fmrib.ox.ac.uk/open-science/community/gitlab_pages_jekyll_template) templates from the [community gitlab pages](https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/gitlab/).
## What is the motivation / use case for changing the behaviour?
Improves accessibility and knowledge sharing
## Other information
Be sure to include details on how to give feedback on the templates, i.e. as issues of MRs on the template repos themselves.https://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/39Upper level links not accessible2022-04-06T11:15:03+01:00Yingshi FengUpper level links not accessible> Thank you for contributing to the Open WIN Community by providing feedback via this GitLab issue.
> Please fill in the details under each of the headings below to give your feedback. You may delete this text when you are done.
Note: F...> Thank you for contributing to the Open WIN Community by providing feedback via this GitLab issue.
> Please fill in the details under each of the headings below to give your feedback. You may delete this text when you are done.
Note: For support requests, please contact cassandra.gouldvanpraag@psych.ox.ac.uk.
## I'm submitting a ...
> Put an x in the appropriate square brackets
- [x] bug/error report
- [ ] feature request
## What is the current behaviour?
> Please describe the problem you have encountered or the feature/content you would like to extend. Please include links to the affected page(s).
- The open WIN community page can only be accessed via open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/ but not any of the upper domain (e.g. open.win.ox.ac.uk, open.win.ox.ac.uk/pages/open-science/community). It could be confusing for users who could like to find the community by typing the weblink.
## What is the expected/preferred behaviour?
> Please describe how the problem could be fixed or what additional feature/content could be included.
> If you are able to, you are welcome to submit new content directly via a merge request. This will ensure you are attributed for your suggestion. See this guide on submitting a merge request via GitLab: https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/gitlab/3-2-collaborating-fork-their-repo/
- The open WIN community page can be directly linked to the root page (i.e., open.win.ox.ac.uk) and the root page should be accessible for users.
## What is the motivation / use case for changing the behaviour?
> Why should we make this fix or include this content?
- To make the open WIN community page more accessible.
## Other information
> Please give any additional detail which may be relevant or useful, for example detailed explanation, stacktraces, related issues, links for us to have context.https://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/40[documentation] GDPR => UK GDPR2022-05-06T14:07:25+01:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.uk[documentation] GDPR => UK GDPR> Thank you for contributing to the Open WIN Community by providing feedback via this GitLab issue.
> Please fill in the details under each of the headings below to give your feedback. You may delete this text when you are done.
Note: F...> Thank you for contributing to the Open WIN Community by providing feedback via this GitLab issue.
> Please fill in the details under each of the headings below to give your feedback. You may delete this text when you are done.
Note: For support requests, please contact cassandra.gouldvanpraag@psych.ox.ac.uk.
## I'm submitting a ...
> Put an x in the appropriate square brackets
- [x] bug/error report
- [ ] feature request
## What is the current behaviour?
documentation currently refers to GDPR. As of 2022 year UK GDPR has passed equivalency testing and is now in use.
## What is the expected/preferred behaviour?
references to "GDPR" throughout the pages should be updated to "UK GDPR"
## What is the motivation / use case for changing the behaviour?
Stay current!
## Other information
[ISO guide](https://ico.org.uk/for-organisations/guide-to-data-protection/guide-to-the-general-data-protection-regulation-gdpr/)https://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/41[documentation] Protocols db administrators guide2022-03-31T10:41:40+01:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.uk[documentation] Protocols db administrators guide## I'm submitting a ...
- [ ] bug/error report
- [x] feature request
## What is the current behaviour?
There is no published administrators guide for the protocols db.
## What is the expected/preferred behaviour?
Detail administrator...## I'm submitting a ...
- [ ] bug/error report
- [x] feature request
## What is the current behaviour?
There is no published administrators guide for the protocols db.
## What is the expected/preferred behaviour?
Detail administrators actions and responsibilities.
To include:
- [ ] Who can be made an administrator (inc. process)
- [ ] What to look for when reviewing open access requests
- [ ] How to contact and communicate accept/deny request. Remembering that the researcher can't edit the entry while it is under review
- [ ] Any other administrator things (e.g. superuser list?)
## What is the motivation / use case for changing the behaviour?
- Sustainability of platform usage
- Will also be useful for the publication supporting the release of the protocols db.
## Other information
See issue [#43 on the tool repo](https://git.fmrib.ox.ac.uk/acquisition/win-protocols-db/-/issues/43)https://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/42[gitlab/github] how to mirror repositories between gitlab and github2022-07-03T11:14:37+01:00Bernd Taschler[gitlab/github] how to mirror repositories between gitlab and githubThere are ways to mirror (and sync) repositories from gitlab to github and vice versa. This is a way of using the strengths of both platforms (e.g. better CI on gitlab, larger community on github, etc.).
The official documentation about...There are ways to mirror (and sync) repositories from gitlab to github and vice versa. This is a way of using the strengths of both platforms (e.g. better CI on gitlab, larger community on github, etc.).
The official documentation about mirroring from gitlab: https://docs.gitlab.com/ee/user/project/repository/mirror/
A useful guide by a developer: https://dev.to/brunorobert/github-and-gitlab-sync-44mn
Quick take-aways:
- Syncing from gitlab to github is easier (apparently can be turned on from settings in a few simple steps).
- Wikis, issues, discussions, boards will not sync between the mirrored repos.https://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/43[website] Add information about how to create and publish interactive figures2022-10-11T19:35:32+01:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.uk[website] Add information about how to create and publish interactive figures## I'm submitting a ...
> Put an x in the appropriate square brackets
- [ ] bug/error report
- [x] feature request
## What is the current behaviour?
Two people have asked me about how to make interactive web-apps to support their pub...## I'm submitting a ...
> Put an x in the appropriate square brackets
- [ ] bug/error report
- [x] feature request
## What is the current behaviour?
Two people have asked me about how to make interactive web-apps to support their publications. We should add this information to the community pages.
## What is the expected/preferred behaviour?
Here is the information I've shared:
## What is the motivation / use case for changing the behaviour?
> Why should we make this fix or include this content?
## Other information
> Please give any additional detail which may be relevant or useful, for example detailed explanation, stacktraces, related issues, links for us to have context.https://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/44[website] import h2mri2023-04-27T23:05:17+01:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.uk[website] import h2mri## I'm submitting a ...
> Put an x in the appropriate square brackets
- [ ] bug/error report
- [x] feature request
## What is the current behaviour?
In 2018-2020, Cass wrote a guide on open science MRI data collection and analysis bes...## I'm submitting a ...
> Put an x in the appropriate square brackets
- [ ] bug/error report
- [x] feature request
## What is the current behaviour?
In 2018-2020, Cass wrote a guide on open science MRI data collection and analysis best practices for [PERL](https://www.google.com/search?client=safari&rls=en&q=oxford+perl&ie=UTF-8&oe=UTF-8). There is some content which could be usefully incorporated into the Community Pages.
## Action to take
Import relevant sections of [https://git.fmrib.ox.ac.uk/cassag/h2mri](https://git.fmrib.ox.ac.uk/cassag/h2mri).
To be considered:
- [x] What "chapters" to include?
- [ ] Where should they go? Analysis? Separate pages on RDM?
- [ ] move the code from git.fmrib...cassag/h2mri to a community repository (perhaps open-science/analysis?
- [ ] flag the known issues with the code! 1) singularity container should not be in there repo (people should pull it using a stated path to the container repo); 2) conda packages should not be in the repo, people should pull them!https://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/45Add links to info about fslpy, data-tree and pipe-tree2022-06-18T09:36:22+01:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.ukAdd links to info about fslpy, data-tree and pipe-tree## I'm submitting a ...
> Put an x in the appropriate square brackets
- [ ] bug/error report
- [x] feature request
## What is the current behaviour?
Some very cool stuff exists on [https://open.win.ox.ac.uk/pages/fsl/fslpy/index.html]...## I'm submitting a ...
> Put an x in the appropriate square brackets
- [ ] bug/error report
- [x] feature request
## What is the current behaviour?
Some very cool stuff exists on [https://open.win.ox.ac.uk/pages/fsl/fslpy/index.html](https://open.win.ox.ac.uk/pages/fsl/fslpy/index.html). Could we link to that from the community pages, e.g. under [Open Analysis](https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/analysis/)?
Also developments on data-tree and pipe-tree would be wonderful to share!
## What is the expected/preferred behaviour?
Submit a merge request to update the [Open Analysis](https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/analysis/) page with some blurbs about (and links to):
1. fslpy and conda installation
2. data-tree
3. pipe-tree
## What is the motivation / use case for changing the behaviour?
Share these developments!
## Other information
> Please give any additional detail which may be relevant or useful, for example detailed explanation, stacktraces, related issues, links for us to have context.https://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/46Community feedback at guidance on pros and cons of sequences2022-07-06T10:52:44+01:00Verena SarrazinCommunity feedback at guidance on pros and cons of sequences
## I'm submitting a ...
> Put an x in the appropriate square brackets
- [ ] bug/error report
- [x] feature request
## What is the current behaviour?
> Please describe the problem you have encountered or the feature/content you would...
## I'm submitting a ...
> Put an x in the appropriate square brackets
- [ ] bug/error report
- [x] feature request
## What is the current behaviour?
> Please describe the problem you have encountered or the feature/content you would like to extend. Please include links to the affected page(s).
After presenting the MR protocol database to my lab, my colleagues suggested that we add a section to the documentation to ask researchers to describe the pros and cons of the sequences.
## What is the expected/preferred behaviour?
> Please describe how the problem could be fixed or what additional feature/content could be included.
> If you are able to, you are welcome to submit new content directly via a merge request. This will ensure you are attributed for your suggestion. See this guide on submitting a merge request via GitLab: https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/gitlab/3-2-collaborating-fork-their-repo/
We have added some new text (commit 3816bfcceb5da160f8edf61a258421d4e2d3f15f) to the documentation in the description section. It would be useful to get feedback from my lab to confirm this meets the requirement.https://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/47[documentation] Interactive web apps2022-10-19T13:12:41+01:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.uk[documentation] Interactive web apps## I'm submitting a ...
> Put an x in the appropriate square brackets
- [ ] bug/error report
- [x] feature request
## What is the current behaviour?
Two different researchers have separately asked for support in creating an interacti...## I'm submitting a ...
> Put an x in the appropriate square brackets
- [ ] bug/error report
- [x] feature request
## What is the current behaviour?
Two different researchers have separately asked for support in creating an interactive web app. Would should publish some information about how to create these on the community pages!
## What is the expected/preferred behaviour?
This issues is to collect that information which I've shared with these researchers. It should next be re-written into something generic and published somewhere. Not sure what topic it would sit under the current structure! Open Data?
## Other information: Central University Support
[Laurence Brown](https://blogs.it.ox.ac.uk/acit-rs-team/team/laurence-brown/) has a lot of experience on this an is willing to give advice/support.
## Other information: Researcher requirements of an interactive web app)
### 1. Interactive table
#### Requirement
> We'd quite like to share a table online as a tool people can interact with and get information from, copy data out of etc (like in an google/xls spreadsheet where you can sort by different columns etc) - it would be not the usual written-up publication format but rather a shared data table summarizing parameters from many previous studies that we have put together.
#### Advice
> You could do this with either a [Jupiter notebook and binder](https://mybinder.org), a [shiny app](https://shiny.rstudio.com) if you’re using R, or a [heroku app](https://www.heroku.com) (free to host as a single app).
>I’ve found [this example](https://the-internet.herokuapp.com/tables) of a data table hosted using heroku, where clicking on the column header sorts the rows (I’m sure you could do more sophisticated things too). [This r-shiny example](https://shiny.rstudio.com/gallery/basic-datatable.html) looks very cool too, and perhaps more what you’re looking for?
> These are the more 'high-tech’ code heavy options, but if you’re not feeling confident going down this route it would still be entirely valid to share it as a nicely commented csv on OSF ([as I have done here](https://osf.io/ery2q/)). Less upfront work for you (and you still get a citable output), but more limited in the end user experience.
### 2. Data simulator
#### Requirement
> We'd like to put up a ‘live’ version of one part of the code in our manuscript – this particular paper would lend itself well to a sort of online simulator that people could run in a browser and play around with, like one of our other colleagues has done here: [http://shapegen.herokuapp.com/](http://shapegen.herokuapp.com/)
#### Advice
> You could do this using a [Jupiter notebook and binder](https://mybinder.org), or a [shiny app](https://shiny.rstudio.com) if you’re using R or a [heroku app](https://www.heroku.com).
> My instinct is the binder option will be less overhead to get it working but potentially less “slick", whereas the heroku app can be prettier (another example here) although may be more work to get started?
#### Response - Researchers
> We prefer the slicker version, like the Heroku app we sent you. Mostly because we think the easier the tool is to use, the more it will be used.
> The only thing is that in our experience, the (free) hosting by Heroku is quite slow, which doesn't help with the user experience. Are you aware of any (paid) services that the university promotes to use?
#### Response - Laurence Brown
> My experience is mostly with Python’s Panel library (https://panel.holoviz.org/index.html), which will let you create small dashboards and apps, including from a Jupyter notebook (A very brief example here in notebook 2D https://github.com/LozRiviera/LAB_Intro_Jupyter)
> There are a number of hosting options, including Heroku, but I succeeded with AWS on their free tier for a while.
https://panel.holoviz.org/user_guide/Server_Deployment.html
> We also have free university hosting of R-Shiny apps (https://idn.it.ox.ac.uk/idn-shiny-service) (I have a small amount of Shiny experience) This has a bit more resource behind it.
> I agree web apps on free resources can be slow. Binder is always a good option, but is on free/donated resources, so again they often have to be frugal. Sometimes this is due to the hosting instance, but it can sometimes be improved by limiting data or options to reduce certain behaviours in the browser.
> There may also be options with Matlab (if that was the original code) and via PowerBI, which the University currently licence.https://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/48[documentation] guide on CRediT2023-02-23T14:14:01+00:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.uk[documentation] guide on CRediT## I'm submitting a ...
- [ ] bug/error report
- [x] feature request
## What is the current behaviour?
Here some draft notes on using CRediT for acknowledging author contributions.
The below needs to be re-written for a general audi...## I'm submitting a ...
- [ ] bug/error report
- [x] feature request
## What is the current behaviour?
Here some draft notes on using CRediT for acknowledging author contributions.
The below needs to be re-written for a general audience and published somewhere.
## Draft CRediT guide
The [CRediT framework](https://casrai.org/credit/) is a useful tool for acknowledging different types of author contributions. This may be particularly relevant if you are publishing non-traditional research outputs, such as data and code.
Using CRediT, you can identify *anyone* who has contributed to the work which went into the object you are publishing, and assign them to any of the roles listed (people can have multiple roles). You can then use [tenzing](https://martonbalazskovacs.shinyapps.io/tenzing/) to create an authorship statement which you add to zenodo. Example of a CRediT statement on [this zenodo entry](https://zenodo.org/record/5826183#.Yo5THC2ZPs0).
As a general rule I’m always super-inclusive on authorship. I don’t think it harms the output to show that the work/efforts of many people made it possible.https://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/49[documentation] Mirroring to GitHub2022-07-03T11:13:31+01:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.uk[documentation] Mirroring to GitHub
## I'm submitting a ...
> Put an x in the appropriate square brackets
- [ ] bug/error report
- [x] feature request
## What is the current behaviour?
It is often beneficial to host material on GitHub, for added external engagement. Th...
## I'm submitting a ...
> Put an x in the appropriate square brackets
- [ ] bug/error report
- [x] feature request
## What is the current behaviour?
It is often beneficial to host material on GitHub, for added external engagement. The recommenced way of doing this is to mirror your GitLab repository to GitHub. We should write guidance on how to do this.
## What is the expected/preferred behaviour?
Link to this guide: https://git.fmrib.ox.ac.uk/help/user/project/repository/mirror/index.mdCassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.ukCassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.ukhttps://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/50Fix typos2023-07-04T09:01:07+01:00Yingshi FengFix typos> Thank you for contributing to the Open WIN Community by providing feedback via this GitLab issue.
> Please fill in the details under each of the headings below to give your feedback. You may delete this text when you are done.
Note: F...> Thank you for contributing to the Open WIN Community by providing feedback via this GitLab issue.
> Please fill in the details under each of the headings below to give your feedback. You may delete this text when you are done.
Note: For support requests, please contact cassandra.gouldvanpraag@psych.ox.ac.uk.
## I'm submitting a ...
> Put an x in the appropriate square brackets
- [x] bug/error report
- [ ] feature request
## What is the current behaviour?
> Please describe the problem you have encountered or the feature/content you would like to extend. Please include links to the affected page(s).
There are a few typos on the community page, suggested by @nym920.
## What is the expected/preferred behaviour?
> Please describe how the problem could be fixed or what additional feature/content could be included.
> If you are able to, you are welcome to submit new content directly via a merge request. This will ensure you are attributed for your suggestion. See this guide on submitting a merge request via GitLab: https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/gitlab/3-2-collaborating-fork-their-repo/
The typos being fixed.
## What is the motivation / use case for changing the behaviour?
> Why should we make this fix or include this content?
## Other information
> Please give any additional detail which may be relevant or useful, for example detailed explanation, stacktraces, related issues, links for us to have context.
We might copy and paste the pages into word for an automatic spelling check, or fix this issue in another session when we have more time.https://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/51[documentation] Add something to the protocols db instructions about sharing ...2022-07-07T13:17:29+01:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.uk[documentation] Add something to the protocols db instructions about sharing custom sequences## I'm submitting a ...
> Put an x in the appropriate square brackets
- [ ] bug/error report
- [x] feature request
## What is the current behaviour?
> Please describe the problem you have encountered or the feature/content you would l...## I'm submitting a ...
> Put an x in the appropriate square brackets
- [ ] bug/error report
- [x] feature request
## What is the current behaviour?
> Please describe the problem you have encountered or the feature/content you would like to extend. Please include links to the affected page(s).
The protocols db instructions assume that we will be sharing standard sequences only. The guidance is incomplete for people who are creating modified/customised sequences as there is an additional layer of contracts required between Oxford, the recipient and Siemens.
## What is the expected/preferred behaviour?
> Please describe how the problem could be fixed or what additional feature/content could be included.
Add a line "if you are intending to openly share a custom sequence, please contact Stuart to arrange a Transfer Agreement and the appropriate approvals from Siemens."
## What is the motivation / use case for changing the behaviour?
> Why should we make this fix or include this content?
to make the documentation appropriate for Physics researchers.https://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/52Links don't work on Open Tasks Pages2022-07-12T12:28:56+01:00Stuart ClareLinks don't work on Open Tasks Pages> Thank you for contributing to the Open WIN Community by providing feedback via this GitLab issue.
> Please fill in the details under each of the headings below to give your feedback. You may delete this text when you are done.
Note: F...> Thank you for contributing to the Open WIN Community by providing feedback via this GitLab issue.
> Please fill in the details under each of the headings below to give your feedback. You may delete this text when you are done.
Note: For support requests, please contact cassandra.gouldvanpraag@psych.ox.ac.uk.
## I'm submitting a ...
> Put an x in the appropriate square brackets
- [x] bug/error report
- [ ] feature request
## What is the current behaviour?
> Please describe the problem you have encountered or the feature/content you would like to extend. Please include links to the affected page(s).
Links on https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/tasks/ for WIN members and external users seem to point to the wrong page. Tried to fix myself, but couldn't work out where the page was. Sorry :(
## What is the expected/preferred behaviour?
> Please describe how the problem could be fixed or what additional feature/content could be included.
> If you are able to, you are welcome to submit new content directly via a merge request. This will ensure you are attributed for your suggestion. See this guide on submitting a merge request via GitLab: https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/gitlab/3-2-collaborating-fork-their-repo/
## What is the motivation / use case for changing the behaviour?
> Why should we make this fix or include this content?
## Other information
> Please give any additional detail which may be relevant or useful, for example detailed explanation, stacktraces, related issues, links for us to have context.https://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/53Roadmap needs updating2022-10-11T19:47:21+01:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.ukRoadmap needs updating## I'm submitting a ...
- [x] bug/error report
- [ ] feature request
## What is the current behaviour?
The [roadmap](http://localhost:4000/pages/open-science/community/Open-WIN-Community/docs/community/roadmap/) is out of date and sh...## I'm submitting a ...
- [x] bug/error report
- [ ] feature request
## What is the current behaviour?
The [roadmap](http://localhost:4000/pages/open-science/community/Open-WIN-Community/docs/community/roadmap/) is out of date and should probably reflect more about the open data portal or what we're working on more broadly.
## What is the expected/preferred behaviour?
Update the roadmap to reflect the project more broadly. Perhaps separate roadmaps for 'community' and 'resources'?https://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/54Meet the Ambassadors 2022-2023 - all information correct?2023-07-04T08:56:12+01:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.ukMeet the Ambassadors 2022-2023 - all information correct?## I'm submitting a ...
> Put an x in the appropriate square brackets
- [x] bug/error report
## What is the current behaviour?
Cass quickly wrote some [stuff to introduce the new ambassadors](https://open.win.ox.ac.uk/pages/open-scienc...## I'm submitting a ...
> Put an x in the appropriate square brackets
- [x] bug/error report
## What is the current behaviour?
Cass quickly wrote some [stuff to introduce the new ambassadors](https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/ambassadors/meet_ambassadors/), but this has not been verified! Also links to some people's departmental pages etc are missing.
## What is the expected/preferred behaviour?
Please review this information and amend as appropriate. Please confirm below if you are happy with all content under your name.
## What is the motivation / use case for changing the behaviour?
This information reflects you, so it should be accurate and consistent with the image your want to show! This is also a useful page which you can use to evidence your engagement with this program (e.g. link to it on your CV), so let's make it good :).
## Confirmed up to date:
- [x] @wym003
- [x] @vyp730
- [x] @pfr545
- [ ] @mtach
- [x] @bpz864https://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/55alternative to Atom text editor2023-07-04T08:54:55+01:00Bernd Taschleralternative to Atom text editor## What is the current behaviour?
The gitlab tutorials are recommending to use the Atom text editor. Unfortunately, Atom has recently been discontinued (see official [blog post](https://github.blog/2022-06-08-sunsetting-atom/)) and alth...## What is the current behaviour?
The gitlab tutorials are recommending to use the Atom text editor. Unfortunately, Atom has recently been discontinued (see official [blog post](https://github.blog/2022-06-08-sunsetting-atom/)) and although people can still use it, it is no longer maintained (i.e. no new security updates, package management stopped working, etc.).
## What is the expected/preferred behaviour?
We should find an alternative and update the community pages accordingly (especially the [Atom tutorial](https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/gitlab/1-3-tools-atom/) page).
## Other information
A potential alternative is sublime text: https://www.sublimetext.com/
Other options: https://stackshare.io/atom/alternativesMiguel FarinhaMiguel Farinhahttps://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/56Update/change issues template2023-02-20T11:29:22+00:00Miguel FarinhaUpdate/change issues template> <p>Thank you for contributing to the Open WIN Community by providing feedback via this GitLab issue.</p>
> <p>Please consider reading out guide on [how to submit an issue in GitLab](https://open.win.ox.ac.uk/pages/open-science/communit...> <p>Thank you for contributing to the Open WIN Community by providing feedback via this GitLab issue.</p>
> <p>Please consider reading out guide on [how to submit an issue in GitLab](https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/CONTRIBUTING/).</p>
> <p>Please fill in the details under each of the headings below to give your feedback. You may delete this text when you are done.</p>
Note: For support requests, please contact cassandra.gouldvanpraag@psych.ox.ac.uk.
## I'm submitting a ...
> Put an x in the appropriate square brackets.
- [ ] bug/error report
- [ ] documentation/typos
- [X] feature request (enhancement)
- [ ] question
## What is the current behaviour?
> Please describe the problem you have encountered or the feature/content you would like to extend.
## Where is the issue?
> Please include links to the affected page(s) and lines or sentences.
## What is the expected/preferred behaviour?
> Please describe how the problem could be fixed or what additional feature/content could be included.
> If you are able to, you are welcome to submit new content directly via a merge request. This will ensure you are attributed for your suggestion. See this guide on submitting a merge request via GitLab: https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/gitlab/3-2-collaborating-fork-their-repo/
Having an issue template that's more intuitive and easier to complete and associated instructions in Open Win Community Pages.
## What is the motivation / use case for changing the behaviour?
> Why should we make this fix or include this content?
Make this simpler to use for non-experienced users.
## Other information
> Please give any additional detail which may be relevant or useful, for example detailed explanation, stacktraces, related issues, links for us to have context.https://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/57[documentation] Add information about deidentifiaction for patient cohorts2023-02-20T12:28:37+00:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.uk[documentation] Add information about deidentifiaction for patient cohorts## Thank you for contributing to the Open WIN Community
## I'm submitting a ...
> Put an x in the appropriate square brackets
- [ ] bug/error report (eg. 404)
- [x] documentation (eg. typos, broken links)
- [ ] feature request (eg. add...## Thank you for contributing to the Open WIN Community
## I'm submitting a ...
> Put an x in the appropriate square brackets
- [ ] bug/error report (eg. 404)
- [x] documentation (eg. typos, broken links)
- [ ] feature request (eg. add GitLab tutorial)
- [ ] question (eg. how does this work?)
## Where is the issue?
> Please include links to the affected page(s) refering to specific lines or sentences.
https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/data/can-i/#deidentification
## What is the issue?
> Please describe the problem you have encountered or the feature/content you would like to extend.
Doesn't include a description of deidentification considerations for patient cohorts, e.g. it may not be possible to make data anonymous if rare cohorts are sampled.
## How do we solve the issue?
> Please describe how the problem could be fixed or what additional feature/content could be included.
Add some text to the deidentification list from line 168 on [docs/data/can-i.md](https://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/blob/master/docs/data/can-i.md?plain=1)
## Anything else?
> Please give any additional detail which may be relevant or useful, for example detailed explanation, motivation, stacktraces, related issues, links for us to have context.
---
## Fix the issue yourself?
If you are able to, you are welcome to submit new content directly via a merge request. This will ensure you are attributed for your suggestion. See this guide on submitting a merge request via GitLab: https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/gitlab/3-2-collaborating-fork-their-repo/https://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/58make open@win.ox.ac.uk the primary contact address2023-02-28T11:34:55+00:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.ukmake open@win.ox.ac.uk the primary contact address## Thank you for contributing to the Open WIN Community
> <p>Please consider reading out guide on [how to submit an issue in GitLab](https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/CONTRIBUTING/).</p>
> <p>...## Thank you for contributing to the Open WIN Community
> <p>Please consider reading out guide on [how to submit an issue in GitLab](https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/CONTRIBUTING/).</p>
> <p>Please fill in the details under each of the headings below to give your feedback. You may delete this text when you are done.</p>
> <p> Note: For support requests, please contact cassandra.gouldvanpraag@psych.ox.ac.uk. </p>
## I'm submitting a ...
> Put an x in the appropriate square brackets
- [ ] bug/error report (eg. 404)
- [x] documentation (eg. typos, broken links)
- [ ] feature request (eg. add GitLab tutorial)
- [ ] question (eg. how does this work?)
## Where is the issue?
> Please include links to the affected page(s) referring to specific lines or sentences.
[Contact page](https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/contact/) and other references to cassamdra.gouldvanpraag@psych.ox.ac.uk
## What is the issue?
> Please describe the problem you have encountered or the feature/content you would like to extend.
Cass' personal email is listed as the primary contact for all enquiries. This would be better handled by a share inbox, to share the learning and outcomes of conversations.
## How do we solve the issue?
> Please describe how the problem could be fixed or what additional feature/content could be included.
Replace appropriate references to cassandra.gouldvanpraag@psych.ox.ac.uk with open@win.ox.ac.uk
## Anything else?
> Please give any additional detail which may be relevant or useful, for example detailed explanation, motivation, stacktraces, related issues, links for us to have context.
---
## Fix the issue yourself?
If you are able to, you are welcome to submit new content directly via a merge request. This will ensure you are attributed for your suggestion. See this guide on submitting a merge request via GitLab: https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/gitlab/3-2-collaborating-fork-their-repo/Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.ukCassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.ukhttps://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/59Report on ambassadors dinner2023-07-04T08:57:04+01:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.ukReport on ambassadors dinner## Thank you for contributing to the Open WIN Community
> <p>Please consider reading out guide on [how to submit an issue in GitLab](https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/CONTRIBUTING/).</p>
> <p>...## Thank you for contributing to the Open WIN Community
> <p>Please consider reading out guide on [how to submit an issue in GitLab](https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/CONTRIBUTING/).</p>
> <p>Please fill in the details under each of the headings below to give your feedback. You may delete this text when you are done.</p>
> <p> Note: For support requests, please contact cassandra.gouldvanpraag@psych.ox.ac.uk. </p>
## I'm submitting a ...
> Put an x in the appropriate square brackets
- [x] feature request (eg. add GitLab tutorial)
## Where is the issue?
> Please include links to the affected page(s) referring to specific lines or sentences.
[Events on community pages](https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/community/events/)
## What is the issue?
> Please describe the problem you have encountered or the feature/content you would like to extend.
Would be nice to include a short write up on the Ambassadors dinner, with photos and chairs notes (see [ambassadors comms folder](https://git.fmrib.ox.ac.uk/open-science/community/open-win-ambassadors/-/tree/master/comms). This is to advertise how nice the event was, and as something to work from for next time :)
## How do we solve the issue?
> Please describe how the problem could be fixed or what additional feature/content could be included.
Write up a short report of the day. Can be narative and general.
## Anything else?
> Please give any additional detail which may be relevant or useful, for example detailed explanation, motivation, stacktraces, related issues, links for us to have context.
---
## Fix the issue yourself?
If you are able to, you are welcome to submit new content directly via a merge request. This will ensure you are attributed for your suggestion. See this guide on submitting a merge request via GitLab: https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/gitlab/3-2-collaborating-fork-their-repo/Peter DoohanPeter Doohanhttps://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/60Update links to WIN intranet when things move over from Sharepoint2023-07-04T08:57:58+01:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.ukUpdate links to WIN intranet when things move over from Sharepoint## Thank you for contributing to the Open WIN Community
## I'm submitting a ...
> Put an x in the appropriate square brackets
- [x] documentation (eg. typos, broken links)
## Where is the issue?
> Please include links to the affected ...## Thank you for contributing to the Open WIN Community
## I'm submitting a ...
> Put an x in the appropriate square brackets
- [x] documentation (eg. typos, broken links)
## Where is the issue?
> Please include links to the affected page(s) referring to specific lines or sentences.
Check accross all community pages.
## What is the issue?
> Please describe the problem you have encountered or the feature/content you would like to extend.
WIN Intranet content will be moved from Sharepoint at the end of March. Some links on the community pages will need to be updated. Links to university Sharepoint pages will also be moved.
## How do we solve the issue?
> Please describe how the problem could be fixed or what additional feature/content could be included.
- [ ] Search across whole project for "https://sharepoint.nexus.ox.ac.uk/"
- [ ] Find replacement pages on new intranet
- [ ] Update links
## Anything else?
> Please give any additional detail which may be relevant or useful, for example detailed explanation, motivation, stacktraces, related issues, links for us to have context.
Cass and @stuart will communicate when new pages are live. Try to replace as quickly as possible to keep community pages current.
---
## Fix the issue yourself?
If you are able to, you are welcome to submit new content directly via a merge request. This will ensure you are attributed for your suggestion. See this guide on submitting a merge request via GitLab: https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/gitlab/3-2-collaborating-fork-their-repo/https://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/61Add info on sharing of data collected under "Technical Development" SOP2023-03-30T11:15:02+01:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.ukAdd info on sharing of data collected under "Technical Development" SOP## I'm submitting a ...
> Put an x in the appropriate square brackets
- [ ] bug/error report (eg. 404)
- [ ] documentation (eg. typos, broken links)
- [x] feature request (eg. add GitLab tutorial)
- [ ] question (eg. how does this work?...## I'm submitting a ...
> Put an x in the appropriate square brackets
- [ ] bug/error report (eg. 404)
- [ ] documentation (eg. typos, broken links)
- [x] feature request (eg. add GitLab tutorial)
- [ ] question (eg. how does this work?)
## Where is the issue?
The [can I share data: ethics](https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/data/can-i/#ethics)
## What is the issue?
No details are available for data acquired under the [Technical Development SOP](https://sharepoint.nexus.ox.ac.uk/sites/NDCN/FMRIB/Shared%20Documents/SOP_Technical_Development_Scanning.pdf)
## How do we solve the issue?
Add the following (maybe a seperate drop down under ethics):
-----
From [SOP OHBA_009_V1 004-V4 (FMRIB)](https://sharepoint.nexus.ox.ac.uk/sites/NDCN/FMRIB/Shared%20Documents/SOP_Technical_Development_Scanning.pdf)
Data acquired under the Technical developmnent SOP may be published as long as:
1. No additional ethical approval was required (see section 4.1)
2. The data was not acquired to develope a sequence to be used in aother study which has or will have seperate ethical approval.
3. The data was not acquired for the purposes of training other researchers or scanner operators.
In all cases, this data may only be shared if it it "completely anonymised". Examples of completely anonymous data include:
- Restructed field of view (i.e. not a whole brain)
- B1 data
- B0 data
- Low resolution reference images (e.g. 6.4 mm isotropic) acquired to support B1 maps.
Please contact open@win.ox.ac.uk to discuss whether other data types can be considered completely anonymous.
------
## Anything else?
> Please give any additional detail which may be relevant or useful, for example detailed explanation, motivation, stacktraces, related issues, links for us to have context.
---
## Fix the issue yourself?
If you are able to, you are welcome to submit new content directly via a merge request. This will ensure you are attributed for your suggestion. See this guide on submitting a merge request via GitLab: https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/gitlab/3-2-collaborating-fork-their-repo/https://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/62Add info on DPIA2023-03-30T11:23:38+01:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.ukAdd info on DPIA## I'm submitting a ...
> Put an x in the appropriate square brackets
- [ ] bug/error report (eg. 404)
- [ ] documentation (eg. typos, broken links)
- [x] feature request (eg. add GitLab tutorial)
- [ ] question (eg. how does this work?...## I'm submitting a ...
> Put an x in the appropriate square brackets
- [ ] bug/error report (eg. 404)
- [ ] documentation (eg. typos, broken links)
- [x] feature request (eg. add GitLab tutorial)
- [ ] question (eg. how does this work?)
## Where is the issue?
[data pages](https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/data/)
## What is the issue?
No guidance or links about DP(I)A.
## How do we solve the issue?
Give some guidance on what we know for certain (e.g. that data are not considered "biometric") and link to university pages.
Would be nice to include some big buttons on the data home page to make this and [data management plan](https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/data/data-management-plans) pages more visibleCassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.ukCassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.ukhttps://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/63Add information about zenodo as a data repository2023-07-04T08:58:41+01:00Cassandra Gould van Praagcassandra.gouldvanpraag@psych.ox.ac.ukAdd information about zenodo as a data repository## I'm submitting a ...
> Put an x in the appropriate square brackets
- [ ] bug/error report (eg. 404)
- [ ] documentation (eg. typos, broken links)
- [x] feature request (eg. add GitLab tutorial)
- [ ] question (eg. how does this work?...## I'm submitting a ...
> Put an x in the appropriate square brackets
- [ ] bug/error report (eg. 404)
- [ ] documentation (eg. typos, broken links)
- [x] feature request (eg. add GitLab tutorial)
- [ ] question (eg. how does this work?)
## Where is the issue?
https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/data/how/#zenodo
## What is the issue?
information incomplete
## How do we solve the issue?
Describe main features and benfits of zenodo. Link to thier guides as appropriate.
Benefits I can think of:
- "restricted access" deposits for reviewer only and senestive materials.
- Could link in the future to a "WIN zenodo community".
- doi versions
- Integration with GitLab CI (see [FSLeyes CI](https://git.fmrib.ox.ac.uk/fsl/fsleyes/fsleyes/-/blob/master/.gitlab-ci.yml))
## Anything else?
> Please give any additional detail which may be relevant or useful, for example detailed explanation, motivation, stacktraces, related issues, links for us to have context.
---
## Fix the issue yourself?
If you are able to, you are welcome to submit new content directly via a merge request. This will ensure you are attributed for your suggestion. See this guide on submitting a merge request via GitLab: https://open.win.ox.ac.uk/pages/open-science/community/Open-WIN-Community/docs/gitlab/3-2-collaborating-fork-their-repo/https://git.fmrib.ox.ac.uk/open-science/community/Open-WIN-Community/-/issues/64[new feature] integrating data sharing decision tree2024-03-06T11:00:12+00:00Bernd Taschler[new feature] integrating data sharing decision tree## Issue
Existing material on data sharing (particularly around WIN's Xnat server) is not integrated yet with the community pages
## Where
- [data sharing repo](https://git.fmrib.ox.ac.uk/open-science/community/data-sharing-decision-tre...## Issue
Existing material on data sharing (particularly around WIN's Xnat server) is not integrated yet with the community pages
## Where
- [data sharing repo](https://git.fmrib.ox.ac.uk/open-science/community/data-sharing-decision-tree)
## What
- [ ] decide on where to put this on the community pages
- [ ] check that existing material is up to date
- [ ] integrate with community pages