hseg

Though looking at `unique-document-keys`, the only way this can help is if this also sets `ref` predictably -- otherwise we're back to papis happily reinserting the same file multiple times

Checking the 1260 PDFs on my system just for the presence of an author and title field, 56% contain both, 15% contain an author, and 27% contain neither. Aggressively filtering...

Fair enough. Perhaps the most sensible solution in the short term is an option to emit the `info.yaml` produced from each extractor and to have interested users manually merge them,...

Perhaps have the `files` entry in the `info.yaml` carry a checksum of each file, and compare the checksums instead? Indeed, with such a setup, both #695 and `duplicated-keys` could satisfy...

Hadn't thought of that usecase, thanks for the pushback. That seems a perfectly reasonable alternative, moreover the checksums could be used for the per-document deduplication I suggested as an extension,...

Testing, I am getting the following behaviour: Without `$XDG_CONFIG_HOME/papis/`: > $ ls "$XDG_CONFIG_HOME/papis/" > ls: cannot access '/home/gesh/.local/etc/papis/': No such file or directory > $ papis > add browse config...

Not yet, can probably check Tuesday. El 13 de marzo de 2024 20:29:50 GMT+02:00, Alex Fikl ***@***.***> escribió: >@hseg Have you had a chance to look at this again? >...

OK, so testing it, it all seems to be fixed! Perhaps the only thing I'd add here is that `papis init` seems to be a common codepath (i.e. I'd expect...

Another example: Trying to add by PDF url https://www.ams.org/journals/tran/2001-353-07/S0002-9947-01-02800-8/S0002-9947-01-02800-8.pdf (which again, in hindsight is lacking any sort of DOI information in the document, but not warning about this failure mode...

Possibly replacing the `[INFO]` message in your screenshot with: ``` [WARNING]: No metadata found, document won't be detected as existing ``` or ``` [WARNING]: Document has no metadata! It won't...