HI!
Thanks for this great module. :)
I'd need to filter the publications listed in the /biblio page in order to show:
- only certain types of publication
- only publications with publishing date after a certain year (or last # of yrs)
Meanwhile, user biblio page should stay as default, listing all user publications from any year.
I suppose I can achieve this with views but i'd need to rebuild all styles and other settings that I like.
I really only need to filter the default /biblio page by type and year range
Moreover, I am using views 3.x.
So, is there a way to filter the /biblio page, maybe modifying the query that generates it?
where should i look for editing this?
Are there any other ways to achieve such behavior?
Thanks a lot in advance
Comments
Comment #1
rjerome commentedYear ranges are currently not supported, but it's a good idea, so I'll keep it in mind.
I don't think it would be trivial to implement in code, but if you want to take a shot, the query builder is in the biblio.pages.inc file in the biblio_build_query() function.
Ron.
Comment #2
Sylvain Corlay commentedHi,
I have a similar request : is it possible to create a "publication" content, which would not be listed in the /biblio page ?
Thanks for this module.
Sylvain
Comment #3
rjerome commented@Sylvain Corlay: This seems like a different issue, but you could un-publish any node which you don't want in the Biblio listing.
Comment #4
Sylvain Corlay commentedThanks for the answer.
The problem is that if I want to cite a paper in a page of the website, an unauthentified user that clicks on the citation link will have an "access denied" message when the corresponding node is not published. Thus, i wondered is there is a way to exclude any (published as a node) publication of the biblio listing.
Comment #5
rjerome commentedNot really. But I'm still not sure I follow you... "exclude any (published as a node)". Biblio entries are nodes just like any other.
Comment #6
Sylvain Corlay commentedThis was just to avoid the tautology "published publication".
The node might be unpublished on the website whereas the corresponding publication has been published somewhere else. Sorry for the misunderstanding. English is not my mother tongue.
Thank for your answer.
Comment #7
bohz commentedHi!
Thanks Ron for your reply and xcuse me for being late.
I did take a shot at the code and found it's actually quite difficult for me to customize the query. :(
Luckily, I was able to bypass the publication year filtering but still need to filter by type of publication.
Namely, I need to show only "journal article" nodes on the /biblio page, while the user publications should remain unfiltered (listing all publication types).
I suppose I'd need to add something like
$where[] = "b.biblio_type='102' "
(102 is the ID of journal publication type)
but i am unsure where to place it within the biblio_build_query() function...
Thanks a lot
Comment #8
bohz commentedUPDATE:
I have solved somehow the issue adding the following code right after the 'biblio_view_only_own' condition @line 163 in biblio.pages.inc (v. 6.x-1.15):EDIT: THIS DOESN'T WORK. Sorry. :(
Any suggestion on how to set a default filter for a particular type of publication or year?
Comment #9
rjerome commentedYou were on the right track earlier, down around line 414, you could add the where statement like this...
Comment #10
GinaF commented//EDIT// Sorry, didn't mean to post this under "issues", have posted under main forum //
I would like to add a tick box to the Biblio Content Type so that some publications aren't shown on the /biblio main page (they would only appear on other pages).
I have had a look at the biblio.pages.inc, but it looks extremely complicated (I have fairly ltd php skills)! I wonder if anyone could give me some help with this - I want to add a bit of code that says "if tick box is ticked, don't show the publication on /biblio main page"
I need the ticked pages to still show up when a search is conducted though, so they just need to not appear on the initial /biblio page.
I have version 7.x-1.0-rc3.
Any help much appreciated.
Gina
Comment #11
Sylvain Corlay commentedHi everyone,
I would also be interesed by the same functionality as GinaF.
Sylvain
Comment #12
liam morlandThis version is no longer maintained. If this issue is still relevant to the Drupal 7 version, please re-open and provide details.