[ https://issues.apache.org/jira/browse/COCOON-1884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Savory closed COCOON-1884. --------------------------------- Resolution: Fixed Added to Daisy. > [Link] Encyclopedia of Life Sciences (Wiley InterScience) > --------------------------------------------------------- > > Key: COCOON-1884 > URL: https://issues.apache.org/jira/browse/COCOON-1884 > Project: Cocoon > Issue Type: Improvement > Components: - Documentation > Affects Versions: 2.1.8 > Reporter: Ellis Pritchard > > URL of the website: http://www.mrw.interscience.wiley.com/emrw/047001590X/home > Title of the website: Encyclopedia of Life Sciences - Wiley InterScience > Cocoon version used: 2.1.8 (with AJAX module and some patches from 2.1.9) > Short summary: Major Reference work in Wiley InterScience, first of many to > be published using Cocoon-based architecture. > How can we verify this site is actually built with Cocoon? Check out the > X-Cocoon-Version header... > - How much time did it take to build the site from design to publication? > Original IA Specification in October 2005, specs for source XML took > approximately 2 months, actual build 3 months; 3 Cocoon-based engineers, 1 > focusing on search, 1 on XHTML/CSS, and one on the rest of the site. We also > had some hard-working Content people working on pre-rendering of XML blobs > and MathML images, and a whole bunch of people in India marking up the XML > content documents. > - How much traffic does the site handle? > 20000 hits on launch day (24 July 2006). > - What made you choose Cocoon to build the site? > 6 month review of available technologies, Cocoon stood out on handling of > XML, Caching, Component re-use and the Sitemap. We also love Views and the > concept of Flows. > - What other information do you want to disclose (e.g. how does it work, how > did > you build it, what parts of Cocoon did you use)? > We've actually got some other parts of the site already implemented using > Cocoon, namely ForwardLinking (Citation-Tracking link on Journal Abstract > pages: Crossref web-service based), Author Services (production process > tracking for authors: uses web-services and FlowScript), plus our (yet to be > launched) RSS and OPML feeds, and will be moving forward with the rest of > InterScience along-side a back-end re-architecture. > We've been able to re-use a number of components from the other Cocoon > projects already, and the bulk of Cocoon work for this site has been XSL and > Sitemap wrangling, rather than application-specific Java code. > We wrote our own Generators and Transformers for DB access and Search > integration (we use back-end CORBA repositories and custom DOA for DB access, > and a legacy Verity engine for search), plus some generic transformers for > SAX manipulation, e.g. pulling single nodes for our AJAX based topic-tree out > of a huge source document. However, the bulk of the functionality is XSLT > based, using a file-system store (i.e. exactly the kind of thing Cocoon was > designed for), preferring Inclusion to Aggregation in most cases. > Access control is not implemented using Cocoon simply due to an existing > available web-server plugin, although we use a Cocoon-based 'Action' for > access control in other parts of the site. > Cocoon has vastly improved our abilty to deliver feature-rich sites on-time > and on-cost, plus, its fun! > - Can you provide a contact email address if people want further information? > [EMAIL PROTECTED] -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.