search

OpenSourceMalaria / OSM_To_Do_List

Action Items in the Open Source Malaria Consortium
82 stars 13 forks source link

Joining OSM - is more information needed? #415

Open alintheopen opened 8 years ago

alintheopen commented 8 years ago

OSM are delighted to see the consortium growing and are also thrilled that more undergraduate classes are synthesising (or will soon be synthesising) molecules for the project. There are a number of "How to" guides published on 'OSM Logos and Templates', but this issue is to check whether we need to produce any further manuals/guides for people joining the project. I will add the featured guides to the issue below and would welcome any comments/suggestions from others about anything that might be missing. Please also feel very welcome to produce any such guides yourself and link below.

alintheopen commented 8 years ago

Existing guides:

First Steps

  1. How To: GitHub
  2. How To: Set up a General ELN
  3. How To: Set up a Chemistry ELN
  4. How To: Set up a Biology ELN

Next Steps

  1. Maintaining OSM Compound List This needs to be updated as we now use the Master Chemical List for This Purpose
  2. Assigning MMV numbers to compounds for testing at Syngene *Note only for those with access to Science Cloud

Curation of Data for Publication

  1. All experimental data should be written up according to this [coming soon] template
  2. OSM teams may keep track locally of characterisation. @edwintse and I use a traffic light spreadsheet and we can share this template.
alintheopen commented 8 years ago
  1. I think we may also need more details about saving 'open' raw data. For example, @lpatiny pointed out the importance of saving nmr as jcamp files so that they can be opened by anyone. As an aside you can also make use of Luc's great site too - great research and educational tool to map actual nmr on top of predicted spectra.
mattodd commented 7 years ago

Thinking about how to move this off an Issue and onto a more permanent place, could we assemble the guides on the "Tech Ops" section of the wiki, or should we place them elsewhere?

I think advice on minimal compound characterisation is an excellent idea, and we could use the relevant section on the Todd group wiki as a starting point there?

I guess we also need a "how to" for Labarchives, right, given that several people are using that platform? Not to duplicate the manuals that exist, but making it clear how to ensure that the lab book is publicly viewable, for e.g.

All of these instructional resources ought to be covered by a general statement that it's the principles that are important: that all experiments need to be public and be accompanied by full data in real time, and covered by a CC-BY-4.0 licence.

alintheopen commented 7 years ago

I think Tech Ops is a good idea and then I will write an updated blog post to send people to.

On Wed, Sep 14, 2016 at 5:54 AM, Mat Todd notifications@github.com wrote:

Thinking about how to move this off an Issue and onto a more permanent place, could we assemble the guides on the "Tech Ops" section of the wiki http://openwetware.org/wiki/OpenSourceMalaria:Technical_Operations, or should we place them elsewhere?

I think advice on minimal compound characterisation is an excellent idea, and we could use the relevant section on the Todd group wiki http://openwetware.org/wiki/Todd:Guidelines as a starting point there?

I guess we also need a "how to" for Labarchives, right, given that several people are using that platform? Not to duplicate the manuals that exist, but making it clear how to ensure that the lab book is publicly viewable, for e.g.

All of these instructional resources ought to be covered by a general statement that it's the principles that are important: that all experiments need to be public and be accompanied by full data in real time, and covered by a CC-BY-4.0 licence.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/OpenSourceMalaria/OSM_To_Do_List/issues/415#issuecomment-246906321, or mute the thread https://github.com/notifications/unsubscribe-auth/ACgUJ1CMPZ6oHkcikRIqo13FdYSxDNtmks5qp34KgaJpZM4JK-PZ .