240 likes | 307 Views
Generic Interfaces for Managing Web Data. Oleg Burlaca Institute of Mathematics and Computer Science Academy of Sciences of Moldova oburlaca@neonet.md. 61% of companies who have already deployed Web content management software still rely on manual processes to update their sites.
E N D
Generic Interfaces for Managing Web Data Oleg Burlaca Institute of Mathematics and Computer Science Academy of Sciences of Moldova oburlaca@neonet.md
61% of companies who have already deployed Web content management software still rely on manual processes to update their sites. • Users would like: • Smaller and less complex systems • Documentation should provide concrete ideas for how to structure project and make maximum use of features • Scalable user interface: features can be removed/added as required • Better UI for content creation and management of workflow. "Web Content Management: Covering the Essentials, Avoiding Overspending", Jupiter Research 2003, http://www.jupiterresearch.com
Major problems when designing for or implementing content management software • Commercial software too expensive and required too much time to implement • Difficult to integrate with other systems • Determining requirements • Migrating old content • Training authors and editors “The Problems with CMS”, January 2003 The Asilomar Institute for Information Architecture (AIfIA) http://aifia.org/pg/the_problems_with_cms.php
Questions • How to view data from different angles and provide facilities to navigate deep hierarchies ? • How to provide an intuitively clear and convenient way to manage entity multirelations ? • How to tie a generic UI to the application logic ?
What is Content Management ? • A set of tasks and processes for managing content • An emerging field that’s concerned with making information easier to manage and access Information Integrate Automate Access Disseminate The main purpose of a CMS: Enhanced integration and automatization of processes that contribute to efficient dissemination of information on the Internet
Generic User Interfaces Advantages: • Reduced development time • Scalability • No hand coding • Less testing • Consistent look and feel Standardization Less training Disadvantages: • The existence of rules • Additional DB overhead • Ascetic look • Troublesome accomplishment of specific tasks
Web site structure Custom pages Index pages Entity pages (item)
1. Item 2. Item 3. Item XML, TXT Item Page Item data Related Items related item’s shared data shared data private data
What is Information Architecture ? • The structural design of an information space to facilitate task completion and intuitive access to content • The art and science of structuring and classifying web sites and intranets to help people find and manage information Intuition Access Structure Classification Find Manage
Entity type definition • Visual appearance • Database fields and associated editors • Relationship specification • Events
Entity type :: database fields <fields> <f name="thumb" editor="ImgEdit" /> <category caption="Brief" /> <f name="brief_en" editor="Memo" caption="En" height="50" /> <f name="brief_ro" editor="Memo" caption="Ro" height="50" /> <category caption="Perioada" /> <multieditor fixed=“1"/> <f name="date1" caption="Start"><default>NOW()</default> </f> <f name="date2" caption="End"> <default>NOW()</default> </f> <multieditor /> <f name="ora1" editor="Time"> <options format="HourMin" /> </f> </fields>
Entity type :: Relationship Common Attributes <linkage mode="tree" > <fields> <f name="info" caption="info" /> </fields> <types> <tip id="1"> <fields> <f name="info" /> </fields> </tip> <tip id="10"> <fields> <f name="info" /> <f name="active" editor="CheckBox“/> <f name="content" editor="Memo" height="100" /> </fields> </tip> </types> </linkage> Related entity Specific Attributes
UI :: Entity Relations Related items Focused item’s relation attributes
2003 2004 A1 A4 A2 A5 A3 A6 Multiple Relations Articles A2 Related Items (8) Similar Articles A1 A4 References A4 A3 Hidden A5 Similar Articles References
Entity type :: Events <events> <OnCreate> <e type="sql">INSERT INTO site_en_related VALUES ($id, 444, 10, 1) </e> <e type="http"> <params> <url>http://neonet.md/cgi/build.cgi</url> <prms>id=$id</prms> <urgent>0</urgent> <method>get</method> </params> </e> </OnCreate> <OnCloseAfterCreate...> <OnOpen ... > <OnRelateNode ... > </events>
Data Shortcuts Ctrl+Enter: Locate & Focus Item
Toolbars from XML doc Search Window Content Tree Monitoring Error logs Search Results FTP Activity Opened entities and tasks HTTP Activity
Experience www.patria.md www.tehnomarket.md www.e-democracy.md www.monument.md russiannet.org www.press.mednet.md www.stats.mednet.md www.csa.acad.md www.pll.md www.profitclub.md http://baraka.neonet.md
Conclusions • Develop primitive UI elements but not complex, customized interfaces • Provide context to manage content • Use well established interface patterns Questions • How to manage n-ary relations ?
WWW FTP DB Content Management System developer’s view Manage HTML Templates Monitoring Log Files Manage Scripts GUI to data Executing raw SQL queries Backup / Restore Get Size & Upload Images Upload documents(pdf,doc) Basic download support
Content Management System user’s view html pdf, xls email templates