Change default of @incollection from type Book to type Conference Paper [#429452]

Hi,

I'm a bit new to drupal, although I'm a long time php developer. I'm still learning this, but have a new client that has had me install this module on their current drupal site and they have a ton of academic papers that need to be imported. On testing a few out, everything seems to go nicely, but they have told me that the @incollection type should go to the default of conference paper and not book, due to the fact that the @inproceedings bibtex export type more closely matches that of @incollection and not book (as the client put it, "Writing a book is different from a paper that appears in a collection."). They would like to see 'incollection' end up one of the custom fields, which is something more of customization for them, and not something I'm asking for (I will develop this on my own and post the patch for anybody who wants it once I've figured this out) but on the whole I believe having @incollection default to conference paper rather than book would is a better solution. I don't mind developing this, in fact I'd be more than happy to do so, but since I'm still a bit new drupal, I'll need someone to help point me in the right direction.

Thanks,
--T

Comments

Comment #1

rjerome commented 10 April 2009 at 00:47

Hi Craig,

I would debate their definition of incollection and inproceedings (the definitions below can be found at http://en.wikipedia.org/wiki/BibTeX)

incollection
    A part of a book having its own title.
    Required fields: author, title, booktitle, year
    Optional fields: editor, pages, organization, publisher, address, month, note, key
inproceedings
    An article in a conference proceedings.
    Required fields: author, title, booktitle, year
    Optional fields: editor, pages, organization, publisher, address, month, note, key

If however, you want to change this, it is really quite easy to do... Just go into the bibtexParse directory and edit the PARSEENTRIES.php file. In there you will find a function called bib2node() in there you will find a switch statement...

      switch ($entry['bibtexEntryType']){
           ...
        case incollection:
          $node['biblio_type'] = 100;
          break;
        case inproceedings:
          $node['biblio_type'] = 103;
          break;
           ....
      }

Just change the values to what ever you want, where the default values are as follows..

  $types[] = array(-1,'Select Type...',NULL,-10);
  $types[] = array(100,'Book',NULL,1);
  $types[] = array(101,'Book Chapter',NULL,2);
  $types[] = array(102,'Journal Article',NULL,3);
  $types[] = array(103,'Conference Paper',NULL,4);
  $types[] = array(104,'Conference Proceedings',NULL,5);
  $types[] = array(105,'Newspaper Article',NULL,6);
  $types[] = array(106,'Magazine Article',NULL,7);
  $types[] = array(107,'Web Article',NULL,8);
  $types[] = array(108,'Thesis',NULL,9);
  $types[] = array(109,'Report',NULL,10);
  $types[] = array(110,'Film',NULL,11);
  $types[] = array(111,'Broadcast',NULL,12);
  $types[] = array(112,'Artwork',NULL,13);
  $types[] = array(113,'Software',NULL,14);
  $types[] = array(114,'Audiovisual',NULL,15);
  $types[] = array(115,'Hearing',NULL,16);
  $types[] = array(116,'Case',NULL,17);
  $types[] = array(117,'Bill',NULL,18);
  $types[] = array(118,'Statute',NULL,19);
  $types[] = array(119,'Patent',NULL,20);
  $types[] = array(120,'Personal',NULL,21);
  $types[] = array(121,'Manuscript',NULL,22);
  $types[] = array(122,'Map',NULL,23);
  $types[] = array(123,'Chart',NULL,24);
  $types[] = array(124,'Unpublished',NULL,25);
  $types[] = array(125,'Database',NULL,26);
  $types[] = array(126,'Government Report',NULL,27);
  $types[] = array(127,'Classical'	,NULL,28);
  $types[] = array(128,'Legal Ruling'	,NULL,29);
  $types[] = array(129,'Miscellaneous'	,NULL,30);
  $types[] = array(130,'Miscellaneous Section'	,NULL,31);

I was planning to have all the various file type mappings stored in the database (rather than hard coded as it is now) but I just have never gotten around to changing that yet...

Cheers,

Ron.

Comment #2

Tecktron commented 10 April 2009 at 23:11

Status:

Active

» Closed (fixed)

Thanks Ron!

I do understand the debate based on the definitions, but I would also agree that the export of a book is much more sophisticated than that of an incollection. Well I guess I can see both sides of it and I'm sure one could argue all day about it. Well, that's great thing about being a developer, is that you don't have to think about things like that as you just do what client or yourself wants. ;)

Thanks again, this is just what I needed!
--Craig

Comment #3

rjerome commented 11 April 2009 at 01:49

Status:

Closed (fixed)

» Active

Hi Craig,

I just realized I may have pointed you in the wrong direction. It's not entirely clear to me if you were looking for the import mapping or the export mapping. I thought you were talking about the import mapping (which is what I was referring to above, however if you were actually referring to EXPORT mapping, then that is done in the biblio.import.export.inc file in the "biblio_bibtex_export" function.

Please feel free to post any modifications you make back to this forum and if they are of a generally useful nature I'll happily include them in the code. I would hesitate to change these particular mappings unless there was a general consensus among the bibtex users since it would kind of mess up this installed base.

Cheers,

Ron.