This is the general User Manual for Arches. It should provide you with background information on Arches, how to install it, and a good overview of its capabilities. While you are using Arches, be aware that much of the content here is also available by clicking the ”?” symbol in the top-right corner of any page. If you are a developer interested in customizing or contributing to Arches, you should also visit our GitHub wiki for more information about how Arches works underneath.
What is Arches?¶
Arches is a web-based, geospatial information system for cultural heritage inventory and management. The platform is purpose-built for the international cultural heritage field, and it is designed to record all types of immovable heritage, including archaeological sites, buildings and other historic structures, landscapes, and heritage ensembles or districts.
Arches allows administrators to create their own database schema, and manage their own thesauri, while end users can search, explore and download the resources directly. In this way Arches is not only a robust and easy to use inventory system, it is also a perfect way to publish and disseminate your organization’s cultural heritage information.
To try Arches out, you can view the v4 demo installation, go to the Arches project page for more background, or join our Google Group to engage with the active Arches community.
Arches is a web framework for Django and is designed to make it easier to build applications that need:
- Geospatial data management and geoprocessing like a GIS (Geograhic Information System) offers, but with a much more flexible approach for modeling the geometries associated with a resource.
- the ability to import arbitrary data schema in the form of graphs as a means of defining the set of attributes that describe data resources
- an Ontology as a means of formally naming and defining data types, properties, and the relationships between the data entities that describe a resource.
- Thesauri to manage the controlled vocabularies needed to describe and index information in a consistent and uniform way.
Arches manages data “resources”. Resources can represent almost anything you want: physical things (such as a cultural heritage object), temporal things (such as activities or events), actors (such as a person or organization), or conceptual objects (such as an image. document, or other information carrier).
Resources are defined as directed graphs (nodes connected by edges). Nodes in the graph are used to represent the attributes (or collection of attributes) of a resource and edges define the type of relationship between attributes. In practice, a resource graph in Arches functions much like a schema does in a relational database.
Arches provides core services for creating, reading, updating, and deleting resources. Because resources are defined as graphs, Arches provides the services needed to import and parse resource graphs, as well the ability to create and interact with instance graphs (e.g.: an instance of a resource graph).
To promote consistent data creation, update, and indexing workflows, Arches implements a Reference Data Manager (RDM) that can manage thesauri. The RDM allows users with the appropriate privileges to update thesaurus entries in a manner compliant with SKOS (http://www.w3.org/2004/02/skos/) and assign the concepts within a thesaurus with data entry forms.
Arches’ User and Developer forum: http://archesproject.org/forum/
v3.0 April, 2015: Updated architecture, inclusion of the Reference Data Manager, updated dependencies (ElasticSearch, OpenLayers, Knockout)
v2.0 March, 2014: Improved upload of digital files, assorted bug fixes
v1.0 October, 2013: Initial Release
Arches is free software and is licensed under the terms of the GNU Affero General Public License (http://www.gnu.org/licenses/agpl-3.0.html)
Who is Arches for?¶
Arches is primarily intended for software developers who need to build flexible and responsive web applications, and who wish to hide the complexities of ontologies, thesauri, and geospatial data management from their users.
The Arches framework is largely invisible to end users; Arches applications are responsible for defining resource graphs and implementing data entry, data presentation, and data reporting workflows.
One major exception to this rule is the Reference Data Manager (RDM). The RDM is a core component of the Arches framework and can support the creation and curation of thesauri without the need to implement an Arches application.
Contributing To Arches¶
Arches is open source software, which means that with your help it will continue to evolve and improve. Contributions to the project can take a few different forms:
- Translations We are always hoping to bring Arches to new audiences around the world. Please get in touch from the main Arches website to express your interest in helping with translations.
- Bug Reports Reporting bugs is strongly encouraged, and can be made at the official Arches GitHub repository. Please read this article before reporting issues.
- Code Contributions For developers, good guidelines on how to contribute to the Arches code-base can be found in our GitHub repo wiki.