Tangential to the keywords issue that you're discussing in http://drupal.org/node/357585, I've found that upgrading the Biblio module from version 5 to version 6 blows away any existing taxonomy terms that you have applied to a biblio and replaces them with the keywords. It would be nice to retain the feature from version 5 that allows the user to opt out of registering the keywords as taxonomy terms in the "free tags" vocabulary.

We're using both Drupal core Taxonomy and Biblio keywords to describe our Biblios, and not registering the keywords in the free tags vocabulary.

Thanks Ron!

Comments

rjerome’s picture

rjerome commented

Just to be clear, you are saying that on the "admin/settings/biblio" page under the taxonomy section, you did NOT have the...

"Use keywords from biblio entries as taxonomy "free tags""

...box checked, but you had created a taxonomy vocabulary and you had associated the biblio node type with it? Then when you upgraded that vocabulary was gone?

john bickar’s picture

john bickar commented

Correct. The vocabularies that I had associated with the biblio content type are no longer associated with that content type (after upgrading), and the relevant entries in the term_node table have been deleted.

I also have noticed when updating the biblio module to a new point release in the D5 branch that the vocabularies that I have associated with the biblio node type get "un-associated", but nothing happens to the rows in term_node, so I just have to manually go back and re-check the boxes to associate the vocabularies with the biblio content type.

rjerome’s picture

rjerome commented

I'll do some testing to see what going on here.

WRT 5.x updates, I'm guessing that you are disabling the module before the update? This not biblio specific but true for any module because if the module is disabled, the taxonomy terms associated with it are no longer valid. In the 6.x version I take care of this automatically in the "enable" and "disable" hooks, but I don't recall if they exist in 5.x, I'll check on this.

Although the docs say to disable the module prior to upgrade, you don't really have to (I never do) and this way you will avoid having to reset the taxonomy stuff.

Ron.

john bickar’s picture

john bickar commented

Yes, I had forgotten that I had posted about the associated vocabularies in the issue queue already and that you had answered.

I've been doing some testing with upgrading our site to Drupal 6 over the last week or so I have in my notes that biblios do not lose their taxonomy terms with the RC2 version, but they do with the dev version. Unfortunately, with the RC2 version, I lost all data in the biblios (Authors, Call numbers, etc.) on upgrade from 6.x to 6.x. I will do some further testing today to verify that this is the case.

rjerome’s picture

rjerome commented

If you are testing the upgrade from 5.x, you should go directly to the -dev version and bypass any betas or RCs. Robert Haschke contributed an excellent upgrade process to go from 5.x to 6.x which is only in the -dev version.

Ron.

john bickar’s picture

john bickar commented

OK, thanks for the update.

I tested the upgrade to RC2 and I was incorrect - it still replaces the existing taxonomy terms with biblio keywords.

mweixel’s picture

mweixel commented
Version: 6.x-1.x-dev » 6.x-1.0-rc2
Category: feature » bug

I can confirm cubbtech's finding that upgrading to RC2 (even from an earlier version of 6.x) blows away taxonomy terms and replaces them with biblio keywords--even if the biblio settings dictated that keywords not be used as a vocabulary.

Was this behavior documented in the differences between RC2 and the Dev version? If so, I really bonked. Fortunately, I have a backup and am in the process of restoring the old node_term references.

rjerome’s picture

rjerome commented

I'm in the process of reworking the keyword handling and any future releases will not have this issue. While people seem to want keywords in taxonomy, there is definitely some inherent danger in entrusting a large part of your data to a third party module. As you have discovered they can become disconnected and reconnecting them can be difficult or impossible.

My plan is to store keywords within the biblio database structure and if people so desire, they will have the option of replicating them into a taxonomy vocabulary. I realize this is a duplication of information, however it will provide data integrity.

john bickar’s picture

john bickar commented

Looks like the most recent dev version fixes this. I'll leave it to you, Ron, to make any changes to the status of this post in the issue queue, but I wanted to point out to folks that may have been waiting for a fix.

Thanks!

rjerome’s picture

rjerome commented
Status: Active » Fixed

Indeed, I guess I forgot to update the issue.

FYI, there should be a final release out within days now.

Ron.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.