Talk:World Archives Project: USHMM - Krakow, Poland, Applications for ID Cards for Jews during World War II (Part 3)

From Wiki
Revision as of 13:18, 7 November 2012 by Annafechter (talk | contribs) (Common Keying Errors Found by Reviewers)
Jump to: navigation, search

Feel free to add to or edit information in this discussion tab as necessary. Please take time to become familiar with the General Keying Standards and be sure to read all instructions on the main project page. (Please note that in case of a discrepancy, project level instructions always trump general keying standards.)

Extra Keying Helps

Common Keying Errors Found by Reviewers

From Krakow part 2

I have just begun to arbitrate these records and notice recurrent problems, some of which have been mentioned before:

1. Please do not put Jude or Judin as a prefix (it means Jew or Jewess)

2. Please do not put a 0 before a number as in a date.

3. Janner should be keyed as Januar

4. a number of miscellaneous documents and residence requests look similar but are not identical and should be keyed

5. Do not key the signature of the German official at the bottom of some miscellaneous documents.

6. Key only what is seen on that image, for example do not enter a name that was on a previous image but is not on the present one.

I am hoping that this will help others and make the arbitration easier.
Patricia Lewin

7. do not create sections for the household members list. --Elisabeth power 10:15, 4 November 2011 (UTC)

8. Remember on Residence Request documents to make sure they are exactly the same if you mark them as a duplicate image.

9. Someone is keying documents that have names and dates on as Cover pages. These should be Miscellaneous and the information entered with the exception of Erganzübogan and Fragebogen card backs, which are cover pages.

10. International characters: Some keyers use characters from the international character board, that are not part of the German or Polish language. "n" with a long line above it signifies "nn". A "u" with a mark above it, simply differentiate "u" from "n". Please do not use the "u" with a bend line.
--Elisabeth power 18:53, 3 September 2011 (UTC)

11.  Duplicate image is when the same document is shown twice in a row. Some keyers marking "residence requests" as duplicates when almost all the information on the documents are the same although they are different documents. One documents shows the ID card number the other does not.

12. 'Document type: the difference between "cover page" and "image with no data" is that the "cover page" is retained as a record even we do not key from it. A researcher can still see it by scrolling backwards or forwards. The "image with no data" is not  retained. 

I mark all second pages and back of cards where no information is keyed from as "cover page". The only time I use "image with no data" is for a blank image or at the beginning of a microfilm, where the first images contain microfilm storage information. *
Sxecano: Example of image that should be marked as cover page,

  • The above explanation is correct, however because the images for the USHMM projects will not be available on Ancestry whether a document is categorized as a Cover page, Image with no data, or Duplicate is not as much of as issue as making sure we are keying the correct records. Only the indexes are available to be searched on Ancestry. For an example of a live USHMM database click here.Annafechter 15:03, 28 August 2012 (UTC)

Questions and Answers

If you have a keying question that is not answered on the project page or in any of the information above, click “EDIT” and ask it here. (If you click on Rich Editor you won't have to worry about formatting your entry.) Then click “WATCH” at the top right on this page and you will be notified via email when an update has been made.


If you have a suggestion or would like to make an addition to the project page, click “EDIT” and post your suggestion here. (If you click on Rich Editor you won't have to worry about formatting your entry.) Then click “WATCH” at the top right on this page and you will be notified via email when an update has been made.