Import load files into FreeEed

[Josh Siegel]

We received data as a load file export from Concordance. We do not have concordance, and natives cannot be produced in this case due to privilege.

Is there a way to import concordance load files into FreeEed? I created a native.zip file of the produced images and text folder, mirroring the standard structure of a FreeEed native.zip file, as well converting the .dat index file from concordance into a load-#.csv; but the upload from the project GUI will not import the concordance data.

Is there a way to import this data so that we might use FreeEed to review projects created in concordance?

Thanks,

[Mark Kerzner]

Hi, Josh,

Let me restate your question, to make sure I understand it correctly.

You have the CSV load file, and you have the native.zip. You would like to import this into the review (FreeEedUI).

I am working on a similar requirement now: I have a CSV file with additional metadata field, and I want to import them together. However, in your case, what stops you from extracting the native.zip and processing it in FreeEed again?

We may need to talk about this, would you like to schedule a call Book a call with me here?

Thank you,

Mark

--
You received this message because you are subscribed to the Google Groups "freediscovery" group.
To unsubscribe from this group and stop receiving emails from it, send an email to freediscovery+unsubscribe@googlegroups.com.
To post to this group, send email to freedi...@googlegroups.com.
Visit this group at https://groups.google.com/group/freediscovery.
For more options, visit https://groups.google.com/d/optout.

[Josh Siegel]

The issue is that we do not have access to the native files, nor will we be able to get access to them, due to privilege.

We do, however, have the metadata in the concordance DAT file index, as well as images and text extracted from the native files. I would like to import this data, exported from concordance, into FreeEed for our employees to review in FreeEed. 

There is an excellent article on how to export from FreeEed into a Concordance load file, but nothing on how to go the other way, from a produced concordance load file into FreeEed for review.

On Monday, January 23, 2017 at 10:00:06 PM UTC-5, FreeEed Team wrote:

Hi, Josh,

Let me restate your question, to make sure I understand it correctly.

You have the CSV load file, and you have the native.zip. You would like to import this into the review (FreeEedUI).

I am working on a similar requirement now: I have a CSV file with additional metadata field, and I want to import them together. However, in your case, what stops you from extracting the native.zip and processing it in FreeEed again?

We may need to talk about this, would you like to schedule a call Book a call with me here?

Thank you,

Mark

On Mon, Jan 23, 2017 at 5:43 PM, Josh Siegel <jasie...@gmail.com> wrote:

We received data as a load file export from Concordance. We do not have concordance, and natives cannot be produced in this case due to privilege.

Is there a way to import concordance load files into FreeEed? I created a native.zip file of the produced images and text folder, mirroring the standard structure of a FreeEed native.zip file, as well converting the .dat index file from concordance into a load-#.csv; but the upload from the project GUI will not import the concordance data.

Is there a way to import this data so that we might use FreeEed to review projects created in concordance?

Thanks,

--
You received this message because you are subscribed to the Google Groups "freediscovery" group.

To unsubscribe from this group and stop receiving emails from it, send an email to freediscover...@googlegroups.com.

[Mark Kerzner]

Hi, Josh,

So you have three inputs: *.dat file, text files, and image. I presume that

1. *.dat can be converted to a CSV.

2. Text files can be matched to the *.dat, line by line.

3. Images are PDF or TIFF.

If this is all true, then we can import the *.dat, one line at a time, match it to the text, and bring this all into the review. This import can be a ccomplished by adding such an option into FreeEed.

For the image, I see neither place (since the image, in fact, is a second form of the same document), nor place. Do you need them?

Thank you,

Mark

To unsubscribe from this group and stop receiving emails from it, send an email to freediscovery+unsubscribe@googlegroups.com.

[Josh Siegel]

That is almost correct. We have folders for Data, Images, Text, and Native. Some native files were determined to not be privileged, and were produced. The majority of the production is in tif and text file format, however, so if we could not get the natives to import, that would still be workable for us, since every native file is also included as an image(though not every image file has a native). In short, we could do without native in this case.

The other issue I ran into was that the metadata fields do not map 1-to1 between the concordance load file and FreeEed. I saw reference in the manual to altering the metadata fields in the "config/standard-metadata-names.properties" file, but the file does not appear to exist in the config directory, so I would need to add fields to the FreeEed import somehow, or lose data on the Bates numbers, etc.

Thank you for your responses on this, I do appreciate it. FreeEed seems like a useful tool and I'd like to be able to use it for load file review as well as generation, and it seems like it should be able to handle it.

[Mark Kerzner]

Hi, Josh,

The metadata has been moved to the database. It is called 'freeeed.db' and is found in the program directory. You can use this browser http://sqlitebrowser.org/ to see and change its values.

M

To unsubscribe from this group and stop receiving emails from it, send an email to freediscovery+unsubscribe@googlegroups.com.

[Mark Kerzner]

Hi, Josh,

I think I get it. You can have the document come from many possible places: txt, tiff, native. You can also have the metadata come from the document, or from the load file.

I think it would be a useful addition. But how do you propose to match the source documents?

For example, can you start with the load file, use the doc id, and try to find it in the txt, tiff, pdf folder? We would also set the order of preference: try native fist, then tiff, etc. And this order should be selectable per project.

How close are we?

Thank you,

Mark

[Mark Kerzner]

Hi, Josh,

Here is the implementation described, http://shmsoft.blogspot.com/2017/02/freeeed-for-ediscovery-response-and-for.html

Thank you

[Josh]

Awesome, thank you!

You received this message because you are subscribed to a topic in the Google Groups "freediscovery" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/freediscovery/ViFmIDaQ43c/unsubscribe.
To unsubscribe from this group and all its topics, send an email to freediscovery+unsubscribe@googlegroups.com.