Hi Ron,

once again we are in sync.

I have written a filter (shamelessly based on the footnote module) for the biblio. It works pretty well but has not been extensively tested. I was planning to submit it later but I have noticed that you have commited some code for a filter. As there is no need to duplicate work, feel free to use my code and modify it. It use the hovertip module (based on jquery) to provide a nice hovertip with the publication. It also print all the references at the end of the page.

It is very crude (it doesn't check the presence of hovertip and so don't degrade gracefully for ex.) but it can be a good starting base. I haven't checked your filter, it is maybe better than mine.

In every cases, feel free to do what you want with that. I think that maybe it should go in a separate module, as well as the import (still to do).

[my lfe] I will do more work on the import and on the filter. I am also planning to start to code some duplication check on the citekey and maybe on the biblio entries but probably not before next week (or next month): I have some hard dead-line at work and incidentally I am moving back to my home country (France) in 4 days so I have a *lot* of stuffs to do (in addition to the regular burden)
[/my life]

damien

CommentFileSizeAuthor
biblio.module_2.patch5.89 KBcirotix

Comments

rjerome’s picture

Thanks damien, I really hadn't done anything along that line yet. I too was looking at the footnote module, but got distracted by other things. What I have done recently is externalize the "node_save" portion of the import chain and changed some of the function calls to use pass by reference in an effort to ease the memory use. Some people (I forget, was it you also?) are importing HUGE files (2500+ entiries), so memory management becomes an issue.

I also added an RSS feed last night which can be accessed at /biblio/rss.xml or via the icon on the new pubs block.

The next thing I would really like to do are create a contributors table to keep all the authors, editors, translators and such in. Although this is fairly straight forward for entries input from the form, it gets ugly quite fast for the "import from file" case. The problem is determining if the author being imported is the same as one that exists in the database. Simple compares don't always work since you might have different combinations of Firstname I. Lastname, or F.I. Lastname.

The duplicate entry checking would be most welcome, I've been meaning to do that for some time.

I was also going to add some auto-complete functions for many of the form fields, to help with consistency in the database.

Good luck with the move, and thanks for the help.

cirotix’s picture

The problem is determining if the author being imported is the same as one that exists in the database. Simple compares don't always work since you might have different combinations of Firstname I. Lastname, or F.I. Lastname.

I am pretty sure that I have already seen some open-source php code which was doing that. I will try to find it

The duplicate entry checking would be most welcome, I've been meaning to do that for some time.

This is related to the previous problem. Uniqueness of citekey is easy to check. Still it is possible to handle that in a nice way: if two citekey are identical the user could get the option to update the previous entry or to create a new one. It should be the same for the duplication of entries: if two entries have an high likelihood ratio, the user should be presented both entries and get the possibility to update the one which is in the db, merge them, discard the new entry or create a new one.

At a certain point the user have to decide (because the machine can't (yet)). The main problem that I an see is the user interface. It should be carefully design in order to avoid cumbersomeness and confusion. Maybe some AJAX bells and whistles could do the trick.

p0732658’s picture

If I may give the point of view of a librarian concerning the validation of authors in the Biblio module, I think you could consider the example of a library catalogue. Librarian when they describe a document and input the description into the library système count on what the call a ''Authority list''. The Authority list contains all the authors present in the system. For each one of those authors, the proper form was entered once respecting the cataloging rules. Whenever a new book or document is entered, the cataloguer check in the authority list for the author and use the same form the new description. In the case of the biblio module, I guest a way to go would be to allowed the creator of a new biblio to browse the authors list already present into the database and then select the proper one. This would ensure that a author name is always entered in the same way...

Hoping this is useful...

Denis

rjerome’s picture

Hi Denis,

Yes that was exactly my plan for the form based input, I am going to implement an auto complete feature using AJAX which will query the database as you are typing the authors last name and present you with a list of possibilities to choose from.

The problem lies on the bulk import (from file) side, when you have to rely on the machine to make the best guess.

Ron.

stanbroughl’s picture

subscribing!

any idea when something working will be up and running? i am in desparate need for this feature!

rjerome’s picture

I assume you are referring to the footnote type stuff?

Unfortunately, I can't really give you a date... I'm just doing this in my spare time (the amount of which varies from day to day :-)

Would you be using this on a single node or a "book" type node?

stanbroughl’s picture

yes footnote stuff. i'm using single nodes only at the moment but possibly books later.

at the moment i'm sticking with the footnotes module but it would be great to combine the functionality of that with the biblio module to build up a library of references and sources - it would be an invaluable addition so let me know if there's anything we can do that would speed up your progress! :D

rjerome’s picture

Ok, this feature is now in the 5.x-dev release.

bekasu’s picture

Status: Needs review » Closed (fixed)

Upgrading to Biblio 6.x gives you this feature as well.
Marking the issue closed.
bekasu