1 / 30

Managing Content in uPortal

Managing Content in uPortal. Susan Bramhall Yale University ITS Technology and Planning. Who am I?. Yale University Portal Implementer Occasional contributor to uPortal Early adopter of Distributed Layout Manager Grandmother. What Will I cover?. The layout manager’s job

henry-bernard
Télécharger la présentation

Managing Content in uPortal

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Managing Content in uPortal Susan Bramhall Yale University ITS Technology and Planning

  2. Who am I? • Yale University Portal Implementer • Occasional contributor to uPortal • Early adopter of Distributed Layout Manager • Grandmother

  3. What Will I cover? • The layout manager’s job • An overview of uPortal layout managers • Distributed Layout Manager basics • Introduction to uPortal users and groups • How to create layout fragments • How user content changes and managed content changes interact

  4. What does the user see? • We want to • Push content to users based on who they are • But, allow users to choose what they see • How? • By working with the layout manager

  5. folder type=“root” folder (tab) folder (tab) folder (tab) folder (column) folder (column) folder (column) folder (column) folder (column) channel channel channel channel channel channel channel The Layout An xml tree of generic folders and channels

  6. The Layout Manager’s Job To direct the show the Layout Manager must • Know where to start • Have rules to follow to include the right content and exclude everything else • And where each segment goes

  7. Of Fragments and Templates • A template is a starting point for personal layout • A fragment is a living segment of pushed content

  8. Publish, Subscribe, , Pull • Publishing is what an administrator does • Subscribing is what a user does • Administrators can also PUSH content • Pull = Subscribe

  9. Concepts • Fragments and Templates • Publish and Subscribe • Push and Pull • Audience • Precedence and Restrictions

  10. Which Layout Manager? • Simple Layout Manager (SLM) • uPortal 1.0 to present • Aggregated Layout Manager (ALM) • uPortal 2.0 to present • Distributed Layout Manager (DLM) • uPortal 2.5 to present

  11. Simple Layout Manager • uPortal 1.0 – 2.5 but no longer default • Based on completely templates • Allows personal layout for each user • But personalized layout is a copy • New content in template is lost on users who have customized

  12. SLM Example:

  13. Aggregated Layout Manager • uPortal 2.0 – now • Will NOT be the future default • Based on fragments (think tab) and templates • Can push fragments • Can subscribe to whole fragments • Allows personal layout for each user but fragments are read only

  14. ALM as Distributed:

  15. ALM major overhaul:

  16. Distributed Layout Manager • Default in uPortal 2.6 • Templates and Fragments • Fragments can be modified • Cannot subscribe to a fragment (yet) • Allows personal layout for each user and user changes are merged with changes to fragments

  17. DLM as it appears in uPortal Head

  18. Steps to Pushing DLM Fragment • Define the fragment in dlm.xml • Login as the fragment owner and set up the layout

  19. Define the Fragments • dlm.xml configuration • Each Fragment definition includes • An owner • Precedence • Audience

  20. Audience • Everyone needs the right audience! • Built-in evaluators • Extensible API • Boolean expressions

  21. What do we know about the user?

  22. Defining the audience Built in Audience Evaluators • GuestUserEvaluatorFactory • AllUsersEvaluatorFactory • GroupMembershipEvaluatorFactory • PersonEvaluatorFactory

  23. User Attributes • IPerson is the basic user object • Attributes come from jdbc or ldap • Or any other source you invent

  24. PersonDirectory.xml • API allows extension • Spring configurable beans • CachingPersonAttributeDaoImpl • MergingPersonAttributeDaoImpl • JdbcPersonAttributeDaoImpl • LdapPersonAttributeDaoImpl

  25. PersonEvaluator Audience • Tabs based on Person attributes • PersonDirectory Flexibility

  26. compositeGroupServices.xml • Starts with Local groups from uPortal database • Includes comments for • LDAP group service (beware) • File System group service • Person Attribute Group service (PAGS)

  27. GroupMembershipEvaluator Audience • Tabs based on Group

  28. Precedence and Restrictions • Administrator sets parameters • User works within boundaries • End result is pushed content merged with personal changes

  29. Create the Fragment Content • dlm.xml is complete • Login as fragment owner • Use preferences channel to create content for the fragment • Header and footer will be removed and other content will become the fragment

  30. Practical DLM See DLM Administrators Guide at http://www.ja-sig.org/wiki/x/pjQ • Experiment in the quickstart… • Login as news-lo/news-lo. See preferences. • Login as student / student. See changes. • Go to preferences, see merging personal changes with pushed fragment

More Related