You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
* 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
BagProfile
offers validation for bothBagConfig
andBag
, but it might be nice to offer more generalized approaches to validation. For example,BagConfig
holds tag files and their key/value pairs in aMap<String, Map<String, String>>
. An extra validation method could be made for the Map.The text was updated successfully, but these errors were encountered: