How to highlight text that is in the next image?
There is this record that spans to 3 images. I can add all the people present in the record in the first image where the record starts. But, I can't highlight some of the people that appear only in image 2 or 3. Because when I navigate to the next image I get "This image has not been indexed."
How can I highlight text in a non indexed image? Or how can I group the images as a single record? Or how can I index the non indexed image?
Answers
-
In the index editor, the answer may very well be "you can't". (It's a highly complicated piece of software that has been plagued from the very beginning by bugs the size of gremlins. I know I'm not the only long-term user of FS who has effectively given up on it.)
I have a suggestion for what to do instead: bypass the index entirely and cite the image(s) as your source. This will not make the new "data quality" algorithm happy, as it considers the lack of indexed sources to be an error, for some incomprehensible reason, but I'm finding it best to ignore that whole thing as much as humanly possible.
3 -
Ok. Let's ignore the indexing.
Your suggestion is that I add all the people in the first image, and don't highlight the ones in the next pages?
0 -
@GustavoFarias84 I think Julia is suggesting that trying to fix the index is a waste of time until editing tools are functioning correctly. Would you share what collection you were working in? Losing indexed data is a separate problem and it's important to know where it is occurring to get it restored.
1 -
@SerraNola It doesn't seem to be a case of lost indexed data. Every 2 or 3 pages (where records begin) there is indexed data. The index is nonexistent only in the in-between pages.
Even with bad tools, how can I fix an index? I see no edit option. See this.
0 -
If, for example, a record is 2 images, front and back of a page, the back is often not indexed because it was not part of the project. You can still attach the record image to the tree profile of the relevant person or people, using your Source Box, or even as a Memory Source.
You may find the Help Article useful.
1 -
Indexing on FS is a whole separate section (Get Involved - Indexing). It uses an online indexing tool. The volunteer chooses the project to work on, but gets assigned a batch randomly; the only choice in the matter is to index it or to return it unindexed for a different volunteer to do. We also have no input into projects: the setup for those is a complex negotiation with the record custodians and with the documents themselves, which are never homogeneous.
Once the Indexing section finishes a project, the text entered by the indexers goes through various post-processing steps and then gets published, i.e., added to the database that Search - Records uses. This database is large and varied, and -- like all indexes -- it has many errors. Some of those errors are user-correctable. That correction process is index editing.
As I wrote above, and as you've observed, the index editing tool is complex and buggy. It works OK if all you want to do is correct the reading of a name, but more complex or structural changes often don't work or aren't possible. In particular, if an image does not have index entries already associated with it, then the tool isn't available on it at all.
However, despite the way FS (like all of the other genealogy websites) treats indexes as "The Data", they aren't, actually. They're just finding aids for the data contained in the historical documents. This is why, when the index is hopelessly wrong, I suggest skipping it entirely and just using the document itself (or an image of it) as your source. Both the index editor's and the catalog's image viewers offer an "Attach to Family Tree" process for doing just that.
1 -
"In particular, if an image does not have index entries already associated with it, then the tool isn't available on it at all."
I would be great if every non indexed image had a auto generated empty fake index just to enable people to use the edit functionality without needing to create the index first via batch and project. Something like a primary name for a "Jon Doe". Then people would add another primary name and remove the fake one.Is there any section here to discuss the bugs in the editor? I would like to understand more. For now I'm satisfied with the index editor. It's not perfect but it's usable. What I dislike is the fact you can edit an index but you can't create one.
0 -
@GustavoFarias84 You have several threads on the same topic. As a result, the answers (mostly the same) are scattered among your several posts.
0
