Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

 

Excerpt

Was released august 21st 2013

Table of Contents
minLevel2

Highlights

  • The harvest history for a domain table is now sortable. See 
    Jira Legacy
    serverSBForgeSystem JIRA
    serverId327e372c81c76265-baf0cab2-3de43ba5-afa1b74d-7694d9fcf12bee7cd9a2765e
    keyNAS-2199
  • It is now possible to exclude domains from a snapshot harvest. See 
    Jira Legacy
    serverSBForgeSystem JIRA
    serverId327e372c81c76265-baf0cab2-3de43ba5-afa1b74d-7694d9fcf12bee7cd9a2765e
    keyNAS-1725
  • The derby database bundled with Netarchivesuite has been upgraded to 10.10.1.1 
    Jira Legacy
    serverSBForgeSystem JIRA
    serverId327e372c81c76265-baf0cab2-3de43ba5-afa1b74d-7694d9fcf12bee7cd9a2765e
    keyNAS-2220
  • The version of Lucene used in Deduplication and by the Viewerproxy has been upgraded to 4.4
    Jira Legacy
    serverSBForgeSystem JIRA
    serverId327e372c81c76265-baf0cab2-3de43ba5-afa1b74d-7694d9fcf12bee7cd9a2765e
    keyNAS-2201

       

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

Jira Issues
renderModestatic
columnstype,key,priority,summary
urlhttps://sbforge.org/jira/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?jqlQuery=project+%3D+NAS+AND+fixVersion+%3D+11447+AND+NOT+component+%3D+Test+ORDER+BY+priority+DESC%2C+created+ASC&tempMax=1000

Known issues

Jira Issues
columnstype,key,priority,summary,fixVersion
urlhttps://sbforge.org/jira/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?jqlQuery=project+%3D+NAS+AND+issuetype+%3D+Bug+AND+affectedVersion+%3D+"4%224.2"2%22+ORDER+BY+priority+DESC%2C+cf%5B10010%5D+ASC%2C+fixVersion+ASC&tempMax=1000