In Depth Notes on pages below
Monitoring and LoggingJMX capabilities of uP 3, Logging Evaluate Yale Customizations
CleanupDatabase Migration
High Avail infrastructure |
New UI / UE design options.Yale Resources (victor and Pat) creating wire frames Work with Unicon to create skin / theme / xsl
High Avail infrastructure
Clean up
|
Victor)| Upgrade Status | Jira Key | Summary | Description |
|---|---|---|---|
| included | YIP-294 | Improve Logging Practices [uPortal 3.x] | The current logging for YaleInfo and catalina.out contains tons of unnecessary items. We need to better manage our logs so that we can identify errors more quickly in the portal. |
| included | YIP-265 | Improve operational monitoring for portal and portlets [Charter] | Need to be able to monitor the "health" of the portal and portlets better. JMX was discussed as a possibility. |
| included | YIP-263 | Clean up YaleInfo Database [uPortal 3.x] | uPortal 3 should help but we need to clean up a lot of database information. Begin with understanding what needs to be removed, prior to uPortal 3.x upgrade. |
| included | YIP-270 | Define high-level information archectural design (Charter) | o produce governing principles for creating new page and portlet collections for new user communityo produce governing principles for modifying existing page and portlet collections for user communityo define known user communities (roles) for current and future implementation planso catalog key portlet candidates for defined user communitieso create wireframes, illustrating key page and portlet layout for defined user communities, based on governing principles |
| included | YIP-264 | Clean up portlet (channel) registry | Determine what channels/portlets are being used and consider removing them, deleting them, etc |
| included | YIP-229 | Improve the way developers work and interact with the YaleInfo portal | Notes:A bundled quickstart for developers would be a great idea. This would allow practically any developer familiar with the concepts to work on content for YaleInfo. A quickstart build process already exists for vanilla uPortal 3.0 and could be used to leverage a YaleInfo environment specific quickstart. |
| included | YIP-231 | Improve deployment and undeployment of content in portal as well as portal framework [uPortal] | The way we deploy individual content and the portal framework itself needs to be rethought. |
| included | YIP-262 | Build-out portal infrastructure [uPortal 3.x] | Build-out portal infrastructure, reducing operational (planned/unplanned) downtime and improve capacity for expected peak-load use cases. Look to migrate to proposed system's architecture. Reconsider application container (jboss, etc). Do we get any advantages from using Tomcat because JA-SIG uses tomcat? |
| included | YIP-33 | Revisit the document cacher [uPortal 3.x] | Create a version of document cacher (retreiver) which can be committed to uPortal head for 2.5 release or better yet, use rutgers filter-ized version |
| included | YIP-245 | Convert projects to use Maven 2 [uPortal 3.x] | Convert all projects except the current YaleInfo 2.6 project to use Maven 2. |
| ? | YIP-273 | Integrate with help desk support software | Consider how we can integrate with the help desk support software. This includes the portal and specifically individual portlets and how we support them. |
| included | YIP-246 | Create Spring Portlet MVC archetype | Create a Maven 2 archetype that uses the Spring Portlet MVC. This will be very useful as a base "skeleton" project to start creating portlets. |
| included | YIP-240 | Create a consistent project structure and build process | There needs to be a consistency in the way projects are structured and built. Current inconsistencies:1. Source directory may be src, source, or WEB-INF/src2. Web root directory is sometimes web, webapps, webpages, webroot3. Libraries may be at the project root in some cases and under WEB-INF in others.4. Some projects have a portaltest and portalprod directory with environment specific files, and others have multiple web.xml files renamed for various environments |
| included | YIP-230 | Determine content to analyze and improve web analytics | 1.) Determine what we would like to analyze. Obviously we want to determine number of visitors, point of entry, and browser demographics. Also, determining what portlets are being used is essential but not so intuitive. 2.) Improve the web analytics tools to achieve our desired analysis We need tools that can analyze a portal environment. Current tools seem to rely on URL patterns to determine paths and content usage, however, a portal's URL does not necessary (most likely not) represent content and usage. |
| included | YIP-222 | Rearrange static content for better performance and teamwork | |
| included | YIP-255 | Upgrade portal technology platform to uPortal 3.0 (Charter) | Upgrade to uPortal 3.0. |
| included | YIP-261 | Create a JSR-168 RSS Reader that aggregates multiple feeds. | The portlet can aggregate multiple feeds and present them in a logical user friendly way. Look to leverage use of TabbedRSSPortlet from Duke University. |
| included | YIP-272 | Create portlet development kit (PDK), supporting distrubute portlet develperment (Charter) | o portal development best practices and governing principleso portlet user interface guidelineso single sign-on standards using Proxy CASo portlet testing / certification guidelineso portlet deployment methods for test and production release |