Difference between revisions of "Slicer3:Web Presence"

From NAMIC Wiki
Jump to: navigation, search
Line 27: Line 27:
 
The move to use Wiki2Web for the Slicer web pages complicates the issue, as the form has to be translated into a MediaWiki page that will translate to the final web page and still work. From Nicole 3 Aug 2007:
 
The move to use Wiki2Web for the Slicer web pages complicates the issue, as the form has to be translated into a MediaWiki page that will translate to the final web page and still work. From Nicole 3 Aug 2007:
 
    
 
    
Marianna and I were working on the Slicer License form this afternoon, trying to get it working within the wiki to web framework, and we've hit a major roadblock.
+
  Marianna and I were working on the Slicer License form this afternoon, trying to get it working within the wiki to web framework, and
 +
  we've hit a major roadblock.
 
   Mediawiki isn't rendering the html form tag, it's printing it out as text.
 
   Mediawiki isn't rendering the html form tag, it's printing it out as text.
 
   From looking at
 
   From looking at

Revision as of 17:41, 12 September 2007

Home < Slicer3:Web Presence

Overview

Infrastructure work to support a uniform Slicer web presence. Work building on AHM 2006 Project Slicer3 Web Presence

Requirements:

  • ability to report number of unique Slicer binaries downloaded per month and per grant year, per release version, as well as aggregate numbers
  • record user information as they agree to abide by the Slicer license agreement
  • integrated download page that will provide links to binary Slicer packages, for nightly builds, developer snapshots, and official releases

Counting Downloads

Needed for grant reporting.

Current page: [to be found]

Parse the apache download logs directly or use multiple configuration files for Webalizer?

License Agreement

Needed for grant reporting.

Current page: [1]

The original license form was written as an HTML form that submitted data to a perl script that would verify the form entries and then write the user information to a series of flat files, one per month.

The move to use Wiki2Web for the Slicer web pages complicates the issue, as the form has to be translated into a MediaWiki page that will translate to the final web page and still work. From Nicole 3 Aug 2007:

 Marianna and I were working on the Slicer License form this afternoon, trying to get it working within the wiki to web framework, and  
 we've hit a major roadblock.
 Mediawiki isn't rendering the html form tag, it's printing it out as text.
 From looking at
 http://meta.wikimedia.org/wiki/Help:Inputbox
 it seems like we could install an extension to get certain pre-defined input boxes, but
 a) we can't get the example to work (following the installation instructions)
 b) once we get the example to work, a new extension will have to be written in PHP to support the license form.

Download Page

Current page: http://www.na-mic.org/Slicer/Download/

Needs to be integrated into the Wiki2Web framework in such a way that supports automatic uploads from nightly builds, developer snapshot uploads, as well as automatic downloads of Windows prebuilt binary sub-packages during the building of Slicer.

From Andy 4 Jun 2007:

 You could also create a MediaWiki extension for downloading files.
 Then you can use W2W to write text around the page, but use the extension to give you the list of files.

Team Members

  • Nicole Aucoin
  • Zack Galbreath
  • SPL system administrators