Page History

...

forms/templates: automate conversion of website content

Wiki MarkupITinfo: write up types of documents; putting articles into normal content tree \ [not done\]

Wiki Markupruntime: have business requirements sorted; \ [done\] have plan for add-on projects (scope v1 vs future); have a first-pass runtime web app for simple cases \ [not done\]

Wiki Markupdeployment: stopgap deployment so we can start to test web app w/content (get runtime system setup) \ [not done\]

Wiki Markuptesting: a simple smoke test; 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? \ [ not done\]

Build 4: May 3

Theme: find a solution to ITinfo

...

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

Task List:

• 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.
• 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)
  • 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-   unmigrated-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)unmigrated-wiki-markup*\
• [Steve\]* ITinfo: start putting articles into normal content tree
• 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
• 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
  unmigrated-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 buildunmigrated-wiki-markup
• *\[Joe\]* Runtime: implement assigned areas ** will need to be refactored, as it is not going to be done in one build
• Wiki Markup*\[Joe,* Hunter] Deployment: deploy-to-filesystem
• Wiki Markup*\[Joe\]* design deployment approach for runtime
• Wiki Markup*\[Hunter\]*Set up apache, tomcat, smb on isda-ist1unmigrated-wiki-markup*-\
• [Who?\]-* Testing: a simple smoke test to see if "build" is broken
• 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://mv-ezproxy-com.ezproxyberklee.flo.org/jira/browse/WCM-87, https://mv-ezproxy-com.ezproxyberklee.flo.org/jira/browse/WCM-88, https://mv-ezproxy-com.ezproxyberklee.flo.org/jira/browse/WCM-93, and https://mv-ezproxy-com.ezproxyberklee.flo.org/jira/browse/WCM-94.
•   Wiki Markup*\[Steve\]* New IA Migration: create JSP to consume RSS feed

Detailed Release Notes:

Build 7: June 21

Theme: real web app, real deployment, ready to test?

• 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.unmigrated-wiki-markup*\
• [Ann-Patrice\]* Forms/Templates: analysis of new web page design to begin creation of xsd/xsl pairs - Work begun.

{dynamictasklist:Build 7 June 21}{dynamictasklist}

Build 8: July 5

Theme: ready for migration 

...

• *\[Ann-Patrice\]*Forms/Templates: refine migration scripts to port content to "general" template when feasible- second roundunmigrated-wiki-markup*\
• [Ann-Patrice\]* Forms/Templates: develop new  two column template for current pages

• Wiki Markup
  *\[Ann-Patrice\]*

  [Steve] 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)unmigrated-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 Alfresco web forms
  Wiki Markup*\
• Image Added [Steve\]* ITinfo: start putting "news" and "articles" into normal content tree
  • Wiki Markup!https://wikis-mit-edu.ezproxyberklee.flo.org/confluence/images/icons/emoticons/check.gif!\Image Added[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

  • [Steve] add automatic "guid" generation function to ITInto web forms
  • Image Added [Steve] scripts to export data & format into xml, ready to load
  • Image Added [Steve] load data into alfresco, to be managed via webform
• Image Added [Steve]

  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)unmigrated-wiki-markup*\
• [Steve\]* Helpdesk questions:
  • Wiki Markup*\[Steve\]*what about Top 5? what is the requirement?unmigrated-wiki-markup*\
  • [Steve\]*Help desk portal page - determine features, integration pointsunmigrated-wiki-markup*\
  • [Steve\]* Find out how Help Desk Wiki will get articles into Alfresco
  Wiki Markup*\
• [Joe\]*make .htaccess emulation work for ordinary contentunmigrated-wiki-markup

• *\[Who?\]* Testing: a simple smoke test to see if "build" is broken

{dynamictasklist:AnnPatrice}{dynamictasklist}

{dynamictasklist:Steve}{dynamictasklist}

{dynamictasklist:Joe}{dynamictasklist}

{dynamictasklist:Unassigned}{dynamictasklist}