Hi,
2010/11/11 Frédéric DEMIANS :
> Thanks all for your suggestions. I have to choose another name for sure.
> Marc::Moose seems to be a reasonable choice. But I'm very tempted by a
> shorter option: MarcX, MarcX::Record, MarcX::Parser, MarcX::Reader::Isis,
> etc. Any objection?
Not from me, but
I think we should revisit "Biblio::". Yes, I know MARC isn't used only for
bibliographic data, but it's sure as hell not used to speak of outside the
library/museum world. 'Biblio' might not be perfect, but it's certainly not
misleading in any meanigful way.
On 11/11/10 10:23 AM, "Galen Charlt
Hi,
2010/11/11 Dueber, William :
> I think we should revisit “Biblio::”. Yes, I know MARC isn’t used only for
> bibliographic data, but it’s sure as hell not used to speak of outside the
> library/museum world. ‘Biblio’ might not be perfect, but it’s certainly not
> misleading in any meanigful way
2010/11/11 Frédéric DEMIANS :
>> Thanks all for your suggestions. I have to choose another name for sure.
>> Marc::Moose seems to be a reasonable choice. But I'm very tempted by a
>> shorter option: MarcX, MarcX::Record, MarcX::Parser, MarcX::Reader::Isis,
>> etc. Any objection?
Since MARC is an
Gah. Replying to all this time instead of just Galen, as I did three
hours ago, for my $0.02...
2010/11/11 Galen Charlton :
> Hi,
>
> 2010/11/11 Frédéric DEMIANS :
>> Thanks all for your suggestions. I have to choose another name for sure.
>> Marc::Moose seems to be a reasonable choice. But I'm ve
I was going to express the same concern. Keeping everything under
MARC:: may also make it a tiny bit easier to find the existing
alternatives for, well, parsing MARC records. I would +1 MARC::Moose.
I understand this point. I don't like the idea of using 'Moose' in the
name of object using Mo
Hello,
butting in an interesting discussion ...
Would Org::Demians::MARC::Record ( or Tamil::MARC::Record ) be very
wrong, unless you aim to provide the ultimate collection of MARC
modules that would make all the others obsolete ?
Moose is great and I love it, but it's not forever ... in a few y
> butting in an interesting discussion ...
Thanks for joining the discussion.
> Would Org::Demians::MARC::Record ( or Tamil::MARC::Record ) be very
> wrong, unless you aim to provide the ultimate collection of MARC
> modules that would make all the others obsolete ?
Yes, I aim to... In the Java
CPAN stores distributions under author subdirectories. But the module
namespace is done separately and reflects the function of the module.
In the case of the MARC:: namespace, I think Ed Summers is the only one
who has remained involved since the beginning (back in the 1990's). Had
we used names a
2010/11/11 Frédéric DEMIANS :
> Thanks all for your suggestions. I have to choose another name for sure.
> Marc::Moose seems to be a reasonable choice. But I'm very tempted by a
> shorter option: MarcX, MarcX::Record, MarcX::Parser, MarcX::Reader::Isis,
> etc. Any objection?
>
I can't think of a b
hello world,
Years ago, i wrote MARC::Template (https://github.com/eiro/MARC-Template)
to ease the process of migrating data to koha ILS. We often use it at
biblibre (http://biblibre.com).
For a MARC to MARC migration, just making some manipulations CRUD manipulations
on fields, cleaning some dat
hello again,
As i wrote my last mail, guys at biblibre really would like to write
tools to ease the programmer in charge of migration process.
MARC::Template is something we're very happy about but we have more
tools that aren't as polished. But we already successfully use them so
we share them wi
Hi,
On Thu, Nov 11, 2010 at 7:27 PM, Marc Chantreux
wrote:
> simple proposition is:
>
> [ [qw/ 001 value /] # example of control field
> , [qw/ 005 value /] # example of control field
> , [ [qw/ 200 0 1 /] # example of data field
> , [ [qw/ a foo /]
> , [qw/ b bar /]
> , [qw/ a foo2
hi galen,
On Thu, Nov 11, 2010 at 07:40:35PM -0500, Galen Charlton wrote:
> I don't see how a structure like this gets you anywhere closer to an
> abstraction layer that would permit somebody to code in terms of
> semantic concepts like title and author instead of MARC tags,
It doesn't: the fact
14 matches
Mail list logo
