We are looking for database programmers who are interested in creating a "Rodent lifespan database" that would summarize all published reports of lifespan extension. Why do we need another such database? Presently, there exist 2 "competing" projects:
1. GenAge - associated with Joao Pedro de Magalhaes:
only tracks Longevity Genes (no drugs or interventions), offers very little quantiative data, little useful meta-data (e.g. study quality, mouse strain), not user-friendly enough (e.g. not sortable), no data on Rats
2. The Lifespan Observations Database - associated with Matt Kaeberlein:
better data quality, but ran out of funding (not up to date), in my opinion even less user-friendly
We are in the planning stage. The database would be set up with the support of Kaeberlein. If you are interested, just send me a message or respond to this thread.
What are the advantages of having such a database? (briefly)
A. Researchers (especially non-experts) will have an easier time to look up data for grants, reviews, research etc. Database as a starting point.
B. Laypeople can look up which interventions are supported by reasonable evidence in rodents
C. If "meta-data" is added, the database can be used for calculations (study quality and husbandry vs. results; "how does animal husbandry change over time?"; identify labs with good husbandry, etc.)
D. Useful for future testing of interventions: easy to look up which compounds need to be re-tested because evidence is weak
E. Future-proofing: mouse lifespan testing will become more common in the future and it will be more and more difficult to keep up to date or remember past research without some sort of database
Proposal: Rodent lifespan database
Team Leaders: Kismet (me)
Leader workload: several hours/week, if the project takes place
Team Members: 1-3
Members workload: unclear, probably several hours/week, if the project takes place
Members only? - No
Funding Required? - Probably, No
Funding Level: 0$, but perhaps the database programmer will require to be paid (a small sum?)
Metrics for evaluating success or failure:
Milestones / Interim Steps: Coordination with Kaeberlein and all other parties; define necessary features of the DB; define the workload for the "programmer"; find someone interested to pursue the project
