Bob, the problem is not with your data, but with the report you try to print in GRAMPS. The report has not been designed to write the information as you want it from the data you have in the family tree.

The solution is to augment the report so it writes out information as you would like to see it.
You should continue to use the bug tracker to draw attention to your problem:

1/create a small test GEDCOM as you have now in your favorite application, eg some 10 people, some families, sources and endnotes. --> file1.ged

2/import in GRAMPS --> file2.gramps

3/produce a report with gramps that you think is not good, eg in opendocument format --> file3.odt

4/open the report and edit it as you think the report should look like --> file3_as_I_would_like_it.odt

Then attach file1.ged, file2.gramps, file3.odt and file3_as_I_would_like_it.odt to a feature request. This will allow a developer to do exactly as you do, and see if he can change the report so the file GRAMPS produces resembles more the file you would like.

The above is the only method I see to get this item fixed.
You should not change your way of inputting data if that method is sound.


2008/2/27, sgtbob <>:

Benny - I've spent the last month trying to find a way to import a GEDCOM
file that would show the endnotes and their association with the applicable
person when making reports (Book, etc., ).  So far I've not been able to
make a GEDCOM prepared from FTM, PAF or Legacy do so - indeed all the
references in the endnotes still show 'imported from xyz.ged'.

I used Legacy and inserted a lot of 'events' with associated sources,
thinking that that program's GEDCOM would emulate the GRAMPS events and
solve my problem - alas, after importing the Legacy GEDCOM into GRAMPS, the
same thing occurs - end notes show as 'imported from xys.ged'. I sent a
sample in an earlier message that shows the type of report I'm trying to
prepare, but haven't had a solution suggested that will get me a report with
the items I would like to see.

My initial finding noted below, of having to re-visit each and every person
in my 16,652 person file and add events and source to each one, appears to
be the only viable solution at the moment. At my advanced age, I'm not sure
I will last that long. :working:

  I tried 3.0 to see if it would address this, but it did not appear to do so
- then perhaps I am not as familiar with it as I should be.

Thanks for the replies from everyone on this issue..


Benny Malengier wrote:
> 2008/2/10, sgtbob <>:
>> I believe I have figured out why I can not see end notes in my book
>> report.
>> It appears that each 'event' for each person must have the event source
>> put
>> into its own source field. Then the event is identified in the text of a
>> report with a number then this number and its source are displayed at the
>> end of the book report. This is great if one is starting out from day one
>> and entering this as such; however, when importing a GEDCOM with 15000+
>> names into GRAMPS, re-visiting each person to get a number of events
>> associated with their source is prohibitive.
>> I have experimented and find that if I click on an event (burial for
>> instance), edit it and add the source reference number to that event.
>> Then
>> upon generating the book, an 'exponent' number will be seen adjacent to
>> the
>> event  in the book and then this number now appears at the end of the
>> book
>> with the source data diosplayed.
>> In testing another program, I acquired the Legacy and installed it.  The
>> GEDCOM imported from FTM into Legacy went just as I wanted.  In this
>> manner,
>> events are identified with the number denoting the endnote, and then this
>> same number is entered at the end of the book with the endnote/source
>> written out.  All this transpired automatically upon import of the GEDCOM
>> file  into Legacy.  I didn't have to re-visit each source/individual.
> how can Legacy know what source must be connected to what event if that
> link
> is not present in your GEDCOM? Or is that link present in some other way
> Is there any way within GRAMPS that this can done and I just haven't been
>> able to figure it out?
> Bob, all data you want is in GRAMPS, except the source to event link.
> cannot guess that link.
> Should GRAMPS on import have known what sources are linked to what events?
> Or should the report just output the person sources in the book report
> too?
> In that case the problem is only a specific report not showing things as
> you
> would want them to be shown. Reports are separate from GRAMPS, in that
> they
> are like plugins,  made in such a way that users can add their own and
> share
> it with other users, see
> a tutorial.
> So in your case, as you probably don't want to learn python to learn to
> program your own report, it comes down to convincing a developer that how
> you want the report to appear is better than what is available. Obviously
> you will already be convinced of this fact. Problem is, a lot reports have
> been donated by users, and most developers, eg myself, don't normally code
> in the reports (the reason is that most developers use GRAMPS itself to
> view
> their data, or the narrative website, and don't use the non-graphical
> reports that much in my impression).
> The way to overcome the above lack of developer interest in changing a
> report in a way you like better, is by making a convincing case for it:
> 1/create an example of how the report should change
> 2/make a design of the report:
> 3/post a feature request on the bug tracker with the relevant information
> 4/help out with testing
> It is important to be very clear in communicating in the above steps.
> Benny
> PS: to quickly add sources of the person to it's event, you can use the
> scratchpad tool (the clipboard icon). Drag the source from the person
> editor
> on the scratchpad, in the event, drag the source from the scratchpad to
> the
> source tab of the events where it has to appear. That is the fastest way
> to
> do this.

> -------------------------------------------------------------------------
> This email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> _______________________________________________
> Gramps-users mailing list


View this message in context:

Sent from the GRAMPS - User mailing list archive at

This email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
Gramps-users mailing list