SDA 4.0 Documentation for UPDATES


NAME

updates - Changes to SDA since Versions 3.5 and 3.6

DESCRIPTION

This is a summary of the differences between Version 3.5 (and the limited-distribution Version 3.6) and Versions 4.0 and 4.0.1 of SDA.


CHANGES TO THE INTERFACE

ACCESSIBLITY VERSION

NEW SDAMANAGER WEB APPLICATION

CHANGES TO ANALYSIS PROGRAMS (after Version 3.5)

CHANGES TO THE UNDERLYING ARCHITECTURE

SDA 4.0 converts completely from CGI to Java servlets for the web user interface. (The previous SDA interface was a blend of CGI and servlet-based components.) For an archivist who is setting up an SDA archive, the installation procedure is simplified. The coordination of CGI and servlet-based components -- which can be tricky to configure -- is no longer necessary. Also, SDA 4.0 requires ONLY a servlet container (Tomcat) to run. An additional web server -- Apache or IIS -- is no longer required (since CGI is no longer used).

UPGRADING FROM A PREVIOUS SDA VERSION

What does this mean for organizations that already have SDA archives? What changes in the new SDA version -- and what doesn't? Many of the pieces of the current SDA architecture remain the same as before. In particular, the SDA assets that organizations have developed -- such as SDA datsets, codebooks, etc. -- are fully compatible with SDA 4.0. The things that DON'T change in the new architecture include:

The things that DO change are:


CSM, UC Berkeley/ISA
February 27, 2017