Biblio import seems to mix up free tagging vocabularies
gsteenss - February 11, 2009 - 19:12
| Project: | Bibliography Module |
| Version: | 6.x-1.0-rc4 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Description
Hi,
I just did a clean reinstall of RC4 and tried to import a number of biblio entries (from RIS format).
It seems during the import it mixes up the free tagging dictionary to use, although correctly configured in biblio/settings,
it is selecting (i guess) the first one, which in my case is a list of forum topics, and thus the taxonomy for biblio entries is wrong after import, linking to the forum topics instead of related biblio entries.
got phpmyadmin out to convince the database otherwise, but thought I might report it here just in case:
I think I configured everything right and got this to work before with RC2, so i guess this may be a bug...

#1
Could you give me a few more details...
Note, you may have to save the settings on admin/settings/biblio even if you haven't changed anything.
#2
Sure... maybe should have done so in the first place, but i think all is as should be:
there exist three vocabularies, two associated with biblio nodes, and one related to the forum.
'Forum' has vid 1, 'Clave' and 'Temas' are 5 and 6.
Temas is the one selected, freetagging enabled (see image attached)
settings were saved repeatedly...
At import,I do not change any of the Taxonomy settings, and it tells me this:
NOTE: Keyword "free tagging" is turned on, consequently all incomming keywords will be added to the Temas vocabulary as specified in the "Keyword" section of the admin/settings/biblio page.
which is fine with me :-)
#3
just in case:
Here's an example RIS file,
please ignore the additional non-standard RIS tags as they are customized for the existing data i need to import...
#4
Hmm, It's not importing them at all on my system. I'll check into it.
#5
OK, I found and fixed this bug.
Ron.
#6
Really? whow, that's fast...
great work! :-)
#7
#8
Automatically closed -- issue fixed for 2 weeks with no activity.