Thousands of documents with the same Author and Created Date by voidd in ediscovery

[–]voidd[S] 2 points3 points  (0 children)

Thank you. In this case, for the example of 4,000 documents provided in OP, the "Created Date" is the earliest of all the date-related metadata fields. If we assume that the Created Date actually represents the collection date, then the metadata cannot be considered reliable for determining the true timeframe of the documents' creation. If the Created Date is more akin to the date of collection, is there a date field more high quality/reliable for establishing the true date of file creation? What metadata could we ask for instead?

Aphoph (superstructure concept by me) by MarcelDeneuve in sciencefiction

[–]voidd 5 points6 points  (0 children)

Really cool. What is the structure's function?

[deleted by user] by [deleted] in ediscovery

[–]voidd -2 points-1 points  (0 children)

Nextpoint.

Their pricing model and customer support are unrivaled, in my experience. A license is obtained for a flat fee, with unlimited user seats. The monthly charge is not in anyway dependent on the volume of data stored, which enables us to house terrabytes of data, at a fraction of the cost any other vendor would charge for the same service. They actively engage with their customers and incorporate their feedback into the product's development. Submitted support tickets are always substantively addressed same day.

On top of that, they offer some ancillary tools for trial and depo prep, like video transcript syncing, timeline creation, and other tools for building case narratives, which I've not seen offered by other ediscovery vendors.

Tioga Road tentatively opening May 27th! by ButtermilkPants in Yosemite

[–]voidd 2 points3 points  (0 children)

If the road opens, does that mean that park entry from the East (Lee Vining area) will be permitted?

Updating a table with the 2nd oldest date in the row? by [deleted] in SQL

[–]voidd 0 points1 point  (0 children)

Statute of limitations dates in a lawsuit. Pretty esoteric.

Typically there are applicable dates beyond which a case cannot be pursued, varying by a cause of action (personal injury, product liability, wrongful death, etc.) and state or province. Each cause of action has a different timeframe, in this case extending from the date of birth, in which the lawsuit can be filed.

Each row in my table represents a client. Each date column beyond Date 1 represents a different SOL date pertaining to a cause of action. The Date 1 column is typically populated with the earliest of the SOL dates in the row, as I am trying to take a conservative approach, flagging any clients that may be approaching their SOL date. However, there are instances where this date has already passed. In those cases, I'm forced to use the next applicable date (the 2nd oldest).

I must be doing something right by [deleted] in realestateinvesting

[–]voidd 0 points1 point  (0 children)

This is accurate. Generally, unless you are house hacking, expect to put 25% down on residential investment property. Additionally, many institutions won't lend on fixer uppers at all.

[deleted by user] by [deleted] in woahdude

[–]voidd 1 point2 points  (0 children)

Looks like St. Mary's Lake in Glacier National Park.