June 26, 2014

Meeting Notes for June 26, 2014

The information below involves some changes to our processes so please read through it carefully.

Workflow: we want to move forward with publishing texts to WWO, so we’re asking folks to prioritize proofing, entering corrections, and checking corrections entry, as well as encoding. The DSG wiki has information on these processes here: http://dsg.neu.edu/wiki/Routine_Encoding_Procedures#Proofreading (The wiki is still being updated, so be aware that some information may be outdated or incomplete.) To familiarize yourself with what proofing looks like, it is a good idea to start with checking: essentially, comparing the handwritten corrections against the TEI files to ensure that all corrections have been completed and properly entered. If you have questions or suggestions about these processes, just let me know.

Dates and status tracking: since these texts go through so many stages and hands, it’s very important to keep track of what you do with them. This means: changing the colored labels and assigning yourself to Trello cards, moving cards in Trello and physical files in the cabinet as texts progress to their next stages, taking note of dates and your progress on the proofing sheets, and keeping a change log of major milestones in the TEI files themselves. Syd mentioned that if you haven’t yet filled in all the change logs on your TEI files, you can check the history in Subversion. To do this, simply control-click on your text in Subversion and select “show history” – then hit “ok.”

Idealized page numbers: we had an interesting discussion about whether these are necessary or significant – the conclusion we reached is that they likely are not. Syd is going to explore this further before we make any permanent changes, but for now, it is okay to stop recording idealized page numbers (but not page breaks!) as you go forward with encoding. If you find an error in the printed page numbers/metawork, use <sic> to mark it, but don’t add a correction in <corr>.

Encoding challenges: Sarah S. and Alicia brought in questions about how to encode braced lists and inset stage directions – these are the examples Julia sent out to the list yesterday. Fuller explanations are to come.