140 likes | 237 Views
Publish and be Damned:. Jeremy Speller & Ian Bartlett UCL. Re-purposing in the real world. Introduction. About UCL The original University of London (1826) 20,000 students 6,000 staff 72 Departments About us Web Services Educational Liaison. About this talk. The Project Why…
E N D
Publish and be Damned: Jeremy Speller & Ian Bartlett UCL Re-purposing in the real world IWMW 7 July 2005
Introduction • About UCL • The original University of London (1826) • 20,000 students • 6,000 staff • 72 Departments • About us • Web Services • Educational Liaison IWMW 7 July 2005
About this talk • The Project • Why… • Who owns the processes? • The problems • Cultural / Technical • The solutions • Cultural / Technical • Measuring success • Where next? • Interaction IWMW 7 July 2005
The Project • The Holy Grail - seamless re-purposing • This means: • Ability to share a data source in real time • No cutting and pasting • No “final solutions” • Leading to: • Consistency • Accuracy • Economy • Pilot • Start small (low budget, low-key methods) but with generic approach • Test-bed for blending technologies • Study Abroad Guide • Annual production cycle • compact, relatively stand-alone project • ideal for proving concept IWMW 7 July 2005
Why… • Educational Liaison (EL) responsible for student recruitment process from initial contact through to arrival at UCL. Produces all UCL’s main student recruitment publications. Content of these is sourced from academic departments and audited by EL staff. Re-purposing should: • Aid consistency of information • don’t want inconsistent information appearing in web and print; students use both media • Improve accuracy of information • Printed text is fully audited; this allows re-use of fully audited text • Improve efficiency of process • Avoid repetitive copying, pasting and re-editing of text from print (Quark) files. IWMW 7 July 2005
Who owns the processes? • "UCL" itself (Educational Liaison - Student Recruitment Publications & Web Office) • Committee for the Recruitment of Students • Departments (authoring their own entries) • Development & Corporate Communications and Design Agency (the look and “voice”) • Web Services (the Web look and CMS) • Information Systems (networks, MySQL) • Management Systems (SITS, Oracle) IWMW 7 July 2005
The Problems: Cultural • Resistance to changing long-standing, proven processes • Lack of resource for training and implementation • Culture change needed to effect change from paper to electronic working, particularly in academic departments • Re-skilling IWMW 7 July 2005
The Problems: Technical • Multi-platform, multi-application process • Quark, Zope CMS, MySQL, Oracle • Windows, Mac OSX, Linux, Unix • Multi skill-base • Differing text needs for print and web • See page 10 / See <link> • Fixed spaces / Open spaces • Many attempts in the past to pass data through to Quark from databases/Word but these have the limitation of "final solutions" with no dynamism on the Quark side IWMW 7 July 2005
The Solutions: Cultural • Devise workflow that ensures essential processes are included • Use pilot project to prove concept and identify problems; training can be carried out after this ahead of next project • Initial data input to be carried out in-house by Educational Liaison staff – flow in from existing Quark document • Change to electronic working an ongoing issue for UCL, but currently undergoing a major change withswitch to use of SITS for admissions and module maintenance. • Most staff happy to re-skill as long as timeallowed IWMW 7 July 2005
The Solutions: Technical considerations • Open architecture / open source where possible • Straightforward and transparent for users • We understand CMS/Apache/MySQL/Oracle but have no experience of integrating Quark with backend data so it was important to establish feasibility first on the basis that the rest could be sorted out to fit. IWMW 7 July 2005
The Solutions: Technical approach • Finding Quark solution: • Programmer • Quark • Xcatalog Pro • LinkUP! Enterprise • Prototype data structure (MySQL) • Develop Quark ODBC experience • Production data structure (Oracle) • Rolling annual updates • Build public interface • Build browser-based author interface IWMW 7 July 2005
Measuring success • The Demo • Success criteria • Do we have a dynamically linked Study Abroad Guide? • Can we re-purpose data? • Is it really more efficient? • Can we update via one interface to appear elsewhere? • Can users tell the difference? • Does anyone complain? IWMW 7 July 2005
Where next? • Major publications • prospectuses • departmental booklets • scholarships information • accommodation information etc. • SITS – use module and programme records for publishing in print and web • Content Management System roll-out • Do you really need that office space; wireless PDA IWMW 7 July 2005
Interaction • Questions • Review Wiki comments IWMW 7 July 2005