Difference between revisions of "Talk:FamilySearch Indexing:US, County Marriage Records, Project Updates"

From FamilySearch Wiki
Jump to: navigation, search
(Two numbers on top of marriage documents: new section)
(North Corolina Marriages: new section)
(38 intermediate revisions by 12 users not shown)
Line 1: Line 1:
'''Help us improve the indexing and arbitration of this project.''' Click the '''Edit This Page '''button to make suggestions. Messages will be removed after careful review by support and any updates will be posted to the Project Updates page.
+
{{Discussion Notice}}
  
Many commonly asked questions, such as indexing crossed out information, have already been answered in the [https://help.familysearch.org/publishing/347/102817_f.SAL_Public.html Basic indexing instructions].
+
== Maiden Names ==
  
<br>
+
You should better emphasize the following basic indexing guideline:
  
It would be most helpful to flip the examples of the overlays so that they can be read. They are sideways on the screen now so it is hard to determine what exactly is on the overlays that we are supposed to index versus the overlays that are to be ignored. If they were photographed so that they could be read it would be much clearer since we could read the examples which we cannot do now. This would apply both to the powerpoint and to the overlay links in the project instructions.  
+
'''Do not assume maiden name is same as father's surname. If maiden name is not recorded on the image, do not index.'''
  
&lt;fck:hr&gt;&lt;/fck:hr&gt;
+
The example given under ''Maiden Names'' in the additional helps tab should include an example where the father's surname is&nbsp;''not ''
  
== Two numbers on top of marriage documents ==
+
== North Corolina Marriages ==
  
&nbsp;&nbsp; A project update item says to use the number on the top that is consecutive.&nbsp; Well, frequently both of the numbers are consecutive.&nbsp;  
+
TRhe latest newsletter said that this was a new project.&nbsp; Why Can't I find any batches to index&gt;
 
 
&nbsp;&nbsp; A project I frequently work on is the US&nbsp;District of Columbia - County Marriages.&nbsp; There are typically 2 pages per image with 1 document per page.&nbsp; Each page has a 3 digit consecutive number typically range from 1 to 500 and a 6 digit number typically greater than 100,000.&nbsp; So the page numbers are repetitive across the many books while the certificate numbers are unique. Also some of the images are letters which a person writes to correct some information and these letters refer to the certificate number.&nbsp; So it makes sense to index the unique certificate number rather than the page number which is not unique.
 

Revision as of 02:05, 23 March 2013

This discussion page is no longer in use. Please use the discussion tab on the FAQ page to make a submission. (Any currently posted issues will be resolved and removed.) The wiki now accepts other observations and questions about the project, not just project update issues.  The new Wiki Presentation will guide you through the process of making submissions and how they will be handled.


Maiden Names

You should better emphasize the following basic indexing guideline:

Do not assume maiden name is same as father's surname. If maiden name is not recorded on the image, do not index.

The example given under Maiden Names in the additional helps tab should include an example where the father's surname is not

North Corolina Marriages

TRhe latest newsletter said that this was a new project.  Why Can't I find any batches to index>