Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BagProfile Improvements #18

Closed
mikejritter opened this issue Apr 3, 2020 · 0 comments · Fixed by #26
Closed

BagProfile Improvements #18

mikejritter opened this issue Apr 3, 2020 · 0 comments · Fixed by #26
Assignees

Comments

@mikejritter
Copy link
Contributor

BagProfile offers validation for both BagConfig and Bag, but it might be nice to offer more generalized approaches to validation. For example, BagConfig holds tag files and their key/value pairs in a Map<String, Map<String, String>>. An extra validation method could be made for the Map.

@mikejritter mikejritter self-assigned this Apr 23, 2020
awoods pushed a commit that referenced this issue Apr 28, 2020
* Add additional validate method for tag files
* Simplify init of Other-Info values
* Use lower-hypen formatting when storing field names for tag files
* Replace sections set with metadataFields keyset
* Add some generic method for validating from a BagProfile
* checkRequiredTagsExist - checks that all tag files in a profile exist
* validateTag - validates given fields for a tag file for a profile
* Additional coverage for BagProfile#metadataFields
* Create method for validating all BagIt tag files
* Add a non-BagConfig way of validating conformance to a BagProfile. This
requires the user to pass the configuration of the tag files in as a
Map<String, Map<String, String>> which is the same data structure which the
BagConfig uses.

Resolves #18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant