Versions Compared

Old Version 4

changes.mady.by.user Catherine T Iannuzzo

Saved on

compared with

New Version Current

changes.mady.by.user Stephen Turner

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin

...

forms/templates: automate conversion of website content

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

runtime: 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\]unmigrated-wiki-markup

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

testing: 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

...

forms/templates: get existing stuff working in 2.01; refine migrated content to go to "general" template when feasible;  develop new templates at the next level

ITinfo:
  - get a representation of the topic hierarchy (with numbers and names) as a static tree (later make it dynamic)
  - in migration, turn keyword string in to separate field values; watch out for character issues w/encodings*
  - describe all types of documents besides Stock Answers & Prod Info; start putting articles into normal content tree

runtime:  design & implement first-pass runtime web app on Tomcat

deployment: stopgap deployment so we can start to test web app w/content 

infrastructure: migrate to Alf 2.01 (partial)

Build 6: May 31 June 7

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

Task List:

  • Image Added [Ann-Patrice] Forms/Templates: refine migration scripts to port content to "general" template when feasible, first pass
  • [Ann-Patrice] Forms/Templates: develop new  two column template for current pages
  • Image Added [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.
  • Image Added [Ann-Patrice] Content Migration: develop scripts to identify pages which are  blue-box, redirects, news or otherwise questionable for migration
  • Image Added [Ann-Patrice] Content Migration: work with Publications side to eliminate pages which are not going to move on to new design.
  • Image Added[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
  • [Steve] ITinfo: get a representation of the topic hierarchy (with numbers and names) as a static xml tree (later make it dynamic)
    • Image Added [Steve] Step 1: put hierarchy into JSP in a form that ALfresco web forms can use as a drop-down list.
    •  [Steve] ITinfo: separate into a pure XML document and a JSP that reads this and formats it for ALfresco web forms
  • Image Added <unnecessary> [Steve] -ITinfo:  in migration, turn keyword string in to separate field values; watch out for character issues w/encodings-   
  • [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)
  • [Steve] ITinfo: start putting articles into normal content tree
  • Image Added[Steve] ITinfo: document how to do content export
  • [Steve] [Joe] [Catherine] Runtime: layout high level architecture of webapp (Spring, MVC, security, sub-components, etc.) & assign areas
  • Image Added [Joe] Runtime: Create svn module for runtime app as a Netbeans project
  • [Craig] [DaveT] advise on use of Acegi in app
  • [DaveT] [Hunter] Runtime: develop Acegi implementations of Moira lists for access control (may involve a web service. Or not)  WE CAN USE LDAP** [Hunter] set up supporting db or other infrastructure
    • [DaveT] create impl ** will need to be refactored, as it is not going to be done in one build
  • [Steve] Runtime: implement assigned areas ** will need to be refactored, as it is not going to be done in one build
  • [Joe] Runtime: implement assigned areas ** will need to be refactored, as it is not going to be done in one build
  • Image Added [Joe, Hunter] Deployment: deploy-to-filesystem
  • Image Added [Joe] design deployment

...

  • approach for runtime
  • Image Added [Hunter] Set up apache, tomcat, smb on isda-ist1
  • [Who?] Testing: a simple smoke test to see if "build" is broken

...

Detailed Release Notes:

Build 7: June

...

21

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

Build 8: June 28

...

  • Image Added [Ann-Patrice] Forms/Templates: refine migration scripts to port content to "general" template when feasible- First round of general template migration completed
  • [Ann-Patrice] Forms/Templates: develop new  two column template for current pages
  • Image Added [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.
  • Image Added [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.
  • [Ann-Patrice] Forms/Templates: analysis of new web page design to begin creation of xsd/xsl pairs - Work begun.
Wiki Markup
{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 round
  • [Ann-Patrice] Forms/Templates: develop new  two column template for current pages
  • [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.
  • [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)
  • [Steve] ITinfo: get a representation of the topic hierarchy (with numbers and names) as a static xml tree (later make it dynamic)
    •  [Steve] ITinfo: separate into a pure XML document and a JSP that reads this and formats it for Alfresco web forms
  • Image Added [Steve] ITinfo: start putting "news" and "articles" into normal content tree
    • Image Added[Ann-Patrice] make forms for "news" and "articles"
    • [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] 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)
  • [Steve] Helpdesk questions:
    • [Steve] what about Top 5? what is the requirement?
    • [Steve] Help desk portal page - determine features, integration points
    • [Steve] Find out how Help Desk Wiki will get articles into Alfresco
  • [Joe] make .htaccess emulation work for ordinary content
  • [Who?] Testing: a simple smoke test to see if "build" is broken
Wiki Markup
{dynamictasklist:AnnPatrice}{dynamictasklist}
Wiki Markup
{dynamictasklist:Steve}{dynamictasklist}
Wiki Markup
{dynamictasklist:Joe}{dynamictasklist}
Wiki Markup
{dynamictasklist:Unassigned}{dynamictasklist}