Today we added collections from WorldVitalRecords. We were able to import about 20% of the 22 thousand collections that WorldVitalRecords has. That percentage will go up overtime as we continue get better insight into our data and indexing process.
We also increased the number of Ancestry collections from 7% to 26%. You can see the details on our repositories page.
Stay tuned for many more updates on new collections; we expect to add many more in the next few weeks.
Wednesday, April 2, 2014
Wednesday, March 26, 2014
Collection Details View
Yesterday we released the new collection details view. Each collection now has its own page that allows you to take a peek into how we indexed the collection.
Above is a screen shot from the collection page for the United States Marriage, 1733-1990 index from FamilySearch. The orange area represents it's coverage between 1803 and 1812. If you search for marriages in Florida in 1805, this collection will not show up.
These new collection pages are beautiful, fun, and useful. We have already identified and fixed several bugs in our indexing process now that we can easily visualize our data. It's also useful for researchers to understand the coverage of particular collections. For example, when searching for records in Eastern New Mexico, it's easy to see why collections from Texas appear in the results.
These new collection detail pages are available from the search results. Just click the "Details" button to open that collection's detail page in a new tab.
Wednesday, March 19, 2014
FAR Chrome Extension and Data Updates
Two things of note for this week.
The first is that we have updated the Find-A-Record Chrome Extension to work with the new search page. We also setup a redirect on the old search page to send you to the new search page. Now that traffic is no longer hitting the old search page and stressing our database, we can continue importing more data and work on creating the new collection details view.
The second is that we figured out why some of the collections available from FamilySearch were being labeled with incorrect record types. First some background. FamilySearch tags their online collections with information about what record types they contain, which is great news for us. They label things as containing, birth, marriage, death, census, and several other tags. But they also label things as "vital" records. Based on what we were seeing initially, it seemed as though collections were being labeled as "vital" if they contained birth, marriage, and death records. Well, it turns out that's not the case. Take the collection Minnesota, Marriages, 1849-1950. This is labeled as vital and not marriage. Why? We have no clue. Thankfully these inconsistencies seems to be limited to the vital tag. To fix this, we ignore the vital label and generate the list of record types ourselves by parsing the title, as we do with all other data sources. That properly gives us a tag of marriage for Minnesota, Marriages, 1849-1950. Much better.
The first is that we have updated the Find-A-Record Chrome Extension to work with the new search page. We also setup a redirect on the old search page to send you to the new search page. Now that traffic is no longer hitting the old search page and stressing our database, we can continue importing more data and work on creating the new collection details view.
The second is that we figured out why some of the collections available from FamilySearch were being labeled with incorrect record types. First some background. FamilySearch tags their online collections with information about what record types they contain, which is great news for us. They label things as containing, birth, marriage, death, census, and several other tags. But they also label things as "vital" records. Based on what we were seeing initially, it seemed as though collections were being labeled as "vital" if they contained birth, marriage, and death records. Well, it turns out that's not the case. Take the collection Minnesota, Marriages, 1849-1950. This is labeled as vital and not marriage. Why? We have no clue. Thankfully these inconsistencies seems to be limited to the vital tag. To fix this, we ignore the vital label and generate the list of record types ourselves by parsing the title, as we do with all other data sources. That properly gives us a tag of marriage for Minnesota, Marriages, 1849-1950. Much better.
Thursday, March 6, 2014
Working on a New Design
We've decided to create a new search experience on Find-A-Record. Let's look at the current search page.
There are a few things about this that can be improved.
There are a few things about this that can be improved.
- The collection results are the most import piece of information, but they're relegated to a portion of the left side of the screen. The map, which is primarily used for searching, takes up most of the screen.
- The expanse of blue lines covering the US makes little sense to anybody but us. What it's showing is that the collection we hovered over was correctly geocoded to historical boundaries of the US (in this case 1767-1950).
- The search can be slow when searching on large complicated polygons like the US.
- The autocomplete for place search doesn't function very well.
Here's a peek at the redesign we're working on.
- The map will only be used for choosing and displaying the search area.
- We have more real estate for displaying information about collections, which is what really matters. We will tell you what record types are included in the collection and whether it's free or behind a paywall and whether it's online or offline.
- The "Search" button will take you to an external web page that allows you to search the collection or gives you instructions on how to access it.
- The "Details" button will bring up a modal dialog that has more details about the collection, such as a description. It will also allow you to explore all of the different boundaries which the collection was geocoded to. We are making the boundaries of a collection a little more difficult to access because most users don't care and because it significantly improves performance.
- We will no longer allow you to search on the borders of a country, state, or county. All searches will be radius searches. If you want to search an entire country you will have to expand the size of the circle to envelope it. This isn't perfect because it's impossible to cover all of Russia without getting China and other nearby countries, but Find-A-Record is most useful when optimized for local searches.
We're also in the early stages of developing a mobile app.
Sunday, February 2, 2014
RootsTech Recap
We are thrilled Find-A-Record was a Developer Challenge Finalist. This gave us great exposure to the press, to bloggers, to potential customers, and to other genealogy companies. Though we didn't win first place, we did meet many people who are ecstatic about Find-A-Record. We were often told, "It solves my biggest problem!" Find-A-Record was validated: it provides a simple solution to a complex problem that many people have.
Here are our short-term plans:
Here are our short-term plans:
- Load as much data into Find-A-Record as we can. There are many people interested in using the API. The more data we have, the more useful our API is.
- Harden our API and back end infrastructure. It needs to be reliable, fast, and bug free.
- Find a way to simplify the search experience. We're concerned that the current experience with the large map is overwhelming and confusing. We will be experimenting with alternative designs.
We have a published list of repositories we plan to index collections from in the near future. Let us know if where else we can find valuable data. You'll notice we're mostly focused on the US and UK right now.
Do you have any ideas about how to improve the search experience? We would love to hear them.
Thursday, January 30, 2014
Boundary Searching
Boundary searching is now live on Find-A-Record. As shown in the Friday video from last week, you can search for collections within an entire county, state, or country all at once. Don't forget to install the Chrome Extension for an enhanced search experience from within FamilySearch and Ancestry trees. Right now we have collections from Ancestry.com, digital collections from FamilySearch.org, and FamilySearch catalog entries for the UK.
Find-A-Record is still in beta. If you have any ideas for new features or find a bug, please let us know.
We are aware that a lot of collections in England are incorrectly mapped to the country level instead of the county level. We have plans to fix that tomorrow.
* This post is a day late because we were heads down preparing for RootsTech yesterday and completely forgot about it.
Find-A-Record is still in beta. If you have any ideas for new features or find a bug, please let us know.
We are aware that a lot of collections in England are incorrectly mapped to the country level instead of the county level. We have plans to fix that tomorrow.
* This post is a day late because we were heads down preparing for RootsTech yesterday and completely forgot about it.
Wednesday, January 1, 2014
We're Going To RootsTech
We will be attending RootsTech on February 6-8 as well as the Innovator Summit on the 5th. Here's what we're looking forward to.
Developer Challenge
We will be entering both Find-A-Record and Open Place Database in the Developer Challenge. The cash prizes are underwhelming but the publicity is priceless. The developer challenge put last years winner, Treelines, on the map and they weren't promised half the attention that even 3rd place will get this year.
FamilySearch Records API
We're hoping for some big news from the session about the FamilySearch Historical Records API. A historical records API that grants access to a collection as vast as FamilySearch's will initiate an exciting new age in the development of genealogy applications.
FamilySearch Records API
We're hoping for some big news from the session about the FamilySearch Historical Records API. A historical records API that grants access to a collection as vast as FamilySearch's will initiate an exciting new age in the development of genealogy applications.
FamilySearch Partner Services Session
FamilySearch will be hosting a session titled FamilySearch is Open for Business! – What is Partner Services? How Can it Help my Business? We're hoping to hear some announcements about an improved experience for FamilySearch partners, such as self-service developer keys.
FamilySearch will be hosting a session titled FamilySearch is Open for Business! – What is Partner Services? How Can it Help my Business? We're hoping to hear some announcements about an improved experience for FamilySearch partners, such as self-service developer keys.
Surprises
RootsTech is always full of surprise announcements from companies large and small. What will happen this time?
Meeting People
We're going to meet some friends from RootsDev for breakfast before the Innovator Summit. We look forward to meeting many others over the course of the four days.
Free Lunch
The Innovator Summit includes free* lunch. Who could pass up an opportunity for free lunch?
*
Free after the entrance fee, of course.
Subscribe to:
Posts (Atom)







