arches 8.1.1

Arches is an open-source, web-based, geospatial information system for cultural heritage inventory and management.

Arches

Arches is a web-based, geospatial information system for cultural heritage inventory and management. Arches is purpose-built for the international cultural heritage field, and designed to record all types of immovable heritage, including archaeological sites, buildings and other historic structures, landscapes, and heritage ensembles or districts. For more information and background on the Arches project, please visit archesproject.org.

For general inquiries and to get technical support from the wider Arches community, visit our Community Forum.

For general user installation and app documentation, visit arches.readthedocs.io.

For the documentation pertaining to the version under development, visit arches.readthedocs.io/en/latest. We welcome new contributors; please see Contributing to Arches for details.

Issue reports are encouraged! Please read this article before reporting issues.

• Report a Bug
• File a Feature Ticket

Version 8.1.1 release notes

Quick Install

Installation is fully documented in the official documentation, arches.readthedocs.io/en/stable, but assuming you have all of the dependencies installed you should make a virtual environment, activate it, and then run

    pip install arches

then

    arches-admin startproject myproject

enter the new myproject directory

    cd myproject

and run

    python manage.py setup_db
    python manage.py runserver

in a separate terminal, activate your virtual environment and navigate to the root directory of the project ( you should be on the same level as package.json)

    cd myproject/myproject

and run

    npm run build_development

to create a frontend asset bundle. This process should complete in less than 2 minutes.

Finally, visit localhost:8000 in a browser (only Chrome is fully supported at this time).

If you run into problems, please review our full installation documentation

Release Cycle

Our general release cycle will typically be a functional release (either major if there are backward incompatible changes or minor, if there are not) every 9 months. Each functional release will typically be followed by one or more patch releases. See semver.org for version numbering.

• Functional releases will usually introduce new functionality to the application, but could also include styling updates, enhancements to the UX, bug fixes, and performance improvements.
• Patch releases are really only concerned with fixing any bugs related to the previous release or any other issues not yet addressed

Support for previous releases

• LTS (Long Term Support) releases will be maintained with patch releases for at least 27 months. Typically an LTS release will be the second minor release following a major release.
• Feature releases (with the exception of stable releases) will be supported only until the next feature release. After that users are expected to upgrade to the latest release on pypi.python.org

For details regarding future releases, see the feature roadmap.