please tell which field is used to hold the subtitle of
* newpaper article
* book
* chapter

I try to import some hundreds of entries, so which format is supported to handle subtitles?

Regards
schildi

Files: 
CommentFileSizeAuthor
#11 biblio-import-4.png15.56 KBschildi
#11 biblio-import-5.png30.93 KBschildi

Comments

rjerome’s picture

Which file format are you using to import?

schildi’s picture

since I will set up a script for creating the import file I will use the format which will fit my needs best.
But my current preference is bibtex.

rjerome’s picture

What about just appending the subtitle to the title (Title: Subtitle)? This would cause the least problems since subtitles are not handled by any of the formatters.

schildi’s picture

I have seen this approach in some endnote blog. But if there is a chance to separate these entries from each other I would like to do so.

rjerome’s picture

That was the "easy" approach, the harder way would be to modify the bibtex parser to identify subtitles and put them in another field like "biblio_tertiary_title" then modify the style you are using to use this field as the subtitle.

schildi’s picture

That is exactly what I am interested in!
But my (actual) knowledge is, that the sequence
title --> secondary_title --> tertiary_title
is the way bottom up. That means it follows the sequence (e.g.)
book-title --> series-title --> whatever-on-top

Isn't subtitle in the hierarchy below title, that means
subtitle --> title --> secondary-title --> tertiary_title

Regards

rjerome’s picture

Well, that may be true, but in the biblio world, some of the fields are multi-purposed based on the type of publication, and in your case, there is no existing subtitle field and the secondary title fields holds the book title, so the next available field would be tertiary. Now if you wanted to add a new field called subtitle then it would be a non-issue, but your database would also become non-standard and thus limit the possibility for upgrades.

schildi’s picture

I'm really confused about that fact that there is no field for a subtitle.
OK, let's not complain about that. But the problem still remains that e.g. for
article: title --> book: secondary_title --> series: tertiary_title
there is no room left for subtitle.

So, this means I have to follow the common way to append the subtitle to the title field (separated by a colon).
This doesn't make me happy!

Regards

rjerome’s picture

Well, I'm sorry your not happy... There are still a few other fields you could possibly use, like biblio_alternate_title, this is a rarely used field would could be a subtitle.

This raises an interesting point, and I guess there is really no reason not to add a subtitle field to the biblio schema, although I haven't encountered any file formats (except maybe for MARC) which actually have a subtitle field.

You might be interested to know that there is a CCK version of biblio in the works and with this (in theory) you should be able to add any number of fields you wish, time will tell.

Ron.

schildi’s picture

Yes, It's surprising that most formats don't support subtitles.
And there is also the question whether the might be a subtitle for each stage, that means
* a subtitle for a chapter heading
* a subtitle for the book
* a subtitle for the series
I really don't know.

May be the answer is that a bibliography entry is always refering to the leaf of the tree, e.g the chapter.
And all the other nodes on the path (book, volume, series ...) are not on focus.

Regards

P.S.
The new development based on CCK is for D7 ?

schildi’s picture

StatusFileSize
new30.93 KB
new15.56 KB

And meanwhile I followed your advice and used ALTERNATE_TITLE for the subtitle.
Everythings worked fine. The only remark I have to append is that the imported XML file did not contain the REFERENCE_TYPE markups (my fault). And as a result all imported records were corrupted (see appended images).

rjerome’s picture

Hi Reiner,

WRT CCK, the current plans are for D6 since this is a Google Summer of Code project it must relate to an existing working codebase. Hopefully, porting to D7 will be reasonably painless :)

WRT imports, looks like you crafted an EndNote format XML file rather than BibTex? If they all happen to be the same type, you could just use an SQL command to set the type, but you probably already knew that.

Ron.

schildi’s picture

Ron, thank you very much for your help!

Yes, I solved my small "REFERENCE_TYPE" problem.

It's out of topic, but may I ask an additional question?
Now, when the new records are imported I like to set up a view to show them in a list.
Therefor I exported the existing biblioview and added a filtering rule like

  $view->filter = array (
    array (
      'tablename' => 'biblio',
      'field' => 'biblio_secondary_title',
      'operator' => '=',
      'options' => '',
      'value' => 'the journal name',
    ),
  );

but when trying to import the filter (new name etc.) I always get an error message

Invalid argument supplied for foreach() in drupal/includes/form.inc on line 950.

It seems that it is not possible to use table biblio / field 'biblio_secondary_title'. When changing these to "node" and "title" the view is created. What the hell is going wrong?

Regards
Reiner

bekasu’s picture

Status:Active» Closed (fixed)

Please start a new issue for new topics.
Marking this issue closed.

Aren Cambre’s picture

Category:support» feature
Status:Closed (fixed)» Closed (duplicate)

It appears this can be fully resolved with fields (CCK) integration, so marking as duplicate of #682044: Support fields (CCK) in D7 Bibliography Module.