I think the ability to integrate to make the Bibliography fields available in views would really make this a powerful module - then you could create a list of authors or a table with all the books and information.

Thanks for all the great work on this module!

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

notarealperson’s picture

Upon further inspection, my issue request was a bit premature. Biblio sorts really well - I guess I'd like to see a sort by Author as well added to the options though.

rjerome’s picture

Sorting by author is coming, but that's a little trickier (because there are so many potential author formats), so this won't happen until I separate the authors into their own table.

Ron.

ktnk’s picture

I would also like to see a views integration because my site has a lot of other content types apart from biblio nodes, and I would like to see them all listed together on certain views.

Is this in the works?

KTNK.

rjerome’s picture

I started work on a biblio-views support module, it probably be a week or so before it's ready for testing.

Ron.

ohzbees’s picture

Good news on Biblio and Views :-). I've been starting to really go wild with the Organic Groups and Views modules -- so this would be a great addition. On my academic sites, I like having very fine control over tabular presentations of site-wide node data, e.g., taxonomy-filtered listings of node titles and URL's for articles, software, data sets, academic groups, journals, government offices, schools, etc.

Ron, thanks for all your amazing progress!

--Neil

rjerome’s picture

I've added a preliminary views integration in the 5.x -dev branch. Right now it exposes all the fields in the biblio table, but I was thinking of added the ability select with fields are exposed on the settings page.

ktnk’s picture

Ah, so that's why I suddenly have so many more fields available in my views!
I didn't realize right away that they were biblio fields since, as I said, I do have many different content types which often share field names such as "date" and "source"

All this to say, Please prepend the word "biblio" to biblio fields! :)

rjerome’s picture

Actually, (as far as I know) they are all prepended with biblio so I'm not quite sure what you are referring to. Could you elaborate as to where you are seeing non-prepended descriptions.

Ron.

ktnk’s picture

I typed without double-checking.
I have updated my biblio and views modules but don't see any biblio entries in the fields.
The entries I do see are my own cck fields from other content types. (cck doesn't prepend its fields with "cck")

Ktnk

rjerome’s picture

So I'm not sure were we stand now. Are you saying the biblio fields disappeared? BTW, the views integration is only in the -dev branch right now.

ktnk’s picture

Hello,

I had gotten sidetracked for a bit, and am back to using biblio to structure my site.

I see a whole bunch of biblio entries in my fields dropdown list in views, which is nice (although I couldn't figure out which one was the actual document type field)

Now, I need to filter my view using these bibilo entries, but there are no biblio entries in my filters dropdown list!

Did I erase something by mistake, or was this never a feature?

I would like to displaysubsets of different biblio types of documents in different parts of my site. How would I do that using views?

Thanks,
Ktnk.

rjerome’s picture

There are no "views filters", and frankly I'm not a big views user or fan so I really haven't put too much effort into it. When you say subsets, how are you defining these sets? Maybe there is an easier way.

Ron.

ktnk’s picture

I am using biblio for a lot of different content types. And will need views for a few different functions:

1. One in particular is books. I have a list of bibliographies of a few hundred books. From these, only a handful have full text available, so I will tag each book entry with a granularity field (no text, full text, summary)
so:
- For users who want to do research, they can look through all books using biblio.
- But for users who want to read a book, I need a view of all books with full text
I can add a cck field called granularity for sorting with views, but I can't filter by biblio content type to only get books, and the granularity cck field would apply to all biblio types, not just the book type.

2. I have different article types defined in biblio. I now want to make a section in my site to display short readings of granularity full text, so I need a view that groups a few different biblio types and that filters by te above granularity field. I don't see a way in biblio to preset a filter or to sort by a custom field.

3. I would like to have a teaser view or a table view of some of my content

4. I haven't figured out how to get a link like this to work with menus:
biblio?sort=type&order=asc or how to incorporate a filter into this url.

I just feel that all these (and more) issues would be solved if only I can filter biblio content using views.
I am completely open to suggestions.

thanks,
ktnk.

pukku’s picture

What field would I use to get the complete citation included in a view? I want to be able to present a list of the publications associated with a study, which is associated via taxonomy. So I have gone through and assigned the correct term to each publication, and I'm building a view, but I can only get at the individual parts of the citation — what I really want is to have a listing similar to what I can get via the page.

Does this make sense?

Thanks,
Ricky

ntripcevich’s picture

I second that request. Basically the two useful biblio listings are
1) the listing that defaults to /biblio which is an attractive layout but relatively limited in terms of display.
2) a tabular layout in views. The table layout is not a bibliographical format but it has the advantage of being sortable by field title.

I guess the ideal is some kind of "View Type" that essentially mimics the /biblio default listing. Correct me if I'm wrong but Views integration hasn't gotten to the point where you can do anything besides table, full-node/teaser, or heading.

Since CCK is headed to the core in v6 and Views is a powerful way to display CCK, it seems like complete integration with Views / CCK is inevitable for this module.

Great module, thanks.

rjerome’s picture

There is a beta version of a biblio_views module which does a pretty good job of recreating the default biblographic listing. The module still needs some work to provide the full fuctionality that currently exists.

Your right though, I have been getting some pressure to provide full views/CCK integration, and it's probably a good idea but I don't know when it's time will come since i would need a fair chunk of time to make this switch.

Ron.

redraven’s picture

Hi,

I've used the biblio module in the past for a project, about a year ago, great to see the ongoing development, thank you!

In the process of evaluating it for another project.

For this project i will need biblio/views integration also, especially filtering by 'publication type' into block views.

The biblio views module in head, will that work fine with the 5.x-1.10 release or do I need to use the head tagged release to use that helper module?

Thanks

rjerome’s picture

Yes, is should work with 5.x-1.10 version (although I haven't tested it). It likely won't work with the HEAD version since that version is for drupal 6.x. Let me know what happens.

Ron.

dlx’s picture

Hi Ron,

In comment #16 you mentioned biblio_views that recreate the default bibliographic listing within views.

Is there any way you could post a link to the module? Sorry, I cannot find it.

Sincerely,
Alex.

rjerome’s picture

FileSize
4.07 KB

Attached you will find a version which will work with Drupal 5.x. I haven't looked at this in a while, and given that the entire "views" world is changing as of Drupal 6.x, don't expect a lot of support on this. I will however revisit the views module once the new views module for 6.x has stablized.

Ron.

dlx’s picture

Hi Ron,

Thank you very much!

Even though not all is working (like View Types: APA, CSA and IEEE), it is possible to create a view of publications using View Type: Biblio Classic and Field: Biblio Original Publication. One can even attach it to a custom node using CCK View field! ;)

Hopefully, this module will be preserved and extended - it is REALLY useful.

Great work! Thanks!

rjerome’s picture

Your welcome, but I can't take credit for it, matt over at http://www.antinomia.com/ was behind most of it. Unfortunately that project kind of fell of the radar screen, but as I said there will be a renewed push once "views 2.0" is out.

Ron.

tatien’s picture

I am hereby submitting a patch that adds a new "style plugin" called "Bibliography" that could be used instead of "Full nodes", "List", etc. It basically reproduces the nice biblio outputs from function "biblio_show_results()" in a view.

For example, I used it for the website of a research center, to restrict biblio listings for a specific "Author" content type, like is asked in the following issue: http://drupal.org/node/210957. I solved the problem by

  1. Creating a content type "Author" (NOT a user because I don't need registered users for each author, but I need some extra infos for the authors, like pictures
  2. Adding a "node reference" field to authors in the Biblio content type
  3. Creating a view with a "Node Reference: field_author" argument
  4. Setting the view type to my new "Bibliography" style plugin

The patch involves a little redefinition of the biblio_show_results() and biblio_db_search() functions among other things.

Anonymous’s picture

I'm also trying to pull out Biblio listings by author.
I will try the biblio_views.zip file but meanwhile I thought I'd try to do this without changing anything or resorting to altering your code.

What I've tried (I did ensure that there was some Biblio content by the author whose page I want to customize):

1) Node: Author Name doesn't work - of course there can be variations on author name & the View choices are only the registered users. Yet when I remove the Author Name restriction and accept anything of type Biblio, the entries still don't appear. The title of the view does appear.

2) So I made a Categories Vocabulary called Authors and added an author as a Term, with variations on author name as synonyms. This gave me a choice in Views called:
Taxonomy Term : is one of : Authors:Marie Curie (whatever)
This didn't work either.

3) So I tried:
Taxonomy: Terms for Authors: Is One of ... but there are no choices in the popup.

Am I overlooking something? Or is it really impossible with Biblio 5.x-1.15 ?

Anonymous’s picture

Title: Integration with Views » File attachment - which Biblio field?

I'm making a list of publications; a Page View (List Type) pulls out all content of type Biblio.
List Type allows you to choose which fields.
Many of the publications come with a downloadable file; this is entered & uploaded via the file attachment field.
Which database table/field corresponds to the file attachment field on the form?
The link is automatigally displayed with Full Nodes, but I just want to show title, year, author, and a link to the download.
I've looked at all the tables named biblio_* and I don't see it.

thanks

rjerome’s picture

File attachements are handled by the upload module, and thus the file name and location information is stored in its tables, check the file table.

Ron.

Anonymous’s picture

Thank you, I stumbled across the solution - the Field option is File:Name :

Fields > File: Name [ Handler: "With download link" (it's a popup, the default is Plain ]

------
p.s. I did follow up on your advice, looked at the files table and upload.module & was puzzling over where in biblio.module the work is done to pick out the filename/path from the database. Maybe in function theme_biblio_list() ?
This would still be interesting to know because the above solution does not take care of listing the file size (a nifty thing).

rjerome’s picture

In the function biblio_show_results() at line 2163 you will see a bit of code like this...

    if ( module_exists("upload") ) {
      $node->files = upload_load($node);
    }

That's where the actual file information is attached to the node. If you look at the files object, I think you will find that there is a filesize property, so you could do this...

      foreach ($node->files as $file) {
        $output .= '&nbsp;<a href="' . $file->filepath . '">' . $file->filename . '</a>&nbsp;('.$file->filesize.')';
      }
bekasu’s picture

Status: Active » Closed (fixed)

Marking this issue closed.
bekasu