Releases: keeps/commons-ip
Releases · keeps/commons-ip
Version 2.3.1
Version 2.3.0
Enhancements
- Add support to bagit-java v5.2.0
Security fixes
- Dependency updates
- logback-classic to 1.3.5
- bagit to 5.2.0
- commons-configuration2 to 2.8.0
- jdom2 to 2.0.6.1
- jackson-datatype-threetenbp to 2.12.5
Version 2.2.1
Version 2.2.0
What's new
Security fixes
Version 2.1.0
Version 2.0.1
Bug Fixes
Null pointer when sip doesn't have any data, documentation and schemas #89.
Version 2.0.0
What's new
Now you can use commons-ip as a command-line tool to validate E-ARK SIP and AIPs against 2.0.4 specification. You can also use it as a Java library to parse, produce or validate E-ARK SIP 2.0.4.
Enhancements
- Added verbose option to CLI.
- Added E-ARK report
Bug Fixes
- CSIPSTR1 - Any Information Package MUST be included within a single physical root folder (known as the “Information Package root folder”). For packages presented in an archive format, see CSIPSTR3, the archive MUST unpack to a single root folder. #47
- CSIP4 - Used to declare the Content Information Type Specification used when creating the package. Legal values are defined in a fixed vocabulary. The attribute is mandatory for representation level METS documents. #49
- CSIP64 - The value in the mets/fileSec/fileGrp/USE is the name of the whole folder structure to the data #50
- CSIP34 - Indicates the status of the package using a fixed vocabulary. #51
- SIP23 - The type of the contact person agent is “INDIVIDUAL”. #52
- CSIP107 - The package’s representation division element LABEL attribute value must be the path to the representation level METS document. This requirement gives the same value to be used as the requirement named “File group identifier” #53
- CSIP88 - The metadata referenced in the administrative and/or descriptive metadata section is described in the structural map with one sub division. When the transfer consists of only administrative and/or descriptive metadata this is the only sub division that occurs. #54
- CSIP95 - The documentation division element in the package uses the value “Documentation” from the vocabulary as the value for the LABEL attribute. #55
- CSIP99 -The schema division element’s LABEL attribute has the value “Schemas” from the vocabulary. #56
- CSIPSTR5 - The Information Package root folder SHOULD include a folder named metadata, which SHOULD include metadata relevant to the whole package. #57
- CSIPSTR10 - The representations folder SHOULD include a sub-folder for each individual representation (i.e. the “representation folder”). Each representation folder should have a string name that is unique within the package scope. For example the name of the representation and/or its creation date might be good candidates as a representation sub-folder name. #59
- CSIPSTR12 - The representation folder SHOULD include a metadata file named METS.xml which includes information about the identity and structure of the representation and its components. The recommended best practice is to always have a METS.xml in the representation folder. #60
- CSIPSTR11: Detection seems faulty #75
- CSIPSTR13: Detection fault #76
- CSIPSTR15: Schema folder detection #77
- CSIPSTR16: Detection of documentation folder. #78
- CSIP1 mets/@OBJID always fires #79
- Parsing of paths from the root METS is faulty #80
- CSIP23 always fires #81
- More informative reporting if the package can't be found #82
- Discrepancies between report results #85
Version 2.0.0-beta2
What's new
Enhancements
- Improved validations in the Commons-ip validator.
Version 2.0.0-beta1
What's new
Security Fixes
- commons-io from 2.6 to 2.7
- commons-beanutils from 1.9.3 to 1.9.4
- junit from 4.12 to 4.13.1
- commons-configuration2 from 2.3 to 2.7
2.0.0-alpha2
Fixes
- E-ARK ingestion fails when packaged item name contains plus (+) symbol (#29)