* Question about user-template configurations

[Gary_G]

Nick;

Can the current Ancestral Sources store more than one configuration for a template of a given name? Some of my templates can handle more than one type of information, but the A.S. fields need to be mapped to different fields in my template to permit it. At the moment, it doesn't appear that A.S. has that ability.

[tatewise]

Playing devil's advocate, I was not sure which templates you were talking about.
AS Templates or FH Source Templates?

[Gary_G]

Sorry, Mike. Thought it was clear from the context in my post. I have an FH-7 user-defined template that could work for one or more of the events for which A.S. is designed to handle. However; some of the fields in my user-template need to be mapped to different A.S. variables in order to be used for citing different events. It looks like A.S. only allows one set of stored mappings per uniquely named user-template. However; I wasn't sure if this assumption was correct.

[tatewise]

Have you investigated using {SOURCETYPE} (i.e. Census, Birth, Baptism, Marriage, Death) to conditionally select the AS fields to use? i.e. Use the =IF[...] function.

[Gary_G]

Unfortunately; that won't work for my template. In my template, A.S. variables are mapped to different fields for different event types. It wasn't designed to reconfigure based on a single field that senses the current A.S. event type.

[NickWalker]

Sorry, Mike. Thought it was clear from the context in my post. I have an FH-7 user-defined template that could work for one or more of the events for which A.S. is designed to handle. However; some of the fields in my user-template need to be mapped to different A.S. variables in order to be used for citing different events. It looks like A.S. only allows one set of stored mappings per uniquely named user-template. However; I wasn't sure if this assumption was correct.

Hi Gary

No the assumption isn't correct. A template can be used with different source types and each 'mapping' between source type and the template can have different template field values specified. So an AS Source Template is effectively a link between a FH Source Template and an AS source type.

Hope that helps

Nick

[tatewise]

I think you need to help us understand the difference between your event types and AS event types.

[Gary_G]

Mike;
It's very simple. I don't want to rewrite my template logic just to use A.S.
It isn't designed to switch the way fields are mapped based upon the A.S. {EVENTTYPE} value.
For Births I have to map certain A.S. fields to those in my template.
For Deaths, I need to map other fields.

It sounds like A.S. is just not capable of multiple configurations for the same named template and so I can't use it.

[NickWalker]

Mike;
It's very simple. I don't want to rewrite my template logic just to use A.S.
It isn't designed to switch the way fields are mapped based upon the A.S. {EVENTTYPE} value.
For Births I have to map certain A.S. fields to those in my template.
For Deaths, I need to map other fields.

It sounds like A.S. is just not capable of multiple configurations for the same named template and so I can't use it.

Did you not see my reply Gary?

[Gary_G]

Nick;
I saw your post after Mike's. I've been multi-tasking to order a new computer for my wife and sometimes I don't end up reading the email notifications in the order they arrived. It's good to hear that A.S. treats a reference to my template for Births as different to a reference to my template for Deaths. Must figure out why I'm having troubles setting it up that way. It's quite likely just me.

Thank you.

[NickWalker]

Here's a screen shot to illustrate. Birth and Death use the same source template, but I've changed the 'Region field' on each to show that they use different settings:

image.png (34.65 KiB) Viewed 251 times

image.png (32.86 KiB) Viewed 251 times

[Gary_G]

Thanks, Nick. I seem to have it saving the configurations now.

[Gary_G]

Just managed to get it to generate a set of decent-looking census-related records. So hooking in my template was a success.

Just need to see if there's some way to split the A.S. {REF} value on the "|" character, so that I can have the first part go to a template field for the archival reference and the last part go to the field that addresses "Where-in" for the footnote. I can't use the {OTHER} value, as it is used for the person-of-interest.

I don't believe that A.S. has the capability to split on a character other than a comma, so I may have to continue to enter some of this manually. I can't do it within the current form of the template despite knowing how to do it with the FH7 formulae. However; it's not the end of the world.

Thanks for the help, Nick.

[NickWalker]

You are correct. There are no functions to do that. Are you not able to use KEYPERSON for your 'person of interest'?

[Gary_G]

Nick;
I was using {OTHER}, because one of your examples reminded me that the {KEYPERSON} is not always the person of interest that needs to go in the template's title to identify the record.

[NickWalker]

This used to be the case but later versions of AS allow you to select the Key Person in the census using the key button on the toolbar.

[Gary_G]

Thanks, Nick. I'll make that change to how I map A.S. variables and check to make sure I have the most recent A.S. The ability to use {OTHER} for the other reference-type data is very welcome. It means that the record's archival reference can use {REF} and the "Where-in" data can use {OTHER}.