39 ms·
I usually rename them manually, with Unix-y filenames that start with the last/company name of the author (e.g., `adobe-postscript-language-reference-manual.pdf
by neilv 4y ago
I usually rename them manually, with Unix-y filenames that start with the last/company name of the author (e.g., `adobe-postscript-language-reference-manual.pdf`, `blandy-programming-rust-1e-early.epub`).
In a company, I put relevant ones in a Git repo, or sometimes in a wiki. (In any case, the company/engineering wiki will probably reference them, and code in the Git repo might as well.)
For non-public documents, I track the provenance of each. In a company Git repo, usually in `README.md`, or maybe `<name-of-the-doc-file>.README.md`. And you have to be clear whether something was received under NDA or other restrictions, which can restrict sharing, quoting, facts, or even who within the organization is allowed to look at it.
For paid docs I personally own, I'm currently experimenting with inventorying all my paid digital content (books, videos, games) in GnuCash (especially since the payment transactions will be there). (I'm still slightly uncomfortable with, say, a $50 `.pdf` just sitting in my homedir, without indication that it's not public and shareable.)