Jump to content


Source Templates To Be Fixed

  • Please log in to reply
45 replies to this topic

#41 MerRhosyn


    New Member

  • Members
  • Pip
  • 1 posts

Posted 01 January 2016 - 02:53 PM

Source Type: Civil Reg., Statutory Registers, Scotland (online images)


Footnote: [Jurisdiction], [Volume]...:<[AccessedType]|accessed> [AccessDate])<;[CreditLine]>.





Implementation of footnote, data from "access type" does not get pulled into display:


Burgh of Perth, County of Perth, citing Statutory Registers no. 387/01 0196, image, marriage registration, John Robertson and Elizabeth Haggie, married 10 December 1855, registered 11 December 1855; database and images, ScotlandsPeople (http://www.scotlandspeople.gov.uk: [AccessedType] 6 January 2009).

#42 Nettie


    Advanced Member

  • Members
  • PipPipPip
  • 1557 posts

Posted 02 January 2016 - 07:12 AM

I would certainly love to be able to merge multiple sources into one. Period.

There is a merge function on the Source List screen.  I have used this many times and it works.  But before I merge them I make a printout of the one that is going away, to make sure all information is transferred to the new Source....

"I work on genealogy only on days that end in "Y"." [Grin!!!]
from www.GenealogyDaily.com.
"Documentation....The hardest part of genealogy"
"Genealogy is like Hide & Seek: They Hide & I Seek!"
" Genealogists: People helping people.....that's what it's all about!"
from http://www.rootsweb....nry/gentags.htm
Using FO and RM since FO2.0 

#43 BarbA


    New Member

  • Members
  • Pip
  • 4 posts

Posted 02 April 2016 - 05:46 AM


Yes, on this first go round we are looking to handle the extraneous punctuation when fields are left empty. It is probably overkill to handle every single field as optional, so we are mainly looking for feedback on source types / fields that can be empty often enough to create this extraneous punctuation more than just rarely. Basically we are trying to tighten up the source templates that currently exist before we get into any new / modified functionality in this area.

This is 2016 and I am finding many questions about this.  It would seem that "overkill" might be the solution.  I have decided that I will use Free Form and other methods for my sources and citations because those extra commas etc. drive me crazy. Here's to hoping the direction is changed on this issue.  Thank you.

#44 Renee Zamora

Renee Zamora

    Advanced Member

  • Support
  • PipPipPip
  • 7956 posts

Posted 02 March 2017 - 03:43 PM

Referencing this forum post.




#45 mgbaird



  • Members
  • PipPip
  • 12 posts

Posted 10 September 2018 - 11:21 AM

In the Source Template for the Type: Church Issued Certificates (single item). The Whenissued field is [whenissued:lower]. When date is entered it returns a low case first letter for the month such as 7 january 2018. I believe the field should be [whenissued:Caps] which delivers 7 January 2018.


#46 mgbaird



  • Members
  • PipPip
  • 12 posts

Posted 10 September 2018 - 12:14 PM

In the Source Template: Drouin Collection – Ancestry. In the footnote template the embedded text:

<i>Ontario, Canada, Catholic Church Records (Drouin Collection), 1747-1967</i>,  Gabriel Drouin, comp. Drouin Collection. Montreal, Quebec, Institut Genealogique Drouin

There is a double space between </i>, and Gabriel. There should be only one space.