Overview of today's meetup.

[Richard Esplin]

Thank you for those who attended today's meetup both in person and online. I am sorry for the confusion around the start time and the late start of the meeting, but I enjoyed the presentation and learned some good stuff. As usual, the conversation was both fun and useful.

Below are my brief notes from the session. If anyone has any corrections or additional insights, feel free to respond.

Richard

----
A few items of business:
* We will only meet twice a year, instead of every quarter.
* Our next meetup will be January 25 at 11AM, hosted again by Eric's team at the LDS Church Riverton Office. Kyle Shepherdson from the BYU team will be presenting on how they use Alfresco.
* Congratulations Craig for landing a position at PWC. We hope to continue to see you around Alfresco events even after you move.
* Todays presentation was by Ben Steckler, who works with Tyler on the LDS ICS Event Central team.

Notes from today's presentation
* They handle translation into 96 languages.
* They are 2 years into project.
* They have Alfresco in production.
* Alfresco handles workflow, version control, meta-data tracking, and provides glue between a lot of different components (multiple services, multiple UI's).
* Content added to Alfresco via email to SMTP aliases which trigger content rules.
* Content rules call .NET scripts to do text cleanup.
* Most authoring is done in Word, and converted to XML, then the Word doc is sent to translation services.
* Alfresco calls a script that uses a Java OpenXML / Word Processing ML library to extract text and insert it into their XML skeleton.
* When the Word doc comes back from translation services, it is used to converted again to XML.
* Uses Maven for builds.

For the April 2012 Conference:
* Processed 1,600 files in 4 days.
* 65 languages total.
* 35 languages available within 30 days.
* Mobile apps updated within 24 hours with corrected pre-event / post-event files for 41 out of 44 talks, all talks within 36 hours.
* Previously it took more than 5 days.

Customizations:
* Some dashlets, such as an unassigned files list that needs review. Triggers off of a property.
* 2 custom forms with preview with specific metadata for the task at hand.
* Metadata around events come in via an XML file from a separate event planning system.
* Webscripts to return the same information (items needing to be reviewed) to external web services.
* Integration between Xopus and Alfresco--Xopus save content into Alfresco.
* External process monitors the Alfresco audit log and pushes content to MarkLogic and other destinations. Evaluating publication service, but likely to keep what they are doing now.

Needs:
* They feel a little blind about the assets in Alfresco and how to see them better.

Insights:
* For their team's use case, they are avoiding using Alfresco as a development platform and instead using it as a contained repo like a database. If it could be argued that piece of logic would make a good stored procedure in a database, then it would probably make a good web script.
* Alfresco serves as the glue between a lot of different services.