Add guidance on custom sequence sharing requirements from #51

docs/protocols/protocols_guide_internal-how-1.md

@@ -80,6 +80,8 @@ If the uploaded file is recognised as a sequence pdf, you should see the `Regist
 ## 3. Top level protocol information
 You can enter details about your protocol which are relevant to the study as a whole, or all sequences. These details are entered at the top of your protocol. These details will help future users understand your decisions or implement your protocol.
 
+NOTE: If you are publishing custom pulse sequences, please be sure to indicate your willingness and requirements for shring the pulse sequence (see [3.4.1 Custom Sequences](#3-4-1-custom-sequences) below).
+
 ![gif - top details](../../../img/img-protocols/gif_top-details.gif)
 
 ### 3.1 Project, hardware and species
@@ -112,8 +114,25 @@ This section should provide high-level instructions for use of this protocol. Wh
 
 You may also like to include some practical guidance, such as the total length of the scanning session, staffing levels, or any peripheral equipment. You may refer the reader to the radiographers procedure file if this is to be attached (see [4. Attachments](#4-attachments)).
 
-You should also highlight non-standard software or sequence requirements, such as custom pulse sequences.
+You should also highlight non-standard software or sequence requirements, such as custom pulse sequences (see [3.4.1 Custom Sequences](#3-4-1-custom-sequences)).
+
+### 3.4.1 Custom Sequences
+If you are publishing protocol which uses a custom pulse sequence, please make it clear whether you are happy to also share the sequence. 
+
+If you are happy to share the sequence, please include the following guideance:
+
+"This protocol uses a user written custom pulse sequence.  The author of the pulse sequence is willing to share it with other labs provided:
+
+- The lab/hospital has the appropriate contracts in place with Siemens and idea licence that allow custom pulse sequences to be installed on their system.
+- We have a version that is available for your platform [(e.g. we currently can only supply for VB11C and VB11E)]
+- You are willing to arrange with Siemens for a C2P agreement for this sequence
+- You are willing to arrange for a sequence transfer agreement between Oxford University and your institution to be signed.
+
+If all of the above apply then please contact [email address if the PI] in the first instance.  Please note that neither Siemens nor Oxford University make no commitment to support this transfer."
+
+If you are not able to share the custom sequence, please include the following guidance: 
 
+"This protocol uses a user written custom pulse sequence.  We do not have the resources to share the sequence with other labs, so the protocol is provided for your information only."
 
 ## 4. Attachments
 Browse to and add any attachments to support the implementation of your protocol. This should ideally include the (redacted) radiographers procedure. You may additionally choose to attach analysis of pilot data, for example.