Technical Details of CollaborationNarration by Nicholas J. Parks

Agenda

Recap Intent of this slide set AAI product suite The NADL product suite from CSDL Proposed Architecture

Products Interfaces

What this Architecture Allows us to do What to do next

Recap…

I have been proposing a collaboration between AAI efforts and the NADL team of CSDL

Both organizations are in the same solution (or problem) space from different angles

Intent of this slide set

The purpose of this slide set is to cover some technical aspects of a proposed collaboration if both organizations choose to go forward together

This slide set does not make any policy or interaction decisions

Slide set is a suggestion and musing of one person

AAI Product Suite

AAI has a completely implemented Application stack

Data Persistence View into data persistence OpenContext is the web application but

there is a data store behind it XML data store Relational data store

NADL Product Suite

Shipwright (Java) Document Analyzer

OnScene (.Net) Configuration prototype of a field collection

device Soap Sync’er (.Net & PHP)

Concept verification Custom Data Representations Interface Stubs

Proposed Architecture

I am proposing a suite of interdependent products Repository Server Adaptive Workspace Document Analyzer Knowledge Engine Some Helper Apps

Proposed Architecture Products (1)

Repository Server Standalone Server where data is stored “ships” with basic interface and

Management Tools Allows for

Separate OLTP and DSS servers that can be synchronized

Simple and Safe Backup Replication and Multiple Sites

Proposed Architecture Products (2)

Repository Server Nothing Innovative here

Database and File system FSDB

Hardware and Base OS

SOAP OAI-MHP

Sync Logic

Hibernate / Propel

Shipping ViewerAdmin

Proposed Architecture Products (3)

Deployed Repository Servers Again, Nothing Innovative Blue: SOAP/OAI

Sharing Content, Shared Replication Red: Site Replication Yellow: Site Backup – OLTP/DSS

RS RS

RS

RSRS

AAIX

INA Bodrum

INA TAMU

Proposed Architecture Products (4)

Adaptive Workspace NADL Office Vista Archaeological Workspace

Due to the nature of the content and the volume for comprehension there is a need for an adaptive information workspace Task User type “Intelligent assisted environment”

Business Intelligence Front-end Concept already exists in financial applications

Proposed Architecture Products (5)

Adaptive Workspace Modeling the business process of

archaeologists through the recurring business cycles of an excavation

Mobile Connectionless Digital Library System Local Cache copy when not connected Connects to “home site” when network capable

Mini Desktop Stack Application Database Soap sync

Proposed Architecture Products (6)

Workspace and Repository Server Workspace is a desktop application LAN and mobile users connect to the RS via SOAP connection

and the “sync logic”

RS

Proposed Architecture Products (6)

Historical Document Analyzer Shipwright Dissection of Nautical Archaeological

Treaties Online and Offline utility Offline similar to the workspace and

launch-able from the workspace environment

Proposed Architecture Products (7)

Knowledge Engine Not a feature that users actively interact

with Native communication with Repository

Server Soul function

Generate your standard indexes Make Semantic Maps Cluster content Any other cool AI stuff you can do with data point

that are not numbers.

Proposed Architecture Products (8)

Helper Apps User Accounts Sync rules Admin stuff…

Proposed Architecture Interfaces (1)

This is Tricky… We have PHP, Java, and .net stuff not to

mention that Virginia Tech OAI-MHP is perl based!

Standard Business Questions Speed Maintenance cost Personnel

Proposed Architecture Interfaces (2)

Luckily… Soap Hibernate / Propel

I am found of full application servers Cold Fusion, Jrun on the inside Jboss (Think Apache-Tomcat) Complete .net environment

Proposed Architecture Interfaces (3)

Recycle! Shipwright is currently in a variation of

Java OpenContext can be the shipping

viewer Soap interface on the servers are trivial

so java or PHP will work, I am found of Jboss here too

What this allows us to do

Obviously, each organization can richly explore individual research areas

We just so happen to create an digital library framework for use by others

Side Topics Privacy, Content Protection, and related Knowledge understanding Ethnography Information infrastructure (CIKM)

What to do next

Face Time! As in the first slide set we need some

face time with each other Goal Setting