- Fixed broken link to batch workflows help document.
- Fixed "percent uploading" going past 100% in job run page.
- Fixed error on S3 download page: if bucket list is unavailable, show only the contents of the bucket specified in StorageService.Bucket.
- Fixed: Save most recent workflow edits when exporting workflow to json.
- Fixed: Allow huge bags (100,000+ files) to complete bagging, validation and upload without interruption. https://trello.com/c/oPPNjCus
- Fixed: When connecting to APTrust remote repository, use the member API, not the admin API. This fixes 403/unauthorized exceptions for valid member users. https://trello.com/c/xU77Ploy
- Added S3 download feature. You can now browse buckets and download files from S3 endpoints configured in Storage Services.
- Fixed an issue that caused bagging to fail when the user's Bagging Directory does not exist.
- Feature: DART now includes upload-only jobs. You can upload previously created bags or files of any kind to remote S3 and SFTP servers.
- Feature: DART can now create, validate, and upload tarred, gzipped bags (.tar.gz or .tgz)
- Feature: DART can now create, validate, and upload loose bags (not tarred or gzipped)
- Feature: DART can save artifacts (tag files, manifests, etc.) to file from the artifacts screen
- Fixed: Menu items on tag file dropdown are no longer stuck on after being clicked
- Fixed omissions in the algorithms lists for allowed manifests and allowed tag manifests in version 2.3 of the APTrust BagIt profile. This list now correctly includes sha1 and sha512 as allowed algorithms.
- Tag Source-Organization is no longer required in APTrust BagIt Profile v2.3 (to match prior profile v2.2).
- Converted app from pure web service to Wails for easier installation and better desktop experience.
- Fixed: Can now drag folder by icon or name when adding files to a bag.
- Fixed: Default StorageService AllowsUpload to true, so service appears in list of Job upload options.
- Fixed: When user chooses to export all settings, export all of them, not just the last one.
- Fixed: Don't add empty list of allowed tag values when user edits a BagIt Profile tag definition.
- Fixed: Stop hiding Storage-Option on job metadata page when using APTrust BagIt Profiles.
- Fixed: When user changes a BagIt profile's required/allowed manifests list, clear out the items they removed.
- Fixed: Return to Dashboard when user cancels settings export.
- Changed: "View Artifacts" to "View Logs, Manifests and Tag Files" #560
- Fixed: Restored missing job status display messages. #563
- Fixed: File and folder count display after job run is now correct. #561
- Fixed: DART 3 can now import settings from DART 2.
- Fixed: Users can now delete imported BagIt profiles.
- First alpha release of DART 3, using Golang instead of Electron and JavaScript
- Fixed "Show Logs" and "About" links not working.
- Updated Electron to 20.0.1
- Updated Electron builder and number of dependencies with security issues including minimatch and JSON5.
- Fixed Date Modified not preserved on Windows
- Fixed DART batch job without upload should not delete bags
- Fixed Certificate expired error when connecting to remote repositories
- Updated Electron from 11.5.0 to 20.0.0
- Updated a number of dependencies that Dependabot flagged as vulnerable
- Fixed BagIt-Profile-Info for BTR profile. (Migration 20220429T182345Z.js)
- Default bagging directory is no longer hidden in ~/home/.dart. A new migration sets the bagging directory to ~/Documents/DART, unless user has previously changed this setting on their own. Fixes Make default bagging directory not hidden?
- Fixed File extension in output path does not update in Packaging window when changing serialisation
- Stopped showing unsupported output formats (zip, gzip, rar, 7z) in list of job packaging format options. We'll re-add these when we support the formats.
- Temporarily disabled tar as a standalone output format (though tarred bags are still supported). This feature is not fully implemented. We'll return it as an option when it's ready. This is a temporary fix to .tar packaging producing no output
- Fixed broken translation/localization
- Updated async library to fix security bug
- Fixed Bagit Profile Export issue with cancelling adding questions
- Fixed security issue, bumping plist from 3.0.4 to 3.0.5
- Fixed security issue, bumping minimist from 1.2.5 to 1.2.6
- Bumped ssh2-sftp-client from 7.1.0 to 7.2.3.
- Updated some build dependencies that don't make into the distributable package (electron-build and xcode version).
This release contains a number of security fixes, but no new features.
- Upgraded Electron from 11.4.10 to 11.5.0 to fix thumbnail vulnerability.
- Upgraded ssh2 from 0.8.9 to 1.5.0 to mitigate CVE-2020-26301 - OS command injection.
The remaining ansi-regex and set-value affect libraries used only in development and testing. These libraries are not included in the DART distribution.
- Fixed a bug that caused empty StorageService.port to be serialized as an empty string instead of zero. This was not a problem for DART, but it was for DART runner, which expects an integer.
- Added Workflow Export feature to work with DART runner.
- This release includes security updates but no new features.
- Upgraded path-parse library to v1.0.7 to fix CVE-2021-23343.
- Upgraded csv-parse to v4.16.2.
- Fixed Apple code signing and notarization to stop "unknown author" warnings on Mac OS.
- Added BSD license.
- Fixed Dart not accepting files in commit eb75c3f.
- Fixed a typo in the "files to package" screen.
- Removed list of allowed values in the bag-info.txt/Bagging-Software tag. That had caused some user-defined custom BagIt Profiles to generate bags that would not validate.
- Extended timeout on a few async tests that sporadically timed out.
- Export BagIt Profiles to match version 1.3.0 of the BagIt Profile Specification
- Fixed regressions: Electron 10+ broke the Help > About and Help > Logs popup windows.
- Added Batch Jobs - Run a workflow batch to create and ship hundreds of bags at once. See the documentation at https://aptrust.github.io/dart-docs/users/workflows/batch_jobs/
- Fixed Unserialized bags which match existing path are invalid
- Updated to Electron 9.0.0
- Updated several npm dependencies
- Settings import question now displays a password field instead of a regular text input for passwords.
- (Internal) Added
npm run bumpto simplify version changes.
- Exported BagIt profiles now include Manifests-Allowed and Tag-Maifests-Allowed
- Settings export no long fails on missing BagIt profiles.
- Progress bars on Job Run page no longer bounce when a bag contains long file names.
- Validation progress bar on Job Run page is marked complete when job succeeds.
- Security updates to underlying npm libraries
- Fixed Bag-Size not written to bag-info.txt
- Security updates for a number npm dependencies
- Added validation-only jobs for users who simply want to validate an existing bag.
- Fixed the "empty" BagIt profile, which allows validation against the basic BagIt spec. Fixed include:
- sha256 manifest and sha256 tag manifest are no longer required.
- Serialization is no longer required.
- fetch.txt is now allowed.
- Added Beyond the Repository (BTR) BagIt profile to the default installation.
- Removed Setup Modules. The settings import/export system serves the same function and is easier to set up and distribute.
- Fixed the filter on sensitive data export. When exporting settings, DART will not export logins, passwords, or API tokens, unless they refer to environment variables.
- Added a migration to remove the DPN BagIt profile. This profile was used for internal testing and does not need to be public. Fixes issue DPN-Object-ID and First-Version-Object-ID not generated.
- Fixed mismatched manifest algorithms in generated bags.
- Added a migration that installs a new "Empty Profile." This profile conforms to the base BagIt Specification but does not require the user to fill in any tag values. This addresses issue #221 Does BagIt Profile need to be mandatory
- Published Empty Profile.
- Fixed issue #222 Value for tag 'BagIt-Profile-Identifier' in bag-info.txt is missing
- Fixed an occasional validation error where manifest parser read empty last line of manifest as a valid entry. Fixed in commit 231afa9