[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
• 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.

@stuart, Tom Okell has given me a good rundown of the process for sharing custom sequences. How would you like this to be referenced in our usage guidance?

changed the description

If the person sharing the protocol is happy to also share the sequence, then I think you need a simple instruction like:

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 name@ndnc.ox.ac.uk in the first instance. Please note that neither Siemens nor Oxford University make no commitment to support this transfer.

If users don't want to share their sequence, then a simple statement like '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.

This is perfect, thank you. I'll get it added to the guidance.

mentioned in commit 8e87717c

Add a not that this can take on average 6 months to get the legal work sorted between the two Universities.