RESI vs. ADDR (and email, phone etc.)
Brought to you by:
canajun2eh,
yalnifj
Menu
▾
▴
How to indicate an address of individual or family or (individuals in a family)? (PGV 4.1)
From GEDCOM 5.5.1:
"ADDRESS_LINE:= {Size=1:60}
Typically used to define a mailing address of an individual when used subordinate to a RESIdent tag. When it is used subordinate to an event tag it is the address of the place where the event took place. The address lines usually contain the addressee’s name and other street and city information so that it forms an address that meets mailing requirements."
It appears that the curretnt GEDCOM defines RESI in Individual or Family attribute structure, and ADDR as subordinate to either RESI or event. I would like to use this convention; I also let users edit their own data, and have co-editors of the growing GEDCOM. I have encountered some issues with it, and would like to share (and also ask if somebody has solution to some of them)
1) RESI for a family has Address structure, and program shows the family Residence data for idividual as well. But EMAIL and commonly cell phones are typically personal. Either I should not include them in the Address structure at all, or need to repeat the whole RESI again for individual which is awkward.
SOLUTION: PGV allows to use EMAIL, PHONE, FAX as subordinate to INDI - here it works better. The list of Facts is configurable, I have added EMAIL, FAX, PHONE to individual's list, and removed ADDR. Also, the "synchronize user data" button in user account does the same thing, i.e. does not create/update a RESI/EMAIL structure but adds/updates EMAIL subordinate to INDI
2) RESI for individual can be added as "Add a new fact" option for individual, but the "Quick Update form" uses ADDR not subordinate to INDI and does not create / update the RESI record. Users can easily use Quick Update to update their own data, and its use is encouraged. I have not found the option for Quick Update to use RESI - perhaps it should be added as an option or as a feature?
3) With most addresses converted to RESI, I lost the use of Address List and Address Labels reports, which now show only ADDR subordinate to INDI (not to FAMS).
SOLUTION: I made a rather clumsy modification to the Labels report, repeating the list part 4 times (ADDR for individuals, ADDR for families, RESI for individuals, RESI for families), but perhaps those could be added as options?
_Marek
Can you post this code?
The report does not work anymore in current version, but the modification was simple. The report files addresslist.xml and addresslabels.xml contain references to the ADDR structure, for example:
<PGVRList list="individual" filter1="ADDR CONTAINS ." filter2="ADDR SUBCONTAINS $address" [...]
I replaced all occurences of ADDR with RESI:ADDR. This makes the report look for ADDR subordinate to RESI, not INDI or FAM.
If you still have ADDR at higher level, you can leave the original reports (and make new version), or duplicate the code with both ADDR and RESI:ADDR sections.
ADDR can occur also in other events e.g. (MARRiage event can have it's own ADDRess), but I presume the address list we are looking for is the list of individual / family addresses.
-Marek
Marek
thanks a lot. I assume you're talking about the Code between lines 47 and 81:
---cut---
<PGVRList list="individual" filter1="$addrfilter" filter2="$addrfilter2" filter3="$email" sortby="$sortby">
<PGVRTextBox width="60" height="52" border="1">
<PGVRText style="text"><PGVRGedcomValue tag="@id" /></PGVRText>
</PGVRTextBox>
<PGVRTextBox width="180" height="52" border="1">
<PGVRText style="text"><PGVRGetPersonName id="" /></PGVRText>
</PGVRTextBox>
<PGVRTextBox width="170" height="52" border="1">
<PGVRText style="text"><PGVRGedcomValue tag="ADDR" /><PGVRGedcomValue tag="RESI:ADDR" /></PGVRText>
<PGVRif condition="@ADDR:ADR1 != ''">
<PGVRText style="text"><br /><PGVRGedcomValue tag="ADDR:ADR1" /></PGVRText>
</PGVRif>
<PGVRif condition="@ADDR:CITY != ''">
<PGVRif condition="$POSTAL_CODE==false">
<PGVRif condition="@ADDR:STAE != ''">
<PGVRText style="text"><br /><PGVRGedcomValue tag="ADDR:POST" /> <PGVRGedcomValue tag="ADDR:CITY" />, <PGVRGedcomValue tag="ADDR:STAE" /> </PGVRText>
</PGVRif>
<PGVRif condition="@ADDR:STAE == ''">
<PGVRText style="text"><br /><PGVRGedcomValue tag="ADDR:POST" /> <PGVRGedcomValue tag="ADDR:CITY" /></PGVRText>
</PGVRif>
</PGVRif>
<PGVRif condition="$POSTAL_CODE==true">
<PGVRif condition="@ADDR:STAE != ''">
<PGVRText style="text"><br /><PGVRGedcomValue tag="ADDR:CITY" />, <PGVRGedcomValue tag="ADDR:STAE" /> <PGVRGedcomValue tag="ADDR:POST" /></PGVRText>
</PGVRif>
<PGVRif condition="@ADDR:STAE == ''">
<PGVRText style="text"><br /><PGVRGedcomValue tag="ADDR:CITY" /> <PGVRGedcomValue tag="ADDR:POST" /></PGVRText>
</PGVRif>
</PGVRif>
</PGVRif>
<PGVRif condition="@ADDR:CTRY != ''">
<PGVRText style="text"><br /><PGVRGedcomValue tag="ADDR:CTRY" /></PGVRText>
</PGVRif>
</PGVRTextBox>
---cut---
Do I understand correctly, that only the place where ADDR is the only value will be replaces with ADDR:RESI?
Andre
Basicaly, the only line I could find which contains only ADDR is:
<PGVRText style="text"><PGVRGedcomValue tag="ADDR:RESI" /><PGVRGedcomValue tag="RESI:ADDR" /></PGVRText>
everything else already contained ADDR:Something ....
I changed that line to ADDR:RESI which the correctly reports only the RESI address, but ignores the netered phone/ fax/email, etc.
I do have additional tags for phone/fax/email, which get printed in the addresslist, but the tag "PHONE" is not available anymore in my pgv version (4.2.2 svn)
Second: It doesn't print the RESI entries I made for families
Thanks
Andre