Difference between revisions of "Web Site Migration"

From HL7 TSC
Jump to navigation Jump to search
 
(9 intermediate revisions by the same user not shown)
Line 1: Line 1:
−
=Web site Migration planning for **Foundation & Technology Steering Division**=  
+
=Web site Migration planning for '''Foundation & Technology Steering Division'''=  
  
−
* Each committee must provide a priority to be used to migrate the content of the [[http://www.hl7.org/|www.hl7.org]]. web site. The highest priority is 1, the lowest priority is 5.  
+
==Objectives==
 +
 
 +
* Each committee must provide a priority to be used to migrate the content of the [[http://www.hl7.org/ www.hl7.org]]. web site. The highest priority is 1, the lowest priority is 5.  
 
* Each may provide a set of external links to related organizations or web-sites.
 
* Each may provide a set of external links to related organizations or web-sites.
 +
* Priority information due on '''October 22nd, 2007'''
 +
 +
== Directions ==
 +
The following are additional directions provided by Ken regarding this excercise to identify the pages and prioritize their migration. Ken who identified the projects and the associated web pages has recommended the following:
 +
 +
{| border="0" cellspacing="0" cellpadding="3"
 +
|-
 +
| align="left" colspan="5" style="background-color: #AACCFF| "[The priority] should be valued from 1 to 5 with 1 being move this first and 5 being this can be the last to move.
 +
 +
I have done my best to match what seems to be defunct content areas to the host committee based on feedback I have received from several sources.  Please review these areas with your Steering division.  If my sources were incorrect, I will be happy to move the content to the appropriate host committee. 
 +
 +
Next, these defunct content areas:
 +
# Need to determine if the content should be folded under the host committee.
 +
## If yes, how to fold the content under the host committee - what goes where.
 +
## Any special consideration?
 +
# or archived and held in off-line storage.
 +
 +
Unlike my original expectation, for all active TC/SIG's their content will be moved.  It will be moved by people outside of HL7 who will follow very rigid rules for content move.  Once the content is moved, the co-chairs of the TC/SIG's will need to review the content to validate the migration was successful.  Archive of active TC/SIG content will be a project that will be considered post web site go-live.
  
 +
I would like to have your priorities back by October 22, 2007.
 +
 +
Thanks,
 +
Ken McCaslin"
 +
|-
 +
|}
 +
 +
== Web pages and prioritization ==
 +
 +
Please edit the priority for you commitee, the default was set to 5 (lowest priority to migrate content).
 
Once we provide the information, the web site content will be frozen for the duration of the migration. If you expect a great deal of activity on your site, you should assign a high priority to your page migration.
 
Once we provide the information, the web site content will be frozen for the duration of the migration. If you expect a great deal of activity on your site, you should assign a high priority to your page migration.
 +
 +
{| border="1" cellspacing="0" cellpadding="3"
 +
|-
 +
| align="center" colspan="5" style="background-color: #9999FF" | <font size="+1">Foundation & Technology Steering Division</font>
 +
|-
 +
| align="left" style="background-color: #FFCCFF"| '''Committees and projects'''
 +
| align="left" style="background-color: #FFCCFF"|  '''Migration comments'''
 +
| align="left" style="background-color: #FFCCFF"|  '''External Links'''
 +
| align="left" style="background-color: #FFCCFF"|  '''Priority (1 –highest, 5-lowest)'''
 +
|-
 +
| align="left" style="background-color: #CCCCFF" | '''IMPLEMENTATION TECHNOLOGY SPECIFICATION SIG''' <br/> (formerly XML)
 +
| valign="top" |...
 +
| valign="top" |...
 +
| valign="top" | 5 (default)
 +
|-
 +
| align="left" style="background-color: #CCCCFF" | '''IMPLEMENTATION/CONFORMANCE'''
 +
| valign="top" |...
 +
| valign="top" |...
 +
| valign="top" |5 (default)
 +
|-
 +
| align="left" style="background-color: #CCCCFF" |
 +
* Conformance
 +
| valign="top" |...
 +
| valign="top" |...
 +
| valign="top" |5 (default)
 +
|-
 +
| align="left" style="background-color: #CCCCFF" | '''INFRASTRUCTURE & MESSAGING (InM)'''
 +
| valign="top" |...
 +
| valign="top" |...
 +
| valign="top" |5 (default)
 +
|-
 +
| align="left" style="background-color: #CCCCFF" | '''JAVA'''
 +
| valign="top" |...
 +
| valign="top" |...
 +
| valign="top" |5 (default)
 +
|-
 +
| align="left" style="background-color: #CCCCFF" | '''MODELING AND METHODOLOGY (MnM)'''
 +
| valign="top" |...
 +
| valign="top" |
 +
* [http://www.uml.org/ http://www.uml.org/ ]
 +
* [http://hl7projects.hl7.nscee.edu/projects/hdf/ http://hl7projects.hl7.nscee.edu/projects/hdf/]
 +
* [http://hl7projects.hl7.nscee.edu/projects/mnm-project/ http://hl7projects.hl7.nscee.edu/projects/mnm-project/]
 +
| valign="top" |1 (highest)
 +
|-
 +
| align="left" style="background-color: #CCCCFF" |
 +
* Harmonization
 +
| valign="top" |...
 +
| valign="top" |...
 +
| valign="top" |5 (default)
 +
|-
 +
| align="left" style="background-color: #CCCCFF" |
 +
* Common Message Element Types
 +
| valign="top" |...
 +
| valign="top" |...
 +
| valign="top" |5 (default)
 +
|-
 +
| align="left" style="background-color: #CCCCFF" | '''SECURITY'''
 +
| valign="top" |...
 +
| valign="top" |...
 +
| valign="top" |5 (default)
 +
|-
 +
| align="left" style="background-color: #CCCCFF" | '''SERVICES ORIENTED ARCHITECTURE'''
 +
| valign="top" |...
 +
| valign="top" |...
 +
| valign="top" |5 (default)
 +
|-
 +
| align="left" style="background-color: #CCCCFF" |
 +
* HealthCare Services Specifications
 +
| valign="top" |What should be done with this page?
 +
| valign="top" |...
 +
| valign="top" |5 (default)
 +
|-
 +
| align="left" style="background-color: #CCCCFF" | '''TEMPLATES'''
 +
| valign="top" |...
 +
| valign="top" |...
 +
| valign="top" |5 (default)
 +
|-
 +
| align="left" style="background-color: #CCCCFF" | '''VOCABULARY'''
 +
| valign="top" |...
 +
| valign="top" |...
 +
| valign="top" |5 (default)
 +
|-
 +
| align="left" style="background-color: #CCCCFF" |
 +
* Term Info Project
 +
| valign="top" |Should this be archived or moved?
 +
| valign="top" |...
 +
| valign="top" |5 (default)
 +
|-
 +
|}

Latest revision as of 14:05, 23 October 2007

Web site Migration planning for Foundation & Technology Steering Division

Objectives

  • Each committee must provide a priority to be used to migrate the content of the [www.hl7.org]. web site. The highest priority is 1, the lowest priority is 5.
  • Each may provide a set of external links to related organizations or web-sites.
  • Priority information due on October 22nd, 2007

Directions

The following are additional directions provided by Ken regarding this excercise to identify the pages and prioritize their migration. Ken who identified the projects and the associated web pages has recommended the following:

"[The priority] should be valued from 1 to 5 with 1 being move this first and 5 being this can be the last to move.

I have done my best to match what seems to be defunct content areas to the host committee based on feedback I have received from several sources. Please review these areas with your Steering division. If my sources were incorrect, I will be happy to move the content to the appropriate host committee.

Next, these defunct content areas:

  1. Need to determine if the content should be folded under the host committee.
    1. If yes, how to fold the content under the host committee - what goes where.
    2. Any special consideration?
  2. or archived and held in off-line storage.

Unlike my original expectation, for all active TC/SIG's their content will be moved. It will be moved by people outside of HL7 who will follow very rigid rules for content move. Once the content is moved, the co-chairs of the TC/SIG's will need to review the content to validate the migration was successful. Archive of active TC/SIG content will be a project that will be considered post web site go-live.

I would like to have your priorities back by October 22, 2007.

Thanks, Ken McCaslin"

Web pages and prioritization

Please edit the priority for you commitee, the default was set to 5 (lowest priority to migrate content). Once we provide the information, the web site content will be frozen for the duration of the migration. If you expect a great deal of activity on your site, you should assign a high priority to your page migration.

Foundation & Technology Steering Division
Committees and projects Migration comments External Links Priority (1 –highest, 5-lowest)
IMPLEMENTATION TECHNOLOGY SPECIFICATION SIG
(formerly XML) 		... ... 5 (default)
IMPLEMENTATION/CONFORMANCE ... ... 5 (default)
  • Conformance
 ... ... 5 (default)
INFRASTRUCTURE & MESSAGING (InM) ... ... 5 (default)
JAVA ... ... 5 (default)
MODELING AND METHODOLOGY (MnM) ... 1 (highest)
  • Harmonization
 ... ... 5 (default)
  • Common Message Element Types
 ... ... 5 (default)
SECURITY ... ... 5 (default)
SERVICES ORIENTED ARCHITECTURE ... ... 5 (default)
  • HealthCare Services Specifications
 What should be done with this page? ... 5 (default)
TEMPLATES ... ... 5 (default)
VOCABULARY ... ... 5 (default)
  • Term Info Project
 Should this be archived or moved? ... 5 (default)
Retrieved from "https://tscwiki.hl7.org/w/index.php?title=Web_Site_Migration&oldid=2245"