Hi all, First I believe in this thread is some confusion about two different things: (i) adding a pdf to BibDesk for which there is no entry yet and (ii) populating meta data for an existing BibDesk entry, e.g. from whatever source. Since there are many ways to skin a cat, I wish to remind some of you that in the first case, when you know the DOI, e.g. by having the pdf opened in front of your nose, then it may also be very convenient to follow this workflow:
1) Select and copy the DOI from the PDF 2) Switch to BibDesk and use the AppleScript 'Import by DOI.scpt’ 3) Paste the DOI from the clipboard to the AppleScript when prompted to do so 4) Run the AppleScript 'Link PDF from Adobe Reader.scpt’ and if the publisher, e.g. Science, Nature and several others, make meta data available via DOI, then your done, i.e. you have a new fully meta data populated BibDesk entry and the pdf nicely linked and auto filed etc. This is at least a workflow I often use. If interested, find the needed AppleScripts at my site: http://se-server.ethz.ch/staff/af/bibdesk/ Then, in case (i) I believe what Januzz wrote is the right approach (thanks Januzz). Re case (ii) if you really wish to populate meta data while you already have a BibDesk entry (probably done it via a less desirable workflow) and have the DOI already entered, then this has basically nothing to do with a pdf. Forget that pdf and retrieve the metadata via the DOI. Since the vast majority of journals now offer citation downloads I believe it is much better to redownload the citation into BibDesk, i.e. create a new BibDesk entry and simply drag/drop the pdf from the old entry to the new one. Then delete the old BibDesk entry. That is likely to be more efficient and more successful than what was suggested here in some E-mails. Of course such a procedure could also be automated in case someone makes a grand transition from another bibliography system. However, as I wish to emphasize once more, that transition has not to go only via pdf’s. There may be much better approaches to accomplish such a transition. I would suggest to transfer also as many meta data as possible via text files and not to try to repopulate all automatically, which is likely to give worse results. Only if such a transfer should not be possible, I would resort to transfer only a minimum. Among the latter I consider should be the DOI’s and file names of the involved pdf’s. But this is only a last resort and I trust can be avoided in almost all situations. Regards, Andreas ETH Zurich Prof. Dr. Andreas Fischlin Systems Ecology - Institute of Biogeochemistry and Pollutant Dynamics CHN E 21.1 Universitaetstrasse 16 8092 Zurich SWITZERLAND [email protected]<mailto:[email protected]> www.sysecol.ethz.ch<http://www.sysecol.ethz.ch> +41 44 633-6090 phone +41 44 633-1136 fax +41 79 595-4050 mobile Make it as simple as possible, but distrust it! ________________________________________________________________________ On 09/10/2014, at 20h17, Januzzz <[email protected]<mailto:[email protected]>> wrote: Hi Antonio, here you go. 1. AppleScript for Hazel to import publication from PDF file <https://gist.github.com/Januzz/e7631c5d8d423cbb657b> 2. Python script that extracts DOI from first PDF page using PyPDF2 <https://gist.github.com/Januzz/01e46431b94dee83c977> As I had problems with some PDFs with the DOI not being correctly identified, I added the Option to enter it manually. If you or anyone wants to improve the AppleScript or maybe finds out how to make the regular expression in the python script work more reliably, you are welcome to modify them... Best, J -- View this message in context: http://bibdesk-users.661331.n2.nabble.com/importing-PDFs-tp7578078p7578132.html Sent from the bibdesk users mailing list archive at Nabble.com<http://Nabble.com>. ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ Bibdesk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bibdesk-users ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ Bibdesk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bibdesk-users
