logo



search arches


Roadmap

Arches v 2.0 has just been released, and we think it’s a significant upgrade of the core technologies and application architecture. The Arches team is pleased to provide an updated project roadmap below.

In addition to the release of v 2.0, we are working on the milestones outlined in the roadmap. Feel free to comment on them by posting your thoughts on the Arches Forum!

It is expected that the roadmap will evolve over time. For example, we have recently been accepted into Google’s Summer of Code program, and once the work to be done during the summer is identified, the roadmap will be updated to reflect those plans.

You can support these or additional enhancements to Arches by submitting code, making a donation to the project, or by becoming a sponsor.

We encourage you to download v 2.0 and start testing this release with either the bundled test dataset (courtesy of English Heritage), or with your own data.

Arches Roadmap

Arches v 1.0
Released October 2013
Initial release.

Arches v 2.0
Released March 2014

  • Update Django from 1.3 to 1.6
  • Tested with PostgreSQL 9.3 and PostGIS 2.x
  • Separate core Arches functionality into a single application
  • Implement a package management system that separates implementation specific configuration information into modules that can be loading into Arches. Packages include:
    • Resource graphs
    • User interface/data entry forms
    • Concept Schema graphs and their data
    • Report templates
    • Data indexing scripts (to support search)
    • Test data
    • System configuration information (e.g., symbols for map display, supported languages)
  • Packages may be created and shared by the Arches community, and can be extended or enhanced independently of core Arches.
  • A CDS (Core Data Standard) v 1.0 Package that implements all the resource graphs, forms, concept schema, indexes, data, and configuration settings that were shipped with Arches v 1.0
  • Bug fixes and enhancements
  • #113, 199, 200, 244, 246, 296, 302, 320, 322, 327, 341, 342, 345, 353, 357, 362, 363, 364
  • Simplified installation scripts
  • Improvements and fixes to the Installation Documentation

 

Arches v 2.1
Planned release, April 2014

  • Support for uploading digital files and associating them with an individual or multiple resources
  • Bug fixes and enhancements tagged as “v 2.1.0″ in the Arches repository

 

Arches v 2.2
Planned release, Summer 2014

  • Bug Fixes and enhancements tagged as “v 2.2.0″ in the Arches repository
  • Better documentation on creating and implementing custom resource graphs
  • Improved workflow for supporting community edits to the Arches documentation

 

Arches v 3.0
Expected to be released at the end of 2014

  • New “Heritage Inventory Package (HIP)” that implements the following resources:
    • Historic Resources
      • This graph will support resource types using concepts from a thesaurus.
      • Historic Resources will be implemented as E18 entities (Manmade things in the CIDOC CRM), and may be used as an alternate means of creating “Architectural Heritage”, “Maritime Heritage”, and “Archaeological Heritage (Element)” records currently implemented in the CDS v 1.0 package
      • Graph will support both description and evaluation of the resource
    • Historic Districts
      • This graph will support resource types using concepts from a thesaurus.
      • Historic District Resources will be implemented as E27 entities (Sites in the CIDOC CRM) and may be used as an alternate means of creating “Landscape Heritage” and “Archaeologic Heritage (Site)” records currently implemented in the CDS v 1.0 package
      • Graph will support both description and evaluation of the resource
    • Activities
      • This graph will support activity types using a thesaurus.
      • Activities may be used as an alternate means of creating “Designation and Protection”, “Historical Event”, “Investigation”, and “Management” records currently implemented in the CDS v 1.0 package
    • Actors (Person, Organization)
      • These graphs will be very similar to the CDS v 1.0 resource graphs
    • File
      • This graph will support the creation of digital file type records using concepts from a thesaurus
      • The resource graph will implement Dublin Core metadata
    • Image and Document graphs in the CDS v 1.0 package will be deprecated
  • Implement a “Resource Description” and “Resource Evaluation” workflow for Historic Resources and Historic Districts
  • Improved Advanced Search
    • Better support for searches across resource graphs
    • Return firstlevel related resources (e.g.: Search for Actor “Frank Lloyd Wright” and automatically return resources that are linked directly to the actor. This would make it much easier to find Historic Resources such as buildings that have a relationship to Frank Lloyd Wright)
    • Improved spatial filtering
    • Support for “not” operator (e.g.: filter for all heritage resources that are NOT neolithic)
    • UI enhancements
    • Improved “simple search”
    • Export search results as kml, csv
  • Related Resources now Managed in Core Arches
    • Simplify all resource graphs by removing all references to related resources
    • Add services to support management of resource relations
    • Add ability to related resources on data import
  • Implement a Reference Data Manager (RDM)
    • The Reference Data Manager (RDM) will provide a UI for creating and managing thesauri within Arches, which will introduce a new role in Arches specifically to support managing thesauri
    • The RDM will allow Arches administrators to interactively build thesauri, associate thesauri with nodes on Resource Graphs, and will support multiparent thesauri
    • RDM will support import/export of SKOS files
route_66_3

Route 66, United States                      Photo: Dave Johnson