Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DNA clamp loader activity vs #12876

Closed
ValWood opened this issue Dec 18, 2016 · 9 comments
Closed

DNA clamp loader activity vs #12876

ValWood opened this issue Dec 18, 2016 · 9 comments

Comments

@ValWood
Copy link
Contributor

ValWood commented Dec 18, 2016

I wanted to update our Elg complex annotations based on:
#12863

previously we had a MF
DNA clamp loader activity
activity annotation (with contributes to) for complex subunits (this will still be valid for some subunits, because some are members of the RFC-loader)

but the unloading term is a process for some reason:
DNA clamp unloading
should it be made into a MF term?

@hattrill
Copy link

Hi Val,

I mulled this one over myself. It's a bit tricky and I came up with no answer - my D.mel examples are "at-arms-length-assays" rather than direct. In many cases the actual activity of unloading isn't really assayed, just the persistence of the clamp in the absence of an unloader. It would be good to have the corresponding MF, as in some cases this has activity has been directly assayed, but recent discussions seem to not favour this sort of MF-BP pattern.

There - that's absolutely no help at all!

@ukemi ukemi self-assigned this Dec 19, 2016
@ValWood
Copy link
Contributor Author

ValWood commented Dec 19, 2016

Lets see what David says....maybe here there is a case for both?

But if we know it is a single step process we can infer that its the function?
Except that for cohesin loading we use process terms.

This one will seem odd because the subunits which are part of the loader and the unloader will sometimes have a MF annotation for loading and a BP for unloading.....

@ukemi
Copy link
Contributor

ukemi commented Dec 19, 2016

I though that the unloading was a process because it consisted of both getting out of the 'bracelet' and the 'safety catch'.

@ukemi
Copy link
Contributor

ukemi commented Dec 19, 2016

Do you have a reference or a review that describes an unloading activity?

@ValWood
Copy link
Contributor Author

ValWood commented Dec 19, 2016

The refs will be the same as for the unloading complex
#12863
Refs:PMID:27664980 & PMID:23499004
(I just wanted to make the functioans and processes match the new complex def)
I don't know the mechanism of PCNA (clamp) loading or unloading, other than its an ATPase....

@ValWood
Copy link
Contributor Author

ValWood commented Dec 19, 2016

for PCNA the loading is a MF in GO, but the unloading is a process?

@ukemi
Copy link
Contributor

ukemi commented Dec 19, 2016

I suspect it was made a process because in PMID:23499004 it says that the unloading must take place repeatedly. Does it make sense to keep the process and then make a function 'DNA clamp unloader' activity that is part of the process?

Or is it just multiple executions of a function? There is only one IMP annotation and several IEAs to the process term. Should we obsolete and create the function, or keep the process and create the additional function?

@ValWood
Copy link
Contributor Author

ValWood commented Sep 5, 2017

this seems to be done? maybe via another ticket

@ValWood ValWood closed this as completed Sep 5, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants