- Portable Genealogy is sound – Ancestry App better than ever
- The Camera App in iOS5 does have a zoom. In fact if you use the familiar “pinch-gesture” you can zoom in/out and the old zoom slider appears too. Also you can use the Volume Up button (on the side of the phone to take a picture — helpful when the camera is rotated.
- Just having the iPhone was very useful during the #RootsTech conference as my note taking device. Until iPad2(3) arrived(s) and it has both WiFi/G3 (LTE) I would have been without blogging capabilities in the Salt Palace convention center when its WiFi would go down. I utilized the #RootsTech App (for iPhone & there was one for Android too).
- In the library it was my digital camera.
- In fact the ImageToText App came in handy to OCR an image of text for me
- I used the Ancestry App to enter the transcribed text from the microfilm images right into the evidence (note area) of the app of an indivividual and attached the iPhone picture too.
- In one case, I was able to get an immediate shaky leaf as a result of my data entry — much to my disbelief (and it was correct). So I could do an immediate on-site analysis and do further microfilm searching as a result.
- I used the Bump App to swap contact info with one genealogist. I cannot wait until all genealogists become mobile-enabled and lose my business cards altogether. Hint to RootsTech Vendors you should use Bumps too to collect user info. Why do I have to drop a business card into a fishbowl??? Do a BUMP, get a chotsky (swag). Leave the fishbowl for the Luddites.
- Are you a Slavic (Czech, Pole, Russian, etc.) genealogist? Then you must be dying for diacriticals. You could add an international keyboard. But why? In iOS5, just press and hold down the ‘ l ‘ key and up will come a list including the slashed-l. Just slide your finger over onto the slashed-l to enter that. Likewise, for entering ‘S, E, A, Z, C, N, etc.’ too — works upper/lower case. Of course if you have German ancestors, you can get your umlauts too in the same fashion. That trick is a Latin Alphabet data entry trick (sorry Cyrillic or Hebrew readers — try the International Keyboard trick).
The above diagram is what Stanczyk had been jabbering about since the #RootsTech conference. Isn’t that much easier on the eyes and the grey matter than a complex UML diagram? Who even knows what a UML diagram is or if it is correct or not?
What does it say is in a GEDCOM file (ex. Eliasz.ged)?
A HEAD tag optionally followed by a SUBmissioN Record followed by 1 or more GEDCOM lines followed by a TRLR tag.
ex. gedcom lines that can be “traced” along the railroad tracks at the top.
0 HEAD 1 SOUR Stanczyk_Software 1 SUBM @1@ 1 GEDC 2 VERS 5.5.1 2 FORM LINEAGE-LINKED 1 CHAR UNICODE 0 @1@ SUBM ... 0 TRLR
OK Stanczyk_Software does not exist, but was made up as a fictitious valid SOURce System Identifier name. The GEDCOM file (*.ged) is a text file and you can view/edit the file with any text editor (vi | NotePad | WordPad | etc.). I do not recommend editing your gedcom outside of your family tree software, but there is certainly nothing stopping you from doing that ( DO NOT TRY THIS AT HOME). If you knew gedcom, you could correct those erroneous/buggy gedcom statements that are generated by so many programs — that cause poor Dallan Quass to ONLY acheive 94% compatibility with his GEDCOM parser.
Have you ever downloaded your gedcom from ANCESTRY and then uploaded it to RootsWeb? Then you might see all those crazy _APID tags. It is a custom tag (since it begins with an underscore – GEDCOM rules dear boy/girl). It really messed up my RootsWeb pages with gobbledygook. I finally decided to edit one gedcom and remove all of the _APID tags before I uploaded the file to RootsWeb. Aaah that is SO much better on the eyes. Oh I probably do not want to re-upload the edited gedcom into ANCESTRY, but at least my RootsWeb pages are so much better! The _APID is just a custom tag for ANCESTRY (who knows what they do with it) so to appeal to my sense of aesthetics, I just removed them — no impact on the RootsWeb pages, other than improved readability. [If you try this, make a backup copy of the gedcom and edit the backup copy!]
Now obviously the above graphic syntax diagram is not complete. It needs to be resolved to a very low level of detail such that all valid GEDCOM lines can be traced. It also requires me/you to add in some definitional things (like exactly what is a level# — you know those numbers at the beginning of each line).
I have a somewhat mid-level graphic syntax diagram that I generated using an Open Source (i.e. free) graphic syntax diagrammer, as I said in one my comments, I will send it to whoever asks (already sent it to Ryan Heaton & Tamura Jones). You can get a copy of Ryan Heaton’s presentation from RootsTech 2012 and compare it to his UML diagram (an object model). I think you will quickly realize that you cannot see how GEDCOM relates to the UML diagram — therefore it is difficult to ask questions or make suggestions. A skilled data architect/data modeler or a high-level object-oriented programmer could make the comparison and intuit what FamilySearch is proposing, but a genealogist without those technical skills could NOT.
I am truly asking the question, “Can a genealogist without a computer science degree or job read the above diagram?” and trace with his finger a valid path of correct GEDCOM syntax [ assuming a whole set of diagrams were published]. The idea is to see how the GEDCOM LINES (in v5.5.1 parlance FAMILY_RECORD, INDIVIDUAL_RECORD, SOURCE_RECORD, etc.) are defined and whether or not what FamilySearch is proposing something complete/usable and that advances the capabilities of the current generation of software without causing incompatibilities (ruining poor Dallan Quass’s 94% achievement). Will it finally allow us to move the images/audio/video multimedia types along with the textual portion of our family trees and keep those digital objects connected to the correct people when moving between software programs?
GEDCOM files are like pictures of our beloved ancestors. They live on many years beyond those that created them. Let’s not lose any of them OK?
Stanczyk, has been churning since about November of last year (2011). I have a number of ideas rummaging around my brain for genealogy apps. For over a quarter century, I have been a computer professional and used and/or developed a lot of programs using a myriad of technologies. At my core, I am a data expert: design it, store it, query it, manage it, analyze it and protect it. It being the data.
Before going to #RootsTech 2012, I knew GEDCOM was the core of our hobby/business/research. GEDCOM is our defacto standard. It is how data in exchanged between us and our various programs. I say defacto because as a standard goes it is not a very open standard (one organization “owns” it, and the rest of us go along with it). It also has not changed in about decade and a half; So Ryan Heaton was correct in calling it “stale”. It does still work .. mostly. Although if a standard does not progress then you get a lot of proprietary “enhancements” that prevent the interchange of data completely — since one vendor does not know how to deal with another vendor’s file in totality.
At present, GEDCOM maxes out at version 5.5, although there are various other variations you might see. But 5.5 was the last standard version. I counted 128 total tags and a provision for creating non-standard tags (they start with an underscore).
[Mike thanks to Tamura Jones! Even though GEDCOM v5.5.1 was never finalized, it IS the defacto max version of GEDCOM. GEDCOM v5.5.1 added 9 tags, removed the BLOB tag, so we now have a total of 136 tags. -- I will need to update even my high level graphic syntax diagram]
Tags are like:
INDI, FAMC, FAMS, SOUR, REPO, HEAD, TRLR etc. -or- ALIA, ANCE
The first bunch is familiar and are probably in your family tree (if you ever exported the GEDCOM file). The ALIA tag is one that Dallan Quass said was universally used wrong by all programs. After seeing its definition, I can see how it is confusing. As for the ANCE, tag I do not recall seeing any program letting me do any functionality that might utilize this tag. This tag is probably one of those tags that Dallan said is not used at all.
I looked at the “MULTIMEDIA” section of the standard. It looks like it is woefully out of date and probably not used at all (at least not in any standard way), which is probably why our pics, audio, and video (or any other media file like PDF, MS Word) do not move with the GEDCOM. Has any program ever used the ENCODING/DECODING of a multimedia file? The standard seems to imply a buffer of only 32K (for a line) and even if you used a large number of CONC tags strung one after another you need 100 lines to store a 3.2MB file in-line in the GEDCOM. I do not think I have seen that in a GEDCOM. They probably stored these binary large objects (BLOBs) outside the gedcom and refer to their path on the computer/network. I did some noodling. I have 890 MB (or approximately 890,000 KB) in pictures and scanned source documents for about 1,000 people in my family tree. So I use nearly a gigabyte (1GB) for my family tree and all other multimedia — and I do not have any audio or video! So I use almost 1MB/person.
If we did have this magical new GEDCOM standard that could carry all of our multimedia from one GEDCOM program to another GEDCOM program, the copying would take a long time. If I uploaded/download it to/from the Internet, I might incur an overage on my ISP’s usage charges, if this were technically feasible! Imagine if I did this multiple times a month (as I got updates). I am beginning to understand why no vendor has tackled the problem. I would also like to store PDFs and other documents besides GIF/JPG/PNG which can be displayed on the Internet web pages natively in a browser. Those are not a part of the existing GEDCOM standard. Let me sling some jargon — I’d want to store any file type that there is a MIME type definition for, that I can currently embed in emails, or utilize in Java programs or that the HTML5 standard will allow for multimedia.
The GEDCOM 5.5 was in its infancy on dealing with character sets. It was predominantly ASCII with some funky ANSEL coding of characters to handle latin alphabet diacriticals, although it is not clear how I would do the data entry for those and it looks incomplete. It did mention UNICODE, but only cursory and just to remind us that the lengths in the GEDCOM standard were in ’characters’ not bytes –which was correct. Although those multibyte characters (say in Hebrew, Russian or Japanese or Chinese) would quickly use up the 32K byte line buffer limit, which would effectively become about 8K characters per line. In fact, GEDCOM 5.5 says it will only deal with LATIN alphabets and leave Cyrillic, Hebrew and Kanji for some far flung future. Stanczyk is Slavic, I need UNICODE to represent my ancestor’s names and places. Fortunately, I do not feel the need for Cyrillic (Russian, Ukrainian, Belorussian, Macedonian, etc.) or I’d be out of luck. I’ll just use the Polish version of those names in their ‘Latinized’ forms.
Oh that is another area the standard needs to be enhanced. NAMES. Dallan mentioned that Personal Names do not get a thorough treatment in the standard (I am refusing to read the data model and I am a Data Architect). Location Names get almost no treatment — they do give you a place to store your locations (PLAC tag). What language should I use, after all my ancestors are from POLAND for God’s sake. Besides the obvious Polish, I have German, Russian and Latin to deal with and being American I prefer English. Slavic names often do not translate well. For example Wladyslaw is Ladislaus in Latin, but in English there is no equivalent — maybe that is why my ancestors use ‘Walter’ instead. But the point is, how should I store the name? Can I store all of the equivalents and search on any of them? Nope.
Damn, Russian is Cyrillic. GEDCOM doesn’t deal with non Latin alphabets; And even though I can read the Russian genealogy records, I ‘d rather not nor would I want to try and do data entry that way either. Besides, the communists reformed the language in 1918 (making War & Peace considerably shorter in Russian); That reform eliminated several characters. Most modern software is not aware of the eliminated characters much less able to generate them. This whole Language/Unicode/Name thing is complicated and I have not even mentioned the changing borders or the renaming of cities in different languages or over time or their changing jurisdictions. I cannot fault GEDCOM for all of these woes. I have them in my own research and I have not yet found any satisfying way to handle them. I find it helps to have a very good memory and keep these things in my head — but there is no backup for that.
How are we ever going to arrive at the vision Jay Verkler put forth at #RootsTech? GEDCOM needs to become an open standard. Once it is standardized again, then it needs to become modern again and deal with the current technology, so we can get around to the tough problems of conforming: names, places, sources/repositories, calendars/dates and doing complex analyses like Social Network Analysis as a way to gather wayward ancestors into a family for which we lack documentation to prove (Genealogically). I hope the future includes Bieder-Morse phonetic matching and can deal with folding diacritical characters into a base character (ex. change ę into e) for searches.
FamilySearch, if you are going to register GEDCOM tools, then please do a few more things for the NEW standard. First, make each vendor add to an APPENDIX the name and complete definition of their NON-STANDARD tags, in case anyone else wishes to implement or deal with them. Put a section in the header (HEAD tag) that lists all NON-STANDARD tags (just once each) along with its vendor so that someone else can go look at the standard and see what these tags mean and possibly implement the good ones. Forget that two byte thing before the HEAD tag. Just make the HEAD tag ‘s CHAR sub-tag indicate the character set (ANSI | ANSEL | UNICODE ). Please administer a #RootsTech keynote to vote on annual changes to the GEDCOM standard. Provide a GEDCOM validator and also a GEDCOM converter webpage to allow users/vendors to validate/convert their gedcom file(s).
Make multimedia be meta-data and allow users to define “LOCATIONS” where multimedia files can be found using either a PATH or a URL (or a relative path / URL). Make it a part of the standard that the meta-data must move, but the multimedia files can optionally stay put. Multimedia should be able to be placed on a LOCAL/NETWORK, or on the INTERNET or on a multimedia removable volume(s) [thumb drives, CDs, DVDs, etc.]. Make the multimedia “LOCATIONS” editable so a user can switch between LOCAL/NETWORK, INTERNET, or REMOVABLE including using some of each type of LOCATION. Allows these files to exist or not (show “UNAVAILABLE” or some equivalent visual clue, if accessed and they do not exist). The mapping between an Individual (INDI) or a family (FAM) or some other future GROUP and its multimedia file(s) must move as a part of the meta-data (even if the multimedia file(s) do not). That way the end-user need only edit his LOCATIONS meta-data (and ensure the files are in that/those location(s)) when he runs the software.
Define an API for GEDCOM plug-ins so that new software can access the GEDCOM without parsing the gedcom file. The API should give the external plug-in a wrapped interface to the underlying data model without having to know the data model, just the individual, family, or location, or a name list of individuals, families, or locations. This will allow new software to provide additional functionality to a family tree or to provide inter-operability between trees/websites. Obviously security/privacy rules would limit this kind of plug-in access.
That’s Stanczyk’s vision of the GEDCOM future!
If you follow Stanczyk‘s posts, then you know the first 2012 Genealogical Website Ratings were published yesterday. I wanted to follow-up on that article’s meme with yet a further muse.
The ratings show that there was quite a bit of a shuffling around. Overall though, genealogy websites are nascent. That is my meme for today: The State of Genealogy is Very Good and Is Improving. In a little over a week, RootsTech 2012 conference will happen. The convention shows many of the top web sites are attending: Ancestry.com, Fold3.com, FamilySearch.org, Mocavo.com, LegacyFamilyTree, MyHeritage, RootsMagic, Geni.com, AgesOnline, etc. In the middle of this conference, the “Who Do You Think You Are“, show will debut (3-Feb-2012). Late March brings us PBS’s “FINDING YOUR ROOTS…” So the first quarter looks promising. Do you doubt this jester?
Perhaps the Baron’s Online article, ” ‘Tis the Season For Ancestry.com” will convince you. Bob O’Brien (the author) analyzes the stock performance of Ancestry in light this convergence. He does not reference RootsTech nor PBS — but this jester does. Also adding to the synergy for 2012 Genealogy is the release of the 1940 US Census on April 2. So 2012 has all the makings for genealogy’s best year ever. Baron’s does mention the 1940 Census too.
Now a successful business climate for genealogy – software, hardware, and services can only mean many good things will be coming for us genealogists. Let me urge you to greater heights in your research by lending your efforts in your research and also in collaborating on the Internet. We can all push our own research (and of course those distantly related to us) forward and ride the rising tides of the 2012 Genealogy Surge.
For good measure the biennial United Polish Genealogical Societies Conference in late April is also happening this year. So Polish Genealogy should be able to ride the tide of popularity too.
RootsTech looks like it will have its emphasis on the Internet with its evolving collaborative tools (social networks, HTML5, new databases, blogs, developer tools/frameworks/standards to enhance the collaborative/connection making nature of genealogy and provide richer search/match tools/techniques, etc.). Catch this break-out year!
That’s the Meme – The State of Genealogy in 2012 is very promising.
Welcome to Stanczyk’s 2012 First Quarter Genealogy Website Rankings. I know I am a week early — c’est la vie! Since my last rankings an array of rank postings [uh, pun partly intended] have appeared. Stanczyk has also received exactly one request for inclusion in his rankings, from .. Tamura Jones about his website: www.tamurajones.net [#58 on the new Rankings]. He also has a worthy Twitter page too. Keep sending in recommendations — I will keep thinking about them or including them if they are worthy. I liked Tamura’s stuff so MUCH, that I added his genealogy page to my blogroll [Modern Software Experience at the right].
I really liked the survey from the Canadian website: Genealogy In Time. I added their magazine/website (#13) as well to my rankings. I found them because they produced an excellent Genealogy Website Ranking (mid January 2012), that included a very thorough discussion of their methodology. They neglected a few Polish Websites that SHOULD have made their list. Also they list Ancestry.com in all of its many global incarnations and this eats up an unnecessary number of the top 125 poll slots. But aside from those minor criticisms, their rankings is very GLOBAL and very good. Who knew there was a Chinese (make sense, considering their billion plus citizens and their excellent genealogical records) genealogy website or a Finnish website too in the top 125???
OK, Stanczyk will keep his Rankings list, because of the emphasis on Polish / Slavic genealogical websites. Stanczyk also has many in the range 100-125 that are very useful though not popular enough to be the Genealogy in Time Rankings. However, the Genealogy-In-Time-Poll, makes a very useful tool in another way. They have graciously included the website links (URLs) of each site, making it rather easy to build a genealogical Favorites/Bookmarks list that is broadly useful. Stanczyk admits to his list being somewhat selective in the lower 1/3 in order to be more valuable to Polish Researchers (in particular to English speaking, though not exclusively so). On a personal note, this blog you are reading is in the top 5.8Million (of all websites world-wide) and is #120 on my Website rankings — come on readers give me a boost, please!
Needless to say, all website rankings I read, agree on the top 20-40 websites (putting aside the multiple listing of Ancestry.com).
Here is a snippet of the Rankings and the rest are on the Rankings Page:
Stanczyk has maintained for a few years that genealogy as a hobby ranks second only to gardening as a hobby engaged in by Americans. Perhaps this is the year we begin the assault on the number one spot.
If you love genealogy (and I assume you do because you read this blog) and/or history and biographies, then 2012 is your year! Of course we all look forward to Lisa Kudrow’s annual send-up, “Who Do You Think You Are?“.
Who Do You Think You Are, the American genealogy documentary series on NBC returns on February 3, 2012. The third season will have shows on: Marisa Tomei, Rob Lowe, Paula Deen, Rashida Jones, Jerome Bettis, Reba McEntire, Helen Hunt, Edie Falco, Rita Wilson, Jason Sudeikis, Martin Sheen and Blair Underwood.
On PBS, if we can divert you from Downton Abbey, we have “FINDING YOUR ROOTS WITH HENRY LOUIS GATES, JR.” which premiers Sunday, March 25th. This 10-part series will delve into the genealogy and genetics of famous Americans. Dr. Gates will cover the family trees of: Kevin Bacon, Robert Downey, Jr., Branford Marsalis, John Legend, Martha Stewart, Barbara Walters and Rick Warren, among others in this 10-part series. Make sure you watch Martha’s show — she’s a Kostyra [i.e. Polish] !
Do not forget that BYU TV channel of course has an ongoing genealogy show (The Generations Project). This channel is not available everywhere (yet) — check it out.
So this jester maintains that genealogy is even more popular than ever! What do you think?
Yesterday in the blog, Stanczyk emailed in an Ancestry database of note. They had an index of Marriages from Cuyahoga County, OH (the Cleveland area) 1810-1973. Most of these are marriage returns from the officiant and list little more than the bride, groom and marriage date and the officiant. Some do in fact list ages of the bridal party or their residences and even two of mine had the parent names.
Now this plays into an earlier blog article of mine about the Cleveland Eliasz/Elijasz, asking for any ancestors to write this jester and discuss family trees. [None so far.]
I was hoping for and found the marriage record of Stanislas Hajek and Agnes Eliasz ! Of all the Cleveland Eliasz/Elijasz this marriage was most convincing to me that they are relatives,as both Stanislas and Agnes (Agnieszka) were from Pacanow, which is my grandfather’s birth village. From a Polish Genealogical Society website (genealodzy.pl) email I received from a Baran, whose grandmother was an Eliasz, and from Ship Manifests, I was able to place this Agnes Eliasz in my family tree as a daughter of Jozef Eliasz & Theresa Siwiec (whose direct line ancestor a while ago sent me my grandparent’s marriages records – civil and church).
Truly the Internet makes this world a smaller place. So today, I am transcribing the married couples from the Cuyahoga County, OH marriages returns of 1913 on the same page with Stanislas Hajek & Agnes Eliasz (from page 193):
Michael Blatnik & Mary Hocevar August 25th, 1913 [#21537]
John Spisak & Veronika Busoge August 25th, 1913 [#21538]
Joseph Wisniewski & Frances Kotecka August 25th, 1913 [# 21539]
Stanislas Hajek & Agnes Eliasz August 25th, 1913 [# 21540]
George Csepey & Helen Weiszer August 26th, 1913 [# 21541]
Boleslas Zaremba & Alexandra Alicka August 26th, 1913 [# 21542]
Louis Rutkowski & Anna Solecka August 26th, 1913 [# 21543]
Aloys Salak & Anna Pisek August 26th, 1913 [# 21544]
Almost all of them look Slavic and most of those names are Polish. Cleveland, a large GreatLakeCity, an American enclave of Poliana in the early 20th century.
Related Ancestry DBs:
US, Ohio, Cuyahoga County, Jewish Marriage Record Extracts, 1837-1934
Ohio Marriage Index, 1970, 1972-2007
Ohio Marriages, 1803-1900
Ohio Divorce Index, 1962-1963, 1967-1971, 1973-2007
The WordPress.com stats helper monkeys prepared a 2011 annual report for this blog.
Here’s an excerpt:
The concert hall at the Syndey Opera House holds 2,700 people. This blog was viewed about 8,300 times in 2011. If it were a concert at Sydney Opera House, it would take about 3 sold-out performances for that many people to see it.
Stanczyk has a lot of catch-up to do. I blame it on the season and the Blood Red Lunar Eclipse — certainly that must be cause of the madness this December.
So many blogs have written about the Social Security Death Master File and the many related issues. First millions of records were dropped by the SSA. Next the SSA, and this has probably been going on for months, started redacting the names of the parents on the SS5 Applications, thus eliminating the usefulness of that research tool. Now Congress has bullied the paid genealogy databases (and even Rootsweb) to drop the SS# from their databases on deaths in the last ten years. Rootsweb just dropped their Social Security Database altogether!
Now let me remind the lame (not lame duck) Congress that the Social Security Death Master File is used to inform banks/financials/loan companies/credit card companies etc. that these SS#’s are of the DECEASED and that they should not grant any NEW credit applications with the Social Security Numbers in the Social Security Death Master File! Ergo, having the SS# of a dead person should not avail any criminal and should in fact result in their arrest for fraud, as the afore mentioned companies are supposed to check the Social Security Death Master File against credit apps. Therefore, there is really is no need to eliminate the SS#’s from Ancestry.com or any other database. By eliminating these numbers you cannot order the SS5 Applications — which is just as well since the SSA has made them much less useful. The result is: genealogists have less data available and the US Government has less MONEY($) available since the genealogists now have two reasons not to order the SS5 Applications any longer. The result is the US Government will now lose another source of income??? Boy, is this CONGRESS the biggest bunch of idiots or what?
Eastmans / Website Rankings
Dick Eastman’s Online Newsletter recently wrote about new website rankings and gave the URL/Link to a Anglo/Celtic website. Needless to say this is the website that caused this jester to produce a BETTER set of website rankings (please see my page above or at Genealogy Website Rankings). I ask you to please utilize my Genealogy Rankings as they are based upon resources in more common use in the USA (and Canada), such as SteveMorse.org or EllisIsland.org or CastleGarden.org or any Polish-related website or blog. So I am compelled — not because I am as popular as EOGN.com (#12), vs Stanczyk (#120). But clearly leaving off the Steve Morse, or Ellis Island or the US NARA or Fold3 is not accurate in the USA and certainly NOT in the GLOBAL Genealogy market as a whole. Now this is foremost a blog about Slavic Genealogy (Russian-Poland overtly emphasized) and so I have made an effort to seek out and reflect Polish websites of Polish Genealogy websites/blogs (when their popularity reflects the need). I have intentionally not included GENPOL.com because its Global Ranking is too low. It is a very well known website to Polish Genealogists and I am sure in Poland itself it would be in the top 125 (just not Globally). So while this blog has a certain voice, my website rankings deserve as much attention as those that Dick Eastman writes about. Perhaps one day EOGN.com will notice this blog and its Genealogy Website Rankings List — you my faithful readers can help me by emailing Dick Eastman and informing him about my set of Genealogy Website Rankings which is very thorough and includes the Top 125 Genealogy Websites — including Polish & American & Jewish (re NonAnglo-Celtic) websites too. EOGN should not be allowed to perpetuate its blind-spot to other genealogies. Now let me hasten to add the other Rankings does in fact mostly agree with my own Rankings on the top 10 or 20 Genealogy Websites — his Rankings lack Polish/American/Jewish sites and my own Rankings miss a few Anglo websites and all of Ancestry.com’s other country sites (UK, CA, DE, AU, etc.) — which should probably be aggregated into Ancestry.com but due to their many domains their totals are segregated by Alexa (ratings agency) and this jester chose not to include so many Ancestry.com properties in the Rankings (which would exclude so many other worthy websites).
As before, let me remind new genealogists that this Genealogy Website Ranking could be utilized to create or augment your genealogy Bookmarks/Favorites. Obviously, they are valuable since a LOT of genealogists visit them.
I forgot to mention about Mocavo.com (I put it into the newest Genealogy Website Rankings). I have briefly mentioned Mocavo.com before (when I found them in my blog analytics). They are a new search engine, akin to Google. However, they are a Genealogy Search Engine and as such is enhanced to understand GEDCOM, genealogy, dates, places, etc. and their search results are more intensely accurate then say what you would get from Google. They also have the ability search databases and include those in results, as well as GEDCOMs. You have the ability to submit your family tree (GEDCOM) to Mocavo and they can provide you with notices of potential new matches — much like Ancestry.com does for their subscribers. So instead of Googling you Family Tree, try MOCAVOing your Family Tree.
Stanczyk was checking out the family search European Holdings for Slavic record counts / images to see what progress was made up through 2011.
It is good if your heritage includes the Germanic peoples or locales which were previously under their dominion. Do not get me wrong. I am thrilled that there now over a million Polish records/images online or indexed at FamilySearch.org.
|Hungary||Browsable Images Only||0.00|
|Slovakia||Browsable Images Only||0.00|
We have the ability to better. Please consider volunteering as an indexer. You can start and stop and start again, your volunteering at any time. Find out more at indexing.familysearch.org. Every little bit helps. Stanczyk managed to do over 150 records this year. Genealogy is collaborative. Helping each other, we also help ourselves. Please pitch in — make this part of your Random Act of Genealogical Kindness efforts.
Bigos – A stew, hunter’s stew rich with meats, mushrooms, sauerkraut and dried fruits.
So today my blog bigos is made up of a slew of blurbs …
From The News.PL, a couple of days ago, they wrote about historians that uncovered a previously unknown memoir by one of the victims of a notorious WW II Nazi operation against Polish intelligentsia (called Sonderaktion Krakau of November 1939).
One of the principals, Zygmunt Starachowicz, kept a memoir of the experience with:
- Interesting Profiles of the detainees
- How he was a law graduate signing documents at Jagiellonian University when he was arrested with 182 academics
- How 20 of the 183 people died in captivity
- A memoir penned in 1941, that lay in unopened envelope for 70 years
Sadly, Zygmunt died in 1944 after being arrested by the Nazis in July 1944 [probably as a result of his activities as a member of the underground, leading clandestine lectures in law and history, and forging documents for the official “Home Army” (AK)].
Stanczyk is always seeking out high quality resources that provide context for understanding and/or to provide ideas for new avenues of research. One of the great resources since about 1985, has been Avotaynu. Besides their journal of the same name which is the largest circulation magazine of Jewish Genealogy, they also publish many reference books for Eastern Europe that are of aid Jewish and Non-Jewish researchers alike.
They maintain an index of their published issues (1985-2008) here (http://www.avotaynu.com/indexsum.htm). It is broken down by various countries. This material can also be found in back issues, libraries, and they offer a CD covering the entire 24 year span. This jester sat down to produce a Polish Index for Polish Genealogists of all stripes (Enjoy!):
|#||Title / Description||ISSUE||YEAR|
|1||Jewish records at the Genealogical Society of Utah||II/1/03||1986|
|2||Index to Polish-Jewish records at Genealogical Society of Utah||II/1/05||1986|
|3||Book review: The Jews in Poland and Russia–Biographical Essay||III/1/38||1987|
|4||Origin of Russian-Jewish surnames||III/2/03||1987|
|5||Breakthrough in access to Polish-Jewish records||IV/1/10||1988|
|6||Book review: Jews of Posen in 1834 and 1835||IV/2/26||1988|
|7||Update on project to microfilm Jewish records in Poland||IV/3/12||1988|
|8||Doing research in the Polish State Archives||IV/3/21||1988|
|9||Jewish Historical Institute in Poland||V/2/07||1989|
|10||Jewish genealogical research in Poland||V/2/08||1989|
|11||Trip to Poznan: The Poland that was not||V/3/16||1989|
|12||Professional genealogists in Poland||V/4/04||1989|
|13||List of former Jewish residents of Lodz||V/4/15||1989|
|14||Caricatures in Polish vital statistic records||VI/1/16||1993|
|15||Polish trip for Jewish genealogists planned||VI/1/41||1993|
|16||Using Prussian gazetteers to locate Jewish religious and civil records in Poznan||VI/2/12||1993|
|17||Sephardic migrations into Poland||VI/2/14||1993|
|18||A genealogical tour through Poland||VI/3/16||1993|
|19||Program Judaica to document Jewish history||VI/3/19||1993|
|20||Jewish researcher in Poland||VI/3/39||1993|
|21||Jews in Poland today||VI/4/63||1993|
|22||Polish maps available in the U.S.||VIII/1/58||1993|
|23||Weiner discusses developments in Poland and Ukraine||VIII/3/64||1993|
|24||A 1992 research trip to Poland||VIII/4/12||1993|
|25||Survey of Jewish cemeteries yields results||VIII/4/17||1993|
|26||Cites Polish “rip off”||IX/1/65||1988|
|27||Asks why survey of Polish cemeteries does not include all regions||IX/1/67||1988|
|28||Polish-Jewish genealogical research–A primer||IX/2/04||1988|
|29||More on the survey of Polish cemeteries||IX/2/13||1988|
|30||Book review: Korzenie Polskie: Polish Roots||IX/2/61||1988|
|31||Polish-Jewish heritage seminar planned for July in Krakow||IX/2/65||1988|
|32||Asks for clarification (of Polish-Jewish records)||IX/3/66||1988|
|33||Stettin emigration lists found||IX/3/67||1988|
|34||Head of the Polish State Archives clarifies policies||IX/4/04||1988|
|35||Book review: Jews in Poland: A Documentary History||IX/4/69||1988|
|36||More on Polish-Jewish Genealogical Research||X/1/12||1994|
|37||Directory of Polish State Archives||X/1/14||1994|
|38||Archives of the Jewish Historical Institute in Warsaw||X/1/41||1994|
|39||Jewish genealogical research in Polish archives||X/2/05||1994|
|40||Jewish surnames in the Kingdom of Poland||X/2/15||1994|
|41||Polish sources at the Central Archives for the History of the Jewish People||X/2/21||1994|
|42||Success in dealing with Polish archives||X/2/48||1994|
|43||Gleanings from a symposium on bibliographies of Polish Judaica||X/4/56||1994|
|44||Polish name lists sought||XI/1/67||1995|
|45||Nineteenth-Century Congress Documents and the Jews of Congress Poland||XI/3/24||1995|
|46||Polish Vital Records for the Very Beginner: The Polish Language Challenged||XI/4/29||1995|
|47||Alternate surnames in Russian Poland||XII/2/15||1996|
|48||Census records and city directories in the Krakow Archives||XII/2/27||1996|
|49||Book review: The Jews in Poland and Russia: Bibliographical Essays||XII/2/63||1996|
|50||Alternative research sources in Poland||XII/2/65||1996|
|51||Jewish Historical Institute in Warsaw||XII/3/51||1996|
|52||Director General of the Polish State Archives dies||XII/3/55||1996|
|53||An interview with the new Polish State Archivist||XII/4/03||1996|
|54||On-site Jewish genealogical research in Poland: an overview||XII/4/04||1996|
|55||The Jewish cemetery in Warsaw||XII/4/56||1996|
|56||Book review: Polish Countrysides: Photographs and Narrative||XII/4/81||1996|
|57||German and Polish Place Names||XIV/2/33||1998|
|58||List of More than 300,000 Polish Holocaust Survivors Received by USHMM In Wash. DC 19th- and 20th-Century Polish Directories as Resources for Genealogical Information||XIII/1/25||1997|
|59||Hamburg Passengers from the Kingdom of Poland and the Russian Empire||XIII/2/63||1997|
|60||Lw¢w Ghetto Records Being Indexed||XIII/3/66||1997|
|61||Cites Location of Polish Directories||XIII/4/98||1997|
|62||Jewish Roots in Poland: Pages from the Past and Archival Inventories; And I Still See Their Faces: Images of Polish Jews; Guide to the YIVO Archives; Luboml: Memorial Book of a Vanished Shtetl||XIV/1/63||1998|
|63||Comments on Jewish Roots in Poland||XIV/2/65||1998|
|64||Report on Jewish Communities in Poland Today||XIV/2/65||1998|
|65||How I Found a New Ancestor in Krak¢w, Poland||XIV/4/65||1998|
|66||18th-Century Polish Jewry: Demographic and Genealogical Problems||XV/4/9||1999|
|67||Tips on Translating Entries from Slownik Geograficzny||XVI/3/49||2000|
|68||The Polish Concept of Permanent Place of Residence||XVI/3/12||2000|
|69||More About Polish Books of Residents’ Registration||XVI/3/14||2000|
|70||Can Jewish Genealogists Successfully Research 18th-Century Poland?||XVI/3/16||2000|
|71||History Book Illuminates Jewish Life in Poland||XVI/3/40||2000|
|72||Book Review: History of the Jews in Poland and Russia||XVI/3/65||2000|
|73||Book Review: In Their Words: A Genealogist’s Translation Guide to Polish, German, Latin and Russia Documents. Volume 1: Polish||XVI/4/87||2000|
|74||Breaking New Ground: The Story of Jewish Records Indexing-Poland Project||XVII/1/7||2001|
|75||Documenting the Fate of the Jews of Ostrow Mazowiecka||XVII/3/19||2001|
|76||German and Polish Archival Holdings in Moscow||XVII/4/11||2001|
|77||Internet Site Names Polish Towns||XVII/4/79||2001|
|78||Researching Pre-1826 Vital Records in Congress Poland||XVIII/2/19||2003|
|79||Book Review: Jewish Officers in the Polish Armed Forces, 1939-1945||XVIII/3/62||2003|
|80||Ashes and Flowers: A Family Trek to Jewish Poland and Romania||XVIII/4/11||2003|
|81||Two Polish Directories Online||XVIII/4/91||2003|
|82||Polish Passport Policy 1830-1930: Permits, Restrictions and Archival Sources||XIX/1/21||1998|
|83||Book Reviews: Zród a archiwalne do dziejów Żydów w Polsce||XIX/3/65||1998|
|84||Jewish Surnames in Russia, Poland, Galicia and Prussia||XIX/3/28||1998|
|85||Using Polish Magnate Records for Posen||XIX/3/25||1998|
|86||Avotaynu Online Database Lists Nobility Archives||XIX/4/21||1998|
|87||Hidden Jews of Warsaw||XX/1/47||2004|
|88||Polish archives in Bialystok, Knyszin and Lomza||XX/2/50||2004|
|89||Polychromatic Tombstones in Polish-Jewish Cemeteries||XX/2/39||2004|
|90||Tracing Family Roots Using JRI-Poland to Read Between the Lines||XX/2/15||2004|
|91||Biographical lexicon of Polish rabbis and admorim||XX/3/47||2004|
|92||Flatow Jewish Cemetery Tombstones Discovered||XX/4/79||2004|
|93||Polish City Directories Now Online||XXI/3/67||2005|
|94||Morgenthau Mission to Poland to Investigate the 1919 Pogroms: A Genealogical Resource||XXII/2/14||2006|
|95||What Can We Learn from Slownik Geograficzny?||XXII/2/31||2006|
|96||Spiritual Genealogy: A Look at Polish Notary Documentation||XXII/2/38||2006|
|97||Notes Polish Book and Magnate Records||XXII/3/63||2006|
|98||Exhibit of the Jews of Poznán, 1793–1939||XXIII/1/71||2007|
|99||Strategies for Assigning Surnames to Early JRI-Poland Records||XXIII/2/22||2007|
|100||Book Review: Posen Place Name Indexes||XXIV/1/51||2008|
Yesterday (20th-November-2011), Stanczyk’s iPhone flagged his attention that his Ancestry.com App had an update available (Version 3.0.1).
What’s New in Version 3.0.1
- Now the App has Shaky Leaves! The “Shaky Leaf” hints point you at possible new discoveries.
- A simple merge tool helps toadd new relatives & info to your family tree
- A new in-app purchase option with special pricing for Ancestry.com.
- This new version also automatically adds information to photos
- It allows you to change your tree privacy settings in the App
- Adds an integrated user feedback & support feature
- Its faster and more stable (Time will tell)
I tried it on a new tree with a few people. When I download the tree and used Roots Magic 4.x to display the Gedcom, I still get a tree without the proper family linkages. This bug appeared before iOS5 and still persists. I do not get it on my older pre-iOS5 trees that existed on Ancestry.com (before the bug). This bug is not an Ancestry App bug. So early adopters will not see this bug unless you create a new tree and download the Gedcom file for use in another family tree program. The tree appears just fine on Ancestry.com and also in the Ancestry App. I am not certain what is happening in the GEDCOM format of the file. I can use Roots Magic 4.x on older Ancestry.com trees (downloaded Gedcoms) and the family relationships are fine.
So I am leaning towards this being an Ancestry.com bug (not a Roots Magic bug).
There was NO mention of whether this makes the Ancestry App iOS5 compatible. It says, it requires iOS4 or later to run the App. It is a 15.9MB download so it takes a bit of time and bandwidth to download. Still it is under the 20MB that forces an iTunes on the computer download. Synching works fine in both directions, so you can create or modify your family tree on the web or in the smartphone App and both sides stay in synch. Because you update to 3.0.1, your entire tree will need to be downloaded. If you get to be about 1,000 people this does take a noticeable amount of time. For 100 people trees or less the delay is miniscule.
Download the new version. Portable Genealogy is back. But please Ancestry, can you fix the Gedcom issue, so I do not need to see people complaining on the Ancestry-app-mailing-list any more? Your website should work interoperable with other genealogy programs that support the GEDCOM standard or Ancestry should remove the feature “Supports GEDCOM”.
Besides all the issues I have previously detailed in my last article (iOS5 First Impressions), I have a new issue. This is my sternest recommendation:
DO NOT UPDATE to iOS5 if you use Ancestry APP or CAMERA APP !
On the Mailing List: ANCESTRY-TREE-TO-GO-APP , people have been complaining that Ancestry APP does not work. Now Stanczyk knew it worked and it worked well … But that was BEFORE iOS5 came out.
I confirmed the problem exists on iOS5. It does not download the tree / GEDCOM properly (you get a synch error). If you had a previously downloaded a tree (before iOS5) then you can use that tree. Obviously any changes made on ANCESTRY.com will not be able to synched to your iPhone/iPad.
HOWEVER, if you update your family tree on the iOS5 device, then your changes can be synched in that direction and saved on the Internet and accessed at Ancestry.com. In fact, after you do that you can then get around the above problem. But you had to have a tree on your iOS device BEFORE you upgraded to do this work-around. After synching from iPhone to web. I am NOW able to synch in both directions again.
I suspect this is an Ancestry problem and not an Apple problem. However for portable genealogy this is a PROBLEM. This is a case where an early adopter is fine and the person who just got his/her first iOS device and it came with iOS5 is not able to participate in the portable genealogy revolution.
ANCESTRY.com when will you update your APP for iOS5 ?
a minor or trivial detail(s, trifles)
Stanczyk has been mired in minutia or since it is a plethora of minutia, then perhaps minutiae is appropriate. However, I like the sound of minutia, while minutiae sounds like a Japanese anime character. You see, I am mired in a mountain of minutia — even my writing has been infected by the minutia.
I Tweaked the Blog Again …
- I deleted a redundant page and now have the TABs (really menus, although not properly used that way) at the top. Down the side I now have: About Stanczyk, Gazetteers, & Maps
- Gazetteers is now complete (or at least no longer under construction) and is a credible resource to start your work on gazetteers.
- The other two pages had slight tweaks to them.
- I am evolving the top TABs (Dziennik Polski, Biechow, Pacanow, etc.) in true menus, with menu items. I hope this will organize my materials for faster finding and utilization and to provide for more content, easily found and to make better use of that scarce real estate at the top.
Keep your eyes peeled.
Roots Technology …
Stanczyk has been trying to get his Roots Tech organized and ready to be deployed. As you know technology is slippery as an eel and hard to master/muster into a kind of electronic Swiss knife. My focus is portable genealogy — taking my research & tools with me into the field (uh, libraries, archives, churches/synagogues, courthouses, vital records offices, and cemeteries). So the smartphone and the cloud have been an emphasis. My latest tool in my bag of tricks is the iPhone app: ImageToText . This little application allows you to take a picture of a page of text, it recognizes the text (in the picture just taken), and then you can email that text to yourself (or anyone else really). So now you do not have to scribble down that paragraph of text or that page from a city directory. Just (1) start ImageToText, (2) Take a picture, (3) Send an email. What comes to your mailbox is NOT the image but OCR’ed (OCR is optical character recognition) text in the body of the email message. I like that a lot.
LDS Films Online …
I have mentioned this a couple of times before. It was a concept that was coming. It came. OK I tried it, but I could not use the first implementation because they could NOT return a list of MY Family History Centers (why would I want to order a microfilm that was only for other states, i. e. UT). Ok ,they have finally fixed their problems and I can now report that My Account is working. So go to familysearch.org/film and create an account, set it up and start ordering microfilm.
https://www.familysearch.org/films/customer/account/ - Keep this handy (Bookmark it / Make it a Favorite). This is the link to your Microfilm/Account Dashboard.
Stanczyk was reading his emails, when he noticed Ceil Wendt-Jensen has published a useful website on the various Polish / Michigan genealogy mailing lists.
As the Article title suggests this is another database of military personnel from World War I. This one is unlike the ones you’d find at genealodzy.pl . It is however, similar to these databases and even links to the same Fallen in World War I website. But as I said this website/database is different from those.
The aim of the Prussian Army project (link: http://www.genoroots.com/eng/databases.php) is to provide an easy way of searching through the Deutsche Verlustlisten. This is the Prussian Army’s Personnel Losses during World War I .
The authors of the project: Aleksandra Kacprzak and Mariusz Zebrowski. They are still updating so check back from time to time. If you click on the “Prussian Army project” link above it will take you to its databases page. There under the ‘Prussian Army’ Heading you will see a link ‘Search’. Click on ‘search’ link. You should see the following search form:
Fill in a name and click on the ‘Search’ button. That is it. Should you find an ancestor, you can email them for more info. There is a very modest charge for this follow-on service (the search is free, the detailed info is where the cost is). So if you find someone, then …
e-mail: firstname.lastname@example.org. When asking for further information, you must provide the ordinal number (‘L.P.’), the first and last name and the rank of the person in question. The additional information costs 2 Euro per name (=$2.82 as of 10/27/2011), payable via PayPal (to email@example.com ). Stanczyk is not affiliated and has no conflict of interest in these entrepreneurial Poles. I did not find any of my ancestors, so I cannot tell you what details you may find. My ancestors were from the Russian-Poland partition (and hence would have been in the Russian army) — keep in mind this Prussian army (not Russian, not Austrian).
Good Luck! Please send me an email with a sample detail if you send for it. Thanks!
Family Chronicle magazine (September/October 2011 issue) has a couple of interesting articles in the current magazine .
Here are some I think you should read …
- Eastern European Research Made Easier!
Lisa A. Alzo discusses seven strategies to help you trace your East European ancestors
- The Case of the Missing Sisters
Donna J. Pointkouski recounts her research quest to find her great-grandmother’s elusive siblings
- Writing a Codicil to Protect Your Genealogy Collection
Patti R. Albaugh, PhD, looks at the simple steps you can take to ensure your family history research lives on
This last one caught this jester’s eye. We spend so much time on this research and perhaps even hire other genealogists to assist us, so there is a very good chance that the information you have collected might not be able to reproduced or it may no longer be cost effective to reproduce. So where are your family tree and source documents going when you have departed?
I think you should do the following (please send me your suggestions — emails can be sent on the right side of this column):
- Place a copy in the Family History Library; at least send your gedcom to FamilySearch.org
- Many local libraries or archives take Family Histories. For example, the Historical Society of PA (HSP.org) has a room of family histories (you should visit it) and if you have written a self-published book make sure a copy goes to your local library.
- You should also make sure that other locales you or your direct line family have lived also have a copy of your genealogy. In my case, I will do at least the State of MI Library , and HSP and probably Toledo Public Library. I may consider Buffalo Public Library (their Grosvenor room) and perhaps Mt Clemens, Public Library too.
- What about the Source Documents (Birth/Death/Marriage/Nat’l Certificates? Bibles? Do you have someone in the family that REALLY wants these heirlooms? I hope they are reproduced in your self-published book.
- Send gedcoms to other genealogists who are family or interested in your family trees. I do this almost annually as a means of backing up my research to CDs and sending them to these remote family researchers; its a good offsite backup. You can put them in EMAILS, Write a CD (with copies of the source documents — fill up the 680+ MB) with the gedcom, use the Internet (Cloud anyone?) — for example use DropBox or Google’s Cloud and grant READ access to other genealogists and interested family members.
That’s my musing for today. I am truly interested in what you are doing. Drop me an email or leave a comment. I am sure other genealogists are thinking about this or perhaps need to be thinking about this.
Oh, have you documented your life too? I think a lot of genealogists, spend time on everybody else but themselves in the family tree. Do not forget to document your life.
Make sure your Will reflects the donations if you do not accomplish them while you are amongst the living. Give considerable thought to your heirlooms. What happens if the intended person pre-deceases you? Make sure your contingencies are accounted for. I do not know about you, but I think I will read Patti R. Albaugh’s article and do some thinking.
This jester thanks my Slavic readers from: Poland, Russian Federation, Czech Republic, Ukraine, Latvia, Belarus, Slovakia, etc and of course their American emigres and American born of that heritage. This is after all predominantly a blog of genealogy that focuses on its Slavic Heritage and especially the heritage of Stanczyk‘s paternal grandparents who were born, married, had children and emigrated from Poland … Russian-Poland also known as Congress Kingdom of Poland and to a lesser degree, Vistulaland (a collection of ten gubernia in the czarist Russian Empire). Poland was occupied and partitioned between three Empires: Prussian (German), Austrian (Austro-Hungarian / Hapsburg), and Russian from 1792-1918. As such, in the Russian partition, they were subject to the Czar’s ukases (decrees).
A UKASE (указ) is formally an “imposition” , usually by the czar, but possibly by an Orthodox Patriarch. But ukase is usually translated as decree or edict.
My ancestors were from the Russian-Poland partition, but just across the Vistula (Wisla) river from the Austrian-Poland partition — which had, to me, a surprising number cross-Empire interaction in vital records. The Russian-Poland nominally a fiefdom of the Russian Czar, who was also titled as King of Poland, as well as Russian Emperor.
There were many Ukases from each czar/czarina. So many so, that Czar Nicholas in 1827 ordered a collation of these edicts (a kind of codification Russian law). The result was a 48 volume collection of ukases. Some notable ukases …
- Created (1791) and others amended the Pale of Settlement
- 1821 Territorial waters off Alaska (affecting British Empire and a young America)
- 1861 Freeing the Serfs
- 1868 Decreed that vital records in the Kingdom of Poland be recorded in Russian
Stanczyk is fascinated by the last one. It is said that it is in the Polish DNA to be multi-lingual. Certainly, my grandmother was capable of four languages (Polish, Russian, German, and finally English). But how did the Catholic priests do this? Switching from recording vital records in Polish to recording them into Russian? The year of the switch-over was 1868. The records start out in Polish but switch during the year to being in Russian ??? Admittedly, the Russian in most cases was a bit … uh “problematic”.
Can you imagine that happening in America? Most of the world thinks of the USA as being linguistically challenged. This jester is fluent only in English. I did receive much French tutelage and can read French. With my genealogy, I have been self taught in Polish, Russian and Latin. Thankfully, Google provides the Google Translator, flawed as it is, for Polish. Still as it was, I was able to use it communicate with a distant cousin in Poland who could not speak any English and my ability to write Polish was so very limited. Yet we overcame and I was blessed with the gift of my grandparent’s marriage record from Biechow church and a civil record of their marriage from a local USC office.
And it was a good thing my cousin sent me both. As the USC mistranslated the Russian language church record on my grandmother’s age. They had accidentally added five years to my grandmother’s age, which I would not have known if I did not have the original church record in Russian (which apparently the local USC could not read as well as I could).
So here is Stanczyk’s UKASE …
All Polish Genealogists must be able to read Latin, Polish, and Russian. (Who can read that German handwriting?)