diff --git a/docs/protocols/protocols_guide_internal-how-1.md b/docs/protocols/protocols_guide_internal-how-1.md index 35e30d26cb64a7a04b1af89fda0c319413487101..26bb8fbc6e521d67fe07fde015dd266373d8b1c4 100644 --- a/docs/protocols/protocols_guide_internal-how-1.md +++ b/docs/protocols/protocols_guide_internal-how-1.md @@ -13,7 +13,7 @@ nav_order: 2 --- - +<!--  --> ## Contents diff --git a/docs/protocols/protocols_guide_internal-how-2.md b/docs/protocols/protocols_guide_internal-how-2.md index 9edfd7bf19e57b0c474a25a260aa13849ae8d3a9..7a7f9ca786d7cf23c0bca8d17866025025d892aa 100644 --- a/docs/protocols/protocols_guide_internal-how-2.md +++ b/docs/protocols/protocols_guide_internal-how-2.md @@ -13,7 +13,7 @@ nav_order: 3 --- - +<!--  --> We suggest you use the free tool Zenodo for creating a doi for your protocol. This will allow others to cite your protocol independently from other work in the study, and add contributors who may not be named elsewhere. diff --git a/docs/protocols/protocols_guide_internal-how-3.md b/docs/protocols/protocols_guide_internal-how-3.md index d4f06dffebfd0052eaa9a75a53b280f5c4a6639e..6f1857c0ffc0f2427b034b38df775f33c243b521 100644 --- a/docs/protocols/protocols_guide_internal-how-3.md +++ b/docs/protocols/protocols_guide_internal-how-3.md @@ -13,7 +13,7 @@ nav_order: 4 --- - +<!--  --> If you are using the protocols datbase to track changes made to your protocol while pilotting, you can amend the entry and create different version which can be reviewed at any point. diff --git a/docs/protocols/protocols_guide_internal-how-4.md b/docs/protocols/protocols_guide_internal-how-4.md index adddb908f36541fea7707c08a10d46baffe8b91c..40c7d6b5f5590d5bc37c5ea141e268357936c7ab 100644 --- a/docs/protocols/protocols_guide_internal-how-4.md +++ b/docs/protocols/protocols_guide_internal-how-4.md @@ -13,7 +13,7 @@ nav_order: 5 --- - +<!--  --> You can track how many times your protocol has been viewed and downloaded from the `Engagement Statistics` panel. Views and downloads are separated into internal to Oxford (where the user has logged in with an SSO) or external. When reporting on the impact of your entry, remember to also include the zenodo download and view statistics, if you used zenodo to create a doi. diff --git a/docs/protocols/protocols_guide_internal-why-use.md b/docs/protocols/protocols_guide_internal-why-use.md index fd28b22afc40c64efbc708bff6132b726d2a97fe..9ea3c56b6edc84bb1748c3a7d93b523167b4f8ec 100644 --- a/docs/protocols/protocols_guide_internal-why-use.md +++ b/docs/protocols/protocols_guide_internal-why-use.md @@ -15,15 +15,15 @@ Why you should consider using the WIN MR protocols database to record and share --- - +<!--  --> -The MR protocol database has been developed to share MR protocols internally across WIN as well as externally. The database provides access to standard protocols and to the latest experimental protocols uploaded by WIN members. The database facilitates sharing your MR sequence with your and other research groups and helps you to keep track of updates via version control. Each deposited protocol contains all information necessary to reproduce that sequence on an appropriately licensed scanner, allowing yourself and others to have a permanent and full record of your data acquisition methodology. +*The MR protocol database has been developed to share MR protocols internally across WIN as well as externally. The database provides access to standard protocols and to the latest experimental protocols uploaded by WIN members. The database facilitates sharing your MR sequence within and between research groups and helps you to keep track of updates using version control. Each deposited protocol contains all information necessary to reproduce that sequence on an appropriately licensed scanner, allowing yourself and others to have a permanent and full record of your data acquisition methodology.* ## Benefits ### Version control  -The MR Protocols database is version controlled, so WIN members are invited to upload their protocols during pilotting to keep track of optimisation and final versions. Comments and notes can be added to each entry to you can keep well structured documentation about why certain decisions were made. You can also link database entries with acquired data held on the [Open Data](../../data) server +The MR Protocols database is version controlled, so WIN members are invited to upload their protocols during piloting to keep track of optimisation and final versions. Comments and notes can be added to each entry to you can keep well structured documentation about why certain decisions were made. You can also link database entries with acquired data held on the [Open Data](../../data) server ### Citable research output  Versions (with minor and major edits) can be assigned a digital object identified (DOI) using the [Oxford Research Archive (ORA) Data repository](https://deposit.ora.ox.ac.uk) using the stable link provided by the MR Protocols database. Once a DOI has been created, your MR protocol becomes a citable object which you can add to your list of research outputs. @@ -34,11 +34,11 @@ Depositing your MR protocol in the database is as simple as uploading the sequen ## Who to share MR data acquisition with? ### Yourself and your research group -The MR Protocols database keeps track of changes to the protocol (for example seuqences added, sequences modified in volume or parameters) for best practice in reproducibility and prosterity. Maintaining your MR protocol in the database can help you keep an accessible record of what changes were made and why, for your record keeping and communication within your research group. +The MR Protocols database keeps track of changes to the protocol (for example sequences added, sequences modified in volume or parameters) for best practice in reproducibility and posterity. Maintaining your MR protocol in the database can help you keep an accessible record of what changes were made and why, for your record keeping and communication within your research group. ### Internally with other WIN members -The MR Protocols database provides full and reproducible information about the protocol efficiently, along with details of your decision making process (if used during pilotting). You can effective share complete details of your protocol with another scan user. +The MR Protocols database provides full and reproducible information about the protocol efficiently, along with details of your decision making process (if used during piloting). You can effective share complete details of your protocol with another scan user. ### Externally with other researchers