My organization will be on D6 for another 1-2 years, and we are rolling out biblio on our site over the next month. I have a handful of patches varying from typo fixes to minor feature enhancements, but the project issue queue is already seemingly overwhelmed and the active developers appear to be focused entirely on D7. Can I get co-maintainer status to keep D6 active? I'll try to port any feature enhancements to D7 as I go... Thanks!

CommentFileSizeAuthor
#2 biblio-on20120807.patch17.88 KBstackpr

Comments

rjerome’s picture

rjerome commented

Could you post the patches so I can take a look at them. I think you will find that issues with patches supplied will be more likely to get rapid attention since, in theory, they won't require large amounts of my time :-)

stackpr’s picture

stackpr commented
Status: Active » Needs review
StatusFileSize
new biblio-on20120807.patch17.88 KB

I had to manually separate my patch files since some changes affected the same files. One patch covering all these issues is attached in case there is a problem with one of the individual patches.
#1717938: Handle biblio_year gracefully when CrossRef returns incomplete date info
#1717944: Fixed typo and missing braces
#1717950: Automatically populate pubmed_id and pmcid using DOI via cron
#1717952: Protect DOIs on nodes (avoid duplicates and edits)
#1717956: Look up DOI (for node creation) on CrossRef by author/title

Feel free to close this issue if the individual patches apply well enough for you to review. I should have discrete snapshots for any further changes. Thanks!

stackpr’s picture

stackpr commented
Status: Needs review » Closed (won't fix)