Joël de Bruijn

  • 2 Posts
  • 118 Comments
Joined 1 year ago
cake
Cake day: June 23rd, 2023

help-circle







  • I don’t know.

    • I don’t need formatting but it doesn’t get in the way either. So I am not bothered by it.
    • Also pdf and especially PDF/A standard is widely used for archiving and compliance regulation concerning archival and preservation.
    • If you want text the same tactic goes: just export in bulk to txt instead of pdf

    My main point is: Why would you want a mail specific stack of hosting, storage, indexing and frontends? If it’s all plain text anyway so the regular storage solutions for files come a long way.

    There is an entire industry (which has its own disadvantages) to get communication artefacts out of those systems and put it in document management systems or other forms of file based archival.


  • I had roughly the same goals ( archive search 2 decades of mail) but approached it completely different: I export every mail to PDF with a strict naming convention.

    • Backend: No mailserver, just storage and backup for files.
    • Search: based on filenames FSearch and Void tools Everything. I could use local indexing on pdf content.
    • Frontend: a pdf viewer.





  • It seems like a no-brainer but actually no.

    Quick test would be for example if there are:

    • at the beginning of the music library a lot of “no artist name” “no album name” entries, so the foldername isn’t used at all.
    • a lot of artist with their own entry with just one album and one song because the actual albumartist collaborated on one song with them and the mp3 resides in the same folder but they got split in the library.
    • if the player doesn’t show music which isn’t part of Playlist.

    So my conclusion is their are even 3 types and corresponding mangement:

    • Folder based requires file management
    • Meta data based requires tag management
    • Playlist based requires Playlist management

    Often players make combinations also I guess.