Posted by anarchivist on April 8, 2009 at 2:58pm
Jump to:
| Project: | MARC |
| Version: | 6.x-2.0-beta2 |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | aaustin |
| Status: | closed (fixed) |
Issue Summary
I've noticed that the MARC module relies on the now-fairly outdated PHP-MARC library developed as part of the Emilda project. I'd like to request that the module be updated to use the File_MARC PEAR module, which is based on PHP-MARC, but is still maintained and under active development.
Comments
#1
The MARC module doesn't even use the PHP-MARC library from Emilda. It uses a method that is unique to the module. The original module was built with the single objective of getting data out of MARC records and importing them as Drupal nodes, with as little effort as possible. Part of this entailed, not requiring any dependencies other than Drupal itself.
But now revisiting this, it makes a lot of sense to use a standard accepted MARC library. I am currently, doing a major rewrite of the module that will focus on turning the module in to a tool to import MARC records and provide an API for other modules to do stuff with the MARC records, such as create nodes. It would make perfect sense to use a standard MARC library along with the API.
#2
I'd be willing to assist with this development - I've been working a lot with File_MARC within Drupal on a module I've written to use the Shrew PHP library to talk to an III web catalog. I'm also looking to (hopefully) take over maintenance of the Z39.50 module, which would rely heavily on parsing MARC records. For what it's worth, File_MARC also has support to parse MARCXML records.
#3
The new version of the module uses File_MARC as an optional library for reading MARC records. However, I did not want to require the use of it, as I think this module best serves smaller applications where less server setup is available or desired.
#4
Automatically closed -- issue fixed for 2 weeks with no activity.