Introduction to Arches Collector¶
Arches Collector is a mobile app that allows you and your team to collect heritage data in the field, and sync it back to your main Arches instance. Database administrators facilitate this process by designing “projects” in the Arches instance, which define who can participate, what kind of data will be collected, where the project will take place, and for how long. Approved users can then connect to the Arches instance, download the project, and collect data, and sync it back to the database.
Arches Collector Workflow¶
Connect to an Arches Instance¶
Begin by connecting to an existing Arches instance. This is a deployment of Arches that you can also view on the web. You’ll use credentials provided to you by the database administrator.
You can create and maintain connections to as many Arches instances as you want.
Download a Project¶
Upon entering an Arches instance, you will see a list of projects. These are all of the mobile data collection projects to which you have been granted access. Choose a one, and download it to begin working.
Once you have downloaded a project, you can enter it and begin collecting data.
A project marked as “Inactive” means that no new users can download it. If you have already downloaded a project that is now marked inactive, you can continue to work with it as before.
Download the Offline Map¶
In some cases, you may expect to collect data outside of wifi/cellular network range, so the database administrator will configure this project with an offline map. This map will be downloaded the first time you activate the “Use offline maps” switch.
Make sure you download the offline map before heading out into the field for the first time! We recommend doing this while connected to wifi, as the offline map file could be large.
From the list of projects, open the settings menu for a project and flip the “Use offline maps” switch.
You can keep your project screen clean by leaving projects if you will no longer be participating (you can rejoin later), or by deleting projects from your device. All unsynced data in a project will be lost upon deletion.
New resources are made from the NEW screen, where you will choose a resource model to use for the new resource. In the following example, a new “Heritage Asset - Monument” resource will be created.
Beginning to create a new resource, you’ll see all of the cards (or “records”) that can be added to the resource.
While the example above shows text and dropdown entries, other types of data will have different input methods.
From the REVIEW screen of a project, you can select resources to edit them. In this example “The Eliza Jane” will be selected.
When you’ve selected a resource you’ll be brought to its RESOURCE REPORT: a summary of all the records that have been added to it. As shown below, you can edit any existing record (as long as you have the proper permissions).
When you have finished collecting data, either creating new resources or editing existing ones, you will sync your local edits to the web Arches deployment. In fact, you can do this at any time during your data collection, and as often as you want.
When you sync your the project on your mobile device, this is what happens:
All local changes will be pushed to the Arches instance.
All local will be made available to all other participants in the same project.
You will download any data changes that other project participants have synced.
You will not download changes that have been made to resources directly in the Arches instance since the project was first activated.
Additionally, some changes occur to the resources you have created in your project:
You will no longer be able to delete entire resources that you created locally.
You will no longer be able to delete resource records that you created locally.
You can sync a project from within the project itself:
Or you can sync from the main project list page: