Hi Marla (and all interested list members), At the Glenbow Museum we use STAR/Museums developed by Cuadra Associates Inc. The Exhibits Management Module in the application includes tasks that allow for the creation and description of an exhibit record (in-house or traveling), the selection and linking of artifacts to the exhibit record, the creation of label and catalog copy for exhibit artifacts, and gallery layout (location of artifacts while on exhibit). Global update functions reserve artifacts, allow for exclusions, update locations of artifacts when exhibits are opened, and return artifacts to a predetermined location when the exhibit is closed. As well, the app has a Crates module and a Shipping module that integrates with the exhibit module.
The Exhibit Management Module was one of the first modules that we integrated into our work processes at Glenbow. Since STAR is a development platform I have been able to make changes to input forms, reports, etc. that didn't quite fit the bill for the way we work here. I started with small changes, for example, a field to capture the names of staff on the exhibit team (the exhibit record only had a place for the coordinator or project leader). I continued by making reports that met the needs of our staff and have even modified the global updates to populate additional fields with relevant exhibit info. One element that the exhibit module doesn't currently handle is the ability to make an exhibit both in-house and traveling. Most of our traveling shows start as an in-house exhibit. That's a future project for me to work on. One of the advantages of a Collections Management System that is a development platform is that you can modify the way the product looks / works. A challenge (one that Glenbow has committed to) is that you need a full time database administrator, money and time for training. There have been very clear benefits to the institution since we started using the Exhibit Module in STAR. In addition to having detailed records about an exhibit for reference purposes, we now have a more streamlined, efficient exhibit process. In the past, Curators created artifact lists in a Word document. These documents were distributed to all parties that required a copy (conservators, installation techs, designers). Often when the curators removed artifacts from their list, updated copies were not forwarded. Mount makers, matters, framers, and conservators spent significant amounts of time working with artifacts that had been pulled from the exhibit. With the linking of artifacts to exhibit records and the ability to exclude artifacts with the click of a button, updated artifact lists can be pulled from the system on a regular basis. Label copy can be created directly in STAR, a report of the copy can be generated, e-mailed from the Window's Client application to a 2-D designer, and imported by them into Design software for enhancing. With each new exhibit we "manage" using STAR we realize new areas of efficiencies, and discover other staff who would benefit from access to the system. Let me know if you have other questions, would like more details, etc. Cathy Cathy Herr Computer Support Specialist, Collections Glenbow Museum [email protected] --- You are currently subscribed to mcn_mcn-l as: [email protected] To unsubscribe send a blank email to [email protected]
