Hi, On Wed, Feb 9, 2011 at 12:58 PM, Brad Baxter <b...@mail.libs.uga.edu> wrote: > I'm not sure what your interface for MARC-in-JSON in > MARC::Record will look like, so maybe this is in conflict > with that -- or maybe not.
Conflict? I wouldn't think so, but perhaps superfluous in the case of MARC-in-JSON. See http://marcpm.git.sourceforge.net/git/gitweb.cgi?p=marcpm/marcpm;a=commit;h=66e7ba36bc974ee068afddc0da9177ac8bebcdc6 The MARC::File::JSON module is consistent with other MARC::File::XXX modules that handle serializing and deserializing MARC::Record objects. MARC::Utils::MARC2Ini is an interesting concept, but it wouldn't take much work to recast it as MARC::File::Ini. By using MARC::File::Foo serializers/deserializers, you could also avoid the need for an explicit MARC::Utils::MARC_in_JSON2Ini; instead, you could just do this: my $rec = MARC::File::JSON::decode($json); my $ini_string = MARC::File::Ini::encode($rec); Regards, Galen -- Galen Charlton gmcha...@gmail.com
