450 likes | 460 Views
Learn from past experiences and feedback to set new goals for the SEG project volumes. Create a modular database and API for editors to work on in an online and print environment. Implement a new editing environment to streamline workflows and enhance control over data. Advantages include saving time on typesetting, better data control, and cost savings. Benefit all involved stakeholders and work towards better integration and sustainability.
E N D
SEG Forward Project Lessons learned Feedback
Goals For all SEG volumes Create database Modular approach Create API Create editing environment For the editors to work in Online and print Create publication environment
Current workflow for SEG print .docx .pdf .docx online .xml
Current publication Print Online
New workflow for SEG .pdf print Editing environment .xml online
Reasons Advantage for editors Save time spent on typesetting Advantage for readers Better control over data Save money spent on creating XML Advantage for Brill Advantage for everybody Better website, integration, sustainability
What is SEG? New readings Bibliography Supplement… To existing corpora Commentaries New inscriptions
Data model for SEG Reference Entry Inscription
Data model for SEG (details) Reference User Entry Place Inscription Inscription Type Index Term
Database https://data.brill.com/sites/segadmin/raw https://data.brill.com/admin/datastore/obj/
API Work in progress…
Editing environment https://data.brill.com/sites/segadmin/ site https://github.com/BrillPublishers/SEGAdmin/wiki wiki https://github.com/BrillPublishers/SEGAdmin-UI code
Project status Finish interface (round 1) Next step Create print Step 2 Create online Step 3 Further development ?
Publication environment (print) BSGRE 11
Workflow for text editions Publication Environment Editing environment Author environment • Copy editing • Indexing • Data enrichment • Version management • Quality control • Writing • Editing • Data creation • Search, browse • Read, analyze • Exchange, download • Print: TeX templates incorporating the Brill Typographical Style • Online: TEI (or Epidoc) XML • Any other data format Plain text MS Word Zotero, TeX, CTE
Workflow for non-CMS Brill MRWs .xml .docx .md • Python scripts are used to convert from one format to another • GIT takes care of version management .pdf print
Publication environment https://labs.brill.com/ site Doesn’t exist… yet? wiki https://github.com/BrillPublishers/scaife-viewer code
Questions (1) CTS CITE Entry: urn:cts:brill:seg.entries.62626 Inscription: urn:cts:brill:seg.inscriptions.iseg62626 Reference: urn:cts:brill:seg.references.ref626261 or Entry: urn:cite2:brill:seg:62626 Inscription: urn:cite2:brill:inscr:iseg62626 Reference: urn:cite2:brill:refs:ref626261 or DTS
Questions (2) Is this a good idea?
Questions (3) What widgets?
Lessons learned More work than you think… Data cleaning Proactive Fast communication Keep it simple Kill your darlings It always takes longer than you hope Inevitable