refined the requirement of XML::SAX::Base
to the specific version 1.04 and I'm awaiting the CPAN Tester reports
to come in: It might well be that more systems than before are entrapped
to install the wrong module when performing "Build installdeps" and thus
effectively cut th
automated / unattended installs
of XML::SAX (like when a smoke tester's environment pulls it in
as dependency of your module)
Unfortunately I have no clue about this might be fixed (apart from changing
the installation behavior of XML::SAX which might for a reason be
as it is)
HTH
Thomas B
ARC however will be very much interested in "/" (or "=") as the first
character of some subfield in 245 if I recall correctly. Not such a big
difference I would think. But maybe a slight complication of the matter,
since MARCspec should have to cope with both approaches...
Th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Carsten,
> I think the whole problem lies in the limited expressivity of strings.
> MARCspec is pretty much close to XPath at its approach, but without regular
> expressions and functions like first(), last() etc. But even with XPath it
> would
>
Carsten,
> Thank you both for bringing the discussion forward. I must admit that I'm
> having some problems following here. I read your mails multiple times, really
> trying to understand your demands. After reading this [1], I hope I'm getting
> closer.
You also could consider to grok Jason Tho
re's also been the regulation for the D-A-CH application layer to move
punctuation which cannot be eliminated to the start of the subfield "it
belongs to", e.g.
245 $a title = $b parallel title
becomes
245 $a title $b = parallel title
probably on the prospect that this could e
feedback if you should run into trouble,
either via the CPAN request tracker for the module at
< https://rt.cpan.org/Public/Dist/Display.html?Name=OAI-Harvester >
or by direct mail.
Sorry for the inconvenience
viele Gruesse
Thomas Berger
Changes to Net::OAI::Harvester since version 1.15
