Open call for testing of the IPT 2.0RC1
Dear all,
The IPT development team are pleased to invite you to participate in the testing of the re-engineered and simplified IPT.
The revised IPT is the result of a re-engineering effort of the 1.0 version of the IPT, specifically to: - Reduce the server requirements significantly - Increase the data import performance by removing the embedded database - Remove the dependency on heavy libraries and tools such as Geoserver - Remove all data interfaces that are not necessary for data publication through GBIF - Improve the robustness of the tool
The result is an IPT that: - is less than 12MB - starts in only a few seconds - supports fast import (1 million records in 15 seconds or so) - includes an expanded metadata profile - supports the importing of DwC Archives - allows multiple organisation support (an IPT may be installed by an institution, but the resource associated with a different institution)
We would like to thank those early testers who have helped us, over the last 5 weeks, identify and address some 81 issues and enhancements already (http://code.google.com/p/gbif-providertoolkit/issues/list?can=1&q=Milest... ).
All reported defects have been addressed, and therefore we have indicated this is a version that is a candidate for being a formal release and therefore labelled IPT 2.0RC1.
Issues are actively being tracked, monitored and will be prioritised and addressed, and I ask that you use this utility to record any issues that you come across: http://code.google.com/p/gbif-providertoolkit/issues/list
The user manual and engineering documentation drafting are under way and expected to be finished by the end of 2010 prior to the general availability (IPT 2.0GA) release. The IPT 2.0GA release is targeted by the end of the 2010 but will only be made available following a successful community test phase.
The IPT 2.0RC1 for this test can be downloaded: http://gbif-providertoolkit.googlecode.com/files/ipt-2.0RC1.war The IPT 2.0RC1 is restricted for use to the GBIF development registry at this stage and therefore can not be used for publication onto the GBIF network during this testing phase.
Please find attached some basic guideline information for testers in the absence of the user manual.
Thank you once again to all IPT contributers.
Best wishes, Tim
Congratulations! It is a pleasure to submit issues, if they are acted upon so quickly! Good job!
Peter
On Mon, Nov 29, 2010 at 11:46, Tim Robertson trobertson@gbif.org wrote:
Dear all, The IPT development team are pleased to invite you to participate in the testing of the re-engineered and simplified IPT. The revised IPT is the result of a re-engineering effort of the 1.0 version of the IPT, specifically to: - Reduce the server requirements significantly - Increase the data import performance by removing the embedded database - Remove the dependency on heavy libraries and tools such as Geoserver - Remove all data interfaces that are not necessary for data publication through GBIF - Improve the robustness of the tool The result is an IPT that: - is less than 12MB - starts in only a few seconds - supports fast import (1 million records in 15 seconds or so) - includes an expanded metadata profile - supports the importing of DwC Archives - allows multiple organisation support (an IPT may be installed by an institution, but the resource associated with a different institution) We would like to thank those early testers who have helped us, over the last 5 weeks, identify and address some 81 issues and enhancements already (http://code.google.com/p/gbif-providertoolkit/issues/list?can=1&q=Milest...).
All reported defects have been addressed, and therefore we have indicated this is a version that is a candidate for being a formal release and therefore labelled IPT 2.0RC1. Issues are actively being tracked, monitored and will be prioritised and addressed, and I ask that you use this utility to record any issues that you come across: http://code.google.com/p/gbif-providertoolkit/issues/list The user manual and engineering documentation drafting are under way and expected to be finished by the end of 2010 prior to the general availability (IPT 2.0GA) release. The IPT 2.0GA release is targeted by the end of the 2010 but will only be made available following a successful community test phase. The IPT 2.0RC1 for this test can be downloaded: http://gbif-providertoolkit.googlecode.com/files/ipt-2.0RC1.war The IPT 2.0RC1 is restricted for use to the GBIF development registry at this stage and therefore can not be used for publication onto the GBIF network during this testing phase. Please find attached some basic guideline information for testers in the absence of the user manual. Thank you once again to all IPT contributers. Best wishes, Tim
IPT mailing list IPT@lists.gbif.org http://lists.gbif.org/mailman/listinfo/ipt
Thanks Tim! well done, I'll download the new version straight away... Bruno
On Mon, Nov 29, 2010 at 5:46 PM, Tim Robertson trobertson@gbif.org wrote:
Dear all, The IPT development team are pleased to invite you to participate in the testing of the re-engineered and simplified IPT. The revised IPT is the result of a re-engineering effort of the 1.0 version of the IPT, specifically to: - Reduce the server requirements significantly - Increase the data import performance by removing the embedded database - Remove the dependency on heavy libraries and tools such as Geoserver - Remove all data interfaces that are not necessary for data publication through GBIF - Improve the robustness of the tool The result is an IPT that: - is less than 12MB - starts in only a few seconds - supports fast import (1 million records in 15 seconds or so) - includes an expanded metadata profile - supports the importing of DwC Archives - allows multiple organisation support (an IPT may be installed by an institution, but the resource associated with a different institution) We would like to thank those early testers who have helped us, over the last 5 weeks, identify and address some 81 issues and enhancements already (http://code.google.com/p/gbif-providertoolkit/issues/list?can=1&q=Milest...).
All reported defects have been addressed, and therefore we have indicated this is a version that is a candidate for being a formal release and therefore labelled IPT 2.0RC1. Issues are actively being tracked, monitored and will be prioritised and addressed, and I ask that you use this utility to record any issues that you come across: http://code.google.com/p/gbif-providertoolkit/issues/list The user manual and engineering documentation drafting are under way and expected to be finished by the end of 2010 prior to the general availability (IPT 2.0GA) release. The IPT 2.0GA release is targeted by the end of the 2010 but will only be made available following a successful community test phase. The IPT 2.0RC1 for this test can be downloaded: http://gbif-providertoolkit.googlecode.com/files/ipt-2.0RC1.war The IPT 2.0RC1 is restricted for use to the GBIF development registry at this stage and therefore can not be used for publication onto the GBIF network during this testing phase. Please find attached some basic guideline information for testers in the absence of the user manual. Thank you once again to all IPT contributers. Best wishes, Tim
IPT mailing list IPT@lists.gbif.org http://lists.gbif.org/mailman/listinfo/ipt
On Mon, Nov 29, 2010 at 5:46 PM, Tim Robertson trobertson@gbif.org wrote:
The IPT development team are pleased to invite you to participate in the testing of the re-engineered and simplified IPT. The revised IPT is the result of a re-engineering effort of the 1.0 version of the IPT, specifically to: - Reduce the server requirements significantly (...) The result is an IPT that:
- is less than 12MB
- starts in only a few seconds
- supports fast import (1 million records in 15 seconds or so)
(...)
Tim, is this reduction of hardware requirements documented somewhere? What minimum hardware is required now? What hardware is needed for the fast start/fast import mentioned?
Thanks a lot
David
SANT Herbarium Universidade de Santiago de Compostela Galicia - Spain
Hi David,
We are currently drafting both technical docs and user guides which aren't yet available, but I'll comment here.
The server requirements are now to have 256 MB memory available to allocate to the IPT reduced from the previous 1GB minimum and 2GB preferred. The import speed is related to both server CPU performance and hardrive speed for the IPT machine, and then any databases involved and the network to connect to them, so it is really very difficult to quantify. The minimum requirements would be the ability to run Java 5 and allocate 256 MB of memory though.
I hope this helps, Tim
On 12/13/10, Herbario SANT sant.herbarium@gmail.com wrote:
On Mon, Nov 29, 2010 at 5:46 PM, Tim Robertson trobertson@gbif.org wrote:
The IPT development team are pleased to invite you to participate in the testing of the re-engineered and simplified IPT. The revised IPT is the result of a re-engineering effort of the 1.0 version of the IPT, specifically to: - Reduce the server requirements significantly (...) The result is an IPT that:
- is less than 12MB
- starts in only a few seconds
- supports fast import (1 million records in 15 seconds or so)
(...)
Tim, is this reduction of hardware requirements documented somewhere? What minimum hardware is required now? What hardware is needed for the fast start/fast import mentioned?
Thanks a lot
David
SANT Herbarium Universidade de Santiago de Compostela Galicia - Spain _______________________________________________ IPT mailing list IPT@lists.gbif.org http://lists.gbif.org/mailman/listinfo/ipt
participants (5)
-
Bruno Danis -
Herbario SANT -
Peter Desmet -
Tim Robertson -
Tim Robertson