Jeremy Cohen: Sharing and Collaboration (in the laboratory) Blogs, Logs and Pods
Laboratory e-Notebook
leverage off things we already do
.. COSHH
.. Process todo vs plan vs record - all integrated diagramatically in PDA
.. Integration of lab records with building management system
. so that PDAs etc can subscribe to building message broker
. after all the building mgmt system knows such things as lab room temp
.. results can be made available WITH data in databases to provide remotely sources for validation
.. record the units
. eg bridge from Germany to Switzerland, didnt meet by 10cm, because elevations against diff sea levels, which differed by 5cm but the sign was got wrong
BioBlog .. http://chemtools.chem.soton.ac.uk/projects/blog/blogs.php/blog_id/15
bioblog templates essential
barcode to url convertion
or 2d-array barcode plus phone conversion to url and retrieval
http://simile.mit.edu/welkin .. Welkin is a graph-based RDF visualizer
discover that the use of blog actually improves the quality of what is recorded.
.. comment by sketch .. chemists are scriblers
also cf .http://wikispaces.com/, which is wiki based
finally still need to link all the component parts from publication to conversations to lab notebook.
LaBlog/wiki .. myExperiment vs ourExperiment.org
semantic web .. data deluge .. maintaining & communicating context
. major problem of communicating meaning
. eg ppt arrows on hebrew system which is a right to left language . which arrow is forward?
ie people and their backgrounds needed..
maybe call this 'semiotics of semantic web' or the 'semiotic web'?
Showing posts with label Open Notebook Science. Show all posts
Showing posts with label Open Notebook Science. Show all posts
Thursday, 11 September 2008
Tuesday, 9 September 2008
AHM08/BoF: e-Infrastructure: Tool for the elite or tool for verybody
Dr Jean-Claude Bradley:
Open Notebook Science in this case chemistry, suitable for anything where IP issues are Open rather than closed:
http://usefulchem.wikispaces.com/All+Reactions?f=print
Useing video and photos published through YouTube & Flickr & Googledocs for results & Wiki for notes & ChemSpider & JoVE for publishing results .. all of which are free and hosted elsewhere, so no overhead in hosting or software maintenance etc.
Anticipate that in future (10yrs ?) many of these experiments will be able to be done with far greater replication, so longevity of data availability isnt an issue but immediacy of availability is. In those circumstances this type of distribution is suitable.
Shentenu Jha
http://wiki.esi.ac.uk/Distributed_Programming_Abstractions
Distributed Appl. programming still hard!
May actually get harder in future because of changing infrastructure - XD, PetaCloud, PRACE
No simple mapping from the application class and its staging to the application type - grid aware vs grid unaware approaches.
In fact for dynamic distributed systems such as Kalman-Filter solutions, where need to embed the scheduler inside the program.
Break-out discussion follows:
What is e-Infrastructure?
Participants representative of Arts, Medical, Geospatial - researchers, providers, developers
Getting beyond usefulness for early adopters to usefulness for mainstream science, is fundamentally about trust ..
Trust that what is learnt will be able to be reused in future as a skill
Trust that a service that is provided will be available in future -
Trust that data storage provision will at least match the longevity of the research funders for data maintenance.
Issue of any digital executable object will have dependencies and the longevity and persistance of those dependencies
Trust in terms of availability of redundant storage sources
Secure in terms of knowledge that service provider is disinterested .. eg not Google.
Evidence of this Trust is driven by perceptions of continuing $$$s
Other questions addressed were:
What do you think e-Infrastructure is and what should it be? For example, is it a tool of use only for tackling the 'grand challenges' in research or could it (& should it) be useful for all kinds of research problem?
Do Researchers need a clearly defined ICT environment and tool suite, or can usage be opportunistic, picking up on functionality that becomes available using light-weight "glue" and pragmatic organisational arrangements? ie Cathedral vs Bazaar
What would be needed to truly embrace the use of e-Infrastructure in your work across the whole research life-cycle?
Open Notebook Science in this case chemistry, suitable for anything where IP issues are Open rather than closed:
http://usefulchem.wikispaces.com/All+Reactions?f=print
Useing video and photos published through YouTube & Flickr & Googledocs for results & Wiki for notes & ChemSpider & JoVE for publishing results .. all of which are free and hosted elsewhere, so no overhead in hosting or software maintenance etc.
Anticipate that in future (10yrs ?) many of these experiments will be able to be done with far greater replication, so longevity of data availability isnt an issue but immediacy of availability is. In those circumstances this type of distribution is suitable.
Shentenu Jha
http://wiki.esi.ac.uk/Distributed_Programming_Abstractions
Distributed Appl. programming still hard!
May actually get harder in future because of changing infrastructure - XD, PetaCloud, PRACE
No simple mapping from the application class and its staging to the application type - grid aware vs grid unaware approaches.
In fact for dynamic distributed systems such as Kalman-Filter solutions, where need to embed the scheduler inside the program.
Break-out discussion follows:
What is e-Infrastructure?
Participants representative of Arts, Medical, Geospatial - researchers, providers, developers
Getting beyond usefulness for early adopters to usefulness for mainstream science, is fundamentally about trust ..
Trust that what is learnt will be able to be reused in future as a skill
Trust that a service that is provided will be available in future -
Trust that data storage provision will at least match the longevity of the research funders for data maintenance.
Issue of any digital executable object will have dependencies and the longevity and persistance of those dependencies
Trust in terms of availability of redundant storage sources
Secure in terms of knowledge that service provider is disinterested .. eg not Google.
Evidence of this Trust is driven by perceptions of continuing $$$s
Other questions addressed were:
What do you think e-Infrastructure is and what should it be? For example, is it a tool of use only for tackling the 'grand challenges' in research or could it (& should it) be useful for all kinds of research problem?
Do Researchers need a clearly defined ICT environment and tool suite, or can usage be opportunistic, picking up on functionality that becomes available using light-weight "glue" and pragmatic organisational arrangements? ie Cathedral vs Bazaar
What would be needed to truly embrace the use of e-Infrastructure in your work across the whole research life-cycle?
Subscribe to:
Posts (Atom)
