The methods in dk.netarkivet.viewerproxy.webinterface.Reporting does not support metadata files using the BNF naming
Field Tab
Test
Field Tab
Test
Description
Checklist
Activity
Show:
SrApril 11, 2018 at 9:24 AM
And I have also tested it using BNF style naming
And it works perfectly
SrApril 10, 2018 at 1:49 PMEdited
I am currently testing your solution with the standard naming setup
SrApril 10, 2018 at 10:08 AM
Yes, the same regexp is used for selecting the correct metadatafile to search in
Sara AubryApril 10, 2018 at 9:02 AM
Will this regexp also fix the bugs on the features "Display crawl lines matching this regexp" and "Browse only crawl-log lines for this domain XXX" ?
Sara AubryApril 10, 2018 at 8:48 AM
Bert says we should stick to his proposal as the metadatafile_suffix starts with a hyphen.
So if you use "-(.*)?", there will be two hyphens in a row which would not match your naming scheme.
Fixed
Details
Details
Details
Checklist
Open Checklist
Checklist
Open Checklist
Checklist
Open Checklist
Created March 22, 2018 at 3:13 PM
Updated April 11, 2018 at 10:15 AM
Resolved April 11, 2018 at 9:33 AM
The methods in https://github.com/netarchivesuite/netarchivesuite/blob/master/harvester/harvester-core/src/main/java/dk/netarkivet/viewerproxy/webinterface/Reporting.java
all use the helper method
This code currently assumes that we do the legacy style naming of the metadatafiles
and not the prefix stile :
https://github.com/netarchivesuite/netarchivesuite/blob/master/harvester/harvester-core/src/main/java/dk/netarkivet/harvester/harvesting/metadata/MetadataFileWriter.java
The difference:
Currently, collectionName is read from setting HarvesterSettings.HERITRIX_PREFIX_COLLECTION_NAME