Hi all,
We've recently installed GeoNetwork 2.1 at our site for metadata search
purposes only, using the harvest functionality to populate the GN metadata
repository from a legacy metadata system. The harvest needs to occur
periodically, which GN supports, although it must occur at a specific time of
the day, which GN does not appear to support very well. It seems that to get
the harvest to occur at a set time each day, the harvest period must be set
to one day and the harvest node activated at the time of day the harvest is
to start. This presents the problem that we need the harvest to occur at
around 2.00am, so manually activating the harvest node via the harvest
management GUI is impractical. The situation is made more complex by the
fact that every time the web container is restarted the harvest node is
deactivated.
A workaround has been to create a "one run only" harvest node and use an
external routine to invoke the harvest node using the login,
xml.harvesting.start and xml.harvesting.run services. The routine is called
via a cron job which gives us total control over the timing of its execution.
Am I missing something with the "out-of-the-box" harvesting functionality?
If not I'd be very interested to hear if anyone has tackled this issue (and
found a better solution than mine!).
Thanks,
Aaron Sedgmen
Geoscience Australia
Dear Aaron,
You are right on. It would need some reviewing of the harvesting scheduler to make it run on a specific time instead of on a time period basis. For now, you'll be stuck with your current practice.
Ciao,
Jeroen
On Apr 23, 2008, at 4:10 AM, Aaron.Sedgmen@anonymised.com wrote:
Hi all,
We've recently installed GeoNetwork 2.1 at our site for metadata search
purposes only, using the harvest functionality to populate the GN metadata
repository from a legacy metadata system. The harvest needs to occur
periodically, which GN supports, although it must occur at a specific time of
the day, which GN does not appear to support very well. It seems that to get
the harvest to occur at a set time each day, the harvest period must be set
to one day and the harvest node activated at the time of day the harvest is
to start. This presents the problem that we need the harvest to occur at
around 2.00am, so manually activating the harvest node via the harvest
management GUI is impractical. The situation is made more complex by the
fact that every time the web container is restarted the harvest node is
deactivated.
A workaround has been to create a "one run only" harvest node and use an
external routine to invoke the harvest node using the login,
xml.harvesting.start and xml.harvesting.run services. The routine is called
via a cron job which gives us total control over the timing of its execution.
Am I missing something with the "out-of-the-box" harvesting functionality?
If not I'd be very interested to hear if anyone has tackled this issue (and
found a better solution than mine!).
Thanks,
Aaron Sedgmen
Geoscience Australia
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
GeoNetwork-users mailing list
GeoNetwork-users@lists.sourceforge.net
geonetwork-users List Signup and Options
GeoNetwork OpenSource is maintained at GeoNetwork - Geographic Metadata Catalog download | SourceForge.net