I would say these are 'tagged'; organized is a bit of a stretch, IMO.
This is some sort of searchable index that reminds me a lot of what the web was like prior to Google; the Altavista days. It's just a jumble of poorly formatted text that isn't really contextually aware and is largely useless for the volume of textual documents.
Then there's the whole 'I landed on an email that offers the text of an email that, I assume, the pertinent information is in the attachment listed, of which I cannot easily access.
--
I'd be more interested to see how you enhance this in v2.
Thanks for your feedback. Agreed it's not perfect and can be improved. That said, I wanted to put it out there in case it did help someone, even in it's imperfect state.
> It's just a jumble of poorly formatted text that isn't really contextually aware and is largely useless for the volume of textual documents.
I did a quick spot check and the lack of _clear_ date field is going to make contextualizing a bit trickier. It looks like most of the `email` have them but other types like `report` may have an unknown "first, created/circulated internally" date and a broader "the public can see it" date.
Nevertheless, it's only a matter of time before this gets loaded into a graph DB so the context becomes more apparent similar to what the journalists did for the panama papers.
This is some sort of searchable index that reminds me a lot of what the web was like prior to Google; the Altavista days. It's just a jumble of poorly formatted text that isn't really contextually aware and is largely useless for the volume of textual documents.
Then there's the whole 'I landed on an email that offers the text of an email that, I assume, the pertinent information is in the attachment listed, of which I cannot easily access.
--
I'd be more interested to see how you enhance this in v2.