G2G: Is there a maximum number of rows in a Table?

Question

Are there any limits on the number of rows x columns for a table in a Freespace profile? I have a transcribed military list 5,000 name row x 20 columns of information. I think the answer is obviously a no because it will be unmanageable, but let me know if you think otherwise. I'm therefore considering making 26 tables, one for each letter of the Alphabet, is that acceptable? From my review of cemetery tables I like the clean look of Robin's IOOF Cemetery table https://www.wikitree.com/wiki/Space:IOOF_Cemetery_Table_of_Graves

or alternatively provide a link to a sortable spreadsheet as Azure has done with an equally large spreadsheet.   https://www.wikitree.com/wiki/Space:Fairmont_Cemetery_Raton_NM_USA

Thanks to both of them for their excellent work.

In my case, I'm thinking of doing both. I expect that people using the site will know the surname of the person they are looking for. The tables will only have the bare minimum of columns necessary plus a column for the WT profile ID to be add. The separately linked spreadsheet will allow sorting by other fields such as religious denominations, occupations, ages, place of origin etc for people using it for other research purposes. Any ideas or comments would be appreciated.

Answer 1

John, I don't know if there is a limit to number of rows/columns in a wiki table, but would expect that there is.  The biography space on WikiTree's page is limited and more columns than can fit in that width would not be displayed in a meaningful way.

Your other example, using a google table linked from the free space page, is beautifully done and the way I would recommend that you do this.  To just list the names (as links to their profiles) on the space page doesn't require a table.

Comments

Hi Gaile, yes that would be my preference as well. At the moment, only 50 of the 5000 names have WT Profile IDs. The Freespace Table would allow free editing to have the WT Profile IDs added over the course of time. The other option is to go the external DB route for such a large data set. That way the normal source citation process could be used.

Answer 2

It should hold 5000, and can be sortable. See https://www.wikitree.com/wiki/Space:Igo_Name_Study_US_Federal_Census_1880 for an example with about 1000. 

However, users might not care to scroll that much. I like your idea of splitting alpha, and I would add a recommendation at the top for them to use the Find in page function of the browser (ctrl+F) to make it easier, although name variants will complicate that.

Also, as Gaile pointed out, selective columns. It will work but it looks like crap and nobody likes horizontal scrolling. 

Comments

Thanks Jonathon, appreciate your feedback. I'm starting to think (having looked at your example) that fewer rows and columns in any single table is preferable. We are trying to do with Tables/Lists what should (especially with large datasets) be done in a database.