Automatic Biblio node creation via RSS + Feeds module?

Yes, it should be quite possible since it is really no different from harvesting an OAI-PMH feed. It's really not a multi-step process assuming the publication type information is contained in the feed. You just need to be able to parse the feed and map the fields to the appropriate biblio fields.

I am actually looking at the Feeds module as a generic import wrapper for all the current biblio file import filters in the 7.x-2.x branch of the code (which is non-existent at this time).

Ron

It should be reasonably straightforward, you would just build a $node array and then call biblio_save_node($node). Any of the xx_parser.inc files will show you an example of mapping fields from an external format to biblio and creating a node.

Ron.

subscribe

I'm looking for a solution here too...

I want to be able to regularly and automatically export a subset of biblio nodes based on a keyword to a sister site. I think it would technically be possible using Feeds, but it seems overly complicated as well due to the huge number of fields that would need to be exported from Biblio. It seems much more easy and efficient to filter based on keyword and export and import the bibtex file to the new one. However I don't see a method to do this automatically say using a cron job or something since there doesn't seem to be a way to grab an export link for a specific keyword something like this: /biblio/keyword/11/export/bibtex

I would hope to be able to point a cron job to grab that link regularly and then somehow automatically import it as well. Any ideas besides using Feeds?

subscribe

subscribe

subscribe

FYI, I've used Feeds to successfully import from a tab-separated file. I created a custom module, in this case nzac_library, refer code below.

It only handles the limited fields I'm interested in, so isn't a general solution. It contains some custom cleanups of incoming data (e.g. editions go from 1st to 1).

HTH

<?php
/**
 * @file
 * Custom functions for NZAC Library feature.
 *
 * Add Feeds support for initial import from TSV file exported from BookCAT.
 */

/**
 * Declare available biblio fields to Feeds Node Processor mapping.
 *
 * Implements feeds_node_processor_targets_alter().
 */
function nzac_library_feeds_node_processor_targets_alter(&$targets, $content_type) {
  //flog_it(__FUNCTION__ .': targets='. print_r($targets, TRUE) .', content_type='. $content_type);
  if ($content_type == 'biblio') {
    $info = content_types($content_type);
    //flog_it(__FUNCTION__ .': info='. print_r($info, TRUE));

    // Declare some biblio fields.
    $targets['biblio_type'] = array(
      'name' => 'Biblio: Type',
      'callback' => 'nzac_library_feeds_set_target',
      'description' => t('The numeric type of bibliographic resource, e.g. 100.'),
    );
    $targets['biblio_type_name'] = array(
      'name' => 'Biblio: Type Name',
      'callback' => 'nzac_library_feeds_set_target',
      'description' => t('The type of bibliographic resource, e.g. Book.'),
    );
    $targets['biblio_contributors'] = array(
      'name' => 'Biblio: Contributors',
      'callback' => 'nzac_library_feeds_set_target',
      'description' => t('Author(s) of publication.'),
    );
    $targets['biblio_date'] = array(
      'name' => 'Biblio: Date',
      'callback' => 'nzac_library_feeds_set_target',
      'description' => t('Date of publication.'),
    );
    $targets['biblio_year'] = array(
      'name' => 'Biblio: Year',
      'callback' => 'nzac_library_feeds_set_target',
      'description' => t('Year of publication.'),
    );
    $targets['biblio_edition'] = array(
      'name' => 'Biblio: Edition',
      'callback' => 'nzac_library_feeds_set_target',
      'description' => t('Numeric edition, e.g. 2.'),
    );
    $targets['biblio_publisher'] = array(
      'name' => 'Biblio: Publisher',
      'callback' => 'nzac_library_feeds_set_target',
    );
  }
}

/**
 * Map incoming values to biblio fields, with appropriate transformations.
 * e.g. book => 100,
 */
function nzac_library_feeds_set_target(&$node, $target, $value) {
  //flog_it(__FUNCTION__ .': node='. print_r($node, TRUE) .', target='. $target .', value='. $value);
  flog_it(__FUNCTION__ .': target='. $target .', value='. $value);
  $value = trim($value);
  switch ($target) {
    case 'biblio_contributors':
      $contributors = explode('&', $value);
      foreach ($contributors as $key => $contributor) {
        $node->biblio_contributors[1][$key] = array('name' => trim($contributor));
      }
      break;

    case 'biblio_edition':
      $value = strtr($value, array(
        '1st' => 1,
        '2nd' => 2,
        '3rd' => 3,
        '3rd rev' => 3,
        '4th' => 4,
        '4TH' => 4,
        '6th' => 6,
        '9th imp' => 9,
        '10th imp' => 10,
      ));
      $node->$target = trim($value);
      break;

    case 'biblio_publisher':
    case 'biblio_year':
      $node->$target = trim($value);
      break;
  }
  // Force biblio type for now.
  $node->biblio_type = 100; // Book
  $node->biblio_type_name = 'Book';
}

subscribe

subscribe

@jonathan_hunt: I'm relatively new to Drupal module development, where would I put this code? I'm trying to incorporate my own Feeds/Biblio importer, but using an XML feed. I wanted to try to understand how your code works first before I attempt to write my own. Would this work with Drupal 7?

@humansky: This code would need to go into a custom module (create a .info file and put the code into a .module file) - there are plenty of docs here on d.o to show you how. Also read the Feeds docs and for Drupal 7 note that some of the hook signatures have changed (see feeds.api.php in the Feeds module directory).

@jonathan_hunt, here is my stab at using Feeds and DSpace:

http://drupal.org/sandbox/humansky/1316642

I got the "dspace" module working, but for some reason can't get the "dspace_biblio" module to populate the "$entity" in dspace_biblio_set_target(). The Feeds author changed, for the better, how they handle target mapping and node processing from Drupal 6 to 7. Just have to figure out how and I should be good to go. Check it out, let me know what you think, it's my first module, so be nice :-)~

This version is no longer maintained. If this issue is still relevant to the Drupal 7 version, please re-open and provide details.