Proposal Migration to New ID

To see the new proposal in ISPyB, a User needs to be added to the proposal in UAS, and this needs to be done by a PI (Principle Investigator) or a AC (Alternate Contact) on the proposal. There are two relatively new roles which you may wish to use:

• Associate - who are merely associated with the proposal, only getting data access to the visits that they are added to, and not having any submission rights.
• ERA Editor - similar to the Associate, but with the ability to put some Safety information in (ERA is "Experimental Risk Assessment")

If you are not able to see the proposal in UAS, contact your PI or AC, or contact mx-usersupport@diamond.ac.uk if you need help identifying your PI or AC.

Proteins are copied from one proposal to the next by the PI or AC. However, note that this generally happens before the end of the prior proposal. This means that proteins added near the end of an older proposal may not appear at first in the new proposal. However, your PI or ACs will be able to copy the validated proteins across at any time.

Note that some long-running groups end up with large numbers of samples in UAS/ISPyB, so you may wish to consider which are still being worked on, rather than simply copying all. 

Once the proteins are in UAS, they will be propagated on to ISPyB. However, for proteins which were used in a prior priosal, you will need to resubmit the sequence and PDBs into the new proposal in ISPyB. See the Registering a Protein page for how to do this. 

The team at Diamond will migrate all your dewars from the old proposal to the new. If any dewars are no longer in use, we can remove them - just email mx-usersupport@diamond.ac.uk and we can do this for you.

The team at Diamond need to migrate pucks (aka "Registered Containers") to the new proposal, so please check this has been done.