SDA 4.0 Documentation for UPDATES


NAME

updates - Changes to SDA since Version 3.5

DESCRIPTION

This document summarizes the differences between Version 3.5 and the subsequent versions.


SUMMARY OF CHANGES BY SDA VERSION



CHANGES BY CATEGORY


CHANGES TO THE INTERFACE (Version 4.0 and later)

ACCESSIBLITY VERSIONS

RE-RUNNING (BOOKMARKABLE) ANALYSIS OUTPUT


NEW SDA MANAGER WEB APPLICATION (Version 4.0 and later)


CHANGES TO ANALYSIS PROGRAMS (after Version 3.5)


CHANGES TO THE UNDERLYING ARCHITECTURE

SDA versions 4.0 and later have converted 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.x 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 SDA Version 3.5 (or 3.6)
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.x.

The things that DO NOT CHANGE in the new architecture include:

The things that DO CHANGE are:


CSM, UC Berkeley/ISA
September 5, 2017