Status Update Page

mdlandrec.net Version 3 Roll Out and plats.net Enhancement

Updated June 8, 2009









mdlandrec.net Version 3 Roll Out

Load testing of application server cluster configuration has begun. Archives also is bringing in some consultant help to assist with system optimization. If all goes well, cluster testing will be completed successfully, any updates to test script and system documentation made necessary by revisions to the application code will be incorporated, and revised and updated system reports and statistical analyses will be in place by the end of the month. Once cluster load testing is successfully completed, internal and external functional testing can begin on or about July 1.

Functional testing should take an additional couple of months, and is expected to reveal user issues that will need to be addressed and corrected. Once these issues are corrected, we will need another round of internal and external functional testing before the system can "go live".

plats.net Enhancement

At the May 18th meeting of the Automation Committee, I was asked to explain more fully Archives' plans to incorporate plats.net into mdlandrec.net.  Specifically, I was asked to lay out in more detail Archives' plans for integrating these two systems, the primary obstacles that we anticipated would have to be overcome in this effort, and a possible timeframe for completing this project. Let me begin by saying upfront that no Archives resources have yet been devoted to combining mdlandrec.net and plats.net into a single system. At this point, that goal remains more a concept and a long-term objective rather than a project plan. But that being said, we have begun to identify some of the major questions that need to be answered, issues that need to be addressed, and design decisions that will have to be made for the integration of plats.net with mdlandrec.net to be realized.

Plats.net and mdlandrec.net, developed at different times and incorporating very different functional requirements, are two very different systems in design and function. A great deal of re-programming and re-design will be needed. While they differ in almost every way, two of the more obvious examples that might serve to illustrate some of the issues are 1) what each serves up as the record, and 2) how the user finds this record.

How does each system serve up "the record"?

How does the user find the record? At this time, we do not know how we will reconcile these very different approaches into a single system. Both approaches have advantages, and both have disadvantages. Neither is a perfect system. Perhaps the best place to begin would be to work with the clerks to develop a better understanding of the business requirements of a new, combined system.

Previous Reports


Last revised July 13, 2009