G
GoMommaGo
I am sure that this has been done before, but I am looking for suggestions on
how to implement OneNote as a secure electronic lab notebook (ELN).
Specifically, it should be able to:
* "lock" pages for editing once a user deems a page complete. This is
essential to ensure that data is not altered at a later date.
* allow peer/manager review, preferably with digital signatures - perhaps in
a separate section that is read only for the notebook owner and read/write
for managers and peers. It should also easily allow managers and peers
ability to see what has changed in a notebook since their last view (this
OneNote feature doesn't seem to work as advertised in a shared notebook.
Currently, we have our trial ELNs stored on an SVN repository with
permissions set for specific sections. We still have not figured out a way
to allow users to LOCK pages for ANY future editing. Our only potential
solution at this point is to run a periodic hash on our entire notebook
database. It is also nearly impossible for managers to determine what has
changed in a notebook since they last looked at it.
While commercial ELNs exist, our engineers prefer the flexible nature of
OneNote - it is more like a whiteboard environment than any other piece of
software out there, which means we have a greater likelihood of documentation
compliance. Of course, its flexibility may also prove its impracticality as
a legally binding notebook.
Anyone?
Thanks,
MaryBeth
how to implement OneNote as a secure electronic lab notebook (ELN).
Specifically, it should be able to:
* "lock" pages for editing once a user deems a page complete. This is
essential to ensure that data is not altered at a later date.
* allow peer/manager review, preferably with digital signatures - perhaps in
a separate section that is read only for the notebook owner and read/write
for managers and peers. It should also easily allow managers and peers
ability to see what has changed in a notebook since their last view (this
OneNote feature doesn't seem to work as advertised in a shared notebook.
Currently, we have our trial ELNs stored on an SVN repository with
permissions set for specific sections. We still have not figured out a way
to allow users to LOCK pages for ANY future editing. Our only potential
solution at this point is to run a periodic hash on our entire notebook
database. It is also nearly impossible for managers to determine what has
changed in a notebook since they last looked at it.
While commercial ELNs exist, our engineers prefer the flexible nature of
OneNote - it is more like a whiteboard environment than any other piece of
software out there, which means we have a greater likelihood of documentation
compliance. Of course, its flexibility may also prove its impracticality as
a legally binding notebook.
Anyone?
Thanks,
MaryBeth