Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Numbering system #91

Open
WGroleau opened this issue Dec 1, 2022 · 13 comments
Open

Numbering system #91

WGroleau opened this issue Dec 1, 2022 · 13 comments

Comments

@WGroleau
Copy link

WGroleau commented Dec 1, 2022

Is it intentional that each generation starts over on the numbering?

1.1.3 can be 1.2 in the following generation.

Is there any possibility of doing the numbering like NGSQ or Register?
https://doczz.net/doc/2652787/ngsq-and-register-styles-comparison-chart

@WGroleau
Copy link
Author

WGroleau commented Dec 1, 2022

That chart describes many other differences that I don't endorse. Too complicated for the reader! But I do like the numbering system and the "+" for persons who will be listed again later.

@JustCarmen
Copy link
Owner

JustCarmen commented Dec 2, 2022

1.1.3 can be 1.2 in the following generation.

That should not be possible. 1.1.3 can be 2.1 in the next generation. Not 1.2.

Currently there is no configuration page in this beta version. It will probably be added before the first stable release.

By default, the show_singles option is set to '0' (= no). Which results in:

image

Only 1.1.1 and 1.1.3 are followed to the next generation since they have a partner and/or children. In the next generation they are the numbers 1 and 2. It is just a general numbering system.

But if the option show_singles is set to '1' (= yes) than all children will be followed to the next generation:

image

Here number 1.1.3 is number 2.3 in the next generation. But if there are multiple families in a generation than the children of the next family will get a higher number in the next generation. It is just a general numbering system created with css.

By the way, when changing the option to '1' it didn't work as expected but I have just solved this problem.

Is there any possibility of doing the numbering like NGSQ or Register?
https://doczz.net/doc/2652787/ngsq-and-register-styles-comparison-chart

I am afraid that system is too complicated. This requires a lot of coding, Besides personally I think it looks very restless with all the superscript numbering inside the text. For now I have no plans of changing the current numbering system.

@WGroleau
Copy link
Author

WGroleau commented Dec 2, 2022

Well, when I wrote it, it was doing the numbers weird the way I said. But now it isn't and I haven't downloaded new code. Strange. But I would still like the same person to have the same number each time he/she is mentioned. And never to have two people show the same numbers.

I like your text the way it is. The NGSQ method of repeating all the ancestors with superscripts is too much clutter. And the superscripts for footnotes are unnecessary, since webtrees has its sources on the facts tab.

But I do like the way they number persons on the left: + or blank for repeated or not, then a number that stays with that individual, and then a number for birth order in that family. The first and third aren't particularly valuable, but a consistent number for a particular person would be good. Otherwise, two different people might have the same name and the same number.

@JustCarmen
Copy link
Owner

JustCarmen commented Dec 2, 2022

but a consistent number for a particular person would be good.

The only purpose of the numbering system is to follow a person easily. Follow 4.2 only means that you can found that person in the fourth generation, listed as second.

But I do like the way they number persons on the left: + or blank for repeated or not, then a number that stays with that individual,

I think it is a very complicated system. But that is because I don't understand the rules. I miss the logic. Maybe you can take a screenshot and write the numbering on an FTV page using the NGSQ method. This might help.

Otherwise, two different people might have the same name and the same number.

I don't understand this. Each person has a unique number. It is not possible for two different people to have the same number. If you see this happening, please take a screenshot.

@TheDutchJewel
Copy link
Contributor

By default, the show_singles option is set to '0' (= no). Which results in:

image

Why not use this numbering:
1 Children of Ewout Ariansz Knegt en Grietge Henricz:
   1.1.1 Arij Eewitse Knegt (1596-) - follow 1.1.1
   1.1.2 Maritge Knegt (1598-)
   1.1.3 Cornelis Eeuwitsz Knegt (1603-) - follow 1.1.3
   1.1.4 Trijn Knegt (1603-)
   1.1.5 Lijsbeth Knegt (1607-)
   1.1.6 N.N. Knegt (1614-)

See for an example with this numbering: Parenteel van Jan Aertsz (van BEUSECUM)

@JustCarmen
Copy link
Owner

See for an example with this numbering: Parenteel van Jan Aertsz (van BEUSECUM)

This is the same system as I use. The only difference is they are using a Roman numbering system. And give the children the numbers 1, 2, 3. But each child gets a sequence number starting with the number of the next generation.

Why not use this numbering:
1 Children of Ewout Ariansz Knegt en Grietge Henricz:
1.1.1 Arij Eewitse Knegt (1596-) - follow 1.1.1
1.1.2 Maritge Knegt (1598-)
1.1.3 Cornelis Eeuwitsz Knegt (1603-) - follow 1.1.3
1.1.4 Trijn Knegt (1603-)
1.1.5 Lijsbeth Knegt (1607-)
1.1.6 N.N. Knegt (1614-)

And then the next one is 1.1.1.1. and the one after that 1.1.1.1.1. I don't see that as an improvement.

Frankly I don't understand why the current numbering system is even a discussion point. It is just a way to follow a person into the next generation. It doesn't mean anything. It is just a numbering system that is pretty much a standard for any list.

@WGroleau
Copy link
Author

WGroleau commented Dec 3, 2022

I was puzzled why what I saw before entering the issue was different from the second look. Now I know—the numbering starts over when I click "read more" to go to the next page. Image attached.
FAD-91
What I like about the NGSQ numbering is that no matter how much text is between two mentions of the same person, the number is the same. In https://unigen.us/tree/HHH/individual/P823/Pierre-Groleau-P823#tab-_jc-fancy-treeview_ , Thomas Groleau first appears as 2.1.3 and later as 3.1

@JustCarmen
Copy link
Owner

the numbering starts over when I click "read more" to go to the next page. Image attached.

I cannot reproduce that. Not even on your own site.

I've used the link https://unigen.us/tree/HHH/individual/P823/Pierre-Groleau-P823#tab-_jc-fancy-treeview_ and clicked in the tab on read more.

On the full page the numbering is correct:
https://unigen.us/tree/HHH/jc-fancy-treeview/P823/pierre-groleau-%28p823%29/descendants/2

In https://unigen.us/tree/HHH/individual/P823/Pierre-Groleau-P823#tab-_jc-fancy-treeview_ , Thomas Groleau first appears as 2.1.3 and later as 3.1

The follow-up links are only visible on the page, not in the tab. On reflection, I think they should be placed there as well. Therefore I'll mark this item as 'to do'.

On the page you will see the reference number to follow the child. So the third child from the first family in the second generation can be followed as the first family in the third generation.

If I comply with your request, I cannot use the generation numbers in the numbering. In the NGSQ system, they use the generation number in the text as a superscript, which I think looks very cluttered. An alternative is simple numbering, like on this site: https://www.genealogieonline.nl/wij-zijn-familie/afstammelingen/I1993/.

This is my own Gedcom, published on a Dutch genealogy site. They just gave each person in the list an ascending number. Children are not numbered separately.

@WGroleau
Copy link
Author

WGroleau commented Dec 8, 2022

The "start over" is either a bug in the Javascript of the module OR a bug in Safari. In Firefox, the numbering is as designed.

I agree that the NGSQ text is too cluttered. I wasn't suggesting that part. the NGSQ numbering system goes like this:

  1. first person … his/her details
    2. first child of that person
    3-8 six siblings
    Second generation
  2. first child of that person (same number—2) and details
    9. first child of first child
    10-13 four siblings
  3. second child of first ancestor and details
    14 first child of second child
    and then, no matter how many pages there are of second generation, to find the details of "9. first child of first child" you can look for Upgrade to the latest version of dompdf #9 again. Instead of seeing 2.1.3 and having to look for 3.1 for the details. Or looking for the name, which could be a different person with the same name.

@JustCarmen
Copy link
Owner

Okay, clearly. But this system only works if everyone appears in the next generation. For performance reasons or to avoid too much text, there is an option not to follow singles (persons without partners and children) to the next generation.

@JustCarmen
Copy link
Owner

JustCarmen commented Dec 11, 2022

Instead of seeing 2.1.3 and having to look for 3.1 for the details.

You don't have to look for it, you can just click the link which will bring you there immediately, even if the target is on the next page.

Okay, that is not quite true for the tab page at the moment. Need to fix that. This counts for the Fancy Treeview page.

@WGroleau
Copy link
Author

Ah, I didn't notice the link. Although, someone might want to print it, which disables the link. Anyway, having the link makes it less of an issue.

@Fa10175
Copy link

Fa10175 commented Oct 24, 2023

I've just tested version 2.0.4 and it works very well.
I just have one comment about the numbering
for example
11.1 Pierre
11.2 Louis
...
11.101Auguste
11.102Marie
as soon as the number exceeds 100, there is no space between the numbering and the person's name.
in the future, please see this to air out the presentation.
I hadn't noticed this before, but it probably existed too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants