1. Government Reports and various other publications may not have any authors, other than the publishing institution. However, if the Authors fields are left blank, the citations do not appear in the bibliography listing unless sorted by a column other than "author". Also, an acronym (e.g., "USEPA") can not be used because Biblio needs a "firstname" or "first initial).
2. It is customary when citing publications with numerous authors (sometimes with only 3) to use "et al" (which means "and others") for the second or last author. However, Biblio considers "et al" a legitimate author and includes it in the authors list.
3. IMPORTANT! Clicking on the links to non-first authors in the Authors table (/biblio/authors) yields "No items found" even though it should. The PRIORITY of this issue should be higher, because the table become dominated with author links which do not yield results (even though they should).
There may be solutions or ways of handling these two situations, but I have not found them yet.
| Comment | File | Size | Author |
|---|
Comments
Comment #1
rjerome commentedIn response to these issues...
1) I've fixed the name parser so that acronyms such as USEPA will not throw any errors (I haven't push the changes to the repository yet though. By setting the category to "Primary" and the role to "Corporate" as shown below, they will show in the list sorted by author.
2) The module automatically inserts et al as required based on the style chosen. You should never enter et al as an author. If you are entering a publication which has et al in the author list, you should leave it out and put the other authors, if you don't know the remaining authors, then just put the ones you have.
3) Clearly there is something wrong with your installation as this should never happen. You might want to visit your "admin/config/content/biblio/author/orphans" page and see if you have any "orphaned" authors. I didn't think they would show up on the /biblio/authors page, but they may be the cause of this issue.
Comment #2
SandPond commentedJerome: Thanks greatly for assistance!
I found the problem to (3) above. I had two sandbox installations that were totally different than the one experiencing the issue. Sandbox #1 was "base", so I installed Biblio, and did not experience the issue. Sandbox #2 was similarly configured to my main system and illicited the problem so I suspected a module conflict or configuration setting was responsible. It turned out to be the latter. I went through and matched the config of #2 to #1, and the issue was resolved. Then I changed setting-by-setting, doing a cron between each, in order to determine the specific setting:
PROBLEM: If the "Biblio Settings/Preferences/Sorting/Sort By" value is set to "Author", or the sort order on the Biblio bibliographic listings page is set to "Author", then ONLY the first author link will work! This true for both the Biblio bibliographic listings page and the Biblio authors listing page.
That is:
WORKS!
Second author link in table of authors from http://myDomain.com/drupal/biblio/authors:
http://myDomain.com/drupal/biblio?f[author]=79
DOES NOT WORK!
Second author link in author-sorted list of short citations:
http://myDomain.com/drupal/biblio?s=author&o=desc&f[author]=79
WORKS!
Second author link in title-sorted list of short citations:
http://myDomain.com/drupal/biblio?page=1&s=title&o=asc&f[author]=79
Comment #3
SandPond commentedTHANKS TO JEROME !!!
The "Author" issue cited in #2 above is FIXED in: 7.x-1.0-rc5+28-dev
This dev version also incorporates several desirable enhancements.
Comment #5
SandPond commentedOops! Actually, the "Author" issue described in Thread #2 above IS NOT "Fixed". And, I did not describe the problem as well as I could have:
NOTE: The example author (Author 21) appears in two citations in the bibliography.
[ 1 ] If the bibliography short citation list is sorted by [Author], the following first author link is generated:
//mydomain.tld/mydrupal/biblio?s=author&o=asc&f[author]=21
This link will not retreive any citations where Author 21 is not the first author (or possibly any other citations?). That is, if Author 21 appears in two citations, the link will only retrieve one. It's a little more complicated, but this should be enough to demonstrate the problem.
[ 2 ] From the "Authors" page at: //mydomain.tld/mydrupal/biblio/authors
Author 21's link yields the correct results. Author 21's link is different though:
//mydomain.tld/mydrupal/biblio?f[author]=21
[ 3 ] If the bibliography short citation list is sorted by [Title]
Author 21's link yields the correct results. Author 21's link is different yet though:
//mydomain.tld/mydrupal/biblio?s=title&o=asc&f[author]=21
[ 4 ] If the bibliography list is opened without sorting, that is left only with the "default" sort, which in this case is "Title", then the following link is produced for Author 21:
//mydomain.tld/mydrupal/biblio?page=1&f[author]=21
Author 21's link yields the correct results. Author 21's link is different yet again:
So 4 different links are produced to query the same author. I understand that different links may be needed because the four examples involve three different types of pages, however, [ 1 ] above does not yield the correct results.
I have tested this many times.
Comment #6
rjerome commentedI'll look into this again, I think I mentioned before, that my current working code (which has not yet been made public) has completely reworked the query portion of the URLs to get rid of this... &f[author]=21 and simply replace it with &author=21. At the same time, I'm trying to add a bit more functionality, so that you can have something like &author=21,24+26 (21 AND 24 OR 26). This has meant some fairly significant changes throughout, so I'm reluctant to release this just yet.
Comment #7
sdrycroft commentedMy users would like to be able to enter "et al". Is there a way of indicating that the authors entered are not the complete set, and that "et al" should be added to the authors string when the biblio node is displayed?
Comment #7.0
sdrycroft commentedEnhance comment for (1); added "IMPORTANT" to (3); added comment that the priorty of (3) should be higher.