Coordinating with other labs and organizations #7

New Issue

Open

opened 2022-10-10 23:47:47 +00:00 by jonny · 1 comment

jonny commented

2022-10-10 23:47:47 +00:00

Owner

This is also described in #1, but I thought it would be useful to have a separate thread for collaborations with other organizations. In general I think we

Labs within UCLA

What is the current state of the collaborative infrastructure at UCLA?
do labs share data with each other regularly?
Are there systems for communication within the whole department?
What would it take to organize an effort like that mentioned in #8 for restructuring IT limitations?

I would really be interested in coordinating development alongside other labs and building something that can be used by everyone, but I don't really know what that would look like at this point (and am willing to figure out as I go if there isn't really a map)

External Organizations

Open Ephys seems like a natural one
Protocol Labs & Knowledge Futures Group for p2p and LD work
ARK and ORCID for identifier assistance
Jupyter and Neuromatch for interface/document design
...?

Would like to also help with connecting us and aligning our work with external organizations!

This is also described in https://git.jon-e.net/work/postdoc/issues/1, but I thought it would be useful to have a separate thread for collaborations with other organizations. In general I think we # Labs within UCLA - What is the current state of the collaborative infrastructure at UCLA? - do labs share data with each other regularly? - Are there systems for communication within the whole department? - What would it take to organize an effort like that mentioned in https://git.jon-e.net/work/postdoc/issues/8 for restructuring IT limitations? I would really be interested in coordinating development alongside other labs and building something that can be used by everyone, but I don't really know what that would look like at this point (and am willing to figure out as I go if there isn't really a map) # External Organizations - Open Ephys seems like a natural one - Protocol Labs & Knowledge Futures Group for p2p and LD work - ARK and ORCID for identifier assistance - Jupyter and Neuromatch for interface/document design - ...? Would like to also help with connecting us and aligning our work with external organizations!

jonny added this to the Project Details project 2022-10-10 23:47:47 +00:00

jonny changed title from ~~Coordinating with other labs and organization~~ to Coordinating with other labs and organizations

2022-10-10 23:47:53 +00:00

jonny added the

proposal

detail

labels 2022-10-10 23:49:52 +00:00

jonny referenced this issue

2022-10-11 00:10:59 +00:00

IT Bureaucracy #8

jonny added

question

and removed

proposal

labels 2022-10-11 01:50:46 +00:00

jonny referenced this issue

2022-10-11 01:52:16 +00:00

Extracurriculars #3

jonny added a new dependency 2022-10-11 02:24:08 +00:00

#1 Scope of Work

daharoni commented

2022-10-11 16:56:13 +00:00

Collaborator

What is the current state of the collaborative infrastructure at UCLA?
There isn't much. I think maybe the human imaging groups have some infrastruture for collaborating but other than that nothing jumps to mind. There is a pretty large group of Miniscope labs at UCLA and I could see most of them being very interested in contributing to a collaborative infrastruture.
do labs share data with each other regularly?
No, not really.
Are there systems for communication within the whole department?
Mostly this is done with email. Most labs also have slack where collaborators from other labs have accounts as well.
What would it take to organize an effort like that mentioned in #8 for restructuring IT limitations?
I have no idea exactly what this would look like. IT will generally move super slowly so we should start a conversation with them very early on. One way or another we can get around them if need be.

I would really be interested in coordinating development alongside other labs and building something that can be used by everyone, but I don't really know what that would look like at this point (and am willing to figure out as I go if there isn't really a map)

So I can think of 3 obvious starting for this:

We currently have a BRAIN Initiative grant which is half way through the 3 years of funding. In this grant we collaborate with 4 research labs (2 at UCLA, 1 at UCB, and 1 in Colorado) and we are suppose to provide the support for group data stroge and analysis. We really haven't done anything on this front yet but I imagine this could be a good starting point.
This is a lot of motivation of basic research labs within Neurology wanting better IT solutions. There is already a working group to discuss and deal with issues and I could see eeveryone getting on board with a solution.
There are around 20 Miniscope labs at UCLA and we all are pretty collaborative. I would bet many of them would be up for contributing/collaborating on this.

* What is the current state of the collaborative infrastructure at UCLA? There isn't much. I think maybe the human imaging groups have some infrastruture for collaborating but other than that nothing jumps to mind. There is a pretty large group of Miniscope labs at UCLA and I could see most of them being very interested in contributing to a collaborative infrastruture. * do labs share data with each other regularly? No, not really. * Are there systems for communication within the whole department? Mostly this is done with email. Most labs also have slack where collaborators from other labs have accounts as well. * What would it take to organize an effort like that mentioned in #8 for restructuring IT limitations? I have no idea exactly what this would look like. IT will generally move super slowly so we should start a conversation with them very early on. One way or another we can get around them if need be. > I would really be interested in coordinating development alongside other labs and building something that can be used by everyone, but I don't really know what that would look like at this point (and am willing to figure out as I go if there isn't really a map) So I can think of 3 obvious starting for this: 1. We currently have a BRAIN Initiative grant which is half way through the 3 years of funding. In this grant we collaborate with 4 research labs (2 at UCLA, 1 at UCB, and 1 in Colorado) and we are suppose to provide the support for group data stroge and analysis. We really haven't done anything on this front yet but I imagine this could be a good starting point. 2. This is a lot of motivation of basic research labs within Neurology wanting better IT solutions. There is already a working group to discuss and deal with issues and I could see eeveryone getting on board with a solution. 3. There are around 20 Miniscope labs at UCLA and we all are pretty collaborative. I would bet many of them would be up for contributing/collaborating on this.