that is, the tag in error isn't there.
Note that the CONC adds one character - a '.' - and the line above ends '..Kingdom'; whereas in the GEDCOM view the last character of that line is a '.' and it ends '..Kingdom.'
David
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
that is, the tag in error isn't there.
Note that the CONC adds one character - a '.' - and the line
above ends '..Kingdom'; whereas in the GEDCOM view the last
character of that line is a '.' and it ends '..Kingdom.'
The error is pointing at the PAGE line, which doesn't conform to the GEDCOM standard. It's too long, and is not allowed to be extended by means of a CONC line.
The text you have quoted properly belongs in a NOTE.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The error is pointing at the PAGE line, which doesn't conform to the
GEDCOM standard. It's too long, and is not allowed to be extended by
means of a CONC line.
The entire entry was created by phpgedview - its a SOUR added to a RESI
tag in a popup edit window.
The text you have quoted properly belongs in a NOTE.
I obviously have the whole 'source citation details' thing wrong. A
commercial site I have used puts that kind of document reference into a
'citation ...' field and I thought that's what I should do here. What
sort of data should go in the 'Citation details' box if what I've been
putting there should be a NOTE?
You should look at Tamura Jones' site, in the "standards" section, where you can find a link to download an annotated edition of the GEDCOM 5.5.1 specification.
You should look at Tamura Jones' site, in the "standards" section,
where you can find a link to download an annotated edition of the
GEDCOM 5.5.1 specification.
I disagree that the fault is with PhpGedView. The GEDCOM checker is to be viewed as providing information only. PhpGedView is actually very lenient when it comes to non-conformance.
It's your responsibility to ensure that you fill in the various fields in accordance with the GEDCOM "standard". There's no way the program can possibly do all that for you.
The PAGE reference is supposed to point to the page in the Source document. Other fields in the SOUR record should enable you to find the source document in question. You have stuffed all of the supporting information into a single PAGE reference.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I disagree that the fault is with PhpGedView. The GEDCOM checker is to
be viewed as providing information only. PhpGedView is actually very
lenient when it comes to non-conformance.
It's your responsibility to ensure that you fill in the various fields
in accordance with the GEDCOM "standard". There's no way the program can
possibly do all that for you.
The PAGE reference is supposed to point to the page in the Source
document. Other fields in the SOUR record should enable you to find the
source document in question. You have stuffed all of the supporting
information into a single PAGE reference.
When using pgpgedview HTML form window fields to enter data it is not
obvious which GEDCOM tag or structure the data you enter is going to be
a part of, therefore you cannot ensure that the data you enter complies
with the GEDCOM rules. The user has no control over CONC or CONT, or any
other for that matter. If it fits in the box you expect it to be ok.
In my error the PAGE line is too long, but there is no indication that
the text entered into the box labelled 'Citation Details' will end up in
a GEDCOM 'PAGE' tag of limited length and with a use more restrictive
than than that given in the Help:
"In the Citation Details field you would enter the page number or other
information that might help someone find the information in the source."
The data I entered fitted that description in the Help. The length of
the data is one code unit over the maximum, but Tamura Jones puts the
onus on the GEDCOM writer software to split and use CONC or CONT lines
to prevent this. I have "stuffed all of the supporting information into
a single PAGE reference" rather than using "Other fields in the SOUR
record" because phpgedview does not give me access to those other fields
other than 'Text' which goes into PAGE.DATA.TEXT
Doing a GEDCOM check for 'errors' I see and invalid tag:
0085070 3 PAGE Archive reference: RG10; Piece number: 4677; Folio: 104C; Page: 36; Schedule: 186; HouseHoldID: 1908792; Record set: 1871 England, Wales & Scotland Census; Subcategory: Census; Category: Census, Land & Substitutes; Collections from: UnitedKingdom
0085071[[4 CONC .]] invalid tag ; see FAM @F31@
0085072 3 NOTE REFN http://search.findmypast.co.uk/record?id=GBC/1871/0009163176&source=GBC/1871/0009163175
Viewing the GEDCOM for that family shows:
3 PAGE Archive reference: RG10; Piece number: 4677; Folio: 104C; Page: 36; Schedule: 186; HouseHoldID: 1908792; Record set: 1871 England, Wales & Scotland Census; Subcategory: Census; Category: Census, Land & Substitutes; Collections from: UnitedKingdom.
3 NOTE REFN http://search.findmypast.co.uk/record?id=GBC/1871/0009163176&source=GBC/1871/0009163175
Note that the CONC adds one character - a '.' - and the line above ends '..Kingdom'; whereas in the GEDCOM view the last character of that line is a '.' and it ends '..Kingdom.'
David
The error is that the PAGE reference doesn't conform to the GEDCOM standard. The text properly belongs in a NOTE.
If you're happy with the citation as you have quoted it, ignore the "error".
The error is pointing at the PAGE line, which doesn't conform to the GEDCOM standard. It's too long, and is not allowed to be extended by means of a CONC line.
The text you have quoted properly belongs in a NOTE.
On 2/7/24 21:59, Gerry Kroll wrote:
The entire entry was created by phpgedview - its a SOUR added to a RESI
tag in a popup edit window.
I obviously have the whole 'source citation details' thing wrong. A
commercial site I have used puts that kind of document reference into a
'citation ...' field and I thought that's what I should do here. What
sort of data should go in the 'Citation details' box if what I've been
putting there should be a NOTE?
David
You should look at Tamura Jones' site, in the "standards" section, where you can find a link to download an annotated edition of the GEDCOM 5.5.1 specification.
https://www.tamurajones.net/standards.xhtml
This document provides LOTS of information, and is searchable.
Mr. Jones is very knowledgable, and has authored numerous very informative articles on genealogy.
On 8 Feb 2024, at 19:34, Gerry Kroll wrote:
Thanks for this. I will study it.
The initial problem however was out-of-spec GEDCOM data generated by
phpgedview.
I did remove the trailing ‘.’ from the PAGE line and the error went
away, so it was only 1 character over.
David
I disagree that the fault is with PhpGedView. The GEDCOM checker is to be viewed as providing information only. PhpGedView is actually very lenient when it comes to non-conformance.
It's your responsibility to ensure that you fill in the various fields in accordance with the GEDCOM "standard". There's no way the program can possibly do all that for you.
The PAGE reference is supposed to point to the page in the Source document. Other fields in the SOUR record should enable you to find the source document in question. You have stuffed all of the supporting information into a single PAGE reference.
On 2/9/24 13:30, Gerry Kroll wrote:
When using pgpgedview HTML form window fields to enter data it is not
obvious which GEDCOM tag or structure the data you enter is going to be
a part of, therefore you cannot ensure that the data you enter complies
with the GEDCOM rules. The user has no control over CONC or CONT, or any
other for that matter. If it fits in the box you expect it to be ok.
In my error the PAGE line is too long, but there is no indication that
the text entered into the box labelled 'Citation Details' will end up in
a GEDCOM 'PAGE' tag of limited length and with a use more restrictive
than than that given in the Help:
"In the Citation Details field you would enter the page number or other
information that might help someone find the information in the source."
The data I entered fitted that description in the Help. The length of
the data is one code unit over the maximum, but Tamura Jones puts the
onus on the GEDCOM writer software to split and use CONC or CONT lines
to prevent this. I have "stuffed all of the supporting information into
a single PAGE reference" rather than using "Other fields in the SOUR
record" because phpgedview does not give me access to those other fields
other than 'Text' which goes into PAGE.DATA.TEXT
David