| Table of Contents |
|---|
...
Update on NAS latest tests and developments
There has been little significant work on NetarchiveSuite since the Release of 7.3 at the end of January
- Some minor improvements to the handling of hdfs-cached warcfiles for hadoop mass-processing
- Some speculative work on making deduplication-indexing more concurrent - shelved as it is not currently a priority
An important question we have to deal with is how to manage the fact that the Netarkivet configuration of NetarchiveSuite has now diverged very markedly from that used by most other users. In particular we no longer use the ArcRepository application (The ArcRepository interface remains in use), BitarchiveServer, BitarchiveMonitorServer, or ChecksumFileServer. According to the usage page at Institutional Usage of NetarchiveSuite this is a particularly strong divergence from the OnB setup - but we are missing data from BNE and KB/Sweden.
So what is the future of these components? I think that we will always need to offer a fully-functional Quickstart environment so we will still need to be able to store files and run batch-jobs. But that can be done with local files (as at BnF) and doesn't require any kind of distributed repository. We don't need to remove any code, but in the long run I don't think KB/Denmark can assume responsibility for maintenance of those parts of the codebase we don't use ourselves, so that the distributed ArcRepository and associated components would ultimately either have to be provided only "as is" or maintained by the institutions that continue to use them.
Status of the production sites
...
- April 12th
- May 10th
- June 7th
- July 5th
- September 6th
- October 4th
- November 8th
- December 6th
- January 10th, 2023
Any other business?
·