Thanks, Ed. That would have been a useful tidbit for me to have added :)
Also, if there's interest, we can set up the Github Wiki for
ruby-marc. There is some functionality that would be difficult to
explain (including the pros and cons) about in the rdocs, such as the
XML parsers (and to write new ones) and there are some caveats on when
to use field maps in MARC::Record and when find/find_all works better.
Anyway, this seems like it might be useful, and if others think so,
too, well, let me know!
On Wed, Mar 16, 2011 at 6:02 AM, Ed Summers <[log in to unmask]> wrote:
> Hi Tony,
> Just in case it wasn't obvious, the source code is on GitHub . As
> Ross said, please consider forking it and sending a pull request for
> any documentation improvements you want to do.
>  https://github.com/ruby-marc/ruby-marc
> On Tue, Mar 15, 2011 at 3:18 PM, Ross Singer <[log in to unmask]> wrote:
>> Hi Tony, I'm glad that ruby-marc appears to be generally useful.
>> Another (even simpler) way to do what you want is:
>> Which, I think, would do the same thing you're doing with MARC::Writer.encode.
>> If you want to write up a block of text to plop into the README, feel
>> free to send some me some copy (wholesale edits also welcome).
>> On Tue, Mar 15, 2011 at 2:40 PM, Tony Zanella <[log in to unmask]> wrote:
>>> Hello all,
>>> If I may suggest adding to the documentation for the marc gem
>>> Currently, the documentation gives examples for how to read, create and write
>>> MARC records.
>>> The source code also includes an "encode" method in MARC::Writer, which came
>>> in handy for me when I needed to send an encoded record off to be archived on
>>> the fly, without writing it to the filesystem.
>>> That method isn't in the documentation, but it would be nice to see there! It
>>> could be as simple as:
>>> # encoding a record
>>> Thanks for your consideration!