Dutch Reformed part F Batch [MQ95-KD5] Index only Parents names?
Answers
-
The General Indexing Guidelines on "What to Do When Records Span 2 Images" says, in part:
- If the first record on an image begins on a previous image, don't index it. The record will be indexed as part of the previous batch. Start indexing at the first complete record.
- If the last record on an image continues to the next image, index the entire record, including what continues to the next image.
This is obviously assuming an entirely different format, but if we extend it to this tabular one, we basically have an entire page of records that begin on the previous image. If the indexer who gets that previous image follows this same logic, then these parents will be included there, and should be marked NED here.
I haven't a clue how likely it is that the other indexer will follow the same logic.
1 -
That is very confusing. The General Guidelines and Project Instructions contradict each other. I think in this instance I should follow the Project Instructions. It is clear they say to index the parents names only.
0 -
The project instructions says:
- Some records may continue to or from another image and you may need to view another image to get information for the fields on the image you are indexing.
Your batch is like the one in the first example with the exception that the register is split into two images. So, if the previous image is the first part of the register, then the indexer was correct to mark this image as No, No Extractable Data. As Julia said, the indexer of the first page will index the parents information with the child's name.
Not to worry that the information won't be indexed on the image you are reviewing. All images marked No, No Extractable Data are reviewed for accuracy. They will make sure that the indexer and reviewer on the previous image did this correctly.
The project instruction that I believe you are referring to as being confusing is:
- If a record does not include a name for the primary person, you should still index the record, marking the primary name fields blank and indexing other names, such as names of the parents, along with any other fields that are present on the record.
That is a little different because the primary person name is not available - like an unnamed infant with parents names and possibly a birthdate and death date that could be indexed.
0 -
DO NOT INDEX REFERENCE IMAGES. Pretty clear of what NOT to do?
0 -
While you do not index reference images, we can take information from the -1 or +1 images. Case in point: The New York and New Jersey Naturalization projects have us index the Record Date. The record date is located in different places, depending on which document you are working on. When it comes to Petition of Naturalizations, the date is found in the Affidavit of Witness section. Older Petitions have this on the same page, which is fantastic, but post-1940 Petitions have the witness section on the back, which is on the same document as the Oath Of Allegiance. This is located on the +1 image. The Do Not Index refers to the Oath Of Allegiance, not the Petition. The Oath is a separate document, is indexed as such and is part of the next batch, so the only thing that we will take from that +1 image is the witness date as the record date, since the Affidavit is part of the Petition, not the Oath. The Oath has a separate date that we use as the record date.
1 -
That FOR REFERENCE DO NOT INDEX wording was added to the reference images so that people don't index them. When indexers are faced with 35 preset entry forms, for example, they were indexing the information from the reference images to fill in the blank forms. That wording was added to try to stop them from doing that.
I cannot find anything in the actual project instructions that says DO NOT INDEX REFERENCE IMAGES. Perhaps I have missed that instruction. Could you copy and paste it?
Your batch is a register where the photographer could not fit the left and right side of the book on the single image. Thus, it becomes a "Record that Spans Two Images". However, the project instruction I posted is a little odd - it says that "Some records may continue to or from another image" which might lead one to think they should look at the previous image and complete their index. This would result in duplicated indexes for the same record. FS needs to take a look at that instruction and think about what it suggests!
We rarely do a look back on reference images (-1 through -5) for information, unless the project instructions say to use them to figure out a date. We often use reference images (+1 through +5) to complete a record. Australia wills come to mind where we often use the +1 through +5 reference images to include a will date or a death date and even a complete name when we are indexing the FIRST image of a will or probate case that continues over several images. But, every single reference image has that red instruction across it "For Reference Do Not Index".
1 -
I find that FS's instructions make the most sense if I figure that they use "index" as short for "create and fill in an index entry for", and "record" as short for (among other things) "a record or entry which begins on the image in the batch".
When you're looking at reference images, you don't create index entries for any of that data. You may, however, use some of the data to complete an index entry from your batch.
Likewise, if a record which begins on the image is missing the primary person's name, you still create an index entry for it and fill in what's available, such as the parents. As Melissa says, this is meant to cover things like stillbirths; it does not apply to the current case, because none of the records begin on the image that's in your batch.
0 -
Don't worry everyone. I have been following the most logical approach you people have written. I N. E. D. the parents only portion. Index the beginning portion and using the Reference images to fill in the blanks IF it matches precisely. Some older records don't match. I have to ignore those.
0