The Form has Marriage License City and county and Marriage County and City. Examples do not.
I am working on batch - Us, Virginia -- Marriage Records, 1853 -- 1935 [M3WK-6LZ]
The examples do not match the form. The Form has entries for marriage license city and county and marriage city and county.
This image has county as listed at the top of the form which is Accomack.
Then on the line for each marriage, there is a marriage town or county column. I am assuming that this is town.
Do I mark the Marriage License City and Marriage License County entries on the form blank or should I enter the same city and county in both marriage License city/county and marriage city/county entries on the form?
Hope that is clear.
Thanks.
Darrel
Best Answer
-
Thank you for your question,
The Marriage County can be taken from the Header of the Image (Accomac).
The License City is Not Identified so it is <Blank>
The Marriage County is Not Shown, but the Marriage Cities are shown under the "Town or County" Heading, so we can Index that as the town Except the rare occasion where it does say "Accomac Co" Then we can use Accomac in the County Field Only.
Since it does not state City or County with most of the entries, the Marriage County should also be <Blank>
Hope this helps .
1
Answers
-
This form is typical of most of these in the collection and is much like Example 1.
The License County is Accomac from the header. But, the Marriage City and County fields are a little more confusing.
The field help for the Marriage City says:
If the marriage place was not clearly indicated as city or county, please index the place in the county field. Do not index places of residence, churches, stores, or other localities in this field.
The field help for the Marriage County says:
If the marriage place was not clearly indicated as city or county, please index the place in the county field. Do not index places of residence, churches, stores, or other localities in this field.
In each of the three examples, the marriage place is indexed in the County field, even the city of Roanoke (which is an independent city of Virginia and seen as a city on the header), and Chincoteague which is is a town on the island of Chincoteague. My understanding of those instructions, in concert with the examples, is that when it isn't listed as a city or a county, we will be indexing most of these places in the Marriage County field.
I would be great if a moderator could check on this next week and figure out exactly what the project managers are expecting.
1 -
I am working on this too but if we know its a city why would we go out of our way to put it in the county field? and since it has the county listed as ACComack above is that the marriage county or where the license is given?
0 -
Mostly we need to index these the way the instructions tell us to because if we don't then it goes through a bunch of reviews and holds up the project. If the column of where they were married (town or county) has Accomack Co written in, then it would be indexed as such. If it doesn't, it would still be indexed in the county field based on the field helps. I don't why they have such an odd instruction, but apparently someone thought this was a good idea.
0 -
Please read the Field Help for Marriage County. On this batch, the county should be indexed as Accomac.
0 -
@Allison Lathrop The question is about the field helps! Should ALL the various places of marriage be indexed in the county field based on the field helps and the examples? Please read my lengthy post above, but, I'll try to be more explicit below:
The field helps for both license and marriages state: If the marriage (license) place was not clearly indicated as city or county, please index the place in the county field.
On Example 1, Chincoteague is indexed as a Marriage County. Chincoteague is a town located on the island with the same name. Chincotegue is part of Accomac County and that is indexed as the Marriage License County. Based on the field helps, that would be correct since the printed header doesn't say whether Accomac is a city or a county. (No red underline or anything crossed out like on Example 3!)
On Example 2, Roanoke is indexed both as a Marriage License City and then it is indexed as a Marriage County. Roanoke is not a county, it is one of the 38 independent cities of Virginia. (However, you will notice on the example, county is crossed out and city is used in the header. But, on the Marriage Place, without clearly indicating it as a city or county, it is then indexed as Marriage County.)
On Example 3, Mecklenberg is indexed both as the Marriage license County and the Marriage Place county - correctly, since it is a county and not a city.
Here's another batch in case the one above is submitted.
https://www.familysearch.org/indexing/batch/afe803eb-bfa5-4297-a5d1-599734cdb4b1
M3WV-23W
You may private message me for more information if necessary. Thanks.
0 -
For the last 2 days it takes forever to move from one line to the next in the entry box. Therefore mistakes are made because I have to wait so long for it to change lines. This has not been the usual problem. I am wondering what is causing this to happen.
0 -
@CarolThomas1 is this happening on all the projects, or just Virginia marriages? I just indexed part of one to see if it would lag for me and it does not. The City Directory project will lag because there is so much data being entered with the 600 + names in a batch.
I suppose several things could be happening. It could be the speed of your internet service. It could also be a glitch with your computer. It could be the browser you are using.
When my computer starts getting glitchy, I clear the browser history and also clear the FamilySearch Cookies. Here is a link to a help center article on clearing the familysearch cookies and temporary files on your computer. At the bottom of the page you will see a link for an article about compatible browsers.
0
