Please do NOT expect all Feature Requests to be actioned automatically. Describing your proposal here will ensure the development team are aware of it, and they will give it careful consideration.
  • Page:
  • 1

TOPIC:

_LOC value in deduplicating window 2 months 9 hours ago #1

  • mariannevanharten
  • mariannevanharten's Avatar Topic Author
  • Offline
  • Premium Member
  • Premium Member
  • Posts: 515
I am merging two trees and after that I am busy to deduplicate many items.
The screen where I see the facts and events were found in both records displays i.e. the same parents (FAMC record) and shows the value connected the FAMC ID. Also for the FAMS record.
I am using the Vesta LOC plugin. In the original tree the item only displays the _LOC ID. The other tree shows the place by text.
I appreciate also the corresponding _LOC value in the screen.

Best regards,
Marianne

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

_LOC value in deduplicating window 1 month 4 weeks ago #2

  • fisharebest
  • fisharebest's Avatar
  • Offline
  • Administrator
  • Administrator
  • Posts: 15173
I do not understand what you are asking.

Perhaps add a screen-dump?
Greg Roach - This email address is being protected from spambots. You need JavaScript enabled to view it. - fisharebest.webtrees.net

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

_LOC value in deduplicating window 1 month 4 weeks ago #3

  • mariannevanharten
  • mariannevanharten's Avatar Topic Author
  • Offline
  • Premium Member
  • Premium Member
  • Posts: 515

In this screen I can see the HUSB and the WIFE and also their name, so I know they are - left and right - the same.
But I can't see the location. Is L331244 the same as Zwammerdam?
Attachments:

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

_LOC value in deduplicating window 1 month 4 weeks ago #4

  • hermann
  • hermann's Avatar
  • Offline
  • Senior Member
  • Senior Member
  • Posts: 432
The left record has no PLAC, it has a _LOC. The right record has a PLAC but no _LOC. You have to combine these records to a new record that has both PLAC and _LOC. But check before if the _LOC record @L33...@ links to a location with the name Zwammerdam otherwise the marriage information is inconsistent.
Hermann
Designer of the custom module "Extended Family"

webtrees 2.0.19 (all custom modules installed, php 7.4.15, MySQL 5.6) @ ahnen.hartenthaler.eu

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

_LOC value in deduplicating window 1 month 4 weeks ago #5

  • mariannevanharten
  • mariannevanharten's Avatar Topic Author
  • Offline
  • Premium Member
  • Premium Member
  • Posts: 515
I prefer to only set a _LOC in each record, no PLAC. The name of the location is set in the _LOC 'table'.
For comparising the left and the right I want to show the value of the name value of the _LOC in my old tree (left column) to compare it to the new tree I.

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

_LOC value in deduplicating window 1 month 4 weeks ago #6

  • fisharebest
  • fisharebest's Avatar
  • Offline
  • Administrator
  • Administrator
  • Posts: 15173
> I prefer to only set a _LOC in each record, no PLAC

Be aware that the _LOC field is defined in the GEDCOM-EL standard, which says
1 <EVENT> 
2 DATE 
2 PLAC <PLACE_STRUCTURE> 0:1
3 _LOC @<XREF:_LOC>@ 0:1

1) there are no applications that expect "2 _LOC" - only "3 _LOC"

2) webtrees 2.1 is more strict about following standards and using valid GEDCOM structures.

Out-of-the-box, it will not recognise "2 _LOC", and you will only be able to add it using raw GEDCOM editing.

It will be possible to add support for this using a (very simple) module.

But why do it? You are making your site incompatible with all other genealogy applications.
Greg Roach - This email address is being protected from spambots. You need JavaScript enabled to view it. - fisharebest.webtrees.net

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

Last edit: by fisharebest.

_LOC value in deduplicating window 1 month 3 weeks ago #7

  • mariannevanharten
  • mariannevanharten's Avatar Topic Author
  • Offline
  • Premium Member
  • Premium Member
  • Posts: 515
I tried to change "2 _LOC" to "3 _LOC". After changing, webtrees didn't show the shared place...
When I use PLAC and _LOC, the item looks like the attachment: the location is twice in this record, so I didn't enter a PLAC record.
How do I prevent displaying the place twice?
Do you have the (very simple) module you referred to?
Attachments:

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

Last edit: by mariannevanharten.

_LOC value in deduplicating window 1 month 3 weeks ago #8

  • hermann
  • hermann's Avatar
  • Offline
  • Senior Member
  • Senior Member
  • Posts: 432
GEDCOM has a level structure, but you cannot skip levels, deeper levels are always +1.

This is ok:
1 BIRT
2 PLAC
3 _LOC

This is not ok:
1 BIRT
3 _LOC

That the information in PLAC and behind _LOC is redundant is to be compatible with standard GEDCOM applications which do not know the extension of _LOC. All applications can understand PLAC.
Hermann
Designer of the custom module "Extended Family"

webtrees 2.0.19 (all custom modules installed, php 7.4.15, MySQL 5.6) @ ahnen.hartenthaler.eu

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

Do you need a web hosting solution for your webtrees site?
If you prefer a host that specialises in webtrees, the following page lists some suppliers able to provide one for you: 
  • Page:
  • 1
Powered by Kunena Forum