Labs in regulated environments such as medical or pharma research have their own rules today, and an industry of vendors who sell enterprise level software for managing data in a compliant fashion.
I was working at a company on the day that US patent law was reconciled with the rest of the world, and the rules for priority changed. That was the last day we were required to keep a lab notebook.
Today, I mainly keep records so I can figure out what I did later on, and the best single tool that works for me is Jupyter.
Otherwise I agree with your answer about Git.
This is basically what the block chain does, except that instead of having somebody designated as special and trusted, they have the signers perform proof of work.
Cant find the article (hash is not a good search phrase when it comes to Findung an article about twitter).
At my work we've used my system for about 2 years now and there is much more engagement with the system than the one it replaced (a custom Lotus Notes application... go figure). People like that they can open the logbook from the lab, write some stuff, save it and edit/publish it later. We also heavily encourage to document anything and everything and use the categories and tags as much as possible to make searching easier.
[1] https://github.com/Academic-Labbook/alp
[2] https://alp.attackllama.com/2019/02/05/labbook-software-shoo...
Formatting is a pleasure (including formulas and LaTeX), tables are decent, you can easily share notes, etc. Code formatting can improve a lot (only basic language semantics/operators/strings); search is decent. Above all: it's incredibly simple to use, and very customizable.
My three big missing features: 1) full API, so you can develop extensions that provide the missing functionality, 2) end-to-end encryption, 3) 2FA.
For now I'm using only for study lab notes, so encryption is not a big deal. But I wouldn't feel comfortable adding anything confidential without a more decent security model.
Re: proprietary, it exports natively in Markdown (including a zip with all images), or pdf, or html. It's not perfect (there's a bug when exporting some LaTeX formulas in .md), but for the most part it works well.
* Ability to share with colleagues - Easy to send pdfs or the raw LaTeX to others.
* Able to simply past in images - I had a folder with dated images, and a macro to insert a graph at the current location (better than floats for labbooks).
* Versioning - Each section had a date in it. Sequential versions were stored in git
* Tables - `\begin{tabular}`
* Code snippets - `\begin{lstlisting}`
* Links, tags, backlinks - `\ref{section_name}`
It could do pretty much anything. Though, you may have noticed that I omitted addressing your first bulletpoint of "simple formatting", as I am not able to keep a straight face while calling LaTeX "simple".
One possible way of harnessing the power of LaTeX while keeping a simple formatting would be to use use `pandoc` and pandoc-flavored markdown. That keeps the formatting simple, while also making it easy to include references, equations, etc. and easy output to LaTeX/PDF/etc.
* We sit on top of git, which remains the single source of truth for your code - versioning, reproducibility, etc.
* Python & R notebooks or simple markdown (also on the web app itself).
* Show or hide code.
* Simple links for sharing reports.
* Tagging.
* Comprehensive search - by tag, keyword and content (soon).
Would be really interesting to hear your thoughts on the fit.
I generated an html spreadsheet for run logs because I wanted an embedded setup. I ran into the limitation of 64K characters per entry. It’s handled by trimming html off the end then autofixing broken stuff. It works so well that it took me a while to figure out why the number of rows was decreasing as more rows were filled out.
It’s all very tidy once enough people are on board. Whole notebook (and subsections) can be exported to html or PDF. There is even a way to have some robotic file uploading a la directory monitoring.
With Word, you might insert an image or try to add bullets to something and end up with your whole document looking completely different, whereas, with markdown, you know that if you put in a ">" for a quote, all that's going to change is that one spot.
Requirements:
versioning is useful to be able to see how knowledge on a subject was updated over time. There is a second level, important to some users though not necessarily me, where physical notebooks use for patents/IP to establish the date of an innovation.OneNote works on most of the above, but:
I've thought about a note-taking app like Obsidian, together with git. But it isn't easy to share notes. its handling of inserted/pasted images is a little jank.