joeldebruijn

joined 1 year ago
[–] [email protected] 1 points 2 weeks ago

Must admit, those fields are precisely the ones I use in my filenaming convention. Other DMS put that in their databases but alas that's just trading one stack for another.

Other ones put it in XMP metadata of the pdf themselves. But I guess the work involved would be similar.

[–] [email protected] 4 points 2 weeks ago

If it's just bookmarks can recommend Floccus and LinkWarden.

[–] [email protected] 2 points 2 weeks ago* (last edited 2 weeks ago) (2 children)

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.

[–] [email protected] 1 points 2 weeks ago (4 children)

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.
[–] [email protected] 5 points 2 weeks ago* (last edited 2 weeks ago) (2 children)

I think he meant save the actual notes themselves. Often necessary for sync engines to replicate the notes to other devices and manage version control.

[–] [email protected] 3 points 2 weeks ago (2 children)

Because the actual export, transform and loading of multiple banks and accounts data is cumbersome its holding me back.

So curious to read about GoCardless.

But is that also for consumer?

And is it this: https://gocardless.com/pricing/

[–] [email protected] 1 points 3 weeks ago

For a moment I thought it was ... Cad Bane ... Sorry not sorry 😁

[–] [email protected] 18 points 3 weeks ago (1 children)

"He himself is a billionaire" ... Glad the forker made that clear in the first paragraph.

[–] [email protected] 7 points 4 weeks ago

Employer on a job meeting on an employer device that is. Clients? Not so much ...

[–] [email protected] 0 points 1 month ago* (last edited 1 month ago)

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.

view more: ‹ prev next ›