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 <houghtoa_at_oclc.org> wrote:
> > From: Code for Libraries [mailto:CODE4LIB_at_LISTSERV.ND.EDU] On
> > Behalf Of Bill Dueber
> > Sent: 23 April, 2008 10:34
> > To: CODE4LIB_at_LISTSERV.ND.EDU
> > 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
Received on Wed Apr 23 2008 - 09:35:22 EDT