The power of Biblio...

You are quite right, this is mentioned biefly in the online help (/biblo/help). You can construct URLs which select author,type or year. So if you want all the books published by denis in 2006 you just enter /biblio/author/denis/year/2006/type/10. And as you discovered, additional terms are "AND"ed on the end.. I supose I could add an "OR" capability if it was useful.

Ron.

This posting makes it look like it is possible to tag an entry with more than one type...your well developed list of standard types, and a custom type. This would allow classification within the site. I have been unable to reproduce the /type/101/type/1001 construction as I can not figure out this 'custom type' that he is referring to. The only option I see, which preserves your elegant visual layout (much better than what views renders) is to create duplicate sets of types for each classification....e.g. book_review, book_member_publication, article_our_own_journal

am I missing something?

Just to be clear, are you trying to get all the type 101 and type 1001 entries?

Unfortunately, these filters are ANDed together, so "/type/101/type/1001" is asking for entries which are of type 101 AND type 1001 which will never return anything because any given entry can only be a member of one type.

I could add an "OR" capability so you could do something like /type/101/or/type/1001 and thus get all entries of both types.

Ron.

that is what I thought...
the post by denis seemed to suggest that it was possible to 'and' a custom type and your standard types in a way that would allow an administrator to create an classification system that was site specific...was this wrong?

again
I'm just looking for an easy way to be able to create custom types so that I can present subsets of a single
e.g.
biblio database in a variety of places.
journal articles (we publish a journal)
material reviews (members' reviews of materials)
course reading lists
member publications

etc.

I can, and have, used taxonomy to do this
but your presentation is far more elegant than what I can build with views

thank you

-peter

If all you want to do is add a new type, then you can do that by going to this page... admin/settings/biblio/types and clicking on "Add New Type". Give it a name and (optional) description, then you will be sent back to the type definition page, scroll down to the bottom and you should see your new type. Click the "Edit" link beside it and you can define which fields are associated with your type and you can change the display names of the fields here too. Your new "typeid" is shown in the left most column and it is this id which you can use to list only this type.

I hope that makes sense.

Ron.

thank you
makes perfect sense
I've done it...and I've created types as follows

article-member_publications
article-journal
article-course_reading_lists
the problem is that I would have to duplicate this for every type you have created...and this would also have to be reproduced in my bibtex database on my computer (which I'm using to generate my uploads)

far easier would be to use the bibtex field custom_1
to place a limited number of classification terms in custom_1 in my bibtext database
to allow me to create a dropdown of acceptable terms for custom_1 for user entry/filtering (simply reading from custom_1 would be adequate as users would not have the ability to create new terms or upload bibtex files)
and then to enable filtering on custom_1

the problem is I need to apply two classifications to the entries
one is biblio-type
the other is our own arbitrary and limited set classification
the 'keyword' sort you enabled is enormously helpful...thank you.

taxonomy does allow me to do this
but I can't get views to pull the biblio_fields as (I think) the handles for views are not embedded in the biblio_module yet
so
I can't get meaningful list or table views
and the teaser views are ill formed

does this make sense?

-p

Ok, if I understand properly, the most elegant/preferable solution would be to be able to filer on taxonomy terms, i.e. "biblio/term/member_publications" is that correct? If so, I think this is doable without too much difficulty.

Ron.

absolutely...
allowing filtering on one (or more) vocabularies specified in the admin area would make presentation of material incredibly flexible

lets say I create a vocabulary called 'term'
consisting of

member_publication
book_review
journal_article
course_readings

then I would be able to build a URL that would filter as follows

~biblio/term/member_publications
to produce a summary list of all member publications

and if things got big
folks would even be able to do complex and filters like

~biblio/type/##/term/abc
or whatever...

this would make it possible for folks (like me) to use biblio as the core of academic-ish sites where different subsets of the total citation database get presented in different areas.

one complicating factor
you most helpfully list keywords below each item summary...and they are clickable. Allowing filtering on a taxonomy vocabulary raises the question of whether the keyword links would pull from the entire database or the subset. I have no preference on this one.

again
a huge thank you
this module is incredibly useful as it is
and I feel like I'm putting upon you terribly with this

Consider it (almost) done! I worked on the filter by taxonomy a bit yesterday and (I hate to say) it looks like it won't be a big deal at all. And yes you will be able to combine filters so you can build anything you wish like biblio/term/book_review/author/smith or /biblio/term/book_review/year/2005 etc.

As for listing the keywords, I could create another style with those included. Which style do you typically use now?

As for what the keyword links return, right now they only include biblio node types. If you want to search all node types, the regular search box would probably be a better route, but I'll think about that one a bit.

Ron.

wonderful !!

I have a naked install that I'm playing with...so when you have something I'm ever so happy to be a guinea-pig

The keyword returns was an 'oh by the way'...not at all a significant issue...a design choice on your part...when looking at filtered returns does clicking on the keyword return filtered or unfiltered results (within biblio)?

Either works for me...just wanted to mention it as a heads up...folks with small databases would probably want it to return unfiltered results while folks with very large databases would probably prefer filtered.

One more thing...and this is showing my ignorance of drupal...

is there an elegant way in drupal to apply a given term to a selection of nodes?
lets say I upload 250 or so records from my bibtex database
100 are journal_articles
50 are member_publications
there must be...

thank you again
-peter

Just send beer! :-)

If you have separate files for each type, you can assign a single term to all the node imported from that file. You will see this option on the file import page.

Ron.

OK folks, I added filter by taxonomy term to the 5.x-dev version (dated Mar. 24), give it a try and let me know what you think.

You can enter a url like /biblio/term/research to get a list of all the biblio nodes associated with the taxonomy term research.

I was thinking maybe a filter by vocabulary might be useful as well and maybe slightly less useful would be a filter by term id.

I played with it
first up
replace the entire biblio module folder and run update.php
I found out the hard way that you made a few changes in the db
doooh

I set up two vocabularies that bear on biblio entries...
one of which was free tagging and identified in biblio as the place to keep keywords (free_tags)
the second was a pre-determined set of 4 classifications (classifications)
I found that
~/biblio/term/free_tags_term
and that
~/biblio/term/classifications_term
both work fine
I found that they work fine with other filters
and I found that the system does not like a ~/biblio/term/free_tags_term/term/classifications_term
structure...nice error
this, however, was just to push the envelope of the esoteric...something to mention in the writeup

I found
of course
that it is not possible to filter by terms that are NOT identified as being related to biblio nodes...
i.e. ~biblio/term/username
produced
file not found...as it should have.

short version
this is just what we need in order to use biblio as the core of complex sites that want to present subsets of a common core in specific parts of their site.

perfect
kudos
thank you

and
if you like this as much as I do
I understand the author accepts thanks paid in full by a single well crafted beer.

:)

-peter

Glad to here it works (more or less) as you had hoped. I could add that multiple term feature if you wish, I don't think it would be that big a deal. While implementing this feature I was thinking that maybe the notion of "collections" might be a useful feature. What do you think?

'collection' is a great language to use to describe this.

one small caveat on the .dev install.
it doesn't like being installed raw.
it needs the latest official release up and happy before it takes.

v. low priority
but neat
would be the ability to AND terms
and to look at all the entries by a given user
something of a history/blog of their contributions
good for an academic community
and for a somewhat lazy prof keeping up on his students' contributions to the communal knowledgebase ;-)
btw...what you have here beats hell out of refworks for elegance.
That system is a dog.
-p

Thanks for the heads up on the install problem, it's fixed now.

Ron.