Weave Admin Console

Video Tutorials

Setting up Weave
 
Setting up MySQL
Setting up Java
Setting up Tomcat
Setting up Flash

Getting Started
 
Part 1
Part 2
Part 3
Geo Layering

Using the Admin Console
 
Import Shape files
Import CSV data
Import SQL data
Creating a Visualization Page

General

The administration console allows the user to set and create the various features of sessions in Weave. The Admin Console is connected to a database (including “localhost”), which is password protected. The following screenshot demonstrates the first page in the Admin Console:

As highlighted in the magnified portion of the screenshot, a log-in is required to open the Admin Console, set by the administrator.

Data Import

Import SQL

Once logged in, the administrator gets a view of the various functions available in the Admin Console. Using the “Import SQL data” button, the administrator can import an existing SQL table through the Weave server. This function does not create a new table in the database, it simply makes the table accessible through the Admin Console.

Clicking on the “Import SQL data” button opens the following window:

Here, the administrator is asked to specify the following: the SQL schema within the database connected to the Admin Console, the data-table within that schema, and the key column in that table.
The following step consists of defining a display name for the selected table which will appear in the Admin Console, and a geometry collection with which the data-table is associated (e.g. the table “obesity by state” will be linked with the geometry collection “U.S. states”):

Once all these requirements are fulfilled, the administrator will receive a confirmation after clicking on the button “Finish”.

Import CSV

Using the “Import CSV data” button, the administrator can import a .csv data file (csv = comma separated values) from the local disk.

The following window will appear after clicking the “Import CSV data” button:

Clicking on the “Upload File” button indicates that the file is sitting on a local disk, while the “Choose File on Server” button indicates that the .csv file is located on a server. After clicking on the “Upload File” button, the administrator is required to specify the location of the .csv file:

Once the .csv file is selected, the administrator will specify the destination SQL schema in which the file will be located and the name of the table in the database. After hitting the "Next" button, the administrator will be provided with the options of :

  • Entering a "Table display name" for the data-table. This is the name that will be visible in Weave.
  • Setting “Null flag values”. If your data has values like "-1" representing missing data, you can enter the values here and Weave will treat them as missing data. Separate multiple flag values by commas.

The "Generate New Primary Key Column" is selected by default. This will generate a new unique key for each row. It is the simplest option, but will not allow you to link the data to other data sets. To link it with other data sets and/or to set a primary key column from the data set, uncheck the box.

The administrator has the option to select the Key Column. The Key Column should have unique values. If the values are not unique you will see an error message as shown in the image below. If your columns don't have unique values you can default to the "Generate New Primary key column" option, or you can use the option of

  • "Format Data for Dimension Slider": Select a secondary key.
  • "Generate filtered column queries" : This option is to be used when the new data table has a column that refers to keys in another data table but the keys do not uniquely identify rows in the new table. Other columns in the new table can be used to generate SQL queries that will return different subsets of the rows. The key column will be used to uniquely identify rows in the subsets.

You can associate the keys with a key type or a a geometry collection.As explained in the previous section (Import SQL data), geometry collection contains a collection of geographic attributes (including a shape-file).

Finally in this process, the administrator is required to enter basic metadata information about the imported data-table:

Generate filtered column queries

Users can use the SQL and CSV import wizards to create columns with sql queries that filter the data by some attribute.
For example, if a table has state-level data for multiple years like this:

FIPS,YEAR,QUARTER,MY_DATA
01,1995,Q1,0.1
01,1995,Q2,0.2
01,1995,Q3,0.3
01,1995,Q4,0.4
01,1996,Q1,0.5
01,1996,Q2,0.6
01,1996,Q3,0.7
01,1996,Q4,0.8
02,1995,Q1,0.4
02,1995,Q2,0.5
02,1995,Q3,0.6
02,1995,Q4,0.7
02,1996,Q1,0.8
02,1996,Q2,0.9
02,1996,Q3,1.0
02,1996,Q4,1.1
...

To create column queries containing data values that filter by YEAR and QUARTER using FIPS as the key column, use this option in the SQL and CSV import wizards
(Users can specify multiple column names that will generate a column query for each unique combination of column values)

The result queries will look like this in the Data tables tab of the Admin Console:

Importing Geometry Collections (“Shape data”)

When clicking “Import Shape Data”, the administrator will be required to specify the location of the geometry collection files on the local disk. The geometry collection consists, minimally, of the following files: shape-file (.shp), (.shx) file, and (.dbf) file. Other files might such as projection files (.prj) might be included as well.
The following example shows the files included in importing a geometry collection of “states” in the U.S.:

Once selected, the files will be uploaded and confirmation will appear on the panel (circulated in red). The administrator is then required to specify the key column which will link the collection with data-tables, the schema in which the collection will be located, and the display name for the collection. The key column should have unique values. If it does not then you will see an error message similar to the one shown for CSV import.

Subsequently, the administrator has the option of specifying a value to replace “Null” values in the .dbf file, a name for the geometry collection (transmitted from the previous step by default), and a “key type” which should carry the same name in this case.

Database connections

Databases connected to the Admin Console can be viewed/edited under the “Database connections” tab. Additionally, the administrator can add database connections, and export the SQL configuration file in .xml:

Geometry Collections

The Admin Console allows the administrator to view and modify detail in the geometry collections uploaded into the connected database. As the two following screenshots demonstrate, geometry collections are searchable (left panel) and modifiable through the following attributes:
· Name of the collection
· Connection to the database
· Key Type for the collection which is used to link it with data-tables
· Table Prefix which shows the display name of the collection within a visualization session
· Projection SRS code which defines the projection of the geometry collection (http://en.wikipedia.org/wiki/Geographic_coordinate_system )
· Import Notes presenting a summary of the collection’s attributes in string

Data Hierarchies

Data tables and column hierarchies can be configured under the "Data Hierarchies" tab. Data is configured by storing public and private metadata for every column. The table below describes some of the properties. If you would like to know how this information is stored in SQL, see this table.

Public or private? Metadata property name Description
public title Display name.
private connection References the name of a connection in sqlconfig.xml to be used when running the sqlQuery.
private sqlQuery A sql query that returns two columns (keys and data) and may optionally contain "?" placeholders.
private sqlParams Optional list of parameters for sqlQuery that will be used as values at "?" placeholders.
This may be provided in JSON or CSV format.
public keyType A name identifying the namespace of key values returned by sqlQuery.
public dataType Specifies the type of data returned by the second column of sqlQuery (string, number, geometry, or a keyType value to indicate a foreign key).
public projection Specifies an SRS code like EPSG:4326 for a geometry column.
public number A number formatting function to be interpreted by Weave's runtime ActionScript compiler. The string variable may be used to get the string value of a record.
Examples:
asNumber(string)
parseDate(string, 'YYYY')
public string A string formatting function to be interpreted by Weave's runtime ActionScript compiler. The number variable may be used to get the numeric value of a record.
Examples:
formatNumber(100 * number, 1) + '%'
formatDate(number)
public min Used by visualization axes and normalization functions.
public max Used by visualization axes and normalization functions.
public dataTable Used by time slider only (for grouping columns).
public name Used by time slider only (for grouping columns).
public year Used by time slider only (for differentiating columns).

Client Configurations:

Under this tab, the administrator can view, search, create, delete, or modify existing visualization sessions in Weave as .xml files (listed in the left panel). Here the user can create a new Weave session by naming the session in the highlighted box below and clicking on the “Create” button:

In the example below, we are creating a Weave session titles “States Test”:

After clicking on the “Create” button, a pop-up window will show up with an empty Weave session (Pop-ups must be enables to get this window), and the administrator will get a confirmation as highlighted below:

The empty Weave session in the pop-up window looks like this:

All data-tables and geometry collections are available to be used in this session, and since the session is opened from the Admin Console, it is editable (i.e. assigned administrator privileges). Here, the administrator can populate the session with tools in Weave and save it to access later from the Admin Console by double clicking on the file appearing in the left panel under the Client Configurations tab:

admin-_data_tables_main.PNG (185 KB) Andy Dufilie, 07/07/2011 12:30 AM

admin-_database.PNG (66 KB) Andy Dufilie, 07/07/2011 12:30 AM

admin-_empty_weave.PNG (33.3 KB) Andy Dufilie, 07/07/2011 12:30 AM

admin-_geo_collection_selection.PNG (101 KB) Andy Dufilie, 07/07/2011 12:30 AM

admin-_client_config_main.PNG (22.8 KB) Andy Dufilie, 07/07/2011 12:30 AM

admin-_confirmation.PNG (38.4 KB) Andy Dufilie, 07/07/2011 12:30 AM

admin-_csv_file_location.PNG (57.2 KB) Andy Dufilie, 07/07/2011 12:30 AM

admin-_csv_main.PNG (76 KB) Andy Dufilie, 07/07/2011 12:30 AM

admin-_geo_collections_1.PNG (80.1 KB) Andy Dufilie, 07/07/2011 12:30 AM

admin-_csv_metainfo.PNG (85.5 KB) Andy Dufilie, 07/07/2011 12:30 AM

admin-_import_sql_tables.PNG (91.8 KB) Andy Dufilie, 07/07/2011 12:30 AM

admin-_import_sql.PNG (33.9 KB) Andy Dufilie, 07/07/2011 12:30 AM

admin-_login_info.PNG (21.9 KB) Andy Dufilie, 07/07/2011 12:30 AM

admin-_metadata.PNG (51.2 KB) Andy Dufilie, 07/07/2011 12:30 AM

admin-_geo_collections_2.PNG (75.5 KB) Andy Dufilie, 07/07/2011 12:30 AM

admin-_geo_collections_main.PNG (99.4 KB) Andy Dufilie, 07/07/2011 12:30 AM

admin-_import_csv_to_weave_2.PNG (98.3 KB) Andy Dufilie, 07/07/2011 12:30 AM

admin-_import_csv_to_weave.PNG (81.3 KB) Andy Dufilie, 07/07/2011 12:30 AM

admin-_session.PNG (139 KB) Andy Dufilie, 07/07/2011 12:30 AM

admin-_import_shape_data.PNG (118 KB) Andy Dufilie, 07/07/2011 12:30 AM

admin-_sql_geometry.PNG (106 KB) Andy Dufilie, 07/07/2011 12:31 AM

admin-_state_tests.PNG (25.6 KB) Andy Dufilie, 07/07/2011 12:31 AM

admin-_table_view.PNG (216 KB) Andy Dufilie, 07/07/2011 12:31 AM

admin-_text_view.PNG (217 KB) Andy Dufilie, 07/07/2011 12:31 AM

admin-_view.PNG (69.6 KB) Andy Dufilie, 07/07/2011 12:31 AM

sqlwizard1.png (26.4 KB) Krithika Manohar, 12/04/2011 06:35 PM

sqlwizard2.png (48.8 KB) Krithika Manohar, 12/04/2011 06:35 PM

filteredqueriesgui2.png (11.9 KB) Krithika Manohar, 12/04/2011 06:55 PM

filtered-queries.png (24.6 KB) Andy Dufilie, 12/04/2011 08:51 PM

CSV_Import_1.png (13 KB) Sebastin Kolman, 03/12/2012 05:12 PM

CSV_Import_2.png (25.3 KB) Sebastin Kolman, 03/12/2012 05:12 PM