...and the other places with XMLout are patron and item card creation, and
the Syndetics external service. Dealing with those places another way
would reduce our dependency on XML::Simple by about half.
-Ian
On Wed, Apr 11, 2012 at 13:15, Ian Walls wrote:
> C4/ILSDI/Services.pm also uses XML::
C4/ILSDI/Services.pm also uses XML::Simple to do output. Strings are
actually composed in the subroutines, making any changes to the schema a
C4-editing patch. Having an ILSDI template directory would serve us much
better here, I think.
-Ian
2012/4/11 Robin Sheat
> Op 11-04-12 23:31, Ian Wal
On Wed, Apr 11, 2012 at 11:34:07PM +1200, Robin Sheat wrote:
> Op 11-04-12 23:12, Ian Walls schreef:
>
> It's not really for that, it's to allow seeking through records on tape
> to be efficient (at least, the way it's designed suggests that to me.)
I'm old enough to confirm thats the purpose alth
2012/4/11 Robin Sheat
> Op 11-04-12 23:12, Ian Walls schreef:
>
> > I'd say just stop counting at 9, and let the export scripts provide
> > the recalculation, truncation or warning. Since we don't include items
> > internally in our MARC except for indexing, we shouldn't run into this
> > si
Dear MJR
First of all I would like to say sorry for not sending the previous mail through a new thread. I'll remember this for future submissions. Thanks for your kind sharing of knowledge. It's really surprising for me that this important features are not finding suitable support from libraries. I
Op 11-04-12 23:31, Ian Walls schreef:
> Right now, the few web services we have all create their XML output
> using XML::Simple. This is not the fastest parser in the world, so I've
> been looking to minimize/remove it's usage.
I work with the maintainer of XML::Simple. I'm quite sure he wouldn't
Op 11-04-12 23:12, Ian Walls schreef:
> Is the record length portion of the leader really useful to anyone
> anymore? It's really a much more valuable concept 30 years ago, when
> storage in bytes was a real consideration.
It's not really for that, it's to allow seeking through records on tape
to
Right now, the few web services we have all create their XML output using
XML::Simple. This is not the fastest parser in the world, so I've been
looking to minimize/remove it's usage. Looking at it in /svc got me
thinking: perhaps we should be using T:T to generate our web services
output instea
On 11/04/12 19:43, MJ Ray wrote:
Partha Mukhopadhyay
Koha does not include (upto version 3.6.4) the provision of MARC 21
authority management from GUI interfaces. For example 1) to import a
MARC formatted authority file (like bibliographic records), 2) to
export authority records from local reco
Is the record length portion of the leader really useful to anyone
anymore? It's really a much more valuable concept 30 years ago, when
storage in bytes was a real consideration.
I'd say just stop counting at 9, and let the export scripts provide the
recalculation, truncation or warning. Sin
Partha Mukhopadhyay
> Koha does not include (upto version 3.6.4) the provision of MARC 21
> authority management from GUI interfaces. For example 1) to import a
> MARC formatted authority file (like bibliographic records), 2) to
> export authority records from local records through GUI
> etc. Pres
Dear Friends
Koha does not include (upto version 3.6.4) the provision of MARC 21 authority management from GUI interfaces. For example 1) to import a MARC formatted authority file (like bibliographic records), 2) to export authority records from local records through GUI etc. Presently it provide
Hie,
That's right, Koha uses both marc and marcxml for data storage.
It costs performance on insert and update.
Can we imagine dropping marc field form database and serialize on demande ?
--
Fridolyn SOMERS
fridolyn.som...@gmail.com
Marsillargues - France
2012/4/10 Ian Walls
> I'd advocate I
Le 10/04/2012 17:15, Ian Walls a écrit :
I'd advocate ISO-2709 only being an import/export format, and never
using it internally. It's just got too many limitations, as we're
seeing here.
On import, we check for valid leaders, and warn if not.
On export, we calculate the leader, and if it exce
14 matches
Mail list logo
