Innovation
Written by Steve Stockstill   

Innovation isn't driven by force or continuing to ask the same questions.
Innovation is born of passion, freedom and sincerity.

Happy Easter!

--steve s

 
Anatomy of an Email Part 3: Email Attachments
Written by Steve Stockstill   

Previous installments in this series have covered the core email architecture of Time Matters, Internal Time Matters Email,and Internet Email in Time Matters. In the last installment of this series we cover the impact and connectivity issues of the email attachment.

History of the Time Matters Email Attachment

Throughout the history of Time Matters, email attachments have been somewhat problematic, primarily due to the resource load they put on the database. Email attachments, in part, contribute to the instability of the professional edition of Time Matters and are susceptible to database corruption. Several recent changes to the Time Matters architecture have significantly improved this issue. For instance, as of Time Matters 9 SR3, email attachments may optionally be stored outside the database. I highly recommend this option when using the professional edition. A more robust option, like TMTools, is offered by OTB Consulting. TMTools has a more robust method for managing attachments outside the database.


Attachment Options

 

Anatomy of the Time Matters Email Attachment

When an email with an attachment is sent from, or received into Time Matters, the attachment creates entries in several tables and is either stored within or outside the database.

Email Table
This table stores the primary email information for email saved to the “Email List”.  The “Attachment” column in the Email Table is extremely important as it identifies the email as an email having an attachment (for instance when Time Matters displays the paper clip in the user interface).

Attach
This is the table that contains the physical attachment or (as of 9+) the acknowledgment that the attachment file is being saved externally.

AttLnk
Is the table that relates (or matches) an email to the attachment(s) for that email. Since a single email can have many attachments, this table will provide the connectivity between a single email and many attachments.

Inbox Table
New internet email is saved to the Inbox Table. No external attachments or attachments records are created for new email stored in the inbox. This is a very important factor that many Time Matters sites do not recognize.

The Life Cycle of a Time Matters Email Attachment

CASE #1: Create and send an Internet email with a single attachment to one recipient.
In addition to the activity covered in previous articles, the following attachment specific database activity occurs:

One record for each attachment is created in the Attachment Table.
One record for each attachment will be added to the AttLnk Table.

CASE #2: Create and send an internal email with a single attachment to one recipient.
In addition to the activity covered in previous articles, the following attachment specific database activity occurs:

One record for each attachment is created in the Attachment Table.

For each attachment, one record for the sender and each recipient will be added to the AttLnk Table (internal emails are duplicated for each user). For example, there will be four AttLnk records when sending two attachments to one person.

CASE #3:  Receiving an Internet Email
In addition to the activity covered in previous articles, the following attachment specific database activity occurs:

Initially there is no activity in the Attachment or AttLnk Tables. New internet email is initially saved to the Inbox Table and all attachments are part of the Inbox.Mime column in the Inbox Table. This column holds a special version of the email that must be parsed to create the individual components of the email, including the attachment.

Implementing What We Know

Summarizing: When an email with an attachment is sent from, or received into Time Matters,  the attachment creates entries in several tables and is either stored within or outside the database. There are several factors that contribute to managing this process.

Options for saving Email Attachments outside the database should be carefully considered. When choosing to save files outside the database take measures to provide mirrored backups at the same time the SQL Database is backed up. Failing to do so can potentially create orphaned attachments in the event of a database restoration. 

Attachments for incoming Internet email are initially saved in the Inbox Table.

Attachments are not perished until the email record is permanently removed from the system. Many firms end up leaving a lot of deleted email in both the “Deleted” folder of the inbox as well as the “Recycle Bin”. This accumulation of otherwise hidden attachments can create unnecessary overhead in the database.

When the sender of an internal email deletes the email record, the attachment will persist until the recipient deletes the email. If the recipient leaves the firm, it may be possible for the attachment to become orphaned in the database.

Data Equity’s SharpShooter has several tests to aid in the management of Email Attachments.

 

 
To the Time Matters Community
Written by Steve Stockstill   

Having been explicitly told not to modify the Time Matters database, Data Equity is unable to adequately provide two-way database services for our Time Matters add-on products. This issue most directly impacts our newest product, GoogleConnect 4TM. We are releasing GoogleConnect with the restriction of allowing Time Matters to “push to Google” only. GoogleConnect will not update Time Matters with changes or new data from Google. The directive also restricts our ability to meet consumer requests to provide two-way database services for MobileTM.

Data Equity has worked with LexisNexis management by extending proposals as well as volunteering to assist in any effort to overcome this unfortunate restriction. Having worked diligently toward this effort for over two years, we are not hopeful  that the restrictions will be lifted in the foreseeable future.

During the 2009 LexisNexis Practice Management conference, Data Equity received strong support from the Time Matters community by encouraging LexisNexis management to rethink this strategy. Unfortunately, the momentum from this outpouring has subsided.  We encourage our customers and other concerned Time Matters users to continue to let LexisNexis know the value of a vibrant third party community.

With hundreds of sites using our Time Matters add-ons, we expect to continue helping to make Time Matters the best practice management software in the industry.  Data Equity is committed to building on our successes by continuing to improve our existing products, releasing new products, and providing a foundation for the future of practice management.


Steve Stockstill
President, Data Equity LLC

 
File Synchronization for Time Matters
Written by Steve Stockstill   

A good file synchronization product can be a great companion tool for Time Matters. There are two very different uses for file synchronization as it pertains to Time Matters.

1.    Local: Synchronizing documents and email attachments in conjunction with the Time Matters built-in synchronization between “host” and “remote” computers.

2.    Enterprise: Synchronizing external files across multiple locations in conjunction with SQL Server Replication. These files include documents, email attachments and full text sync files.

Since these two uses may require potentially very different synchronization solutions, I’ll break the conversation down by “Local Synchronization” and “Enterprise Synchronization” models.


Local Synchronization

Many of us have been using local synchronization products for many years. In addition to traditional synchronization tasks, this genre of product is often used to perform file and folder level backup operations. Typical functionality you should look for includes:

The capability to perform bi-directional or one-way synchronization.
Can copy open files.
File versioning
Encryption and compression support
Bandwidth throttling
Deletion propagation to ensure that files are removed when appropriate.
Chained synchronization support (Computer A syncs to USB, USB Syncs to Computer B
FTP, WebDav and Amazon S3 Support (with SSL option)
Selective include/exclude filters (by name pattern, date, etc)
Automation support (logging, scheduling, real-time: when files change)

Three of the most popular products for this level of synchronization are: GoodSync, SyncBack and ViceVersa. Each of these products offer most of the features listed above, offer trial editions and are normally priced between $30 and $50.


Enterprise Synchronization

This class of product is considered on the “Enterprise” scale of software and generally provides a higher degree of fault tolerance and is designed for multi-site implementations. These products generally include the same features as the “Local” class products with the following significant additions:

Always on, real-time synchronization and/or mirroring.
Byte level differential synchronization (only transfers changes in large files) beneficial when trying to synchronize large files where only a small amount of data has changed.
Support for transferring “locked” files.
Push or pull from any direction, server to server, workstation to server, server to workstation.
Support for multiple operating systems (Windows, Linux, Mac).
Centralized (usually web based) management console.

A few compelling features in this group include byte level file updates for large files, continuous monitoring for file changes and the ability to transfer locked files. This functionality allows for the possibility of centrally managing the Time Matters Data Indexer at a single site, opposed to trying to manage the process at multiple locations which is, at best, fraught with difficulties.

Products with these capabilities are significantly more expensive, ranging in price from $600 to $1000 and more, depending on the number of sites in the synchronization cluster. Some popular choices in this category include PeerSync, FileReplicationPro, LinkPro, and SureSync.

 

Hybrid Solutions

PowerFolder

One product that includes functionality from both Local and Enterprise models is PowerFolder. PowerFolder is licensed for $30 per year with significant discounts for multiple licenses. In addition to the core functionality of local synchronization tools, PowerFolder also supports byte level differential synchronization for large files. PowerFolder will also allow internet based synchronization which is unique when compared to other products in this price range that require WebDav or FTP for internet connectivity.

Super Flexible File Synchronizer (SFFS)
Like PowerFolder, SFFS will perform differential file synchronization which can significantly reduce bandwidth by only transferring the “changes” in the file as opposed to the entire file.

 

Conclusion
I have been using GoodSync for mirror backups to Amazon S3 and a local data store. It’s fast, accurate and very flexible to setup and maintain. We are currently testing PowerFolder and Super Flexible File Synchronizer (SFFS)
due to their ability to synchronize partial file updates.

The ability to synchronize partial file updates will allow us to configure Time Matters replication in a new way. We are disabling the TM Database Indexer on remote sites with the host site managing the index and synchronizing it to the remote sites. We’ll keep you posted on how this testing goes.


 
<< Start < Prev 1 2 3 4 5 6 7 8 9 10 Next > End >>

Page 3 of 16

Site News

Legal Technology News

Sponsor Spotlight

Hosted By Site5.com

Site 5 Offers a phenomenal deal: 750GB disk space, 7.5TB bandwidth, unlimited domains, $5 a month.

Archives

Blog Archives

Sponsor Spotlight

  Your Advertisement Here

Blog Archives

Links

Sponsor Spotlight

Your Advertisement Here

External Links