March 2, 2017 Update from Sarah Bradham

Building on last week’s work in the Website Phase of the project, OMBU delivered version 2 of the site map to the Mazamas. The site map was reviewed and conversation led to several additional tweaks and revisions to the proposed site map. Version 4 of the site map is the version that OMBU will use to build wireframes of the site (wireframe: an image or set of images which display the functional elements of a website or page, typically used for planning a site’s structure and functionality).

OMBU will present the wireframes to the Mazamas on March 9.

We are also beginning work on the Data Collection part of the project. Data Collection involves getting data from a variety of locations, including the current Mazamas Access Database (DB), Mazamas2 hiking DB, climb data from Expression Engine (where our current website is built), and various excel documents and Google docs being used by committees. The type of data we are working to collect in order to populate the new system:

  • Membership Info (held in the Mazama Access DB)
  • Climb Data (some is in the Mazama Access DB, some is in Expression Engine)
  • Hike Data (Mazamas2 SQL DB)
  • Volunteer Data (some is held in spreadsheets)
  • Participation & Enrollment data (some is held in spreadsheets)

In addition to needing to collect the data that we already have that exists in the locations listed above, we are working to create new data to link everything we are building together. In our current setup, none of our “systems” talk to each other. So while we have climb data that we are tracking on our website, it doesn’t connect to our Access DB. In the new setup, the majority of our systems will be connected. In such a relational database, you need to have data that can be easily connected, and in order to do that, you have to standardize and split your data into different tables.


  • Current system: We have a multitude of Mt. Hood climbs that can be scheduled by climb leaders
  • We have a multitude of Mt. Hood climbs that can be scheduled by climb leaders
  • These climbs exist in one single table, where you enter the climb name “Mt. Hood South Side,” data about the climb including elevation, distance, drive time, etc …

New system

  • There will be a Places table
  • Within this Places table, Mt. Hood will be a mountain
  • There will be an Activity table
  • Within the Activity table, Mt. Hood South Side will be a Climb, and its place will be Mt. Hood, which will establish a link between the Activity and Place table
  • In order to create the Place table we have to create … Places!

The Places to populate the Places table is just one example of a data set that we need to create by pulling together data from a variety of different sources.

We expect this data collection phase to take approximately three weeks, and we are reaching out to committees that might have some of this data in order to get it into the appropriate data migration templates.

We are shooting for having 60% of our data collected by the end of March. At this time OMBU will work to build scripts to migrate the data into the new CRM. They will then push that data into the CRM and we will be able to work with this real data as we test the new CRM, website, and eventually CMS tools.

Over the summer we will continue to work on populating these data collection documents, and we will likely ask for some of your help as we do this work. By the end of the summer we need to have this data 100% ready for transition into the new system. Once we are closer to the launch of the actual site, we will push this updated data into the CRM, replacing the nown old test data.

Leave a Reply

Your email address will not be published. Required fields are marked *