I would like a global person index that I can easily share with family.
I am building a google spreadsheet manually because I can’t figure out how to pull the information from GRAMPS. This is painstaking, error prone, and hard to keep up to date.
For each person I want the following:
name: surname suffix, first “nickname” middle
birth date*
death date*
findagrave id with link to page - the link is in a citation note and the id needs to be parsed
familysearch PID with link to page (possibly multiple - definitely volatile) - the id is an attribute, hopefully with a link note
ssn (have not included links… they vary greatly)
JCPHauck page # and family # in citation (0-2i instances)- can I use @ to pull in scans on google?
HauckDesc - pull in number from descendant outline report
link to obit? with death date? or something more official? idk yet.
*If there are multiple dates, the prefered should be used but tagging would be nice
The dates are needed to distinguish people of the same name.
Looks like a generation job similar to NarrativeWeb except you don’t output an HTML page but a CSV file.
The difficulty here is to combine data from a Person (object) with other data extracted from secondary objects (Citation, Event?, Note?, Attribute, …).
If you’re brave enough you could take inspiration from NarrativeWeb (but not an elementary task) and program the required code (as a plugin – similar to how NarrativeWeb is implemented).
Another option would be to use the SQLite Export addon, and then write some SQL to do the work. This is not trivial either, and you would first need to apply some patches mentioned in the “See also” section of that wiki page.
Is that number generated by the report (and therefore not stored in Gramps)? IF that’s the case, you would need to program that logic as well.
Just curious, do you already share your Gramps data with them in one way or another (reports, generated web pages, Gramps web, etc.)? How would they use this index?
Just curious, do you already share your Gramps data with them in one way or another (reports, generated web pages, Gramps web, etc.)? How would they use this index?
I like the outline descendant report for myself and email branches upon occasion.
I like that I can pull a bunch of descendant reports into a book with a people index.
I am disappointed that I can not pull a source/citation index and footnote the reports.
That should probably be a different enhancement request.
I am using google docs to run OCR/translate old letters.
I can then share that work with google account authentication and commenting enabled for conversation. My family did not use that concept in the work sense so still tend to contact me offline. I have yet to link that work into GRAMPS. Since google docs does not support building a book based on including files, I am looking using libreoffice and how to use the indexing method from the book report.
I have not attacked the whole set up a secure website thing - and my synology is unhappy this year.
Looks like a generation job similar to NarrativeWeb except you don’t output an HTML page but a CSV file.
I started trying to set up a different descendant report with a format
descendant - spouse (residence)
child birth death marriage spouse birth death
…
I configured a linux sandbox and git, configured the files to print a title.
The overhead for the infrastructure here is way more complex than in lifelines which had obvious iterators and get type functionality. I had to learn not just the tree stuff, but menu stuff, and print stuff. It was taking a magnatude more time than I hoped.
Another option would be to use the SQLite Export addon, and then write some SQL to do the work. This is not trivial either, and you would first need to apply some patches mentioned in the “See also” section of that wiki page.
In my early GRAMPS days, I tried to do some command line sql queries. Then the executable disappeared??? Looked thru the obvious save space and malware logs but never did figure out why. Did install PatchMyPC and sql but got distracted. I’ll have to look into this. I suspect I’ll be dreaming sql queryies based on my knowlege of gedcom 5.5. I need to figure out how not to drop things that don’t have something in the join like familysearch id. I suspect adding an attribute for findagrave is easier than searching citations. Although given some of the other things in the back of my mind, it may be a place to start.
I have often wished to get reports based on stuff displayed in GRAMPS. This sounds promising on that whole scale.
It depends on how large the shared information is and how willing you are to disseminate detailed data.
As already suggested by @GeorgeWilmes, why don’t you generated a NarratedWeb collection of HTML pages. Do this without including media to speed up the process and to minimize storage space.
NarratedWeb has a global person index, without all the desired detail though. But, after a click on the person name, you access all details in the dedicated page.
There is no need to create a webserver. HTML files can be opened in any browser. You put the directory containing the NarratedWeb pages on a USB key and that’s it. To make things simple, open first the file named index.html, then navigate as usual.
I believe both recommendations to use NarratedWeb come from @pgerlier.
I did actually generate it this morning, just to look at it as a report without the share considerations. The person index does not contain nicknames, nor death date.
The individual page has link type notes printed out, but they are not live - not a hyperlink that can be clicked on (and definitely not verified for current functionality). Another short coming is that any notes (links, citations, source text) attached to the source are not included, only the citation. So it fails as a dump mechanism.
The thing I was hoping would be obvious from the spreadsheet is what work had been done and not been done on individuals at a glance. The collection of webpages does not make this obvious.
It depends of the name format in the display tab.
For the death date, we show them only if they are present
The following snapshot shows an extract from the individuals index page for the example.gramps. The third column is the birth date and the fourth the death date.
This is configurable. Death dates are listed in my NarratedWeb (but perhaps I patched the generator?)
This is indeed a shortcoming but you can compensate for that by formatting your links as “link” in any note.
???
If I understand correctly your request, you’d like the “annotations” of the source to be repeated in every citation ? It is easier to click on the source and open the source page to see the “annotations” there, without repetition.
This is configurable. Death dates are listed in my NarratedWeb (but perhaps I patched the generator?)
I don’t see either
by formatting your links as “link” in any note.
that sent me down a rabbit hole. As I do not see this as the sharable option this is not worth pursuing.
If I understand correctly your request, you’d like the “annotations” of the source to be repeated in every citation ? It is easier to click on the source and open the source page to see the “annotations” there, without repetition.
I went back and included sources.
All notes got the heading “narrative” with loss of the note type.
Another option would be to use the SQLite Export addon, and then write some SQL to do the work. This is not trivial either, and you would first need to apply some patches mentioned in the “See also” section of that wiki page.
I am not so familiar with this SQLite3, but my thought is generally that you can read multiple and lock once for writing. Why do I need to export to run a bunch of select statements for viewing data?
I already protested against this change in recent versions. All notes are not “narratives”. A note can be something else, like a link or a technical memo for the researcher, a call number, … So I reverted the patch in my copy.
Because, unfortunately, the data area stored in “pickled BLOBs” which can only be understood by Python code. The exported version does not have these. There’s a plan to replace the pickled BLOBs with with JSON, but I don’t know when that will ever happen. Although SQLite3 has some JSON capabilities, I imagine the queries would still be trickier to write than using the exported version.
