forked from tfmorris/scribeAPI
-
Notifications
You must be signed in to change notification settings - Fork 1
Workflow design
Tom Morris edited this page Apr 23, 2016
·
1 revision
This page contains thoughts, proposals, and experiments related to the Scribe workflow design for the NYC Marriage License Application registers.
Page -- Is there info to transcribe (Yes/No -- pickOne) (ANZAC)
If Yes, is the image an index of Brides or Grooms (Bride/Groom -- pickOne) (ANZAC)
If No, next image.
Mark Records -- Name (Surname, Given Name(s) -- Composite) (EmigrantCity)
-- Citation (Volume, Page, Number -- Composite) (EmigrantCity)
-- Date (Month, Day, Year -- Composite) (EmigrantCity)
Is there anything else to mark? -- (Yes/No -- pickOne) (ANZAC)
- How do we handle dittos? Preliminary position (Ben/Tom) to transcribe as is and normalize in post processing.
- Do we want to separate volumes by borough or borough & year into collections that volunteers can choose to work on separately? See for example Old Weather ship voyages or Science Gossip magazines. (Tom thinks so)
- What classes of unusual stuff do we want to handle separately from the "anything else" catchall? Examples might include "No Return", "Dup", empty page, unreadable/bad page