This patch adds a setting that allows the node form to submit immediately after the form is populated using the DOI on the assumption that the DOI provides accurate information that is sufficient for citation. Combine with automatic PubMed automatic updates and pathauto to create a use case for skipping the manual node-add form review.
Furthermore, the system looks for a self-referencing destination query string parameter that allows an admin to create an interface that kicks them back to the node creation to enter the next DOI. The URL for rapid entry would be formatted like this:
http://example.com/admin/node/add/biblio?destination=admin/node/add/biblio
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | biblio-autocreate_nodes-1765924-1.patch | 4.57 KB | stackpr |
Comments
Comment #1
stackpr commentedPatch attached.
Comment #2
rjerome commentedI presume you are aware that you can import list of DOI's from a text file, much like you would with a bibtex or EndNote file?
Comment #3
rjerome commentedOpps, I engaged the keyboard prior to engaging the brain. I take that back you can't do that with DOI's, just with PMID's. Perhaps we should do the same for DOI's?
Comment #4
stackpr commentedThat does sound helpful, but it addresses a different use case than this patch.
The specific use case I am looking at is that we get reference lists at the end of articles without DOIs or PMIDs. We'll use the author-title lookup feature to find DOIs and then auto-submit from there. When CrossRef is able to find an article, the process will have now been reduced to:
A. Click "Add biblio" -> B. copy/paste author/title -> C. select appropriate DOI -> D. node is created and kicks you back to (B) without further interaction.
My association works primarily with university faculty that publish regularly (such that they have DOIs), but none of them use citation management software, and very few of them have heard of DOIs. As a result, my focus currently is on making it really quick and easy to manually migrate citations (that may not be structured properly) into biblio nodes for consistent handling and presentation - and eventually to provide CrossRef cross-linking compliance.
Comment #5
liam morlandThis version is no longer maintained. If this issue is still relevant to the Drupal 7 version, please re-open and provide details.