6. Christian Science Church
• Started with eZ via Christian Science
Monitor
• Replace 40 co-mingled WPMU sites,
Java/XML based CMS
7. Christian Science
Publishing Society
• Handles all publishing operations of
the church
• Christian Science Monitor
• Christian Science Journal
• Monthly publication
• First edition in 1883
8. Christian Science
Publishing Society
• Christian Science Sentinel
• Weekly Publication
• First edition in 1898
• Christian Science Herald
• 14 languages
• Various schedules
• First edition in 1903
16. Project Overview
• Bring every article published in
these periodicals online.
• Permissive business model to grant
subscribers access and allow for
content sharing and free content
selected by editors.
17. Project Overview
• Bring every article published in
these periodicals online.
• Permissive business model to grant
subscribers access and allow for
content sharing and free content
selected by editors.
• Deep search functionality to support
archivists as well as casual
searchers.
19. Methodology
• All back issues destructively
scanned and OCR’d.
• Each article manually converted to
PRISM XML, OCR errors removed,
and marked up.
• eZ imports PRISM XML to digitally
re-assemble issues.
• Scans provided for access to
original content placement.
32. Agile as a Consultant
• Agile: “Keep iterating until it’s right”
• Consulting: “Tell me how much to
budget and when we’ll be done”
33. Agile as a Consultant
• Agile: “Keep iterating until it’s right”
• Consulting: “Tell me how much to
budget and when we’ll be done”
• Loads of discussion, not used much
in practice
34. Agile as a Consultant
• Agile: “Keep iterating until it’s right”
• Consulting: “Tell me how much to
budget and when we’ll be done”
• Loads of discussion, not used much
in practice
• Massive pressure to bill hours
instead of build process
35. Agile as a Consultant
• Agile: “Keep iterating until it’s right”
• Consulting: “Tell me how much to
budget and when we’ll be done”
• Loads of discussion, not used much
in practice
• Massive pressure to bill hours
instead of build process
• Payoff in the long run
36. Phases
• Project broken down in to
manageable major phases
• Each ~6 weeks - 6 months
• Worked as individual projects, with
eye towards dependencies
• Each phase launch-ready
44. Client Involvement
• Ideally, single point of contact to
serve as project manager
• Client involved with testing and
feedback
• Client directly participates in issue
tracker
48. Dates
• eZ Date datatype: 1970
• Older PHP date functions: 1901 (32-
bit int)
• Communication with Solr for range
functions, etc.
• BlendArchiveDate: drop-in
replacement for eZDate
