 |
 |
Right. I keep a "sequence" number for the fields so they can be re-ordered if need be, but it just seemed too much of a pain (and edge case) to worry about subfield order. On Wed, Apr 23, 2008 at 10:38 AM, Houghton,Andrew <[log in to unmask]> wrote: > > From: Code for Libraries [mailto:[log in to unmask]] On > > Behalf Of Bill Dueber > > Sent: 23 April, 2008 10:34 > > To: [log in to unmask] > > Subject: [CODE4LIB] MARC::Record::JSON perl and javascript > > modules on Google Code > > > > The MARC::Record::JSON data structure itself is *not* > > round-tripable (order of subfields within a field is not > > preserved), but makes for an easy-to-work-with format in > > read-only situations that one would probably be encountering > > within a web page. > > Depending upon how you structure your JSON, you could make it > round-tripable where the order is preserved. There are some > tradeoffs, though. > > > Andy. > -- Bill Dueber Library Systems Programmer University of Michigan Library