Sorry all for the multiple messages, I've been experimenting,
exporting, importing, making reports, reading GEDCOM and trying to see
how it works.
I read this in the very beginning but only now have I saw it as
something that makes real sense (as opposed to something utilitarian
yet only done because of lack of better alternative)
Benny said:
>I believe you say that sourceref needs a description. A running text to make clear what it references in the source.
> Do a feature request. You can misuse the page field to achieve it somewhat:
I've been reading about it and it makes sense to put that description
in the source reference. Especially given that I found this:
----
EVENTS_RECORDED:=
{Size=1:90}
[<EVENT_ATTRIBUTE_TYPE> |
<EVENTS_RECORDED>, <EVENT_ATTRIBUTE_TYPE>]
An enumeration of the different kinds of events that were recorded
in a particular source. Each
enumeration is separated by a comma. Such as a parish register of
births, deaths, and marriages would
be BIRT, DEAT, MARR.
----
So, this answers a small discomfort I was having with my Source
definitions since I have "Baptism Records of the Parish of St. John",
even if the "baptism" part is something that has not direct relation
with the actual source (as I learned upon finding mixed books in
Parishes that contain baptism, wedding and death records
intermingled). Changing the Source to "Parish of St. John" makes it
perfectly natural do add in the source reference something like
"Baptism record of John, 1856, Pg. 13". This eliminates the need for
the "description" field I was talking about, and actually looks better
in reports (I was having duplicate TEXT entries).
Also, in terms of handling the different relevance of different
sources, I found this interesting:
--------
EVENT_TYPE_CITED_FROM:=
{SIZE=1:15}
[ <EVENT_ATTRIBUTE_TYPE> ]
A code that indicates the type of event which was responsible for
the source entry being recorded. For
example, if the entry was created to record a birth of a child, then
the type would be BIRT regardless
of the assertions made from that record, such as the mother's name
or mother's birth date. This will
allow a prioritized best view choice and a determination of the
certainty associated with the source
used in asserting the cited fact.
--------
This would also aid in arranging the more relevant sources in some
kind of order.
After better analysing all of this - and reading the GEDCOM standard
closer was a big help in understanding why things are done the way
they are and why some suggestions are difficult or make little sense -
most of my doubts are answered, and much of what I said was due to a
misunderstanding on my part of the role of source references.
A way to find them and a way to identify images would still be good,
but other than that I'm actually happy now. I've changed several
records and the appearance of it is impecable and the more
event-orientated sourcerefs (with small citations supporting the
event, etc) are a big help.
If nothing else this conversations are a good way to learn all of
this, but my apologies if I wasted anybody's time!
Regards,
Frederico
------------------------------------------------------------------------------
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com_______________________________________________
Gramps-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gramps-users
Locked
