Skip to content
This repository

Academic Laboratory Management

branch: master

Fetching latest commit…

Octocat-spinner-32-eaf2f5

Cannot retrieve the latest commit at this time

Octocat-spinner-32 app
Octocat-spinner-32 config
Octocat-spinner-32 db
Octocat-spinner-32 lib
Octocat-spinner-32 log
Octocat-spinner-32 public
Octocat-spinner-32 script
Octocat-spinner-32 spec
Octocat-spinner-32 vendor
Octocat-spinner-32 .gitignore
Octocat-spinner-32 .htaccess
Octocat-spinner-32 Gemfile
Octocat-spinner-32 Gemfile.lock
Octocat-spinner-32 README.md
Octocat-spinner-32 Rakefile
Octocat-spinner-32 config.ru
README.md

Note: This project is no longer under active development.

alm: Academic Laboratory Management

alm is my approach at an academic laboratory management system.

It will serve to:

  • Keep track of orders
  • Keep track of where stuff is stored
  • Keep track of protocols and experiments
  • Keep track of the materials used in the experiments
  • Keep track of the samples generated in an experiment

In my experience, workflows in academic research labs are often not connected: If a reagent is ordered, chances are the order is recorded in an Excel(R) file. When the reagent is received, maybe there will be a freezer or shelf log to indicate where it is stored. The experimental protocols will certainly mention what reagents were used, but maybe they will not contain any information about the maker of the reagent and the order number. Finally, the samples generated in the experiment will of course be recorded in the lab notebook, but may or may not appear in the general storage catalog.

alm is supposed to be a central organizer for all things research lab. I have conceived it as a server app with a web interface, so that several people can share the same data and access it from any computer that has a network connection.

It is my first Rails app, and I am going to build it piece by piece.

If you have any suggestions or ideas, please let me know.

Something went wrong with that request. Please try again.