Versions Compared

Old Version 23

changes.mady.by.user Ann-Patrice Hickey

Saved on

compared with

New Version 24

changes.mady.by.user Catherine T Iannuzzo

Saved on

Key

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

...

Theme: more Alf 2.01 integration, real web app & deployment

Task List:

  • Image Added
    Wiki Markup
    *\[Ann-Patrice\]*
     Forms/Templates: refine migration scripts to port content to "general" template when feasible, first pass
  • Wiki Markup
    *\[Ann-Patrice\]*
     Forms/Templates: develop new  two column template for current pages
  • Wiki Markup
    *\[Ann-Patrice\]*
     Forms/Templates:  investigate ( design?) a template between "blob" and "general" which has header+footer+left   nav+right blob - investigation showed little utility for a midway template.
  • Wiki Markup
    *\[Ann-Patrice\]*
     Content Migration: develop scripts to identify pages which are  blue-box, redirects, news or otherwise questionable for migration
  • Wiki Markup
    *\[Ann-Patrice\]*
     Content Migration: work with Publications side to eliminate pages which are not going to move on to new design.
  • Image Added
    Wiki Markup
    *\[Ann-Patrice\]*
     Content Migration: Update wget of IS&T site on bi-weekly basis and run scripts to capture changes from step above as well as new pages
  • Wiki Markup
    *\[Steve\]*
     ITinfo: get a representation of the topic hierarchy (with numbers and names) as a static xml tree (later make it dynamic)**  
    • Image Modified
      Wiki Markup
      *\[Steve\]*
       Step 1: put hierarchy into JSP in a form that ALfresco web forms can use as a drop-down list.
    **
    •  
      Wiki Markup
      *\[Steve\]*
       ITinfo: separate into a pure XML document and a JSP that reads this and formats it for ALfresco web forms
  • <unnecessary>
    Wiki Markup
    *\[Steve\]*
     -ITinfo:  in migration, turn keyword string in to separate field values; watch out for character issues w/encodings-   
  • Wiki Markup
    *\[Steve\]*
     ItinfoItinfo: Verify that Google search either uses the keyword string as-is or ignores keywords completely (in which case we may decide to discard keyword data)
  • Wiki Markup
    *\[Steve\]*
     ITinfo: start putting articles into normal content tree
  • Image Added
    Wiki Markup
    *\[Steve\]*
     ITinfo: document how to do content export
  • Wiki Markup
    *\[Steve\] \[Joe\] \[Catherine\]*
     Runtime: layout high level architecture of webapp (Spring, MVC, security, sub-components, etc.) & assign areas
  • Image Added
    Wiki Markup
    *\[Joe\]*
     Runtime: Create svn module for runtime app as a Netbeans project**
  • Wiki Markup
    *\[Craig\] \[DaveT\]*
     advise on use of Acegi in app
  • Wiki Markup
    *-\[DaveT\]&nbsp;\[Hunter\]-*
     Runtime: develop Acegi implementations of Moira lists for access control (may involve a web service. Or not)  WE CAN USE LDAP**  
    Wiki Markup
    *-\[Hunter\]-*
     set up supporting db or other infrastructure
      *
    • Wiki Markup
      *-\[DaveT\]-*
       create impl ** will need to be refactored, as it is not going to be done in one build
  • Wiki Markup
    *\[Steve\]*
     Runtime: implement assigned areas ** will need to be refactored, as it is not going to be done in one build
  • Wiki Markup
    *\[Joe\]*
     Runtime: implement assigned areas ** will need to be refactored, as it is not going to be done in one build
  • Image Added
    Wiki Markup
    *\[Joe,*
     Hunter] Deployment: stopgap deploy-to-filesystem so we can start to test webapp w/content**  
  • Image Added
    Wiki Markup
    *\[Joe\]*
     design deployment approach for runtime
  • Image Added **
    Wiki Markup
    *\[Hunter\]*
     Set up apache, tomcat, smb on isda-ist1
  • Wiki Markup
    *-\[Who?\]-*
     Testing: a simple smoke test to see if "build" is broken
  • Image Added
    Wiki Markup
    *\[Who?\]*
     Testing: define a process for integration, testing, roll-out. Staging is our integration point, yet it is also the "ready to deploy" point. How do we do this?
  • Wiki Markup
    *&nbsp;\[Joe\]*
     Infrastructure: Continue to integrate 2.0.1 on isda-cs1
  • Wiki Markup
    *&nbsp;\[Joe\]*
     Fix/workaround bugs https://confab.mit.edu/jira/browse/WCM-87, https://confab.mit.edu/jira/browse/WCM-88, https://confab.mit.edu/jira/browse/WCM-93, and https://confab.mit.edu/jira/browse/WCM-94.
  •  
    Wiki Markup
    *\[Steve\]*
     New IA Migration: create JSP to consume RSS feed

...

  • Wiki Markup
    *\[Ann-Patrice\]*
     Forms/Templates: refine migration scripts to port content to "general" template when feasible- First round of general template migration completed
  • Wiki Markup
    *\[Ann-Patrice\]*
     Forms/Templates: develop new  two column template for current pages
  • Wiki Markup
    *\[Ann-Patrice\]*
     Content Migration: work with Publications side to eliminate pages which are not going to move on to new design.- work ongoing- new lists distributed June 20 for blue-box, redirects and non-conforming pages.
  • Wiki Markup
    *\[Ann-Patrice\]*
    Content Migration: Update wget of IS&T site on bi-weekly basis and run scripts to capture changes from step above as well as new pages- wget from June 9 analyzed and migrated.
  • Wiki Markup
    *\[Ann-Patrice\]*
     Forms/Templates: analysis of new web page design to begin creation of xsd/xsl pairs - Work begun.

...

Theme: ready for migration 

  • Wiki Markup
    *\[Ann-Patrice\]*
    Forms/Templates: refine migration scripts to port content to "general" template when feasible- second round
  • Wiki Markup
    *\[Ann-Patrice\]*
     Forms/Templates: develop new  two column template for current pages
  • Wiki Markup
    *\[Ann-Patrice\]*
     Content Migration: Update wget of IS&T site on bi-weekly basis and run scripts to capture changes from step above as well as new pages- wget from June 9 analyzed and migrated.
  • Wiki Markup
    *\[Ann-Patrice\]*
     Forms/Templates: analysis of new web page design to begin creation of xsd/xsl pairs - next round (To be specified in more detail)
  • Wiki Markup
    *\[Steve\]*
     ITinfo: get a representation of the topic hierarchy (with numbers and names) as a static xml tree (later make it dynamic)
    •  
      Wiki Markup
      *\[Steve\]*
       ITinfo: separate into a pure XML document and a JSP that reads this and formats it for ALfresco web forms
  • Wiki Markup
    *\[Steve\]*
     ITinfo: start putting "news" and "articles" into normal content tree
    • Wiki Markup
      !https://wikis.mit.edu/confluence/images/icons/emoticons/check.gif!\[Ann-Patrice\] make forms for "news" and "articles"
    • Wiki Markup
      \[Steve\] scripts to export data & format into xml, ready to load
    • Wiki Markup
      \[Steve\] load data into alfresco, to be managed via webform
  • Wiki Markup
    *\[Steve\]*
     Itinfo: Verify that Google search either uses the keyword string as-is or ignores keywords completely (in which case we may decide to discard keyword data)
  • Wiki Markup
    *\[Steve\]*
     Helpdesk questions:
    • Wiki Markup
      *\[Steve\]*
       what about Top 5? what is the requirement?
    • Wiki Markup
      *\[Steve\]*
       Help desk portal page - determine features, integration points
    • Wiki Markup
      *\[Steve\]*
       Find out how Help Desk Wiki will get articles into Alfresco
  • Wiki Markup
    *\[Joe\]*
     make .htaccess emulation work for ordinary content
  • Wiki Markup
    *\[Who?\]*
     Testing: a simple smoke test to see if "build" is broken