Skip to content

Milestones

List view

  • The user is shown errors and potential errors in their GEDCOM file and given the option to make corrections. The corrected genealogy may then be exported back to GEDCOM or to another format.

    No due date
    0/2 issues closed
  • Implementation of algorithms that can identify typo errors in dates and suggest the right correction, e.g. where someone's age is -256, because they were born in 1733 and died in 1989, the algorithm will check relatives dates of birth and see that mother is born in 1907, father in 1905 and brother in 1930 and suggest a typo correction of Birth date '1933'.

    No due date
    0/1 issues closed
  • Make the application (especially the errors checked) configurable per user. For example, some users might want to check for dates before 1000 A.D., while others might already be suspicious when there are dates before 1500 A.D.

    No due date
    1/3 issues closed
  • Create pages with statistics and graphs (Google Charts) on: - the current file (extend the existing page) - all the user's uploaded files - all the files (publicly available?)

    No due date