Kraft & Kennedy, Inc. provides technology and strategic consulting services to law firms, corporate legal departments and financial services firms. We can help you analyze, plan, implement and manage business and technology solutions to optimize your organization's functionality and processes.
Security is always a concern in a law firm, and is especially important in the legal department of a corporation. Lawsuits sometimes include the company’s co-workers, competitors, or other sensitive information, where certain matter information needs to be completely hidden from all but a few matter assignees. Securing documents or DMS folders is often simply not enough protection.
Does the system hide the matter from appearing when doing a table look-up on a search form? Does it hide the matter when accessing the matter table via the DMS web module? For some cases, you want to hide the actual matter itself, so users won’t even know it exists.
Continue reading…
Whether or not SharePoint can be a viable DMS at a law firm has been a big point of contention in the legal community. A lot of this comes down to the mentality and size of the firm, and the specific requirements that the firm has for document management. With proper planning and one or two simple addins, SharePoint may be a viable DMS for certain firms that are flexible and willing to invest in a development effort.
The advantages of using SharePoint as a DMS are many:
Recently, Kraft Kennedy became one of the first integrators in the industry to complete an implementation of iManage 8.5 GA in production at a law firm. This particular firm is taking advantage of the predictive Email Filing and Email Management capabilities of FileSite 8.5 GA and the WorkSite Communication Server 8.5 GA, complete with OffSite for offline access and the iManage 8.5 IDOL Indexer handling search requests.
After the initial roll-out of the GA release, there were several issues that appeared, and were confirmed with Autonomy iManage technical support. The first issue involved security inheritance, and manifested itself when saving documents into folders with specific users or groups added to the permission ACLs. In these instances, the document would simply inherit the default security of the folder (Public, View, Private), ignoring any additional ACLs. The second issue regarded Outlook stability, where toggling between a WDS-integrated Outlook search and the Inbox would result in a crash of Outlook. This crash was fairly common, since users tend to search their mail items daily. The third issue was more cosmetic, but annoying nonetheless. When disregarding a draft email, the message remained in the Drafts folder of Outlook. Again, not earth-shattering, but annoying to have to see Drafts (15) in your mailbox after a few days.
In the past couple weeks, Autonomy has released WorkSite Server 8.5 Update 2, along with the FileSite/DeskSite/OffSite/EMM 8.5 All Languages release (you will know if you are running the All Languages release of the iManage client software because the build number will be 8.5.200.x). We are happy to report that this back-end and client update neatly addresses and resolves all three of these issues, in addition to several others. Outlook is more stable, and there is no longer any issues with security inheritance. If anyone is hesitant about moving to iManage 8.5, rest assured that the latest release appears to be stable and functions as advertised.
For those with access, more information on these updates can be found in the WorkSite 8.5 Resource Center at the iManage technical support web site.
World Software Corporation just released their latest version of their DMS product, Worldox GX2. It is available for new installs now, but the upgrade package for existing customers is still a few weeks away. The upgrade will be free for customers who are current on maintenance. A couple of the key new features of Worldox GX2 are the improved Outlook integration and the ability to create Ethical Walls.
We have been running a Beta version in our virtual research lab for a few months now, and tested these new features as well as a few other highlights.
A few screenshots and comments are below the fold.
In my previous post, I discussed ways of bringing the legal user community into the matter centric design process. That’s only the first battle. Once attorneys are able to visualize the concept behind the organizational folders of a matter centric WorkSpace, they may want the structures to mimic what they are used to — especially if they’ve never used a DMS before. They may want to stay within their comfort zone. And these may be the most powerful voices in the Firm.
Usually, what they are used to is an inconsistent, multi-level directory structure with custom folders containing perhaps a handful of specifically categorized documents each. This kind of structure makes sense when the only way of finding a document is by knowing which folder it’s in — as is the case without a DMS. In this scenario, you wouldn’t want to scroll through hundreds or thousands of documents in a folder. Rather, if you can limit the number of documents in a folder to a handful, then it is easier to find the document you need. This is what leads to the numerous directory levels and (in my humble opinion) overly specific classifications.
In the DMS world, there are much better ways of finding documents. The obvious option is the full-text search, which will provide efficient results (given the user properly knows how to perform a full-text search). In addition to the search, folder lists can be sorted and filtered based on any metadata column, and the WorkSite Miner is a nice utility to carve up the contents of a folder into more manageable groups.
iManage offers two levels of classification for documents — the Class (which generally corresponds to a WorkSpace folder) and it’s child Subclass. As the designer of the WorkSpace structure and metadata, you may get requests for numerous Subclasses. There are two main disadvantages of using Subclasses. First, requiring the Subclass adds dreaded extra clicks and keystrokes to each save action. If the Firm decides on using Subclasses, it is a best practice to make them required. If they are optional, they lose all value. There’d be no guarantee that searching for the “Loan Agreement” Subclass will return all loan agreements. This leads to the second key disadvantage — it will prevent the proper update of metadata when dragging-and-dropping documents from one WorkSpace folder to another, since it is up to the user to select a Subclass when saving into a folder.
So how do we get attorneys to accept not using Subclasses? Make sure they grasp all the different ways documents can be identified, sorted, filtered, and found in the system. Perhaps bring up the idea of a naming convention for the description of documents. Or perhaps make a deal — try it without Subclasses for six months, and then the issue can be re-evaluated. Chances are they will appreciate the ease of simply saving into a WorkSpace folder, and agree that there is no need for Subclasses. After all, less is more.
So you’ve decided to implement Matter Centricity at your firm. Whether you are using Autonomy iManage (formerly Interwoven), Open Text eDOCS (formerly Hummingbird), or another Document Management System (DMS), the basic idea behind Matter Centricity is the same — to present virtual Redwelds for each matter, with folders to categorize and classify documents within. Couldn’t be simplier!
But in order to design these virtual Redweld structures (iManage calls these “WorkSpaces”), input is needed from each Practice Area or department of the firm. Since many of the users have no idea what Matter Centricity is, and some may not have any idea what a DMS is to begin with, it can be difficult to obtain the information needed to design a structure.
Here are a few tips to get the message across:
Using these tips, the hope is not only that the users better understand the concept in general, but also have a better idea of how their input for the design will be translated into technology and their daily work process.
In future posts, I’ll discuss how to interpret all this input and combine it with iManage and Kraft Kennedy’s best practices.