From 3bb69485d3b40900b21daef0ab2bdcd0e8da9442 Mon Sep 17 00:00:00 2001 From: Dave Thaler Date: Thu, 30 May 2024 10:00:09 -0700 Subject: [PATCH 1/3] Add tech faq discussion about source URLs Fixes #174 Signed-off-by: Dave Thaler --- _pages/techfaqs.md | 47 ++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 47 insertions(+) diff --git a/_pages/techfaqs.md b/_pages/techfaqs.md index a412335..404f291 100644 --- a/_pages/techfaqs.md +++ b/_pages/techfaqs.md @@ -334,3 +334,50 @@ unknown parties. Relative paths, however, are permitted in both GEDCOM and GEDZIP files and so may be more convenient to use in both cases. Any tool that converts FamilySearch GEDCOM 7.0 to GEDZIP should convert local file URLs to relative paths within the resulting GEDZIP file. + +# How do I record the URL of a source? + +While `EVENT_DETAIL` and `REPOSITORY_RECORD` both allow a URL to be placed in a `WWW` substructure, +`SOURCE_CITATION`, `SOURCE_RECORD`, and `SOURCE_REPOSITORY_CITATION` do not. + +Some applications might put the source URL for an `EVENT_DETAIL` in a `WWW` substructure +in parallel to a `SOURCE_CITATION` as follows: + +``` +1 DEAT +2 DATE 14 DEC 1799 +2 WWW https://www.findagrave.com/memorial/1075 +2 SOUR @FindAGraveSourceRecord@ +3 PAGE Memorial: 1075 +``` + +However, since there can be multiple source citations per event, this does not allow associating the URL +with a specific source citation. Instead, the URL can be placed in the `PAGE` structure. For example: + +``` +1 DEAT +2 DATE 14 DEC 1799 +2 SOUR @FindAGraveSourceRecord@ +3 PAGE Memorial: 1075, URL: https://www.findagrave.com/memorial/1075 +``` + +Similarly, some applications might put the source URL for a `SOURCE_RECORD` in a `PUBL` substructure +as follows: + +``` +0 @S1@ SOUR +1 TITL Grave of George Washington +1 PUBL https://www.findagrave.com/memorial/1075 +``` + +while others might put it in the `CALN` of a `SOURCE_REPOSITORY_CITATION` as follows: + +``` +0 @S1@ SOUR +1 TITL Grave of George Washington +1 REPO @FindAGraveRepositoryRecord@ +2 CALN https://www.findagrave.com/memorial/1075 +``` + +Note that unlike the `PAGE` structure, the `CALN` structure has no current recommendation about using +label: value pairs. From e5e0c75b7ccf29acd724167132c08ea76adca9c3 Mon Sep 17 00:00:00 2001 From: Dave Thaler Date: Thu, 30 May 2024 12:19:04 -0700 Subject: [PATCH 2/3] Update _pages/techfaqs.md --- _pages/techfaqs.md | 10 +--------- 1 file changed, 1 insertion(+), 9 deletions(-) diff --git a/_pages/techfaqs.md b/_pages/techfaqs.md index 404f291..67d23b8 100644 --- a/_pages/techfaqs.md +++ b/_pages/techfaqs.md @@ -341,15 +341,7 @@ While `EVENT_DETAIL` and `REPOSITORY_RECORD` both allow a URL to be placed in a `SOURCE_CITATION`, `SOURCE_RECORD`, and `SOURCE_REPOSITORY_CITATION` do not. Some applications might put the source URL for an `EVENT_DETAIL` in a `WWW` substructure -in parallel to a `SOURCE_CITATION` as follows: - -``` -1 DEAT -2 DATE 14 DEC 1799 -2 WWW https://www.findagrave.com/memorial/1075 -2 SOUR @FindAGraveSourceRecord@ -3 PAGE Memorial: 1075 -``` +in parallel to a `SOURCE_CITATION`. However, since there can be multiple source citations per event, this does not allow associating the URL with a specific source citation. Instead, the URL can be placed in the `PAGE` structure. For example: From 29b9f5e578ba60cb80a159e92f48b29f71b8018f Mon Sep 17 00:00:00 2001 From: Dave Thaler Date: Thu, 30 May 2024 12:20:24 -0700 Subject: [PATCH 3/3] Update _pages/techfaqs.md --- _pages/techfaqs.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/_pages/techfaqs.md b/_pages/techfaqs.md index 67d23b8..4cb3f65 100644 --- a/_pages/techfaqs.md +++ b/_pages/techfaqs.md @@ -341,9 +341,7 @@ While `EVENT_DETAIL` and `REPOSITORY_RECORD` both allow a URL to be placed in a `SOURCE_CITATION`, `SOURCE_RECORD`, and `SOURCE_REPOSITORY_CITATION` do not. Some applications might put the source URL for an `EVENT_DETAIL` in a `WWW` substructure -in parallel to a `SOURCE_CITATION`. - -However, since there can be multiple source citations per event, this does not allow associating the URL +in parallel to a `SOURCE_CITATION`. However, since there can be multiple source citations per event, this does not allow associating the URL with a specific source citation. Instead, the URL can be placed in the `PAGE` structure. For example: ```