Jump to content


Defining a website source - template-based fields?

source-templates citations

  • Please log in to reply
2 replies to this topic

#1 A_M



  • Members
  • PipPip
  • 25 posts

Posted 18 March 2015 - 01:17 PM

Hi everyone


I have been wondering how to deal with web sources with parametrized URLs, where you want to have the dynamic part of the URL to be inserted into another field.


Say there is a website "myfamily.com" which employs URLs along this pattern "myfamily.com/person/[ID]/view" and I found information on my grand-grandparents: Betty Smith and John Doe.


For Betty Smith:

   the ID is 123

   I would cite her life by supplying ddetail field 123

   her final URL would be: myfamily.com/person/123/view


For John Doe

   the ID is 456

   I would cite his life by supplying detail field 456

   his final URL would be: myfamily.com/person/456/view


I imagine In the Source Template I would define 2 fields:

1. Field "URL" of type URL (new type): "myfamily.com/person/{{ID}}/view

2. Field "ID" of type text, source detail

As you can guess, the {{ID}} would be then inserted into URL field, and yes - you guessed it: - when rendered on screen it would be clickable.


[Of course a validation should occur to prevent circular references of field to itself]


I tried to achieve something similar using default Ancestral File, online, but to no avail.

How do you cope with a similar scenario?


#2 Laura


    Advanced Member

  • Members
  • PipPipPip
  • 4276 posts

Posted 18 March 2015 - 03:32 PM

A URL entered into a Master source or Source detail is not dynamic. It is just text.

You can add a Webtag to the Master source, Master text or the Source details, Detail text screens.

Highlight the desired Webtag on the Webtags screen and click on Go to access the website.

See WebTags in Help or Webinar 44, New Web Tags in Rootsmagic 6, on RootsMagic's main web site under Learn.

#3 A_M



  • Members
  • PipPip
  • 25 posts

Posted 23 March 2015 - 05:16 PM

Yes, I realize it is not dynamic, and I think it is a limitation. But thanks for pointing me to WebTags - I underestimated this feature.