Add historical events, which can be shown in timelines to give context.

For example, for relatives in WW2, you might have "Start of WW2", and "D-Day" that can be added.

These should be global settings that can be toggled. So, all relatives alive during the right time period would have these events displayed on their timeline

Context events should be displayed differently on the timeline, to indicate that they are context events. Use CSS classes to power this. Then in CSS, perhaps they're a different color, or use a different icon.

Users should be able to create a source with various fields and associated media, and then that source can be listed on one or more fact. Eg: A person's b-date could supported by several facts (some census records, a tombstone, etc)

Some examples of types of sources:

• Census record
• Birth record
• Death record
• Marriage record
• Webpage
• Book
• Newspaper (Obituary)
• Verbal Account
• Written Account (letters)
• Tombstone

http://bootswatch.com/

It would fit better in the footer, next to "Powered by Kinship". Also, it should probably be it's own site, rather than included in the app. Maybe a github.io site.

A source importer would be awesome. The idea would be that you give the importer a URL (or perhaps text, and other document types), and it auto populates as many fields as it can, from that source. Then, prompt user for confirmation, before automatically adding it to certain objects in the database.

This is obviously dependent on sources, which is going to be implemented in #4.

This should probably be the first thing that gets done.

It shows up in the timeline and detail views

The way this will work is an admin can upload a GEDCOM file, and it will get imported into the database.

This will require a script that parses GEDCOM and puts it into the database.

• File upload in admin portal (#40)
• Import people (#40)
• Import sources
• Import places (dependent on #39)
• Import images (dependent on #26)

The CSS should support mobile devices.

Right now, media is only attached as a person's "profile picture". We should pull this out, and create a Media model that can then be linked to the Person, as well as to other models such as Facts, etc.

Related to #2, an admin should also be able to export a GEDCOM file for use in other sites.

When adding a parent to a person, it doesn't automatically link them to the child

If a place already exists, a new one that is exactly the same should not be created.

There should be a view that shows a kinship chart for a person.

The idea here is we'd have something like a pedigree chart, but with more structure and more people. We should include not only direct ancestors, but children of those ancestors, children of the root person, and spouses of each person.

I think this can be done with d3.js. I started a jsfiddle here: http://jsfiddle.net/WHq77/7/

Put in Gemfile the ruby version. What is?

https://matthew.mceachen.us/blog/how-to-test-your-rails-application-with-travis-ci-on-different-databases-engines-1220.html

https://github.com/dkniffin/kinship/blob/master/features/step_definitions/person_steps.rb#L56

There should be some settings in the admin interface that control what is displayed to the world, and what should only be displayed to logged in users.

• Add place field to forms
• Add integration tests
• Add more unit tests
• Clean out un-used view files
• Make sure maps work as intended

• Remove help from nav bar
• Remove help related views
• Remove help controller
• Any other references to help

There should be a parent model called "Event" that will have several child models:

• Birth
• Death
• Marriage
• Divorce
  • could be it's own fact, or simply attributes on Marriage
• Residence
• Census
• Burial
• Occupation
• Other
  Trying to define an Event. I think it should have a data, and possibly a place.

• Deprecation warnings
• Stub out calls to external APIs

Once media objects get implemented (#5) media should be able to be tagged, and have thumbnails created for it. For example, a user could upload a family reunion photo, and tag each person, and that tag could be used for the person's "profile pic"

Should be under "Look and Feel" in the admin interface.

As http://openhistoricalmap.org becomes more developed, include support for it in Kinship. This will be a very useful feature of Kinship, as it will allow a better look into historical data in relation to genealogy.