Background
Through history we can trace the processes by which Queenslanders
have
'made' Queensland. The natural setting has been occupied, 'settled',
modified, engineered, re-made as a cultural landscape. Less tangible
are the ways that the Queensland setting has shaped identity, as the
landscape has served as a powerful presence in the stories,
perceptions, social activities and cultural traditions of
Queenslanders. The Queensland Historical Atlast (QHAtlas) [1] aims to
explore and map the ‘nature-culture’
dialogue through time in the Queensland setting.
The QHAtlas project has two major deliverables:
1. QHAtlas Print
A large-format, c.300 page book co-published by the Queensland
Museum (QM) and a
commercial/academic publisher. This would be targeted at students,
researchers and general readers as a reference work with a strong
interpretive edge, encapsulating scholarly work in environmental
history, historical and cultural geography, archaeology, anthropology,
and heritage studies.
2. eQHAtlas
The Project
This project focuses on the "back-end" data management aspects of the Queensland Historical Atlas. We have built a prototype Web 2.0 Internet application powered by the Storage Resource Broker (SRB), a middle-ware data-grid technology that provides a uniform interface to large heterogeneous data collections ([2] and [3]). This will allow collaborators/authors of the QHAtlas project to manage and maintain the large amounts of data necessary for both the print and electronic atlas. These data include the Queensland Museum's cultural heritage collection that contains over 300,000 objects. Our web interface is designed to be a living research tool, able to be enlarged and expanded in the future.System Architecture

Figure 1.
QHAtlas Data Storage System Architecture
The QHAtlas Data Storage system architecture is shown in Figure 1. To understand its functionality, let us examine the data flow (from 1 to 6) that happens behind the scenes as a user interacts with the QHAtlas webpage:
- Events from webpage
When a user interacts with the QHAtlas webpage such as requesting for some data, he or she sends events to the Javascript engine
- HTTP requests
The Javascript engine processes the user-generated data request event and sends it in HTTP requests to the web sever.
- SRB data request
The web server passes the received HTTP request to the PHP process that in turn uses the SRB bindings to communicate with a SRB repository via SRB data requests.
- SRB federated data I/O
In this example data flow, the requested data actually resides on a 'federated' SRB repository. SRB technology redirects the data I/O to come from the external source. This occurs seamlessly without user intervention [4].
- Asynchronous XML response
After the data is retrieved from SRB and cached on the web server, the data is returned using the XMLHttpRequest object. The asynchronous nature improves speed, interactivity, and usability in the web interface as the entire web page does not have to be reloaded each time the user performs an action.
- Update dynamic content
Finally the Javascript engine parses the XML response and updates the dynamic content on the QHAtlas webpage. The entire data flow repeats with the next user action.
Screenshots
Desired Functionality
CORE (Completed) |
EXTENDED (In development) |
|
|
Downloads
Instructions for building from source
|
PHP-SRB bindings source code:
PHP-SRB AJAX test page source code:
|
References
[1] Queensland Historical Atlashttp://www.uq.edu.au/qhatlas
[2] The SRB Project @ UQ VisLab
http://www.vislab.uq.edu.au/research/SRB/index.html
[3] SDSC Storage Resource Broker official site
http://www.sdsc.edu/srb/index.php/Main_Page
[4] SRB zones @ UQ VisLab
http://www.vislab.uq.edu.au/research/SRB/zone.html
Acknowledgments
Created by Eric LIAO <e.liao at uq.edu.au>Funding through UQVislab and QCIF.
- Last updated December 18, 2007 -






