Collaborate on family history documentation.
Here are the easiest ways to begin:
So, you've got a number of files you want to share, and you want others to get new versions automatically.
Here are ways to set up each folder.
Do you want to share it with the entire world?
The Thomas Tolman Family Organization publishes it's genealogy data publicly, and you can subscribe to data updates using P2P tools.
If you want to test out any of this back-and-forth sharing (or any other approaches), drop me a line. If you've got any other ideas, drop me a line. There are a bunch of other people working on related issues, so I'm sure you'll find a group with similar interests. This is getting fun!
Beyond just sharing files and stories, it's very useful to "index" your files and identify people to link all these to other documentation; this makes it easier to search for people and correlate them. By modifying your HTML files according to the standards below, you make it possible for programs to automatically link your information with other documents. This is much like what the Family Search indexing project is doing, though they have tools that make it even easier to add the semantics. (I'd love to create/find open-source versions of those tools as well.)
Note that the methods here are specifically for files in HTML format. If you're not accustomed to HTML documents, try an online tutorial or ask a friend for a quick explanation.
Wherever there is a person's name (or other useful data) a your document, add tags that link it to other references for that person; then programs can detect and point people to those references.
Here is sample text from the start of this document.
"So what?" Well, here's what: now you can use semantic tools to start browsing around these files.For example, here's a little bookmarklet that will guide you to those linked sites: first, install this "activate ancestry links" bookmarklet (by dragging that link to your bookmarks); then, go here to see a copy of the full file and click on that that bookmarklet to activate the links that are hidden within it. To see this in action, watch this video.
To see the whole process of adding semantic tags, watch this video.
For those of you passionate about local apps, you can run this locally without a network connection: download all the files and edit the setup.js file to point to those local files, and then you can edit the bookmarklet to point to that setup.js file.
The "url" linkprops are a very basic form of linking, pointing directly to some web location, which I don't think is a good long-term solution. The right way to do this is to reference these shared datum with URIs or XRIs instead. The same Aaron Bracken can be located in multiple locations; we know Family Search has some info, so if we want to see the Family Search version then we should be able to simply store his ID (KWVP-7PM) and the owner of that ID (FamilySearch.org), and then the tools can look him up in a browser with their URL scheme (eg. appending their ID to "https://familysearch.org/tree/#view=ancestor&person=").
My current problem is that I don't know of the perfect scheme to store these IDs for arbitrary systems. Here are a few possibilities:
My next problem after that: how to store these IDs for reference in our local, private copies of the data. A good start might be the relative references in URIs; the GEDCOM X file format has a blurb on that kind of usage, albeit inside a self-contained bundle.
Any ideas or other pointers welcome.
If you're a descendent of Thomas Tolman, you might be able to find histories of your ancestors in the Tolman Family collection. These are provided by the Thomas Tolman Family Organization, and you can subscribe to their data updates using P2P tools.