SAGE Online Content Repository: Six Years with RSuite
•
2 gefällt mir•1,155 views
In this session Keith Lawrenz, Sr. Business Analyst will discuss how RSuite has helped transform their business over the past six years. As an early adopter, SAGE initially implemented RSuite for their journals content. Today both journal and eBook content are managed in this "lights out" system to aggregate and distribute content in a fully automated process. (Original date of presentation: May 28, 2014)
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Mehr von SAGE Publishing
Mehr von SAGE Publishing (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (16)
SAGE Online Content Repository: Six Years with RSuite
- 1. Los Angeles | London | New Delhi Singapore | Washington DC May 28, 2014 SAGE Online Content Repository Six Years with RSuite
- 2. 2014 RSuite User Conference Los Angeles | London | New Delhi Singapore | Washington DC Keith Lawrenz Senior Business Analyst & Content Systems Supervisor, Publishing Technologies, SAGE Publications • 8 years with SAGE • 23 years with Kinko’s • Electrical and Computer Engineer
- 3. 2014 RSuite User Conference Los Angeles | London | New Delhi Singapore | Washington DC SAGE Publications ● Independent, global, scholarly publisher ● Books, journals, reference, primary sources
- 4. 2014 RSuite User Conference Los Angeles | London | New Delhi Singapore | Washington DC Back to 2007…
- 5. 2014 RSuite User Conference Los Angeles | London | New Delhi Singapore | Washington DC Platforms…
- 6. 2014 RSuite User Conference Los Angeles | London | New Delhi Singapore | Washington DC
- 7. 2014 RSuite User Conference Los Angeles | London | New Delhi Singapore | Washington DC Content management…
- 8. 2014 RSuite User Conference Los Angeles | London | New Delhi Singapore | Washington DC PDF Conversion to XML Load to Staging Editorial Review Edits ~ 45 days 2.2 deliveries ~ $10 / article
- 9. 2014 RSuite User Conference Los Angeles | London | New Delhi Singapore | Washington DC
- 10. 2014 RSuite User Conference Los Angeles | London | New Delhi Singapore | Washington DC XML Conversion Vendor(Jouve) OnlineContent Editor Content Recepients SOCR Journal Production Unit of Content is a Journal Issue Start FTP (UK) or NFS (US) Zip Final Print-Ready PDFs Ingest Unencoded Issue Store in Repository Deliver Unencoded Issue FTP Create SAGEMeta XML Nomalize PDF Files Zip Issue FTP Store in Repository Deliver HW Issue Ingest Encoded Issue FTP – HighWire Express Process Issue for Hosting Quality Check Issue Changes? Edit Articles Approve Issue Deliver Full Issue Deliver PubMed Abstract XML FTP and/or NFS sites Online Preview Issue Online Issue Online? End Deliver XML Issue End Yes Yes OK to Host? Yes
- 11. 2014 RSuite User Conference Los Angeles | London | New Delhi Singapore | Washington DC XML Conversion Vendor(Jouve) OnlineContent Editor Content Recepients SOCR Journal Production Unit of Content is a Journal Issue Start FTP (UK) or NFS (US) Zip Final Print-Ready PDFs Ingest Unencoded Issue Store in Repository Deliver Unencoded Issue FTP Create SAGEMeta XML Nomalize PDF Files Zip Issue FTP Store in Repository Deliver HW Issue Ingest Encoded Issue FTP – HighWire Express Process Issue for Hosting Quality Check Issue Changes? Edit Articles Approve Issue Deliver Full Issue Deliver PubMed Abstract XML FTP and/or NFS sites Online Preview Issue Online Issue Online? End Deliver XML Issue End Yes Yes OK to Host? Yes Ingest print-ready article PDFS
- 12. 2014 RSuite User Conference Los Angeles | London | New Delhi Singapore | Washington DC XML Conversion Vendor(Jouve) OnlineContent Editor Content Recepients SOCR Journal Production Unit of Content is a Journal Issue Start FTP (UK) or NFS (US) Zip Final Print-Ready PDFs Ingest Unencoded Issue Store in Repository Deliver Unencoded Issue FTP Create SAGEMeta XML Nomalize PDF Files Zip Issue FTP Store in Repository Deliver HW Issue Ingest Encoded Issue FTP – HighWire Express Process Issue for Hosting Quality Check Issue Changes? Edit Articles Approve Issue Deliver Full Issue Deliver PubMed Abstract XML FTP and/or NFS sites Online Preview Issue Online Issue Online? End Deliver XML Issue End Yes Yes OK to Host? Yes Deliver to encoding vendor
- 13. 2014 RSuite User Conference Los Angeles | London | New Delhi Singapore | Washington DC XML Conversion Vendor(Jouve) OnlineContent Editor Content Recepients SOCR Journal Production Unit of Content is a Journal Issue Start FTP (UK) or NFS (US) Zip Final Print-Ready PDFs Ingest Unencoded Issue Store in Repository Deliver Unencoded Issue FTP Create SAGEMeta XML Nomalize PDF Files Zip Issue FTP Store in Repository Deliver HW Issue Ingest Encoded Issue FTP – HighWire Express Process Issue for Hosting Quality Check Issue Changes? Edit Articles Approve Issue Deliver Full Issue Deliver PubMed Abstract XML FTP and/or NFS sites Online Preview Issue Online Issue Online? End Deliver XML Issue End Yes Yes OK to Host? Yes Ingest xml encoded issue
- 14. 2014 RSuite User Conference Los Angeles | London | New Delhi Singapore | Washington DC XML Conversion Vendor(Jouve) OnlineContent Editor Content Recepients SOCR Journal Production Unit of Content is a Journal Issue Start FTP (UK) or NFS (US) Zip Final Print-Ready PDFs Ingest Unencoded Issue Store in Repository Deliver Unencoded Issue FTP Create SAGEMeta XML Nomalize PDF Files Zip Issue FTP Store in Repository Deliver HW Issue Ingest Encoded Issue FTP – HighWire Express Process Issue for Hosting Quality Check Issue Changes? Edit Articles Approve Issue Deliver Full Issue Deliver PubMed Abstract XML FTP and/or NFS sites Online Preview Issue Online Issue Online? End Deliver XML Issue End Yes Yes OK to Host? Yes Deliver to hosting platform
- 15. 2014 RSuite User Conference Los Angeles | London | New Delhi Singapore | Washington DC XML Conversion Vendor(Jouve) OnlineContent Editor Content Recepients SOCR Journal Production Unit of Content is a Journal Issue Start FTP (UK) or NFS (US) Zip Final Print-Ready PDFs Ingest Unencoded Issue Store in Repository Deliver Unencoded Issue FTP Create SAGEMeta XML Nomalize PDF Files Zip Issue FTP Store in Repository Deliver HW Issue Ingest Encoded Issue FTP – HighWire Express Process Issue for Hosting Quality Check Issue Changes? Edit Articles Approve Issue Deliver Full Issue Deliver PubMed Abstract XML FTP and/or NFS sites Online Preview Issue Online Issue Online? End Deliver XML Issue End Yes Yes OK to Host? Yes Support editorial approval process
- 16. 2014 RSuite User Conference Los Angeles | London | New Delhi Singapore | Washington DC XML Conversion Vendor(Jouve) OnlineContent Editor Content Recepients SOCR Journal Production Unit of Content is a Journal Issue Start FTP (UK) or NFS (US) Zip Final Print-Ready PDFs Ingest Unencoded Issue Store in Repository Deliver Unencoded Issue FTP Create SAGEMeta XML Nomalize PDF Files Zip Issue FTP Store in Repository Deliver HW Issue Ingest Encoded Issue FTP – HighWire Express Process Issue for Hosting Quality Check Issue Changes? Edit Articles Approve Issue Deliver Full Issue Deliver PubMed Abstract XML FTP and/or NFS sites Online Preview Issue Online Issue Online? End Deliver XML Issue End Yes Yes OK to Host? Yes Track go-live on hosting platform
- 17. 2014 RSuite User Conference Los Angeles | London | New Delhi Singapore | Washington DC XML Conversion Vendor(Jouve) OnlineContent Editor Content Recepients SOCR Journal Production Unit of Content is a Journal Issue Start FTP (UK) or NFS (US) Zip Final Print-Ready PDFs Ingest Unencoded Issue Store in Repository Deliver Unencoded Issue FTP Create SAGEMeta XML Nomalize PDF Files Zip Issue FTP Store in Repository Deliver HW Issue Ingest Encoded Issue FTP – HighWire Express Process Issue for Hosting Quality Check Issue Changes? Edit Articles Approve Issue Deliver Full Issue Deliver PubMed Abstract XML FTP and/or NFS sites Online Preview Issue Online Issue Online? End Deliver XML Issue End Yes Yes OK to Host? Yes Deliver to additional recepients
- 18. 2014 RSuite User Conference Los Angeles | London | New Delhi Singapore | Washington DC Learnings
- 19. 2014 RSuite User Conference Los Angeles | London | New Delhi Singapore | Washington DC Learnings
- 20. 2014 RSuite User Conference Los Angeles | London | New Delhi Singapore | Washington DC 2011 we released SOCR-2 Ingest Store Deliver Enforce quality Normalize content Enforce quality Version control Transform (PDF, XML, & Images) Package Deliver (and track) Analytics
- 21. 2014 RSuite User Conference Los Angeles | London | New Delhi Singapore | Washington DC Capabilities Store Transform DeliverEnrich Ingest
- 22. 2014 RSuite User Conference Los Angeles | London | New Delhi Singapore | Washington DC SOCR-Journals Ingest • Issues, OnlineFirst, Continuous Publication, Launch & Archive • Over 200 quality checks for a current article Deliver • 47 delivery recipients • 13 delivery formats in use • Batch delivery for launch content
- 23. 2014 RSuite User Conference Los Angeles | London | New Delhi Singapore | Washington DC - 200,000 400,000 600,000 800,000 1,000,000 1,200,000 1,400,000 Articles
- 24. 2014 RSuite User Conference Los Angeles | London | New Delhi Singapore | Washington DC Load to Staging Editorial Review Edits 45 days down to ~ -5 days 2.2 down to 1.2 deliveries $10 / article down to ~ $1
- 25. 2014 RSuite User Conference Los Angeles | London | New Delhi Singapore | Washington DC
- 26. 2014 RSuite User Conference Los Angeles | London | New Delhi Singapore | Washington DC SOCR-Books Ingest • Books - TEI • Implemented RelaxNG schema validation • Over 100 quality checks applied Deliver • Platform content • Discoverability and content licensees • Interactive DOI Registration
- 27. 2014 RSuite User Conference Los Angeles | London | New Delhi Singapore | Washington DC 0 1000 2000 3000 4000 5000 6000 Books
- 28. 2014 RSuite User Conference Los Angeles | London | New Delhi Singapore | Washington DC
- 29. 2014 RSuite User Conference Los Angeles | London | New Delhi Singapore | Washington DC Learnings X
- 30. 2014 RSuite User Conference Los Angeles | London | New Delhi Singapore | Washington DC Learnings People Process Software
- 31. 2014 RSuite User Conference Los Angeles | London | New Delhi Singapore | Washington DC SOCR-3 – SOCR As A Service
- 32. 2014 RSuite User Conference Los Angeles | London | New Delhi Singapore | Washington DC Learnings
- 33. 2014 RSuite User Conference Los Angeles | London | New Delhi Singapore | Washington DC Questions? Keith Lawrenz Sr. Business Analyst & Content Systems Supervisor Publishing Technologies SAGE Publications keith.lawrenz@sagepub.com twitter: @keithlawrenz
Hinweis der Redaktion
- Ok, so just some quick facts about SAGE, as a foundation for my talk. Sage is a nearly 50-year old global, independent scholarly publisher with editorial offices in the Los Angeles, Washington DC, London, New Delhi and Singapore. We publish around 800 new print and digital books annually – primarily textbooks and a journal publishing program with over 900 titles. We have a number of imprints and subsidiaries {CLK #1} such as Corwin, CQ Press, Adam Matthew and most recently MD Conference Express. {CLK#2} We publish online through an ever-growing list of content platforms.
- Thinking back to 2007… The Sopranos ended The final Harry Potter book was published President Bush was facing Barack Obama for the presidency And Barry Bonds beat Hank Aarons home run record (but that didn’t quite work out…)
- In 2007… SAGE published around 300 journals OnlineFirst was supported for 2-3 journals Back file fill to Volume 1, Issue 1 was the big idea Publishing Technologies was focused on refreshing the SJO platform to support the transition of our “collections” product line from CSA
- SAGE also introduced our first online reference platform, SAGE eReference, with 45 titles
- Our content management practices were pretty manual Maybe 10,000 zip files Each containing an issue made up of XML and PDF “pairs” Stored on disks This presented many challenges: Sales and marketing wanted a count of articles to support pricing decisions. A simple ad hoc content delivery took days of effort and consistent, reliable scheduled deliveries were at best hit and miss There was certainly no thought of reconciling our internal archive with our hosted content The content inside the zips stayed inside the zips – with no thought of mining trends in our journal content stream
- The online journal workflow took the PDF from the typesetter, sending it out for conversion in India – 10 days after it was released to the printer Those XML and PDF zips were returned from India maybe 10 days later. The content was loaded to HighWire and went through an editorial review process Sometimes we made the edits in-house and other times we sent the content back to India. This was what we call header-footer encoding. For most journals, the online product included title, authors, abstracts and encoded references. A select group of journals were hosted in full html, or full-text. On average – {click – click – click} 45 days from the print distribution 2.2 deliveries to HighWire – so every issue went through multiple editorial views Hard conversion costs were roughly $10/article
- In late 2008 we released the first generation SOCR after18 months of development
- The initial implementation was solely focused on the online journal issue production process. - Basically the system did one thing – pretty well…
- This initial solution was delivered through two ingestion workflows, one status checking workflow and four delivery workflows plus about 3-4 additional worflows to support the full-text processing. The solution was barely performant for the current content production. The journals business wanted to grow – fast – and we had collected around 40 – 50,000 additional zips that represented back content. They needed all of the content in a secure accessible platform. Oh yeah, by the way, the online books business was building - adding titles to SAGE eReference - experimenting with eBooks - thinking about new online book opportunities.
- Don’t try to boil the ocean – we did too much and it took too long Minimum viable product
- Content architecture matters – the system was slow… because we did not optimize our metadata against our queries MarkLogic and RSuite were “young”
- On ingestion - we implemented a common journals workflow – transitioning to NLM - we implemented Schematron for many of the checks that were previously implemented as custom workflow steps On edit we also implemented the Schematron checking – ensuring quality On delivery we implemented custom delivery formats using a configurable delivery specification. We benchmarked system performance using a representative set of 100 journal issues and we achieved a over 400% increase in performance.
- A virtuous cycle
- The online is up – on average – 5 days prior to the print release. This is a 50 day improvement in making content accessible to the reader. We have reduced average deliveries to HighWire from 2.2 to 1.2 and negotiated a low six figure savings in hard production costs. In addition, the SOCR automation of launch content loading is expected to save SAGE another low-six figures in 2014. Finally, the standardization on NLM, and training our Typesetters to deliver XML directly to SOCR has reduced hard cost per article from around $10 to $1. All of these benefits are not just due to SOCR – but they are enabled by SOCR. The extensible Schematron error checking is the largest single factor
- The business continues to move faster – today we have - 1.2 million articles – issues, onlineFirst, continuous publication in 2 varieties to support new Open access publishing models SAGE Research Methods – launched with around 300 titles including books, journals and videos growing to over 600 tiles plus extensive “born digital” content SAGE Knowledge – launched with 2,500 titles and has been adding
- We released SOCR books in early 2012. Our TEI encoded book content required us to implement RelaxNG schema validation into Rsuite. Using the same model as we have for journals allowed us to develop this capability in around 3 months concurrently with other projects Most recently, Sal implemented automated DOI registration workflows that communicate directly with the CrossRef REST service to transmit and confirm DOI registrations 14,000 DOIs were automatically deposited in around 10 days when we turned this on.
- Just over 5000 titles ingested since April of last year. The hardest thing with ingesting the book content is that the Schematron rules are catching errors we missed when loading the content directly. With 5000 titles we can easily ingest and reload the content on our host platform, thereby improving the content quality delivered to our subscribers.
- Probably the most exciting recent enhancement is the implementation of what we call HubXML for encoding book content. Implemented in weeks, not months, we can ingest this new content type and deliver to either TEI for our SAGE Knowledge or Research Methods, or go to ePub (2 and 3) for our eBook distribution through Core Source. SOCR is now nimble and adaptable and for possibly the first time we are almost ahead of the business. The systems was in place to accept HubXML book number 5. We are ready to ramp this capability to all new books by year end. Once again saving near 6 figures in conversion costs to either ePub or TEI.
- Early adoption is very hard And adopting others best practices is a much better idea
- Great software is not enough. Having the right people on the team is key to success. John and Sal, With SAGE take the lead in working with Elver and Daniel, RSI development resources in Columbia. The critical skill sets are building CMSs, Marklogic Xquery and JAVA. We have a small but very effective team building and maintaining SOCR But another key portion of our recent success happened around a year ago. We focused on solid development methodology. - Build documentation using Confluence - We brought our job ticketing solution in-house with JIRA - We also brought our code repository in house and spent countless hours reconciling our code that had been left behind by many previous developers - Possibly most importantly we built automated code deployment process with Jenkins 2 years ago we avoided deployments, because deploying new code too often broke something, and without a solid code repository, documentation, and repeatable deployment process finding the cause was often a struggle. The remaining piece here that we need to work on is automated system testing. Automated end to end system testing processes has so far eluded us. But we know we want it. The current challenge is to complete a major overhaul and upgrade.
- We call the next generation SOCR-3 Upgrading to RSuite 4 – we have a prototype instance running today with test content. The plan is to deliver a fully operational system by year-end. A REST validation service that will deliver all necessary validations checks through Schematron rule sets and related services to deliver Schema, PDF and image validations. One service call will be used for any content type. And this service will be accessible to internal workflows and upstream production systems. The packaging service takes advantage of the power of MarkLogic to deliver content from Rsuite. Image transform service will give us RESTful access to Apogo PDF enhancer to reformat PDFs and ImageMajik to perform image manipulations. Ingestion, Dispatch, and metadata will be thin wrappers around existing RSuite functionality. But this will position us for future enhancements and scaling. Event logging and Reporting will initially be focused on handling transactional logging and reporting.
- A CMS is not a project. It must be a log term program that must integrates with most everything you do. To be successful, you need a knowledgeable, dedicated team that can be focused on making your CMS effective.