A new cellphone app touts itself as a way for Iceland's singles to avoid sleeping with relatives — as the isolated country's small population of 320,000 means most people are related. The acquaintances just have to bump their phones together and it tells them instantly if they're family, News of Iceland reports. Three Icelandic engineers designed the app with the help of the Book of Icelanders that contains data from 720,000 people born in Iceland. News of Iceland says, "Everyone has heard of (or experienced) it when someone goes all in with someone and then later runs into that person at a family gathering some other time. This new app might just prevent such awkward moments."
Genealogy notes and news
Notes and news on genealogy and family history by Steve Hayes and Val Greene. We live in Tshwane, South Africa, and we are especially interested in family history in southern Africa, the UK, Germany, Australia, New Zealand and Canada.
Saturday, April 20, 2013
New app prevents incest in Iceland
New application for computerised genealogy: New app prevents incest in Iceland | World | News | The London Free Press:
Monday, April 08, 2013
With all the eulogies on Margaret Thatcher, remember this
The Right got it so wrong on Nelson Mandela – Telegraph Blogs: It’s easy with the passage of time to forget how the Conservative Right in Britain got it so badly wrong on South Africa, and today how long it has been since the British Left got it so right.
Friday, April 05, 2013
Where does the time go?
I've sometimes downloaded time tracking software to see how much time I spend on various projects, but most if it is so complex that you spend more time on the tracking than on the project. But here is one that looks simple enough even for me Where does the time go?:
Back in November, I decided I wanted to track the time I spent on various genealogy projects. One reason for this was to be able to better plan my monthly to-do lists (I have a tendency to overbook myself). I knew I wanted a web-based system (preferably one that was free). There are several available, but Toggl appealed to me as soon as I saw it, so I decided to give it a test run. I’ve been using Toggl for three months now and I don’t know how I lived without it. (Note that this is toggl – no e.) Everything about Toggl is so easy and intuitive. To get started, you can either sign up by entering your email address and a password or simply log in with your Google account. It doesn’t get any easier than that!
Labels:
time management,
time tracking
Tuesday, March 19, 2013
Where on earth is the Shoshongo Dum?
Edward C. Tabler, in his book Pioneers of South West Africa & Ngamiland makes quite frequent reference to the Shoshongo Dum. It does not, however, appear on modern maps of Namibia or Botswana (the area covered by Tabler's book). Nor does it appear on any ancient maps that I've been able to look at. So where on earth is the Shoshongo Dum?
Tabler says, on page 36, of the trader Axel Wilhelm Eriksson (who married Fanny Stewardson, a relative of my wife), that "Eriksson's party trekked down the Shoshongo Dum in October 1878, travelled up the Okavango to the Omuramba Ombongo, and returned to Omaruru by way of eastern Ovamboland."
Several books with the writings of 19th-century travellers have been printed or reprinted in the last 30 years, and they often provide a "Register" giving a summary of information about the people and places mentioned in the book. But none of those I have seen gives any explanation of the Shoshongo Dum.
Tabler's text suggests that the Shoshongo Dum might be a river, and might possibly be a tributary of the Okavango. But the Okavango is a pretty big river, and flows through three countries -- Angola, Namibia and Botswana, so, if the Shoshongo Dum is a river, where does it join the Okavango? And what is its modern name, so one can find it on a map?
Nowadays such things should be easy to find. We have the World Wide Web which has accumulated a huge amount of information since it started 20 years ago, and there are search engines to help you find it.
So I did a Google search for Shoshongo Dum, and when I had managed to convince Google that I was not looking for "Shoshone Dam" or "Shoshone Drum" it spat out just one reference: Oxen or Onions? The Search for Trade (and Truth) in the Kalahari, an article in Current Anthropology published in 1991. Other search engines returned nothing at all, so Google is still the top search engine on the Web.
There was nothing on Wikipedia, so I thought I'd put a stub of an article there, just in case anyone else should be looking for the Shoshongo Dum and wondering what it was. But Wikipedia would not let me link to the one article Google found that contained the term (and even there, only in a footnote). Wikipedia had blacklisted it.
Still, I suppose if I'd tried to look for it in the 19th century it would have taken me several months, if not years, instead of a few hours.
So if anyone is looking for the Shoshongo Dum, and Wikipedia continues to block the article, maybe this blog post can help people to find it.
And if anyone knows the modern name for it, or why it was called Shoshongo Dum in the first place, I hope they will let me know.
Tabler says, on page 36, of the trader Axel Wilhelm Eriksson (who married Fanny Stewardson, a relative of my wife), that "Eriksson's party trekked down the Shoshongo Dum in October 1878, travelled up the Okavango to the Omuramba Ombongo, and returned to Omaruru by way of eastern Ovamboland."
Several books with the writings of 19th-century travellers have been printed or reprinted in the last 30 years, and they often provide a "Register" giving a summary of information about the people and places mentioned in the book. But none of those I have seen gives any explanation of the Shoshongo Dum.
Tabler's text suggests that the Shoshongo Dum might be a river, and might possibly be a tributary of the Okavango. But the Okavango is a pretty big river, and flows through three countries -- Angola, Namibia and Botswana, so, if the Shoshongo Dum is a river, where does it join the Okavango? And what is its modern name, so one can find it on a map?
Nowadays such things should be easy to find. We have the World Wide Web which has accumulated a huge amount of information since it started 20 years ago, and there are search engines to help you find it.
So I did a Google search for Shoshongo Dum, and when I had managed to convince Google that I was not looking for "Shoshone Dam" or "Shoshone Drum" it spat out just one reference: Oxen or Onions? The Search for Trade (and Truth) in the Kalahari, an article in Current Anthropology published in 1991. Other search engines returned nothing at all, so Google is still the top search engine on the Web.
There was nothing on Wikipedia, so I thought I'd put a stub of an article there, just in case anyone else should be looking for the Shoshongo Dum and wondering what it was. But Wikipedia would not let me link to the one article Google found that contained the term (and even there, only in a footnote). Wikipedia had blacklisted it.
Still, I suppose if I'd tried to look for it in the 19th century it would have taken me several months, if not years, instead of a few hours.
So if anyone is looking for the Shoshongo Dum, and Wikipedia continues to block the article, maybe this blog post can help people to find it.
And if anyone knows the modern name for it, or why it was called Shoshongo Dum in the first place, I hope they will let me know.
Labels:
Africa,
Botswana,
exploration,
geography,
history,
location,
maps,
Namibia,
place names,
places,
search engines,
Shoshongo Dum,
toponymy,
Wikipedia
Thursday, February 21, 2013
Resources for the Online Genealogist
Here's a useful list of online resources. I knew about some of them, of course, but there are others I did not know about. I think the "must have" applies only to genealogists in North America, and that people in other places might add a few that aren't there, and leave out a few that are not really essential. But it's still useful to have: 88 Must Have Resources for the Online Genealogist | Free People Search:
This collection of resources can help you uncover nearly all of the missing leaves on your family tree. Included are searchable databases of vital records, helpful guides, genealogical communities, unique tools, regionally targeted articles with a global reach. The first portion is entirely free. Those that require payment are listed at the end. While not every record is available online through every service, it is possible to use database searches to uncover local records you require, then community based organizations to share labor and access what you normally would be unable to all from the comfort of your own home.Hat-tip to Randy Seaver, whose blog Genea-Musings: What are the Must-Have Resources for Genealogists? is one of the resources mentioned. Randy regrets that his name was not mentioned in the list, so I have mentioned it here.
Wednesday, February 06, 2013
Racism in South African genealogy
About a week ago someone remarked, on a South African genealogical mailing list, that he had found that some people were compiling "indexes" to some civil registers that had been made available for browsing online, But he had found that those indexes were not complete, and appeared to exclude those with obviously African names, and even those judged to be coloured. He queried this practice, and asked why an index should not be a complete index.
I had not consulted either the indexes or the records themselves, so I cannot say that I know for certain that indexers have been excluding entries on the grounds of perceived race, but I did say that, as a matter of principle, I thought that partial indexes would be worse than useless, particularly if there was no indication that they were partial, and no indication given of the criteria for inclusion or exclusion.
I was rather surprised by the the vehement response on the part of some participants, who saw this as an unfair attack on those who had so unselfishly given their time and energy to providing indexes for the use of researchers, and praised them for what they were doing, and said that they should not be deterred by those who questioned the exclusionary practices. Those who questioned these practices were labelled "grumpies", which seemed to be regarded as a sufficent defence of the practices themselves. It was basically an attempt to evade the issue, thus making it clear that there is a great deal of racism in South African genealogical circles.
The racism has been there for a long ntime.
When I first became seriously interested in genealogy, when I got married in 1974, I joined the Genealogical Society of South Africa (GSSA). It soon became apparent that the main focus of the society was was the genealogy of white Afrikaans-speaking South Africans. That was the genealogy of "the South African nation". English-speaking South Africans were very much second-class citizens, and the attitude towards them was rather condescending. Including black South Africans was unthought of and probably unthinkable to those who ran the show. And it seems that those attitudes persist in some genealogical circles in South Africa even today, and they try to justify them by calling those who question them "grumpies".
Perhaps someone could write a doctoral thesis on racism in South African genealogy, and maybe do a comparison with the Nazi Sippenbucher in Germany.
Quite apart from the question or racism, however, there is the problem of being honest (or dishonest) with the historical record. Omitting records in a public index is a form of falsification, as is adding false records, in the way this article describes.
There has been some discussion of that article in the soc.genealogy.britain newsgroup, and one poster there said it didn't matter if the records were falsified because genealogy is "only a hobby".
It may be "only a hobby" to some people, but genealogy is also an ancilliary science of history, and the study of genealogy can reveal a great deal about political, economic and religious history. You want to know why such-and-such a firm in Port Elizabeth exported the products of such and such a town in the Karroo? Because the biggest shopkeeper in that town was the brother-in-law of the owner of the firm in Port Elizabeth. In politics, nepotism is rife and always has been. In religion, you can see missionaries go to a place and start a church, and as it grows, many of the new members are relatives of the first members.
The role of the Msimang family in the growth of Methodism in both Natal and Swaziland is of interest to church historians, and their activities had political and economic repercussions as well. Now if someone decides, on the basis of a personal whim, or racism, to omit members of the Msimang family from a public index, they could mislead historians who are interested in more than just genealogy for its own sake. It's more than "just a hobby".
I once, in the course of a historical research project, interviewed a lot of black Anglican clergy in Zululand, and I asked them about their family history. One of them said to me, "We Zulus think we know a lot about this, but we don't."
I would like to see more South Africans, of all racial and ethnic backgrounds, become interested in genealogy and see that "the South African nation" is indeed a rainbow nation, and if that makes me a "grumpy", then long live grumpiness.
I had not consulted either the indexes or the records themselves, so I cannot say that I know for certain that indexers have been excluding entries on the grounds of perceived race, but I did say that, as a matter of principle, I thought that partial indexes would be worse than useless, particularly if there was no indication that they were partial, and no indication given of the criteria for inclusion or exclusion.
I was rather surprised by the the vehement response on the part of some participants, who saw this as an unfair attack on those who had so unselfishly given their time and energy to providing indexes for the use of researchers, and praised them for what they were doing, and said that they should not be deterred by those who questioned the exclusionary practices. Those who questioned these practices were labelled "grumpies", which seemed to be regarded as a sufficent defence of the practices themselves. It was basically an attempt to evade the issue, thus making it clear that there is a great deal of racism in South African genealogical circles.
The racism has been there for a long ntime.
When I first became seriously interested in genealogy, when I got married in 1974, I joined the Genealogical Society of South Africa (GSSA). It soon became apparent that the main focus of the society was was the genealogy of white Afrikaans-speaking South Africans. That was the genealogy of "the South African nation". English-speaking South Africans were very much second-class citizens, and the attitude towards them was rather condescending. Including black South Africans was unthought of and probably unthinkable to those who ran the show. And it seems that those attitudes persist in some genealogical circles in South Africa even today, and they try to justify them by calling those who question them "grumpies".
Perhaps someone could write a doctoral thesis on racism in South African genealogy, and maybe do a comparison with the Nazi Sippenbucher in Germany.
Quite apart from the question or racism, however, there is the problem of being honest (or dishonest) with the historical record. Omitting records in a public index is a form of falsification, as is adding false records, in the way this article describes.
There has been some discussion of that article in the soc.genealogy.britain newsgroup, and one poster there said it didn't matter if the records were falsified because genealogy is "only a hobby".
It may be "only a hobby" to some people, but genealogy is also an ancilliary science of history, and the study of genealogy can reveal a great deal about political, economic and religious history. You want to know why such-and-such a firm in Port Elizabeth exported the products of such and such a town in the Karroo? Because the biggest shopkeeper in that town was the brother-in-law of the owner of the firm in Port Elizabeth. In politics, nepotism is rife and always has been. In religion, you can see missionaries go to a place and start a church, and as it grows, many of the new members are relatives of the first members.
The role of the Msimang family in the growth of Methodism in both Natal and Swaziland is of interest to church historians, and their activities had political and economic repercussions as well. Now if someone decides, on the basis of a personal whim, or racism, to omit members of the Msimang family from a public index, they could mislead historians who are interested in more than just genealogy for its own sake. It's more than "just a hobby".
I once, in the course of a historical research project, interviewed a lot of black Anglican clergy in Zululand, and I asked them about their family history. One of them said to me, "We Zulus think we know a lot about this, but we don't."
I would like to see more South Africans, of all racial and ethnic backgrounds, become interested in genealogy and see that "the South African nation" is indeed a rainbow nation, and if that makes me a "grumpy", then long live grumpiness.
Friday, January 11, 2013
South African archives computers down for a week
Researchers trying to consult the computers that hold the indexes to the South African archives have been greeted with this message since last week:
The computer systems are used by the archives staff, and by researchers in such topics as history and genealogy, either remotely via the web, or at the archives themselves.
When researchers began reporting that the system was inaccessible last weekend, there were some jokes about civil servants not working at weekends, and people expected the system to be up and running again by Monday or Tuesday at the latest.
When it wasn't, people began looking a bit more closely at this "SITA", and discovered that it is not run by civil servants at all. It seems that a lot of the state's information and computer services have been privatised. SITA's web site tells us
It also tells us that it is SITA (Pty) Ltd, which means that it has been wholly privatised.
Perhaps it is time for some investigative journalists to start looking into SITA and how it operates, who it is responsible/accountable to, if anyone. Privatising an important strategic resource for government somehow doesn't seem like a good idea.
SITA Inverse Web Proxy Server
The requested URL could not be retrieved
While trying to retrieve the URL:
http://www.national.archsrch.gov.za/sm300cv/smws/sm300dl
The following error was encountered:
Connection FailedThe system returned:
(60) Operation timed out
The remote host or network may be down. Please try the request again.
Your cache administrator is sitasc@sita.co.za.
The computer systems are used by the archives staff, and by researchers in such topics as history and genealogy, either remotely via the web, or at the archives themselves.
When researchers began reporting that the system was inaccessible last weekend, there were some jokes about civil servants not working at weekends, and people expected the system to be up and running again by Monday or Tuesday at the latest.
When it wasn't, people began looking a bit more closely at this "SITA", and discovered that it is not run by civil servants at all. It seems that a lot of the state's information and computer services have been privatised. SITA's web site tells us
SITA is committed to leveraging Information Technology as a strategic resource for government
SITA was established in 1999 to consolidate and coordinate the State’s information technology resources in order to achieve cost savings through scale, increase delivery capabilities and enhance interoperability.
It also tells us that it is SITA (Pty) Ltd, which means that it has been wholly privatised.
Perhaps it is time for some investigative journalists to start looking into SITA and how it operates, who it is responsible/accountable to, if anyone. Privatising an important strategic resource for government somehow doesn't seem like a good idea.
Wednesday, January 02, 2013
Computers and genealogy -- some pitfalls
When we started on genealogy soon after we were married, back in 1974, we didn't have a computer. Nobody we knew had a computer either. The only computers we encountered were in building societies (remember them?). Even the banks that later took over the building societies didn't have computers, but entered transactions manually in savings passbooks.
I kept hoping that somewhere, somehow, a computer would become available where one could enter information once, and instead of labouriously writing out family group sheets by hand to send to distant relatives by snail mail, one could just print them out. And when the reply came that great uncle Joe was born on 3 November and not 3 July, one could just correct it once.
Well, within ten years the dream came true, and we could do just that.
We had an Osborne portable computer (not a laptop, it was the size of a small suitcase, or a large briefcase). It came woith a word processor (Wordstar) a spreadsheet (Supercalc) and a database (Personal Pearl). It stored its programs and data on two 185k floppy disks. We bought a genealogy program, Roots/M, which cost $US49.00, which, in the days before the Rubicon Rand, was quite affordable.
And so we enjoyed all the things we had only dreamed of before. We began typing in the family tree, and could print out family group sheets to send to relatives (still by snail mail, but it was a lot easier than writing them by hand). We also discovered limitations. Roots/M loaded all its data into memory, and the Osborne computer only had 128k of memory. The disks, with 185k, were also rather small. But we began typing some of the paper documents we had -- wills and the like. The handwriting was often hard to read, so typing them up made it easer to find things.
Fast-forward to 2013.
A relative of a relative of a relative (don't ask!) writes from Montreal to say he can look up information for us about John Gray, the founder and firs tpresident of the Bank of Montreal. He wanted to know the source of the information we already had, so he could know where to start looking.
Ah, yes, we had typed out the will of John Gray in 1987, on the Osborne Executive, in WordStar, running under the CP/M operating system.
And, when we had got an MS DOS computer later that year (with a hard disk with all of 20 megabytes) I had taken the precaution of using a disk conversion program, called UniForm, to copy the Osborne data files over to disks in MS DOS format. .
So yes, there is a copy of the will on my hard disk in an archive somewhere. But it is in WordStar, and I no longer have a copy of WordStar on my disk, and even if I did, I doubt that I could remember how to use it.
But what I do have on my disk is a word processor conversion program, called Word for Word. It also dates from about 1987, when there were about 20 or more different word processors on the market, each using a different format. But not one of them can be read by the word processors in common use today, LibreOffice and Microsoft Word.
So I convert it into XyWrite III+, which I do still have on my computer. But XyWrite III+ was designed for publishing, and all publishers' typesetters knew that you set underlined text (typed on a typewriter) as italics. So you used Mode Underline, and set the printer to print it as italics (laser printers were versatile in those days). You could typeset a book in XyWrite, no problem. That's what it was designed for. As a word processor, MS Word still hasn't caught up, 25 years later. Word has more bells and whistles, yes, but not as many pistons and cylinders as XyWrite.
The trouble is, XyWrite is a DOS program, and modern dumbed-down printers can't cope. So I convert it to XyWrite 4.0, and make one change. I type "ch /MDUL/MDIT/" that converts all the underlines to italics, which modern printers can understand.
Then I save the XyWrite 4.0 document as an RTF file (Rich Text Format), and import it into LibreOffice or MS Word, and print it as a PDF (Portable Document Format) file, which I send to the guy in Montreal.
So now I have these copies of John Gray's will on my computer: GRAYWILL.TXT (WordStar), GRAYWILL.XY3, GRAYWILL.XY4, GRAYWILL.RTF, GRAYWILL.ODT and finally GRAYWILL.PDF.
Six copies, where there was only one before. Am I going to delete any of them, as "surplus to requirements"?
Not a chance. Who knows when some "advance" in computer technology might make it impossible to read one or more of them? The workaround was cumbersome, but it was a lot easier than retyping the will of John Gray.
And the lesson for genealogists is this: when you "upgrade" to a new computer, don't be conned by some glib salesman into just buying the latest and greatest.
First make sure that you can use it to access and work with the data you have spent hours and hours and days and days typing in. You might find that Gee-Whiz graphics and amazing surround sound are a poor compensation for all that lost labour.
I kept hoping that somewhere, somehow, a computer would become available where one could enter information once, and instead of labouriously writing out family group sheets by hand to send to distant relatives by snail mail, one could just print them out. And when the reply came that great uncle Joe was born on 3 November and not 3 July, one could just correct it once.
Well, within ten years the dream came true, and we could do just that.
We had an Osborne portable computer (not a laptop, it was the size of a small suitcase, or a large briefcase). It came woith a word processor (Wordstar) a spreadsheet (Supercalc) and a database (Personal Pearl). It stored its programs and data on two 185k floppy disks. We bought a genealogy program, Roots/M, which cost $US49.00, which, in the days before the Rubicon Rand, was quite affordable.
And so we enjoyed all the things we had only dreamed of before. We began typing in the family tree, and could print out family group sheets to send to relatives (still by snail mail, but it was a lot easier than writing them by hand). We also discovered limitations. Roots/M loaded all its data into memory, and the Osborne computer only had 128k of memory. The disks, with 185k, were also rather small. But we began typing some of the paper documents we had -- wills and the like. The handwriting was often hard to read, so typing them up made it easer to find things.
Fast-forward to 2013.
A relative of a relative of a relative (don't ask!) writes from Montreal to say he can look up information for us about John Gray, the founder and firs tpresident of the Bank of Montreal. He wanted to know the source of the information we already had, so he could know where to start looking.
Ah, yes, we had typed out the will of John Gray in 1987, on the Osborne Executive, in WordStar, running under the CP/M operating system.
And, when we had got an MS DOS computer later that year (with a hard disk with all of 20 megabytes) I had taken the precaution of using a disk conversion program, called UniForm, to copy the Osborne data files over to disks in MS DOS format. .
So yes, there is a copy of the will on my hard disk in an archive somewhere. But it is in WordStar, and I no longer have a copy of WordStar on my disk, and even if I did, I doubt that I could remember how to use it.
But what I do have on my disk is a word processor conversion program, called Word for Word. It also dates from about 1987, when there were about 20 or more different word processors on the market, each using a different format. But not one of them can be read by the word processors in common use today, LibreOffice and Microsoft Word.
So I convert it into XyWrite III+, which I do still have on my computer. But XyWrite III+ was designed for publishing, and all publishers' typesetters knew that you set underlined text (typed on a typewriter) as italics. So you used Mode Underline, and set the printer to print it as italics (laser printers were versatile in those days). You could typeset a book in XyWrite, no problem. That's what it was designed for. As a word processor, MS Word still hasn't caught up, 25 years later. Word has more bells and whistles, yes, but not as many pistons and cylinders as XyWrite.
The trouble is, XyWrite is a DOS program, and modern dumbed-down printers can't cope. So I convert it to XyWrite 4.0, and make one change. I type "ch /MDUL/MDIT/" that converts all the underlines to italics, which modern printers can understand.
Then I save the XyWrite 4.0 document as an RTF file (Rich Text Format), and import it into LibreOffice or MS Word, and print it as a PDF (Portable Document Format) file, which I send to the guy in Montreal.
So now I have these copies of John Gray's will on my computer: GRAYWILL.TXT (WordStar), GRAYWILL.XY3, GRAYWILL.XY4, GRAYWILL.RTF, GRAYWILL.ODT and finally GRAYWILL.PDF.
Six copies, where there was only one before. Am I going to delete any of them, as "surplus to requirements"?
Not a chance. Who knows when some "advance" in computer technology might make it impossible to read one or more of them? The workaround was cumbersome, but it was a lot easier than retyping the will of John Gray.
And the lesson for genealogists is this: when you "upgrade" to a new computer, don't be conned by some glib salesman into just buying the latest and greatest.First make sure that you can use it to access and work with the data you have spent hours and hours and days and days typing in. You might find that Gee-Whiz graphics and amazing surround sound are a poor compensation for all that lost labour.
Wednesday, December 19, 2012
Can Clooz replace the Research Data Filer to keep track of paper files?
For a long time now (about 20 years) I have been using the Research Data Filer program to keep track of paper files in my genealogical research.
As you might guess, a 20 year-old-computer program is getting close to retirement age, ready to hand over to a younger and more vigorous successor, and take a well-earned rest.
The trouble is that there is no successor anywhere in sight. There is no program that I know of that can do what the Research Data Filer (RDF) did (and for me, still does).
In 38 years of genealogical research one accumulares a lot of paper -- notes, letters, family trees sent by other people, notes from books and other published sources. How do you keep track of this stuff? How do you remember where you put that note or letter?
Using the ResearchData Filer (RDF) you give every document a number, and you file the documents in numerical order, like this:
There is no need to file them in any order but numerical, in the order in which they are filed (the KISS principle -- Keep It Simple, Stupid).
Then you use the Research Data Filer to write a description of each document, like this:
(Sorry that the reduced functionality of Blogger makes the screenshot small and hard to read - that's one of the reasons I've moved my other blogs to Wordpress)
If you look hard you can see that item 3, DOC 00003 is a printed book. No, I did not put the printed book in the file. What I put in the file was a piece of paper with biblographgical information about the book, and extracts of relevant information from it. When I want to see what I put in those notes again, and want to remember where I put them, RDF tells me that it is filed as Document 3, which I filed between Document 2 and Document 4. Simple, isn't it?
If I'm not sure which document has the relevant information, I can search the document descriptions. RDF has a "focus" capability. I can focus on all document descriptions that contain the word "death", for example, and then I can focus again on only those that contain the word "Beningfield"
But that's not all.
In addition to the "Document" file, RDF also has a "Data" file, which indexes the data within documents. Because we're doing genealogy, we're interested in people, and that's what it indexes.
That screen shows a "focus" search on Id 14952, which happens to be the RIN of Adam Cottam in my main fata file. It shows references to one document on this screen, but could also show references to him in many documents. The fields shown are Name, Sex, ID, Event, Event Date, Event Place, Relations, Ids of Relations, Comments, and of course the Document number. And one can sort the results of a "focus" by name, Id, date, place or relations, and print them out, or save them to another file.
There's more about RDF and how tt helps me to keep track of my paper files here.
RDF used to come with early editions of PAF, the Personal Ancestral File program distributed by the Church of Jesus Chrtist of Latter-Day Saints. PAF itself has been updated to a Windows version, but RDF hasn't. It is more difficult to use in Windows, because most Windows printers won't print output from DOS programs directly, and you have to resort to clumsy workarounds that take longer.
Also, RDF was designed in the days when most genealogists who used computers had computers with 360k floppy disks and no hard disks at all, so one of the important design considerations was to take up as little disk space as possible. My GENERAL.DAT file is about 1,2 Megabytes, which would be reaching the limits of a high-density floppy disk of the late 1980s.
Nowdays, with hard disk capacities being measured in terabytes rather than kilobytes, it would be nice to have an updated version that would give a little more room for additional information.
And there's the rub, because there isn't an updated version. RDF was designed in 1989 or earlier. But it still hasn't been surpassed. I know of no other program that can do what it does, as well as it does it. I can think of lots of ways in which it could be improved, but it still does what it does better than any other program out there.
I've looked at some other programs that I thought might be possible replacements. There were Genota and Genforms being developed by Dennis Allsopp in Australia, which didn't do quite the same thing, and there was Clooz. I bought Clooz 2.0 to test as a possible replacement, but found it too clunky and awkward to use, and entering information was too time-consuming.
Clooz 3 is now available -- an updating and streamlining of Clooz 2. But they are now working on Clooz 4.0, which will be a complete redesign and rewiting of Clooz 3 from the ground up, rather than a mere tweak. So I'm now hoping that, whatever else it includes, it will include the functionality and capability of RDF, enhanced, rather than diminished.
Yes, you could keep the information in RDF .DOC and .DAT files in a spreadsheet, but most spreadsheets still can't handle dates before 1900, nor can they handle partial or fuzzy dates like "ABT May 1832" or "AFT Sep 1856".
I wish I knew who wrote RDF. It was a work of genius, making the most of the capabilities of computers of its time. If it were updated to make use of today's computers, it would be very powerful indeed.
As you might guess, a 20 year-old-computer program is getting close to retirement age, ready to hand over to a younger and more vigorous successor, and take a well-earned rest.
The trouble is that there is no successor anywhere in sight. There is no program that I know of that can do what the Research Data Filer (RDF) did (and for me, still does).
In 38 years of genealogical research one accumulares a lot of paper -- notes, letters, family trees sent by other people, notes from books and other published sources. How do you keep track of this stuff? How do you remember where you put that note or letter?
Using the ResearchData Filer (RDF) you give every document a number, and you file the documents in numerical order, like this:
There is no need to file them in any order but numerical, in the order in which they are filed (the KISS principle -- Keep It Simple, Stupid).
Then you use the Research Data Filer to write a description of each document, like this:
(Sorry that the reduced functionality of Blogger makes the screenshot small and hard to read - that's one of the reasons I've moved my other blogs to Wordpress)
If you look hard you can see that item 3, DOC 00003 is a printed book. No, I did not put the printed book in the file. What I put in the file was a piece of paper with biblographgical information about the book, and extracts of relevant information from it. When I want to see what I put in those notes again, and want to remember where I put them, RDF tells me that it is filed as Document 3, which I filed between Document 2 and Document 4. Simple, isn't it?
If I'm not sure which document has the relevant information, I can search the document descriptions. RDF has a "focus" capability. I can focus on all document descriptions that contain the word "death", for example, and then I can focus again on only those that contain the word "Beningfield"
But that's not all.
In addition to the "Document" file, RDF also has a "Data" file, which indexes the data within documents. Because we're doing genealogy, we're interested in people, and that's what it indexes.
That screen shows a "focus" search on Id 14952, which happens to be the RIN of Adam Cottam in my main fata file. It shows references to one document on this screen, but could also show references to him in many documents. The fields shown are Name, Sex, ID, Event, Event Date, Event Place, Relations, Ids of Relations, Comments, and of course the Document number. And one can sort the results of a "focus" by name, Id, date, place or relations, and print them out, or save them to another file.
There's more about RDF and how tt helps me to keep track of my paper files here.
RDF used to come with early editions of PAF, the Personal Ancestral File program distributed by the Church of Jesus Chrtist of Latter-Day Saints. PAF itself has been updated to a Windows version, but RDF hasn't. It is more difficult to use in Windows, because most Windows printers won't print output from DOS programs directly, and you have to resort to clumsy workarounds that take longer.
Also, RDF was designed in the days when most genealogists who used computers had computers with 360k floppy disks and no hard disks at all, so one of the important design considerations was to take up as little disk space as possible. My GENERAL.DAT file is about 1,2 Megabytes, which would be reaching the limits of a high-density floppy disk of the late 1980s.
Nowdays, with hard disk capacities being measured in terabytes rather than kilobytes, it would be nice to have an updated version that would give a little more room for additional information.
And there's the rub, because there isn't an updated version. RDF was designed in 1989 or earlier. But it still hasn't been surpassed. I know of no other program that can do what it does, as well as it does it. I can think of lots of ways in which it could be improved, but it still does what it does better than any other program out there.
I've looked at some other programs that I thought might be possible replacements. There were Genota and Genforms being developed by Dennis Allsopp in Australia, which didn't do quite the same thing, and there was Clooz. I bought Clooz 2.0 to test as a possible replacement, but found it too clunky and awkward to use, and entering information was too time-consuming.
Clooz 3 is now available -- an updating and streamlining of Clooz 2. But they are now working on Clooz 4.0, which will be a complete redesign and rewiting of Clooz 3 from the ground up, rather than a mere tweak. So I'm now hoping that, whatever else it includes, it will include the functionality and capability of RDF, enhanced, rather than diminished.
Yes, you could keep the information in RDF .DOC and .DAT files in a spreadsheet, but most spreadsheets still can't handle dates before 1900, nor can they handle partial or fuzzy dates like "ABT May 1832" or "AFT Sep 1856".
I wish I knew who wrote RDF. It was a work of genius, making the most of the capabilities of computers of its time. If it were updated to make use of today's computers, it would be very powerful indeed.
Tuesday, December 18, 2012
Technorati verification
It seems that Technorati had lost this blog's RSS feed, so am attempting to reapply it:
Technorati will need to verify that you are an author of the blog by looking for a unique code. Please put the following short code 527CQC975QC5 within a new blog post and publish it. This code must appear in the published post and it must also appear in your corresponding RSS feed once published.I wonder if that will work
Labels:
blogging,
blogs,
Technorati
Saturday, October 27, 2012
Rising costs of travel to the UK makes Ancestry.com look like a bargain
Seven years ago my wife and I travelled from South Africa to the UK for a holiday. It was the first time I had visited the UK for nearly 40 years, and it was only after I had been there the first time that I had become interested in family history, and discovered where many of my ancestors had lived. We hired a car and drove around for three weeks, visiting living relatives and some old friends, and visiting places where our dead ancestors had lived. You can see some of the places we visited here.
We have thought of doing the same thing once more before we die, but rising costs make it seem impossible. Seven years ago, the cost of a subscription to Ancestry.com looked exorbitant. Now a single visa to visit the UK costs more -- before thinking of paying plane fares, airport taxes and all the rest. In 2005 we did not need visas at all.
Permira to Buy Ancestry.com for $1.6 Billion - NYTimes.com:
But if the recession has affected the cost of travel, it has also affected Ancestry.com, because further on in the article we read:
But, recession or no recession, that still looks like a very healthy profit margin to me.
I wonder how much the UK government is making on its visas.
We have thought of doing the same thing once more before we die, but rising costs make it seem impossible. Seven years ago, the cost of a subscription to Ancestry.com looked exorbitant. Now a single visa to visit the UK costs more -- before thinking of paying plane fares, airport taxes and all the rest. In 2005 we did not need visas at all.
Permira to Buy Ancestry.com for $1.6 Billion - NYTimes.com:
A consortium led by the European private equity firm Permira has agreed to buy Ancestry.com for around $1.6 billion. Under the terms of the deal, Permira and its partners will pay $32 a share for Ancestry.com, a genealogy Web site. The agreement represents a 40 percent premium to the company’s closing share price in June, when the potential acquisition was first reported. Permira, which will retain majority control, is partnering with Spectrum Equity, a venture capital firm and an early backer of Ancestry.com, and several of the European private equity firm’s direct investors. The Web site’s management also will invest in the deal.
But if the recession has affected the cost of travel, it has also affected Ancestry.com, because further on in the article we read:
After hitting a $45 high in 2011, its stock price has tumbled to around $29 on concerns that consumers are reducing their spending because of the economic crisis.
The company was started in the 1990s, and has remained profitable despite concerns about the revenue growth of other Internet businesses. Last year, Ancestry.com’s net profit roughly doubled, to $62.9 million, on revenue of $400 million. It has more than two million subscribers who pay up to $34.95 a month to use the service.
But, recession or no recession, that still looks like a very healthy profit margin to me.
I wonder how much the UK government is making on its visas.
Thursday, September 06, 2012
Continental Civil Registration conference
This news item nearly slipped beneath my radar, and I haven't seen much discussion on it in genealogical circles, perhaps because we have our noses so deeply buried in the past that we don't notice the future creeping up on us, but this could have important implications for future genealogists. allAfrica.com: Africa: Experts At CRVs Conference in Critical Talks:
Experts meeting at the 2nd Civil Registration and Vital Statistics Conference are currently locked in critical discussions and debates on how to improve the field on the African continent.The experts are meeting in Durban until Wednesday and are expected to set the tone for the ministerial meeting and to a large extent, influence the shape of its outcomes, said Dimitri Sanga, Director at the African Centre for Statistics at the United Nations Economic Commission for Africa."It is extremely crucial that in the next three days, experts discuss and debate all technical issues related to the improvement of civil registration in Africa... in order to help your ministers provide clear policy guidelines in the improvement of these systems," he told the delegates at the start of the conference on Monday.
Sunday, August 05, 2012
Clooz 3.0 is on the way
Clooz is a genealogical research tool that enables you to analyse your data in various ways, and possibly open up new avenues for research.
Development of the program was recently taken over by Ancestral Systems, and they are now offering a free trial of Clooz 3.0, which is due to be released soon.
As they say, Clooz:
At the moment users are trying out the new version, reporting problems, and suggesting improvements to the program.
Check the Clooz web site to learn more.
Development of the program was recently taken over by Ancestral Systems, and they are now offering a free trial of Clooz 3.0, which is due to be released soon.
As they say, Clooz:
Clooz is NOT just another genealogy program. It is THE database for systematically organizing and storing the clues to your ancestry discovered through years of research. Clooz functions as a sophisticated research assistance tool and electronic filing cabinet. Clooz enhances your research with search and retrieval of important facts that you find during the hunt for your ancestors. Clooz interfaces with certain established family tree programs, depending on the producers allowing us access to your data stored in their program.
At the moment users are trying out the new version, reporting problems, and suggesting improvements to the program.
Check the Clooz web site to learn more.
Wednesday, June 13, 2012
Growing cities face a grave problem
There's been quite a bit of discussion in the South African Genealogy Mailing List recently about the problems of growing cities and lack of cemetery space. The latest round was sparked off by the news that Buffalo City (East London) Municipality is considering re-using graves because of shortage of cemetery space. And as people have contributed to the discussion, there are various stories about other cities thinking of doing the same.
But there's nothing new in this. In the very same week, this news story surfaced in San Francisco - Tombstones from long ago surfacing on S.F. beach:
I wonder if the inscriptions on these tombstones were recorded before they were dumped?
In the UK burials often took place in churchyards, but as villages were swallowed up in urban sprawl, cemeteries were established, and many of the churchyards have been cleared of graves. One solution has been to put all the old gravestones around the walls of the churchyard. I must admit I hadn't thought of them being dumped into the sea.
I also wonder about the culture clash in South Africa. There have been some claims to land restitution on the grounds that people's ancestors are buried in such and such a place. And in the past there was a lot of resistance to people being forcibly moved in the ethnic cleansing that took place under apartheid, on the grounds that they did not want to be moved from the places where their ancestors were buried. I wonder how well the Buffalo City Municipality's plans will sit with people who see things in that light?
But there's nothing new in this. In the very same week, this news story surfaced in San Francisco - Tombstones from long ago surfacing on S.F. beach:Strong winds and shifting sands have uncovered an eerie reminder of San Francisco's past: discarded gravestones and broken tomb markers used decades ago to shore up the Ocean Beach seawall.The tombstones became visible this week, including bits and pieces of marble and granite that once marked the final resting places of citizens long dead.One of them is the nearly intact marble tombstone of Delia Presby Oliver, who died at the age of 26 on Apr. 9, 1890.
Her remains were removed and reburied when San Francisco authorities closed nearly all the city cemeteries and moved the bodies to Colma in the early 20th century - part of a move to make space for the growing city. Oliver's original tombstone and thousands like it were used as landfill or in other ways throughout San Francisco.
Some were used as breakwaters. Pieces of others were used to line the gutters of Haight-Ashbury's Buena Vista Park. Some gravestones were used to build the seawall along the Great Highway. Large tombs and crypts were dumped into San Francisco Bay.
I wonder if the inscriptions on these tombstones were recorded before they were dumped?
In the UK burials often took place in churchyards, but as villages were swallowed up in urban sprawl, cemeteries were established, and many of the churchyards have been cleared of graves. One solution has been to put all the old gravestones around the walls of the churchyard. I must admit I hadn't thought of them being dumped into the sea.
I also wonder about the culture clash in South Africa. There have been some claims to land restitution on the grounds that people's ancestors are buried in such and such a place. And in the past there was a lot of resistance to people being forcibly moved in the ethnic cleansing that took place under apartheid, on the grounds that they did not want to be moved from the places where their ancestors were buried. I wonder how well the Buffalo City Municipality's plans will sit with people who see things in that light?
Wednesday, June 06, 2012
Popularity of names
One of the things that can sometimes help genealogists is to know the popularity of names at different periods and in different places. Names can very often date people, sometimes quite precisely.
One of the most spectacular examples in recent times is Nevaeh ("heaven" backwards), which in England and Wales at least has grown spectacularly in popularity for girls, thought not at all among boys.

You can find this, and other information on the popularity of names in England and Wales here Babies called Nevaeh in England & Wales since 1996.
One of the things I find slightly odd about these sites is that they are almost always called "Baby names", but those before 2000 are now teenager names, not baby names.
Another thing to watch out for is the way names change sex. That does not seem to have happened to Nevaeh yet, at least not in the UK, where it seems to be strictly a girl's name.
But when I was growing up, for example, anyone called "eslie was invariably male, and the feminine form of the name was Lesley. More recently, however, I've come across some female Leslies, and some male Lesleys. With some names, like Ashley/Ashleigh, it's impossible to tell.
That's OK when you know the people concerned, but when you are entering the names of relatives you've just discovered into a genealogy program it often wants to know their sex, and sometimes you just don't know.
One of the most spectacular examples in recent times is Nevaeh ("heaven" backwards), which in England and Wales at least has grown spectacularly in popularity for girls, thought not at all among boys.

You can find this, and other information on the popularity of names in England and Wales here Babies called Nevaeh in England & Wales since 1996.
One of the things I find slightly odd about these sites is that they are almost always called "Baby names", but those before 2000 are now teenager names, not baby names.
Another thing to watch out for is the way names change sex. That does not seem to have happened to Nevaeh yet, at least not in the UK, where it seems to be strictly a girl's name.
But when I was growing up, for example, anyone called "eslie was invariably male, and the feminine form of the name was Lesley. More recently, however, I've come across some female Leslies, and some male Lesleys. With some names, like Ashley/Ashleigh, it's impossible to tell.
That's OK when you know the people concerned, but when you are entering the names of relatives you've just discovered into a genealogy program it often wants to know their sex, and sometimes you just don't know.
Subscribe to:
Posts (Atom)


