Add own (non standard) gedcom tags in source templates

RootsMagic
1

I want to ask that we can add own (non standard) gedcom tags in source templates. The gedcom export would be much clearer and easier to deal with. Here an example:

Now:
2 _TMPLT
3 FIELD
4 NAME NameOfCitation
4 VALUE Matricula Online / Startseite / Österreich / Oberösterreich: Rk. Diözese Linz / Traunkirchen / Taufen - Duplikate 1910 | 106/1910
3 FIELD
4 NAME PageNo
4 VALUE V/1
3 FIELD
4 NAME SeqNo
4 VALUE 10
3 FIELD
4 NAME URL
4 VALUE Taufen - Duplikate 1910 - 106/1910 | Traunkirchen | Oberösterreich: Rk. Diözese Linz | Österreich | Matricula Online
3 FIELD
4 NAME PageId
4 VALUE PfmF839 - 00786
3 FIELD
4 NAME AccessDate
4 VALUE 29 April 2023

Then:
2 _TMPLT MyOnlineSourceTemplate
3 _NAMEOFCITATION Matricula Online / Startseite / Österreich / Oberösterreich: Rk. Diözese Linz / Traunkirchen / Taufen - Duplikate 1910 | 106/1910
3 _PAGENO V/1
3 _SEQNO 10
3 _URL Taufen - Duplikate 1910 - 106/1910 | Traunkirchen | Oberösterreich: Rk. Diözese Linz | Österreich | Matricula Online
3 _PAGEID PfmF839 - 00786
3 _ACCESSDATE 29 April 2023

2

That has almost no chance of happening. It would require a major change in data structure for templates. They are currently in XML format which is strictly hierarchical. The tags Field, Name, and Value are standard XML tags. The GEDCOM export supports them. Collapsing the structure into a custom concatenation makes it more difficult for the importing software to parse and probably impossible if it has no foreknowledge, e.g., user-defined templates.

3

Dear Tom,
sorry, but I disagree.
Of course it would require changes both in export and import but e.g.
3 _PAGENO V/1
can be “translated” to
3 FIELD
4 NAME PAGENO
4 VALUE V/1
and treated in that way.

4

Okay. Technically feasible. See if you can get @rzamor1 to accept it as an enhancement request.

5

Confirming request has been reported to development.