Take the 2-minute tour ×
Genealogy & Family History Stack Exchange is a question and answer site for expert genealogists and people interested in genealogy or family history. It's 100% free, no registration required.

When I started recording my tree I recorded the fact that an ancestor was present in census as such. This produced, as expected, a census (CENS) record in my Gedcom.

After working with my tree on Ancestry for a while I decided to download the tree as a Gedcom, only to find that all census references I had added were recorded as residence (RESI) records with a reference to the census as a source.

Is there a 'right' way to record a census event? Should it use a census record or a residence record?

share|improve this question
    
If it turns out that this only happens with the UK census then someone will need to add another tag to the question to provide the appropriate filter. –  ACProctor Nov 16 '12 at 18:07
    
Happy to add another tag if someone could confirm a difference. –  OldCurmudgeon Nov 16 '12 at 23:10
    
Tagging is interesting - will meta about whether we should add "residence" tag and/or "event" tag. –  GeneJ Nov 16 '12 at 23:36
    
Thanks for an interesting discussion. IF, for example, ancestry.com's gedcom feature makes it suited to be a "master data repository" for your genealogical information, can anyone suggest a robust alternative? s a programmer I love using git to manage my source code. I'd love to have asimilar tool for my geenalogical database. –  peterbooth Oct 15 at 11:11
    
@peterbooth I converted your "answer", which was asking a new question, into a comment. I welcome you to ask a new question to obtain the solution that you seek. –  PolyGeo Oct 15 at 21:31

4 Answers 4

What has to be understood is that the Ancestry Member Tree feature is a display application and not really a genealogy program. Thus the GEDCOM it generates for download is a non-standard 'flavor' of GEDCOM.

When saving a census document to a Member Tree, it is saved as a Residence event.

If you want a Census Event, you must create it manually and then save the census document as a source for that census event.

share|improve this answer

I don't know the actual reason for the switch over but this is entirely wrong and shouldn't have happened.

A census is - as you say - an "event". It has both a place and a date associated with it. It should, therefore, be recorded as an event.

To use the census address as a residential address is an error because many people were not present at their normal residental address on census night. They may have been visiting, lodging, working, travelling, etc.

I don't use Ancestry's trees. Is this reproducible? I'm wondering why no one else has complained about it. Can you add precise details of how you added the census events to your tree?

share|improve this answer
    
It's reproducible Tony - I loaded a GEDCOM to Ancestry and then downloaded it. GIGO. As in - GEDCOM In, Garbage Out. OK, that's pushing it a bit - but not a lot. I guess Ancestry are more interested in exchange directly to FTM. Whether that's similarly affected, I don't know. –  AdrianB38 Nov 16 '12 at 17:54
    
Just checking up again on my own Ancestry tree. If I try to attach a Census Record from Ancestry to a person, it offers to add or update Name, Birth, Residence - no sign of a Census, even though it's a type of Event that the Ancestry tree supports. –  AdrianB38 Nov 16 '12 at 18:00

The fact that Ancestry generates a Residence when downloading a GEDCOM shows that Ancestry and GEDCOM have a nodding acquaintance but are not intimate friends, one might say.

There is a Census event in GEDCOM, therefore the "expectation" is, I suggest that Census is the one to use. However, what you also add alongside the Census event is a bit more of a moot point.

Some will contend that it is not correct to a Residence event for UK censuses, because UK censuses only describe where someone is on the night of the census, not where they are resident. Given that standard descriptions of lodger, boarder and visitor are used for the relationship to the head-of-house, I think the chances of people without those descriptions not being resident is slim, so I add a separate residence to each person.

I'll also add occupation attributes, and add the census to the birth event as a secondary source of evidence for that.

share|improve this answer
1  
You can't always rely on the 'role' to distinguish people not normally resident at the same address Adrian. I have seen household returns where someone is simply recorded as, say, 'son' but I know from other records that they lived nearby but not at that particular household. –  ACProctor Nov 16 '12 at 18:02
    
I've come across instances where the same people are listed in multiple census records, once for the birth family, and once for (presumably) the foster family. –  Gene Golovchinsky Nov 16 '12 at 21:59
    
Tony - you're right that you can't always rely on that role. And equally, we know you can't even rely on a nephew being a nephew and not a son they're trying to hide, or similar. My own decision was that I'd believe the role unless I found evidence to the contrary - I acknowledge that there's a risk. Ironically, I've just been working on my 4G grandmother who, on re-marriage, claimed that she was resident in Madeley, Staffs, when it's clear she was still living 9m away in Haslington, Cheshire. She was the older woman, you see... So you can't always believe them even when they're explicit! –  AdrianB38 Nov 16 '12 at 22:47
    
Gene - I find multiple listings more in the US, where the concept of "usual residence" seems to be, shall we say, open to interpretation. And with US censuses taking several days to compile, all sorts of possibilities arise. In the UK, the census gets done in 1 day for exactly where you are. Even so, double reports exist - often for people on overnight journeys who get recorded at both ends. Usually though, one or both ends are clearly hotels, barracks, etc. Usually. –  AdrianB38 Nov 16 '12 at 22:53

There are two elements to your question and they need to be dealt with separately.

Ancestry changed your GEDCOM

And almost any other application package would have done so, too. Not always in the same way and sometimes you may not notice the change, but it will happen.

GEDCOM is now an aging standard and software developers have added their own extensions and enhancements. Moving a file from one package to another leads to "approximations" and "compromises" as they push oval pegs into round holes.

The way to avoid difficulties is to select your preferred software (preferably on your own computer, not web-based) in which all changes are made in native file format and DO NOT EVER IMPORT into that application. Create new sources, events and citations from scratch in that application to match your preferred methods.

When you want to use another application for a particular purpose, by all means export a GEDCOM but DO NOT BRING IT BACK. Any data file export should be regarded as disposable.

What should you do with the changes you made while on-line after importing the data? Open your main application and redo them there! And resolve not to be seduced by waggling green leaves again.

How should you use a Census record?

You should consistently apply a system that makes sense to you and to those with whom you plan to share.

For me, that means that I use a census return as a source of information concerning residence, occupation, education, religion, marital status and whatever else is available in particular jurisdictions at a given point in time. I acknowledge that a census "has both a place and a date associated with it" but so does the publication of an edition of The Sydney Morning Herald newspaper from which I might obtain some of the same information about an ancestor.

For my purposes, the decennial census is no more an event in the life of my family than a triennial election. Of course I use the information recorded in the electoral roll; but unless 3xgreat grandfather was a candidate, the election was not an event to be recorded.

On the other hand, if you are part of a genealogical community that exchanges information on a regular basis, then you need to find their conventions and follow them. It is quite possible that you will find groups prepared to argue for each approach with equal fervour. The right way is the one that suits your needs.

share|improve this answer
    
Interesting - "the decennial census is no more an event in the life of my family than a triennial election". I do record the census as an event in my database but whenever I produce reports for anyone, I exclude it as (to me) what matters is what it tells us, not the fact of its occurrence - i.e. I agree with you as far as reports go. I do record its occurrence but only to be able to track whether or not I've found it and used it. –  AdrianB38 Nov 17 '12 at 10:08

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.