Complete the Database
Records that most need work, ranked by the priority profile below. Open a record to see what is missing; signed-in contributors can propose values and flag records.
Frequency of use is only one of the criteria; it does not mean that a record is historically more significant. Completeness counts public fields only and says nothing about evidence quality.
How to help
- Pick a record from the list below, or filter it by type. The higher the priority, the more your work helps; the last column says what is open.
- Open the record: its page lists every public field with its state, and says for each open field how to fix it.
- Propose a missing value or a correction, always with its source, or flag a field that needs research or looks wrong. A record that does not exist yet can be requested: request a record (needs an account)
- Reviewers check every proposal before it counts as documented, and settle disputed fields. Until then a value shows as “proposed, not reviewed”.
- Many records at once: import a CSV file (templates show the columns); Bible passages that cannot be mapped between versifications go to the mapping tools. Import a CSV file (needs an account) · import templates (needs an account) · mapping tools (needs an account)
Proposing values, flagging and importing need an account. Links with a lock need an account and lead to the sign-in first. Sign in
What each field state means and how to fix it
- not yet researched
- Nobody has researched this field yet. Look it up and propose the value with its source; if your research finds nothing, propose “unknown” so the next person does not search again.(needs an account: sign in first)
- proposed, not reviewed
- A value has been proposed and waits for review. Reviewers approve or reject it in the review queue; anyone else can support it by proposing the same value with a second source.Review queue(needs an account: sign in first)
- disputed
- Sources disagree on this field. Add the evidence that decides it (a proposal with a source); reviewers settle the dispute on the conflicts page.Settle disputes(needs an account: sign in first)
- unknown (researched)
- Researched, but no value was found. Propose a value only if you have a new source.(needs an account: sign in first)
- not applicable
- This field does not apply to the record. If that is wrong, flag the field as a possible error.(needs an account: sign in first)
How the records are ranked
Published on 2026-10-25.
| Criterion | Weight | How to work on it |
|---|---|---|
| Required fields still missing | 3 | Open the record and propose its identifying fields first (with a source): without them it cannot be told apart from others.(needs an account: sign in first) |
| Core fields still missing | 1 | Open the record and propose its core fields (with a source).(needs an account: sign in first) |
| Values proposed but not yet reviewed | 1 | Proposed values count only after review.Review queue(needs an account: sign in first) |
| How often the record is used (each further use adds a little less) | 1 | Records named by many uses come first. More uses are added one by one or as a CSV import.Add a use(needs an account: sign in first) |
| Fields with conflicting values | 2 | Disputed fields need a decision.Settle disputes(needs an account: sign in first) |
| Time since the last update (each further day adds a little less) | 0.5 | Records not touched for a long time come first. Nothing to fix: open one and check it. |
| A documented source exists | 1 | Records with a documented source come first, because a source makes them easier to complete. |
| Flagged for research by contributors | 2 | Contributors flagged these records for research.Records that need research |
Priority = the sum of each criterion times its weight.
Technical details
Priority profile default (version 1)
missing_required- missing required identifying fields
missing_core- missing core fields
unverified- proposed but unverified fields
usage_occurrence_count_log- ln(1 + number of usage occurrences)
conflicts- fields with conflicting claims
days_since_update_log- ln(1 + days since the last update)
has_sources- a documented source exists
research_flags- open research flags
45,385 records
As of 2026-11-10 01:30 (UTC): the statistics worker updates the records that changed every 15 minutes, all others once a day. Completeness counts public fields only.