ARK2/Avalon2 - Revision history

John Layt: /* Avalon 2 */

2016-12-30T11:19:42Z

‎Avalon 2

John Layt at 14:25, 17 December 2016

2016-12-17T14:25:14Z

John Layt at 21:21, 15 December 2016

2016-12-15T21:21:06Z

John Layt at 21:16, 15 December 2016

2016-12-15T21:16:45Z

John Layt: Created page with "= Avalon 2 = Avalon is the project management ARK for LP Archaeology. Avalon triggers the creation of a job folder on the local server, which is then synced to the other serv..."

2016-12-15T21:09:38Z

Created page with "= Avalon 2 = Avalon is the project management ARK for LP Archaeology. Avalon triggers the creation of a job folder on the local server, which is then synced to the other serv..."

New page

= Avalon 2 =

Avalon is the project management ARK for LP Archaeology. Avalon triggers the creation of a job folder on the local server, which is then synced to the other servers. If a GIS is required, then standard shapefiles are created in the job folder, and all the GIS data is stored in the job folder. Any Project that also requires a site recording ARK then sets that up separately.

A number of issues exist here:
* File syncing is slow, resource intensive, and error prone
* GIS data is heavily duplicated, wasting space
* GIS data is fractured, i.e. finding what data we already have requires manual searching of folders, and may lead to the purchase of duplicate data
* Use of ARK for data recording is time-consuming to set up so often not done
* Many jobs are deemed too small to bother entering the data in ARK, this makes querying our data corpus or automating many report writing functions impossible
* Versioning files, submitting them for review, and checking they have been is a manual process and open to abuse

ARK 2 provides several new features that can alleviate this:
* File management and file versioning support
* Workflow management
* Easy automated creation of new ARK instances
* Multiple sites and schemas in a single ARK install
* Support for running on PostgreSQL, and consequently support for PostGIS

The proposal for Avalon 2 is as follows:
* A single ARK install running both Avalon and all site ARKs, either as a single instance or two instances sharing a single user database
* The database will run on PostgreSQL, providing both the Avalon/ARK data server and a GIS database in a single install
* The GIS database will manage as many shared vector and raster resources as possible, including the GIS for each Project
* On creation of a new Project, the PM can choose to create a GIS and an ARK, or trigger this at any time later

← Older revision		Revision as of 11:19, 30 December 2016
Line 29:		Line 29:

	* Integrated Wiki to replace Mediawiki		* Integrated Wiki to replace Mediawiki
		+
		+	* https://github.com/charlesroper/OSGB_Grids

← Older revision		Revision as of 14:25, 17 December 2016
Line 27:		Line 27:
	* A connection to Harvest will be created using their API, allowing for combined reporting, and automated creation of projects and allocation of staff.		* A connection to Harvest will be created using their API, allowing for combined reporting, and automated creation of projects and allocation of staff.
	* Later Avalon could seek to replicate the required features of Harvest itself.		* Later Avalon could seek to replicate the required features of Harvest itself.
		+
		+	* Integrated Wiki to replace Mediawiki

@@ Line 7: / Line 7: @@
 * GIS data is heavily duplicated, wasting space
 * GIS data is fractured, i.e. finding what data we already have requires manual searching of folders, and may lead to the purchase of duplicate data
-* Use of ARK for data recording is time-consuming to set up so often not done
+* GIS Figures are still too complex to produce and could be automated more.
 * Many jobs are deemed too small to bother entering the data in ARK, this makes querying our data corpus or automating many report writing functions impossible
 * Versioning files, submitting them for review, and checking they have been is a manual process and open to abuse
@@ Line 23: / Line 24: @@
 * The GIS database will manage as many shared vector and raster resources as possible, as well as the GIS for each Project.
 * On creation of a new Project, the PM can choose to create a GIS and an ARK, or trigger this at any time later.
 * A connection to Harvest will be created using their API, allowing for combined reporting, and automated creation of projects and allocation of staff.
 * Later Avalon could seek to replicate the required features of Harvest itself.

@@ Line 19: / Line 19: @@
 The proposal for Avalon 2 is as follows:
-* A single ARK install running both Avalon and all site ARKs, either as a single instance or two instances sharing a single user database
+* A single ARK install running both Avalon and all site ARKs, either as a single instance or two instances sharing a single user database.
-* The database will run on PostgreSQL, providing both the Avalon/ARK data server and a GIS database in a single install
+* The database will run on PostgreSQL, providing both the Avalon/ARK data server and a PostGIS database in a single install.
-* The GIS database will manage as many shared vector and raster resources as possible, including the GIS for each Project
+* The GIS database will manage as many shared vector and raster resources as possible, as well as the GIS for each Project.
-* On creation of a new Project, the PM can choose to create a GIS and an ARK, or trigger this at any time later
+* On creation of a new Project, the PM can choose to create a GIS and an ARK, or trigger this at any time later.