Read a File's Details

Purpose: see what Forage knows about one file: where it is, what Forage did with it, whether its contents were read and, if not, why.

1. Open a file. Select a file in Search results, or a file listed on Exceptions, Labels, Overview, Files to Protect, Ask AI a Question, Reports or the Log. The File details window opens over the page. Close it to go back to where you were.
2. Read the top. It shows the file's name and a tag for where it is kept, SharePoint or Archive. Beside it are its reading state, Waiting, Being read, Searchable or Couldn't be read, and how much was read: Read in full, Partly read, Not read or Not read yet, with the reason after "because", for example "Not read, because it's password-protected". A file Forage left out on purpose, such as a file that is not a document, says "Skipped" in grey. For a file that has not been read, a line under it explains that Search still finds the file by name and folder, and that rules on its name, folder, type, size or date still apply.
3. Read the address. A file in SharePoint has a link that opens it there. A file in the archive shows its SharePoint address as text to copy, says it will not open until the file is restored, and offers Restore from the archive, which opens the Archived Files page in a new tab, searching for the file. Opening that page restores nothing.
4. Under About the file, read the Site, Size, Modified, Last accessed, In the archive, Deleted in SharePoint and Archive placeholder rows. Where SharePoint has no file to ask, a row says Not known yet while Forage is still waiting to check again, and Not known once Forage has stopped looking. For such a file, Deleted in SharePoint says "Not known, as it wasn't found there", because a file that cannot be found has not been recorded as deleted. For a file SharePoint does not have, if a read file of the same name is in the same or another site, the window lists it, saying it may be the same document, moved. For a file that was deleted in SharePoint and kept by the archive so it can be recovered, extra rows say when it was deleted, who deleted it and where the kept copy is.
5. Under What Forage did, read the File type, when it was Listed, which site it was Moved here from (if it was moved), when it was Made searchable, its Last problem (or Why it is waiting, with when Forage will try again), How much was read, the number of Pages, and, when only part of the text was read, Text read with the reason.
6. Under Identical copies, see how many other files have exactly the same contents, byte for byte, with each one's name, whether it is in SharePoint or the archive, and its site. Select a name to open that file, or, for a file in the archive, to search for it on Archived Files. If there are none, the window says so. A file with copies shows "Duplicate: 1 other copy", or the number of copies, in Search, and Reports has a Duplicate files report.
7. Under The text Forage read, select Show text to read the text Forage took from the file, and Hide text to close it. The window says how many characters it shows out of the total, and that this is the text the rules check. A file that was read and held no text says so, and that nothing went wrong; a file that has not been read has no text to show.
8. Under Problems reading this file, see each problem with its date, the step it happened at (for example while Forage was downloading the file), whether the file was still in SharePoint or the archive at the time, and, if Forage tried again later and read the file, that it did. If there were none, the window says so.

Good to know: the window changes nothing in SharePoint or the archive, and opening a file is recorded in the Log. The labels recorded for each result are shown in Search, and Labels lists the files under each label with the rule that found them (see what a label or rule found).

Questions go to sales@smikar.com.