Arches for HERs is a comprehensive data management platform for UK Historic Environment Records (HERs). Arches for HERs is purpose-built for HERs and any organization that conforms to the standards specified by the Forum for Information Standards in Heritage (FISH), including MIDAS Heritage.
You can find out more about Arches for HERs at https://www.archesproject.org/arches-for-hers/
-
Clone the arches-her repo, making sure to change the default target folder to arches_her and then run pip install:
pip install -r ./arches_her/arches_her/install/requirements.txt
If you are installing Arches for HERs on Windows, follow the instructions relating to the GDAL_LIBRARY_PATH detailed in the Installing Core Arches documentation.
-
Set up your database and load the package with the following command in the arches_her directory:
python manage.py packages -o load_package -s <path_to_arches_her_directory>/arches_her/arches_her/pkg -db -y
-
Start the Arches for HERs project
python manage.py runserver
-
Install and build front-end dependencies
Before you can use browse the application you will need to build the front end asset bundle. From the directory containing the package.json file ([workspace]/arches_her/arches_her)
yarn install yarn build_development
This will allow you to run the application locally, but is not suitable for running on a web server. Please see the guidance for deploying an Arches project like Arches for HERs into a server environment.
https://arches.readthedocs.io/en/latest/deployment/
If you are setting up a development enviornment then please see the Arches documentation on how to do this:
https://arches.readthedocs.io/en/latest/installing/installation/
You will need to use the dev/7.5.4
branch for the arches repository.
The arches_her/install/requirements.txt file will also need to be edited in order to remove the arches==7.5.4
requirement, as you will have cloned and installed the arches core code seperately.
You can also run Arches in a Docker development environment. To do this, pull the arches
repo and use the two compose files docker-compose-dependencies.yml
and docker-compose.yml
.
-
Clone both the
arches
andarches-her
repository:/workspace $ git clone https://github.com/archesproject/arches.git /workspace $ git clone https://github.com/archesproject/arches-her.git arches_her
As mentioned before, ensure the
arches
repo hasdev/7.5.4
checked-out. -
Navigate to the folder where the compose files exist, then compose up:
/workspace $ cd arches_her/docker/arches_her /workspace/arches_her/docker/arches_her $ docker compose -f docker-compose-dependencies.yml up -d /workspace/arches_her/docker/arches_her $ docker compose -f docker-compose.yml up -d
The first time you compose up - the database, Elastic indices and package data will get created and loaded. Be patient. Once complete, navigate to
http://localhost:8002
.
When finished, compose down:
docker compose -f docker-compose.yml down
docker compose -f docker-compose-dependencies.yml down
Administrators of an instance of Arches for HERs should configure their implementation having installed the out-of-the-box version. Ways in which you can configure and customise an instance include:
- The homepage provided (
arches_her/arches_her/templates/index.htm
) is a template that requires modification to suit the implementation. This should include branding, images, and replacing the highlighted content with appropriate information. A bespoke homepage can be created by replacing the contents ofindex.htm
. - Configuring functions against specific graphs. The initial installation of Arches for HERs includes the following functions:
- BNG Point to GeoJSON function
- GeoJSON to BNG Point function
- Consultation Status function
- Branding emails sent by the application
- Setting Accessibility mode to be on
- Configuring basemaps available in your Arches for HERs instance (using the instructions in the Core Arches Documentation).
❗️ Please note: you will need to configure a MapBox key in the user interface for the default mapping to appear, as per the Default Map Settings Core Arches documentation.
Field tag replacement in the templates can easily break if styling changes occur within the Word documents. The internal “style runs” provide rich formatting for the letters, but if a style partially touches a field tag (a field name surrounded by angle brackets), the field tag is physically split across several style runs. When this happens, it is no longer possible for the field to be substituted with its data value.
It is good practice to run the docx management command after working on the letter templates and before committing to source control. The full command is:
python manage.py docx fix_style_runs --dest_dir docx
The --dest_dir
parameter is optional and defaults to the docx
folder.
The Word files in the destination folder are processed in turn, and the command looks for pairs of angle brackets that may span multiple style runs. When this happens, they are joined together, thus restoring the full field tag.
A number of guidance documents are available in arches_her/media/guides
that can be used to help users understand how to use the system. These documents are in PDF format and can be linked to within your implementation if you do not have your own help documentation.
An example of how to include them within your implementation can be found in the index.htm template, which includes a link to the introduction guide.