Two problems with places in Narrative Web Site

My thought is:
If GRAMPS allows such a places structure (or something other), and even more such a structure can actually exist as a normal behavior in the World, then export tools should not impose additional restrictions on it.

The index of pages is the most complex page in the narrative web.

I’m trying to explain how the narrative web works:

  1. Either you use a filter or the complete database.
  2. In any case, the report must know what we are going to display. This is to avoid 404 errors.
  3. For this the report uses dict indexed by name or handle.
  4. it works correctly for all pages except places pages. Why?
  • The name of the location depends on the format you use in the preferences.
  • We may have alternate place names depending on the dates.
  • For alternate names to work, we have another dict based on names. For this, we cannot have several identical names.

For the moment, the best solution should be to add the gramps-id of the place. But will it work for all cases ?

I’ll put the first version of my patch into the bug report.

1 Like

I will give the patch a try.

There is apparently something different between the places index and
other indices in the narrative web report. The indices I usually build
are Individuals, Surnames, Families, Places, Sources, Media, and
Updates, and recently I have started playing with Heatmaps. I do not
expect duplicates in Surnames, Sources, Media, and Updates, but there
are certainly duplicate names in the Individuals index as well as
duplicate names in the Person field in the Family index and duplicates
of nearly all families in the Family field, one entry for each partner.
I realize alternate names and date ranges for places complicates things
for them, but duplicate names alone cannot explain the problem if it
works for other indices.

I just tested the patch and it fixed the problems with duplicate names
for the places I checked. I still have a problem with places enclosed
by both Washington state and Washington territory, but I think I can fix
that by cleaning up the data now that I have a better understanding of
how things work, because it did work for Arizona state and Arizona
territory.

Thank you,
Allen

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.