NetarchiveSuite 4.2 Release Notes

 

Was released august 21st 2013

Highlights

  • The harvest history for a domain table is now sortable. See  NAS-2199 - Getting issue details... STATUS
  • It is now possible to exclude domains from a snapshot harvest. See  NAS-1725 - Getting issue details... STATUS
  • The derby database bundled with Netarchivesuite has been upgraded to 10.10.1.1  NAS-2220 - Getting issue details... STATUS
  • The version of Lucene used in Deduplication and by the Viewerproxy has been upgraded to 4.4 NAS-2201 - Getting issue details... STATUS

       

Upgrade-notes

The harvest database need to be updated before starting NetarchiveSuite 4.2 the first time using the HarvestdatabaseUpdateApplication program.  Information on how to do that can be found in the additional tools manual under Harvester tools. If you don't do it, the following two applications will not start:  GUIApplication and HarvestJobManagerApplication .

Table 'jobs' moves from version: 8 to 9 with the following change:

ALTER TABLE jobs ADD COLUMN harvestname_prefix VARCHAR(100) DEFAULT NULL

Table 'harvestdefinitions' moves from version: 2 to 3 with the following change:

ALTER TABLE harvestdefinitions ADD COLUMN audience VARCHAR(100) DEFAULT NULL

 

The choice between asking Heritrix to writer ARC of WARC files is now a system-wide decision

In 4.0, this choice was made on the harvest-machines. Now this choice is performed in the HarvestJobManager when creating the harvestjob. The decision is made by reading the setting harvester.harvesting.heritrix.archiveFormat. The choice of metadataformat is still decided by the value of harvester.harvesting.metadata.metadataFormat on the harvestmachines. But ofcourse the supported way is to use the same metatadataFormat for all harvests.

Full list of issues resolved in this release

type key priority summary

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Known issues

type key priority summary fixVersion

Unable to locate Jira server for this macro. It may be due to Application Link configuration.