Plone

McCall Design Group

McCall Design Group

McCall Design Group is an architectural design firm encompassing flagship projects with national and international retail and hospitality giants such as Limited Brands, Inc., Starwood Hotels and Resorts Worldwide, Inc., Gap, Inc., and Williams-Sonoma, Inc.

Case Study

Development for McCall's extranet using Plone was done to meet the demanding needs of the firm's daily operations. The firm operates on both a national and international level where communication, time and content management is critical.  Plone's ease of use allowed content to be updated and managed easily through the web anywhere in the world. Plone's user permissions and group management also played a key part in defining content access on a project by project basis.  Shop drawing logs, email correspondences, and external file system storage were some of the many features that were integrated and developed.

Moving Content to the Web

Previously, items such as shop drawing logs and updates were written by hand on paper, and then mailed or faxed. Remember those days?

The "Old way"

Photo of a Shop Drawing Log

With Plone, all content is created, managed, and updated through the web.

The Plone Way

Screenshot of adding a new log

Email Integration

Each project consists of email correspondences on daily tasks and issues. Project managers needed to record and track these correspondences. A custom application was developed that allowed Plone to connect to McCall's email server and create copies of each email within Plone.

Screenshot of Project Emails

Database Integration

When project managers create new projects, Plone automatically generates a project folder with information from a relational database about location, contact info, project status, etc. based on the project id entered.

Screenshot of realtional database connection

File System Storage

As an architectural firm, you can image the massive amounts of photos and files that are needed for each project. The solution was to store all files externally using FileSystemStorage instead of within the ZODB to avoid unnecessary growth. This also allowed for easier and quicker maintenance since it kept the Data.fs file small and manageable.

Go Back