• Alison Bell Update
    • What should we be spending time on?
    • What matters and what doesn't matter?
    • Project Update
      • Wireframes designed
      • Usability testing completed
      • Usability testing compiled on Monday or Tuesday
      • Designs presented, whittling them down
    • What has she been doing with the content?
      • Started with content matrix
      • Looking at new IA infrastructure
      • Matching the two up
      • Seems to be fairly one to one
      • What are they aiming at?
        • Service oriented site
        • What do the users want?
        • What do people think about us?
      • Finding all of the pages in a certain section and tries to fit them into the buckets of the new IA
      • Next step - talking to content owners
      • Archiving pages
    • What should we be caring about?  What is in the AFS locker vs. what we need?
      • Content matrix is based on a user visiting the site
      • AFS locker questions should be directed to Kris and Sam
    • Expectation - everything that is within the IS&T website WILL look the same... how is this going to play out politically?
  • Issues
    • What are we going to do with the old / archived information that is currently in AFS?
    • What happens when we move the pages and all of the URLs change?  How do we redirect?
    • Who's job is it to identify what is "the IS&T website"
    • The hard part will not be how hard the template is... the hard part will be massaging the content to be usable for templates
    • Porting
      • Identifying what content we need to port
      • Take .html documents and run a script over them that pulls out content and converts them into .xml documents that have just the content
      • Apply a template to the content .xml documents
      • ...
      • Separate content from formatting into XML
      • Preparation for getting new templates
      • We build new templates, schemas, workflows
      • We have content mapping
    • Our job
      • Porting existing content into new site
      • Building new templates, schemas, forms, workflows
    • Their job
      • Mapping the content
      • Identifying what content on the old site goes where in the new site
      • Adding or changing content level changes (one-off changes)
    • Question - what happens with the one-off changes... the development team is not willing to perform content level changes
    • Define our scope to what is reachable via the website
      • Looking at only .html documents
      • Not looking within linked documents (.doc, .pdf)
    • What is going to happen with Stock Answers?  Should this be replaced with a new "Search our Answers" feature?
    • TinyMCE Issues
      • Seeing different versions
      • WCM-31
  • Notes
    • Biggest win for the project - ITInfo
      • Already structured content
      • Script to turn content into .xml
      • Turn database record into .xml file and easily make an .xsl that will make that .xml file look like something
      • Hard part
        • Building an index page for these things
        • Searching
      • 2 parts
        • Product pages
          • Model this as xml files within Alfresco
          • Filtering of information
          • Functional application
          • Once we have the data, we can pull that out and store it somehow
        • Stock Answers
          • A lot more data in this section
          • How many people actually use this
          • New IA - "Ask a Question" box... search stock answers box
          • Should this be replaced with a new feature?
    • Do not want to rely on Alfresco as a runtime backend system - would rather rely on java?
  • To Do's
    • Talk to production about what is where and what we need to be worried about
    • Get Kris and Sam involved in this process of identifying what IS and what IS NOT the IS&T website
    • Talk to Carol about what can increase collaboration between our teams
    • Targets
      • Content goal - via scripting, peel the content accessible via spider out of the current website and into .xml and some set of .xsd / .xsl pairs.  Import the .xml and see the .html in preview
      • ITInfo goal - export the product info, import as .xml file, edit as .xsd / .xsl, and preview it as .html
      • This will let us know about these cycles and then we will dig down to the next layer of problems
        • Content deployment
        • How do we edit the workflows
          • Refreshing content that has dependencies
          • ...
        • Link management, linking to document
    • Development plan
      • What are the stop-gap measures?  What are the other pieces of development?
      • Dependency management
      • Link management
      • Content porting
      • Content deployment (includes content regeneration and some link management)
      • Link validation
  • No labels