Tag Archives: UI

Migration of UI Complete, Coding begins

Today we have successfully moved the user interface from Earth to GIS. The new URL is http://gis.cofc.edu:10080/avkat.html. We will now move our 2 databases(avkat, avkat_mysql) over to server GIS to make a full migration of Avkat Informatics, without any ties to server Earth, or Geodata. We are currently digging through the code to find all of the data retrieval endpoints, which we will now direct to GIS. I have identified the main endpoint to be the file OpenDB.php. The endpoint has now been updated to gis.COUGARS.INT without any visible problems. We must continue to make sure all of the data pointers are consistent. The next step will be to connect the UI to our tabular data on avkat_mysql. Doing so will add functionality to the left panel of our current UI. Multiple breakthroughs were achieved today, progress should move much faster from this point.

Leave a comment

Filed under Project Updates

Migration from Server Earth to GIS

We are now in the process of making a transition from hosting our current UI on earth to the Server GIS. We have migrated our Avkat project folder to GIS and are in the process of migrating our 2 Sql Server databases (Avkat and Avkat_MySql). We have run into a snag recently when looking through our project folder. It is currently unknown as to which of the UI code is actually running live. Once we identify the code of our current working version, we will then upload it to our proteus directory on GitHub. GitHub will help us manage our subsequent versions as we begin to manipulate the code. To get Proteus running live on GIS we must change the pointers to our databases. In our current live version the databases live on Geodata. Once we migrate our databases to GIS, we will be able to establish GIS as our full hosting server for the Avkat project. Doing so will help tremendously from an organizational standpoint. We are still waiting on the help of John Wall do direct us on the logistics of pushing proteus live onto GIS.

Leave a comment

Filed under Project Updates, Setting Up

Proteus Migration to Beta Server

The last 5 weeks we have encountered numerous setbacks as well as many successes in moving forward.

  • We have set up a workspace in the Visualization Lab at the College of Charleston Santee Cooper GIS Lab.
  • This workstation currently has two machines running with arcgis 10.0 and numerous other programs
  • We have three more machines ready to be imaged after the first two to provide extra work stations
  • We have set up a development server called gis.cofc.edu with the programs necessary.

To set up our beta server we had to:

  • Successfully identify where all of the databases are stored.
  • We are in the process of copying the databases to the beta server for testing purposes.
  • Find all of the relevant code for the website and then upload to our github repository for versioning
  • We have copied the majority of the data from geodata and earth to our new beta server for testing

Problems we have encountered include:

  • We attempted to implement arcgis server 10.1 on our beta server with the assistance of a local charleston called ROK Tech.
  • After discussing our options we have decided to revert to the stable version of arcgis server 10.0, the newer version has many problems still to be solved and is not suitable at this time for live production hosting.
  • We communicated with other members of the proteus team who had done the initial setup of the current alpha version of the website UI. Due to their busy schedules and their not being on location with us it took time to sort out where all of our data was located.

We will continue to work diligently on the beta server migration. Our next step is to setup a live closed beta of the current website UI that will be hosted on gis.cofc.edu. This will allow us to continue on to upgrading the UI, as we will then be starting with the base version that is the current standard.

Leave a comment

Filed under Project Updates, Setting Up

Classics 399: Applied Archeoinformatics

This course is a directed study course with Dr. Jim Newhard, Dr. Norm Levine, and Dr. Paul Anderson at the College of Charleston that brings together the Classics, Geology, and Computer Science departments. Using advanced GIS techniques in combination with SQL server we will attempt to improve the current viewing solution to Avkat Informatics. I will be working alongside another student, Matt Mazzarell, to display the GIS data in the Web View on our server, earth.cofc.edu.

On Tuesday, September 11, 2012 Norm gave Matt and I a quick lesson on the mapping of network drives that will be used to ensure consistency across the project. This is the same mapping that is used by all involved in the GIS work at the College of Charleston. He also walked through some basic server setup and maintenance to allow us to have access to remote login to the server, earth. All involved in the Avkat project have been granted access to the server at this point and can proceed to work.

Leave a comment

Filed under Project Updates

Query Interface

We have now begun working on developing the query interface for the Avkat Informatics project. The interface allows for the query of four parameters. Artifact Type, Time Period, and Unit Type correspond to specific attribute values. A second option for time allows a user to enter a range of values and retrieve all information that potentially falls within that date range. Lastly, the Search Comments of Forms allows users to enter in words to search the comments. The goal is to replicate the query interface of search engines familiar to the end-user.

The design of the Query Interface is highly important. Here, users access data in a fashion that is influenced both by the organizational structure of the database, the query, and the user’s internal notion of what would ‘make sense’. The goal of any data system is to provide structure and organization, while at the same time to allow for new systems of organization to emerge as the data is explored.  The query interface is that point where the questions of the researcher are addressed by the data system, and the types of questions that the interface allows (or doesn’t allow) can reveal potential research biases latent in the database structure, such as:

  • favoring one type of evidence over another (such as pottery shape over pottery function),
  • the way in which time is divided into periods, thus reflecting biases towards ‘important’ events of history that may or may not reflect actual cultural shifts;
  • potential artifact misclassification, owing to a lack of ‘unknown’ options
  • the inability to attach  two or more categories to an object due to uncertainty.

Our initial foray into the query interface is focused clearly upon the questions of ‘what’ and ‘when,’ and is designed to be a very bare-bones system to find and extract the data, understanding that further analysis will occur in 3rd-party applications. Our system is not intended to be the venue where complex analytics are performed. Our purpose is to provide an easy means of serving datasets to end users, who will manipulate the queried data within applications specifically constructed their needs.

1 Comment

Filed under Project Updates