uPortal 4 DLM Fragment Manager Interface

Background

Currently, the only way to update fragments in uPortal4 is by editing *.fragment-definition.xml files in the source and running a data import ant target. A graphical interface can make the process faster, easier, and reduce errors.

A UI that can accommodate every possible fragment configuration may not be feasible. Therefore, the goal of the design should be to make most of configurations easy to implement and leave special cases to the current data import process.

See the Jira

UP-3367 - Getting issue details... STATUS

 

Design

The proposed design consists of three screens: the list of fragments, and edit screen, and a create screen.

The list screen, called the Fragment Registry, lists all existing fragments and allows their order of precedence to be changed via drag and drop.

The edit and create screens (essentially the same) allows an administrator to give the fragment a name, set the Owner ID, and specify an audience. The audience is defined by setting an audience type and optionally — in the case of "by group" and "by username" — adding a hierarchical set of rules. ("By profile" may also accept rules, but I don't know what they could be at this time.)

 

Working HTML Mockup

I attached a zip file containing a working HTML mockup of the Fragment Manager: Working HTML Mockup

 

  File Modified

PNG File fragment-create.png 02. Create Fragment

May 17, 2012 by Peter J. Hart

PNG File fragment-editor.png 03. Edit Fragment

May 17, 2012 by Peter J. Hart

PNG File fragment-registry.png 01. List Fragments

May 17, 2012 by Peter J. Hart

ZIP Archive fragment-admin-05-17-2012.zip Working HTML Mockup

May 17, 2012 by Peter J. Hart