Web based family history software

Question Handling non-standard xref

  • WGroleau
  • Topic Author
  • Offline
  • Platinum Member
  • Platinum Member
More
1 year 1 month ago #1 by WGroleau
Handling non-standard xref was created by WGroleau
Several of my sources are family histories compiled by relatives.  Now these may not be the best references, but they're far from the worst.

I find it convenient to use (for example)
Code:
1 AUTH @P321@
within the SOUR record.

I would like for any appearance of @xref@ other than at the zero level be displayed in a manner similar to that used above FAMC or HUSB in the "Edit raw GEDCOM" panels; or to be a link to the record cited, or both.

--
Wes Groleau
UniGen.us/

Please Log in or Create an account to join the conversation.

  • bertkoor
  • Offline
  • Platinum Member
  • Platinum Member
  • Greetings from Utrecht, Holland
More
1 year 1 month ago #2 by bertkoor
Replied by bertkoor on topic Handling non-standard xref
My initial reaction to make this more GEDCOM compliant:
Code:
0 @S1@ SOUR 1 _ASSO @P321@ 2 TYPE author

stamboom.BertKoor.nl runs on webtrees v2.1.20

Please Log in or Create an account to join the conversation.

  • WGroleau
  • Topic Author
  • Offline
  • Platinum Member
  • Platinum Member
More
1 year 1 month ago #3 by WGroleau
Replied by WGroleau on topic Handling non-standard xref
For that, I'd say omit the underscore. But I prefer the other as shorter and more direct. Mainly, I'd like the link to work.

github.com/FamilySearch/GEDCOM/issues/356

--
Wes Groleau
UniGen.us/

Please Log in or Create an account to join the conversation.

  • bertkoor
  • Offline
  • Platinum Member
  • Platinum Member
  • Greetings from Utrecht, Holland
More
1 year 1 month ago #4 by bertkoor
Replied by bertkoor on topic Handling non-standard xref
As this is not going to be standard GEDCOM, the underscore tag prefix is mandatory to indicate that.

Same with ASSO at level 2 (part of event) in person records. Perhaps this changes with GEDCOM v7, I don't really follow that.

Since webtrees v2 it is being more strict with following the standard. It used to be that you could throw any imaginary constructions at it, and webtrees would render it mostly as expected.

I have not tried how this renders. You can try, just edit raw and see what comes out...

stamboom.BertKoor.nl runs on webtrees v2.1.20

Please Log in or Create an account to join the conversation.

  • WGroleau
  • Topic Author
  • Offline
  • Platinum Member
  • Platinum Member
More
1 year 1 month ago #5 by WGroleau
Replied by WGroleau on topic Handling non-standard xref
Unfortunately, we can't edit raw on a SOUR, but I imported a test GEDCOM.

1 AUTH @P517@ can be done without erasing and importing.  This is rendered 
I would like for it to show the preferred INDI:NAME for that person instead of or in addition to the ID, and make it a link to the INDI record.

1 ASSO @P517@
2 TYPE Author

can only be done by editing raw outside of webtrees, then erasing and importing.  This is rendered 
I would like this, and any other xref to show the preferred name instead of the ID (or show both) and make it a link to the INDI.
But I would prefer to use the first non-standard format (which I have requested be standard in GEDCOM 7).

_ASSO or ASSO are practically the same in terms of editing and display.

--
Wes Groleau
UniGen.us/

Please Log in or Create an account to join the conversation.

Powered by Kunena Forum