|The problem is that this is ALL custom. I'm actually using it for
hierarchies of security log information (IP addresses, ports,
protocols). This is all generated by a program I have created.
I'm thinking about just exporting to a self designed XML repository at
this stage though. Greenstone has been good so far, but we're looking at
scaling up even farther and I don't know how it can be done using GSDL.
[mailto:email@example.com] On Behalf Of
Sent: October 18, 2005 5:28 PM
Subject: Fwd: [greenstone-users] Out of Memory Error
What is contained in your metadata.xml? What filetypes are in
your collection? Is there any way you could build an equivalent
collection without using the metadata.xml? Have you experimented with
a custom import plugin?
Greenstone Digital Library and Digitisation Specialists
Begin forwarded message:
> From: "Nathan Einwechter" <firstname.lastname@example.org>
> Date: 19 October 2005 10:04:14 AM
> To: <email@example.com>
> Subject: RE: [greenstone-users] Out of Memory Error
> Does anyone know the maximum size I can have for a metadata.xml
> file for
> a given amount of ram etc.?
> -- Nathan
> -----Original Message-----
> From: firstname.lastname@example.org
> [mailto:email@example.com] On Behalf Of
> John Rowe
> Sent: October 17, 2005 10:03 PM
> To: firstname.lastname@example.org
> Subject: Fwd: [greenstone-users] Out of Memory Error
> it seems that the Greenstone import process is simply not built
> to handle a metadata file that large. The easiest solution would be
> to split your import directory (and metadata.xml file) up into
> smaller directories under the main import directory. The filesystem
> should end up looking something like the following:
> Hope this helps.
> John Rowe
> DL Consulting
> Greenstone Digital Library and Digitisation Specialists
> greenstone-users mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
greenstone-users mailing list