User talk:Moverton


Welcome [22 January 2011]

Welcome to WeRelate, your virtual genealogical community. We're glad you have joined us. At WeRelate you can easily create ancestor web pages, connect with cousins and other genealogists, and find new information. To get started:

If you need any help, I will be glad to answer your questions. Just click on my signature link below and then click on the “Leave a message” link under my name in the upper left corner of my profile page. Thanks for participating and see you around! Debbie Freeman --DFree 13:54, 11 October 2010 (EDT)

GRO Certificates [4 March 2012]

Thanks for clarifying this point about uploading certificates, I was very unsure about the copyright situation. However, do you know if a similar situation applies for copies of those vital records recorded prior to civil registration and obtained from sites such as ScotlandsPeople. Looking at their website it seems to indicate that we cannot upload these records.--Kenamoore 03:20, 22 January 2011 (EST)

Sorry, but I do not know the answer to that. That would be a good question to ask the users at large. Moverton 03:54, 22 January 2011 (EST)
Has there been further discussion about this anywhere? I've been uploading a few certificates lately, following the advice given on the National Archives website (which states that we "are authorised to reproduce the layout of the form in any format including on the web, in films and in print". I made a template to use on these works, {{Crown Copyright BMD}}. What do you think?
Even if we're not allowed to publish the actual certificates, there is no copyright in the facts written on them, so we're perfectly allowed to transcribe!
Sam Wilson ( TalkContribs ) … 21:05, 2 March 2012 (EST)
Seems ok to me, though I don't pretend to be an expert on copyright. It would be nice if the drop-down on the images included one specific to GRO certificates. I never have been quite sure which option is best. —Moverton 19:03, 4 March 2012 (EST)

WeRelate Featured Page - Week of April 18th [19 April 2011]

Hello, just wanted you to know that your page Leavenworth, Kansas - 1880 Census Population Schedule, has been selected the WeRelate Featured Page for the week of April 18th. Great job and keep up the good work!

Best regards,

Jim Co-Administrator on 18:01, 19 April 2011 (EDT)

Valley View Memorial Cemetery [22 June 2011]

Re: Place:Valley View Memorial Cemetery, Gypsum Creek, McPherson, Kansas, United States, if the oldest headstones predate 1877, why is that the "established" date? Is there a source for this from the town? — Parsa 17:36, 22 June 2011 (EDT)

If you follow the link for the source of the "former name", the dates were given there. It could be that the cemetery's association was established in 1877. And it could be that it was private until that date. I haven't done any further research. Moverton 17:49, 22 June 2011 (EDT)

Transcriptions of GRO docs [4 March 2012]

Hi! I like what you're doing at User:Moverton/sandbox#GRO_transcripts. Do you think there's a need for some templates for doing these sorts of transcriptions? I've been having a go at some myself, and would love to hear what you think. Something like {{Scotland. Statutory Marriage Record}}, for example.

I was thinking that I'd include the transcription firstly on the MySource page (I create one for each certificate), and then perhaps also on the Person or Family page to which it's most pertinent (e.g.). Then, I started wondering how to tie all the transcriptions together, so there was a place in which we could see all our own certificates, and others' too. Then I got confused.... ;-)

Any ideas?!  :-) Thanks! — Sam Wilson ( TalkContribs ) … 21:12, 2 March 2012 (EST)

Templates might make transcriptions easier to do if they are being placed into a table. Some users won't want to have to mess with the table syntax. (Obviously not a problem for me.)
My own preference is to just leave any transcriptions on the image pages if they have been uploaded (example). In some cases I may just excerpt a portion of text or provide my own summary of the information on the person's page, rather than replicating what is readily viewable in the original image. I try not to create any more of the MySources than I have to.
Previously I had been thinking about transcriptions of records or indexing, but not until the recent discussion did I decide to get started on it. After playing around with them a little, it is not obvious to me what the structure of a document containing all the transcriptions for a given district would look like, or whether it would need to be subdivided in a certain fashion. Perhaps it would be easier to create an index based on the GRO with certain enhancements (i.e. including the precise location, person's age, and other names mentioned). Those additional fields could only be filled out once the record was obtained, but it could still be linked to the person that a researcher believes it refers to. The additional names contained in the record could be linked to their pages, and if the certificate was uploaded, it could be linked to the record. —Moverton 18:52, 4 March 2012 (EST)

let source citation speak for itself [25 June 2013]

Re: Family:Samuel Peacock and Mary Kittredge (1). Curious why you added the description to the marriage for the following reasons: (1) it is redundant, the presence of the fact implies Samuel married Mary, why have the description field repeat that? (2) why emphasize Kittredg by quoting it. According to published VR, the compiler indicates this spelling came from the duplicate record, meaning it was a fluke of spelling based on who made the second record, and not a universal spelling used during their lifetime? (3) the only interesting information added is the name of the minister, but not sure that is necessary. The only reason for making the third point is that there are two sets of people looking at the page. One set is trying to quickly identify if this page is the person they want, and they probably only need the basics, unless they find themselves to be more interested. Most won't. The relatively small set that is interested in this person will read everything posted on a page, so if there is information in one of the source citations, they will find it without needing to promote relatively trivial information like the minister's name to prominence, cluttering up what seems like a summary?--Jrich 10:52, 25 June 2013 (EDT)

I'll grant you the second point. If the original has the normal form (or if it isn't known for sure) then the normal form of the name without quotes should be used. If only the name, date, and location is known, I wouldn't see a need for the additional text unless I was trying to give the form of the name used (nickname, alternate spelling, middle name not present elsewhere, etc.). I usually include the text when there is additional information that can be presented, such as the name of the officiating person, who each of their parents were, or where they were living at the time. One of the reasons why I do that is so it carries over to the person pages where readers can see it. I have my doubts that many casual readers would spend much time on the family pages since most of them don't have much additional information to offer. (This site is a bit unusual in that it has separate family pages with article text, the Family History, which is not included in the person pages.)
I decided a while back that I didn't feel like taking the time to duplicate all the facts from the list above into the main text below (Personal History or Family History) in typical genealogical form when I could just use the description field in the list to write about each item. I typically treat the source references here the same as I would anywhere else: the reader shouldn't be forced to read the references to find the information being presented. If the references were sorted by date or some other logical fashion, maybe it would make more sense to try that. The text field under each source can be used for quoting or discussing the merits of the source, but that is all I use it for. One example of what I'm driving toward is Person:Alford Overton (1). If someone else came along later to rewrite the page into a more normal genealogical biography, I'd be okay with that. But this is just my method of compiling information. -Moverton 19:41, 25 June 2013 (EDT)

Census transcripts [9 November 2014]

Hi there. I saw the very impressive work that you have done on the Lincoln 1841 census transcripts and just wanted to mention to you about "freecen" if you haven't come across them before. They are working to transcribe all the UK census records and so far have managed to complete an impressive proportion. Link is here: - I'm sure they would be very grateful for any help you could give! AndrewRT 19:42, 6 April 2014 (UTC)

Thank you. I doubt that I will participate in that project. But anyone who wants to use the transcripts here for their project is welcome to do so. Moverton 19:42, 7 April 2014 (UTC)

Hi Michael. I was reviewing recent edits and noticed you've done some census transcript pages. I thought I'd draw your attention to the ones I've done; I don't have a strong preference on format and I'm still toying with it, but thought we might build on each other. I did mine with nested templates, and one (WeRelate) page per (census) page, although I think I like the look of yours a little better. Example: Transcript:Overton, Tennessee, United States. 1850 U.S. Census Population Schedule/p116B. Best, --Amelia 06:03, 7 November 2014 (UTC)

I think it would be good to have a consistent approach and harmonizing of formats. I'll just put out a few initial thoughts on my approach so far:

  • I'm open to using templates, but since I am adept at using the raw code, I haven't bothered to try to create any. I realize that it would be friendlier for some people who might not want to bother figuring out the code, or whose eyes may glaze over when they try to edit a page and see all the code that goes into a table.
  • My only real criteria on the format was to choose one which was faithful to the original organization of data (doesn't have to be exact), was easy to read, and was simple enough for anyone to understand. Things like font size, color and spacing could easily be changed if people found what was being used to be less than ideal. (Although I like the smaller font, others may disagree.)
  • I also added a lead text box for all of the defining source info and other descriptions which may be either critical to the transcription or just informative. This could probably be easily converted into some type of flexible template.
  • I have found that creating a transcription can be easier when multiple schedules are placed on a single Transcript page. In some cases the original page numbering is awkward or just plain wrong. And often there is more than one numbering scheme, which would mean different transcribers may use different page numbering. In the case of 1820 Morgan Co. (transcript) the pages appear to have originally been bound together like a book, and the bottom of the page doesn't necessarily follow the top half. This was why I decided to do the complete county transcript after some confusion when trying to view the images on (which often has its own organizing scheme). I had to create a new series of page numbers after reorganized all of the pages to get the proper original order of the information.
  • Viewing the pages may be easier if all of the district (or civil division) schedules are located on the same Transcript page. Families can sometimes be split between two schedules, and using Ctrl-F to find text becomes an option. I have tried to group the pages by the smallest logical unit (typically the enumerator's district, or the township) which makes sense and preserves the context of the information. I realize some districts may be much larger than others and maybe we would eventually find one that is just too big for a single Transcript page, but I haven't seen it yet.

Moverton 18:34, 7 November 2014 (UTC)


Just as a starting point, what's your goal? My idea in starting these was to have a page linked to the source citation on a person page that shows the neighbors, who are in turn (eventually) linked back to person pages for those pages. I started doing them on people I wanted to understand context for, basically. My theory is that there are other transcripts many places; the value here is the cross-linking and annotations. I work on them only every so often when I have large chunks of time, so they have to be easy to create and remember.

On your points above,

  • If anyone else is going to make things look like consistently with what you/me/we do, it's going to have to be templates. While I can do the code too, it's tremendously harder with tables this large, and it gets messed up very easily. Expecting anyone without a lot of time on their hands to both hand code in the first place, and then figure out which copy/paste operation messed up by one character to screw up the entire table is just not scalable. We lose not just others creating, but editing as well (which is the only way we crowd-source the links and the notes).
  • Defining the source seems like something that should really go on the source page, or at least the transcript parent. It's information common to the entire XXXX population schedule, not just this transcript.
  • Your effort here is way outside the scope of anything I have thought of doing. I'm happy to leave this project to the many large funded entities that transcribe these things in bulk :-) I'm not terribly concerned about page numbers as long as the scheme picked is semi-logical - it's a citation mechanism, and the original is messed up, so be it. On the level I'm working, it doesn't matter how many schedules are on one page except that 1) it's easier to link a single page to a source citation; and 2) it's much easier to edit. While the contextual benefit increases as the page gets bigger, the usability correspondingly decreases.
  • To that point, I think trying to put all the schedules in a district on one WeRelate Page is asking for trouble. It's a mess of editing, and then the person coming there from a Person page faces a ton of data and has to ctrl-F, which is both annoying and may not work with bad spellings. To me, that defeats the point. I'm not really interested in transcribing large swaths of data, either, which means I'd either leave pages incomplete or just not start them because the bar is too hight.

One other related point: is there some reason your pages are sub-pages of the national census page instead of the county page? That would seem to make a lot more sense.

Anyway, all just discussion points. As I said, I don't have much time to work on these, but was interested to see someone else doing it! Best,--Amelia 15:46, 8 November 2014 (UTC)

My primary goal is just having a transcription to link to and from. So whether a person wants to see the greater context, do a little research on related families living nearby, or just see the additional information that I'm not putting in Person or Family pages (I don't do any census transcriptions on those pages), the reader will have the transcription available if they want it. Big databases like the one at can be more useful for the average user, and I doubt anyone will come here to do their primary census searching. I don't have the time to do a full census transcript and will only work on those areas where many of the families I research are from. Maybe over time the amount of the transcribed census hosted here will increase if more people find value in having it or just have interest in creating a linkable transcription. But I'm not concerned about that. Some of the census transcriptions I have done are just partials.

Because it was a national census, I use the national Source page. Each individual enumerator taking the census may have operated over the entire county (or a larger territory) or over just a small local division like a township. That individual census return could be thought of as a source unto itself, but it is customary to cite it within the context of the larger census. Also, each of those individual returns were compiled by county into state volumes, and each of those state volumes may occupy multiple rolls of film. So the source could just as easily be defined at the state level. I never use other local (county) source pages when citing my sources because I don't believe that most of them provide any added value.

I am not really trying to define the source per se, other than to provide an understanding of where this transcription fits into the whole and to provide relevant information that may not be covered on the Source page. For example on this transcript, I attempted first to define where this portion of the census can be found and provide a little bit of historical context for the locality (which of course is just whatever I happen to know about it and is not required). I believe that notes about how the transcription was done or other oddities should be included on each relevant page because people aren't always likely to navigate from the main page down through the tree to get there, and they may not otherwise realize there is a note somewhere else that explains what they are seeing.

The way I solved the multi-page problem was to use a hidden <h3> element containing a page number. This has the double benefit of providing an anchor for linking to the page from other WeRelate pages and to provide an edit link before each page of the transcription. It may not be obvious, but if you click on the edit link to the upper right of the page of the schedule you want to edit, you will only be presented with the code for that individual page. If I were using this in combination with templates it would probably be simple enough for most people to edit.

Moverton 22:57, 9 November 2014 (UTC)

"British America" [21 September 2014]

There have been in the past edit wars over the then political reality of a certain event (such as the William Trask marriage you changed) and the current place name. Changing every one in your tree is just asking for an edit war, so I would leave it alone until there is a proper WR rule on it. Eventually it is my hope to make the name of countries, etc a display preference.--Daniel Maxwell 04:28, 21 September 2014 (UTC)