Academic Websites in Plone

652 views
574 views

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
652
On SlideShare
0
From Embeds
0
Number of Embeds
58
Actions
Shares
0
Downloads
4
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Academic Websites in Plone

  1. 1. Academic Websites in Plone Sally Kleinfeldt Plone Symposium Midwest 5 June 2013
  2. 2. Why Plone? Fundamentals • Secure • Accessible (Section 508) • Scalable (users, pages) • User friendly editing • Flexible, granular permission system (global and local roles) • LDAP/Active Directory integration
  3. 3. Why Plone? Theming • Give the site a custom look and feel • Plone 4.3: TTW Diazo theming • HTML/CSS development only • No Python required
  4. 4. Why Plone? Custom Types • Give the site custom behavior • Plone 4.3: TTW Dexterity content types • Add plone.app.workflowmanager for business process automation • Also uwosh.northstar, uwosh.pfg.d2c
  5. 5. Why Plone? Subsites • Manage many sites (departments, schools) together • Lineage (collective.lineage) - see Notre Dame presentation tomorrow • Also ftw.subsite, or a lightweight site customization
  6. 6. Why Plone? Fundraising, CRM • Salesforce.com integration suite • collective.salesforce.fundraising - see Nonprofit Fundraising presentation tomorrow • Work is beginning on a new message queue based Salesforce integration - come to the BOF!
  7. 7. Why Plone? Calendaring • Lots of calendaring tools are available • Built in events, calendar • Solegma.fullcalendar • uwosh.timeslot • SignupSheet
  8. 8. Why Plone? LIMS • Laboratory Information Management System • Roles and workflows tailored for labs • Bika LIMS
  9. 9. Why Plone? Online Exhibits • Multi-section exhibits from Plone content • collective.exhibit
  10. 10. Why Plone? 2 Venerable Add-ons • Faculty/Staff Directory • CMF Bibliography AT
  11. 11. Faculty/Staff Directory • Personnel directories tailored for educational institutions • Integrates with Plone users and groups (Membrane) • Created in 2007, current version 3.1.3 • Widely used, actively maintained
  12. 12. Faculty/Staff Directory • Tightly coupled to an academic organizational model • Classification (Staff/Faculty/Student) • Department • Committee • All are AT content types
  13. 13. Faculty/Staff Directory • Honed for use in educational institutions • Inflexible, difficult to adapt to other membership situations • People cannot have different roles within a group (committee chair, member)
  14. 14. Faculty/Staff Directory • Work is beginning on a new membership add-on, provisional name Roster • Keeps membership separate from committee, department, etc. objects • Captures metadata about the user’s membership in a group • David Glick can tell you more!
  15. 15. Faculty/Staff Directory • What is the future of FSD? • Feature complete for the niche it occupies • Tweaks, bug fixes - yes • Dexterity rewrite? not likely...
  16. 16. CMF Bibliography AT • Create and manage bibliographic references • Provides 16 different types of references as AT content types • Schema follows BibTeX - LaTeX’s reference management system • Supports numerous import and export formats and easy to add new ones
  17. 17. CMF Bibliography AT • Widely used, invaluable on academic sites • Created in 2005, current version 1.1.2 • Has not changed in 2 years • Big, complicated code base - includes a CMF layer
  18. 18. CMF Bibliography AT • Cautionary notes when importing large numbers of references: • Many keywords (tags) will make editing impossible due to bug in keyword widget • Many references in one bibliography folder will clobber the nav portlet - hide them from nav
  19. 19. CMF Bibliography AT • What is the future of CMFBibliography? • Feature complete for the niche it occupies • Tweaks, bug fixes - yes • Dexterity rewrite? not likely... • If the CMF layer is removed, many academic sites will be prevented from upgrading...
  20. 20. Discussion?

×