Versions Compared

Old Version 2

changes.mady.by.user Former user

Saved on

compared with

New Version 3

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • SAK-14279 Avoid wasteful calls to resolveUuid
  • SAK-14280 Improve efficiency of form handling by caching schemas
  • SAK-14165 Portfolio assembly is slow with many completed Forms
  • SAK-13146 Add custom form as an option on main page of wizard
  • SAK-13719 (IUPUI) Matrix tool / tracking permission changes
  • SAK-14417 Improving the Portfolio User Experience
  • OSP Design and Development
  • SAK-14279 Avoid wasteful calls to resolveUuid. The UUID is now looked up only once, not twice. Should this be merged with 2.5? (UM will be merging it into production this week and will let the community know how it goes.)There were no objections. This is in trunk.
  • SAK-14280 Improve efficiency of form handling by caching schemas. When working with multiple instances of the same form type, the schema is retrieved and deserialized for each form. The StructuredArtifactHome can be cached to avoid the expensive cycles. Since schemas are rarely changed and only through administrative action, they can likely be cached indefinitely. At the least, caching at the thread level helps significantly. No objections. This is in trunk.
  • SAK-14165 Portfolio assembly is slow with many completed Forms. Noah is working on a change to make looking up forms more efficient. Charles Hedrick thinks it makes more sense, both functionally and for efficiency, to only search the user's worksite for forms. Noah will implement change so that by default the behavior is the same (look everywhere for forms), but it will be done more efficiently. Then we can think about Charles Hedrick's approach.SAK-14214 list of users to share can get impractically long; optionally limit users. Charles Hedrick finished this. It allows sites to limit the number of users displayed in the share list if the site has too many users. The limitation is done by role, so that you can list faculty members but not the students. This is controlled by a sakai.properties settingThere are patches attached to the ticket, but they are not going into 2.6. UM will be running the patches in production.
  • SAK-13146 Add custom form as an option on main page of wizard. This is 3/4s done and will be finished for 2.6Chuck Hedrick wasn't on call to discuss his progress.
  • SAK-13719 Matrix tool / tracking permission changes (IU). These changes have only been made to the matrix, not the wizard. This will have to be taken into account when the community decides whether or not to merge the IU branch into trunk. Sean agreed to update the Jira with a screenshot and comments made by Mark BreukerIU will be going live with this next week. Lynn will do a demo sometime afterwards.
  • SAK-13725 patch to enable exposed matrix and exposed wizard in OSP. You canThis isn't just enable it -- there are other bugs that have to be fixed first. Beth has a comment to that effectready for production, so it will not be in 2.6.
  • SAK-1417 Redesign Portfolio User Experience. Beth created this ticket as a place for tracking plans for the Portfolio Tool redesign. It links to Nathan's mockups and also to a page for adding requirements.

New Development for 2.6

  • Screen 1.1: The "Options" column should probably be renamed "Actions"
  • 1.After: We would like to see a mockup of how the screen would look in the case where many portfolios have already been shared with the user. That is a situation in which it is useful to be able to hide some of the portfolios in the list. Also, since there is not always a portfolio outline form, the number of steps is not set. Would it be better to have a TurboTax-like breadcrumb trail at the top that users can click on to go from step to step. How easy would it be technically to have contextual information about the steps? Nathan liked the breadcrumb idea, and pointed out that that moves us towards the "hub" UI model, where you have a central page from which you go off to perform tasks, then come back to the central page. Nathan will mock up a hub interface so we can see what it would be like.1a: Perhaps making the portfolio active or inactive should be an option in the pop-up menu. Under comments, it would be nice to have some way of indicating that unread comments have been added.
  • 1: Approved
  • 2: The question arose whether anyone has large numbers of portfolio templates, which would make this screen unwieldy. Probably not.
  • 3:
    • Does the screen take up too much room once you put the Sakai navigation in?
    • Is the progress indicator misleading, since it would say "Complete" before you are finished with, say, adding all the pages you want. Perhaps it would be better to say "Ready" rather than "Complete".
    • Should the Status section be moved to the Sharing page? This would take up less real estate on this page, but would make the Sharing screen more cluttered.
    • Nathan explained that it is generally a good principle of UX design to allow multiple ways of accomplishing the same important task, which is why he put in tabs as well as links for actions such as "Add/Edit Content".
  • 3a: The question arose of when the Preview button should become available. Nathan thought it should always be there, but show a blank screen with a message like, "No portfolio is ready for previewing".
  • 3b:
  • 4:
  • Screen 2.After: It must be possible to select free-form portfolios. Also, it is often the case that there is only one portfolio template available for a site. Is this page even necessary if there is only one? Can't the single template just be assumed to be the user's selection?

...