-
Notifications
You must be signed in to change notification settings - Fork 5
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* Initial BagItProfile work * More testing * More tests * Track serializations * Load and validate profiles * Return file path in archive type exception * Windows test * Clean up extension handling * Add more profile tests * Fixes and more profile tests * Always check for Allow-Fetch before Require-Fetch, so the reverse test is unnecessary * Fix callable in array_filter * Move json into tests * More tests * Add methods to add profile to bag and some tests * Allow other bag-info tag options * Test bag is valid before creating a package * Read BagIt Profile identifiers from bag-info.txt and validate Additional tests Handle long lines without a space to break at * Add a change log * Some tidying * Correct PIPEWAIT and add test for trait
- Loading branch information
Showing
28 changed files
with
3,714 additions
and
392 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,44 @@ | ||
# Change Log | ||
|
||
The purpose of this document is to provide a list of changes included in a release under the covers that | ||
may have an impact on the user. This is not a comprehensive list of all changes, but hopefully catches most and | ||
provides a reasoning for the changes. | ||
|
||
## v5.0.0 | ||
|
||
### Added | ||
|
||
#### BagIt Profile support. | ||
You can now add BagIt Profile(s) to a newly created bag and/or they will be downloaded and parsed when validating an | ||
existing bag, assuming the profile is available at the URL specified in the bag-info.txt file. | ||
|
||
Profiles are validated against the [BagIt Profile Specification (v1.4.0)](https://bagit-profiles.github.io/bagit-profiles-specification/) | ||
and profile rules are enforced when validating a bag (`$bag->isValid()`) and any errors are displayed in the `$bag->getErrors()` array. | ||
|
||
To add a profile to a bag you can use either: | ||
- `$bag->addProfileByJson($jsonString)` - To add a profile from a JSON string. | ||
- `$bag->addProfileByURL($url)` - To add a profile from a URL. | ||
|
||
Profiles are stored internally using their `BagIt-Profile-Identifier` as a key. You can only add a profile once | ||
per identifier. If you try to add a profile with the same identifier it will be ignored. | ||
|
||
To remove a profile you can use `$bag->removeBagProfile($profileIdentifier)` to remove a profile. | ||
|
||
You can also use `$bag->clearAllProfiles()` to remove all profiles from a bag. | ||
|
||
#### Package command validates the bag | ||
|
||
Previous versions allowed you to package without validating the bag. Now the package command will validate the bag | ||
before packaging. If the bag is not valid the package command will fail with a `BagItException::class` being thrown. | ||
|
||
This is due to the addition of BagIt Profile support, if you add a profile to a bag we want to ensure you do not package | ||
an invalid bag. | ||
|
||
TODO: Validate the serialization being attempted during package validation. | ||
|
||
### Removed | ||
|
||
#### PHP 7 Support | ||
|
||
This library now requires PHP 8.0 or higher, while PHP 8.0 is already end of life we will support it for the time being. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.