keeps/commons-ip
Commons IP is project that provide a command-line tool and Java Library to validate and manipulate E-ARK Information Packages, so to create or process E-ARK SIP and AIP and also validate them against official specifications.
JavaLGPL-3.0
Issues
- 0
- 0
Software version METS agent note is empty when generating SIPs in development mode
#119 opened by prettybits - 0
Metadata references with `MDTYPE` "OTHER" should generate `OTHERMDTYPE` containing the original type information
#120 opened by prettybits - 3
Administrative metadata only handled for preservation metadata / `digiprovMD`
#118 opened by prettybits - 4
- 1
Improve Report of Validator
#83 opened by JoaoGomes2110 - 1
Schemas file group missing in created roots METS
#116 opened by prettybits - 1
Exception when creating a SIP without representations
#112 opened by luis100 - 1
Command-line SIP creator gives an error when the metadata is of type other
#115 opened by JoaoGomes2110 - 2
command-line tool validator throws an exception with an undocumented option
#109 opened by yonnycardenas - 0
- 0
Simple CLI for creating SIPs
#103 opened by luis100 - 0
Support for empty folders in METS of SIP-S
#107 opened by JoaoGomes2110 - 0
- 0
SIP shallow support
#105 opened by JoaoGomes2110 - 4
How is compliance with CSIPSTR10 established
#74 opened by carlwilson - 2
Compliance with CSIP 2.0.4
#42 opened by hsilva-keep - 3
Compliance with SIP 2.0.4
#43 opened by hsilva-keep - 0
- 1
Discrepancies between report results
#85 opened by carlwilson - 2
- 2
Validation REST API
#44 opened by hsilva-keep - 4
CSIP1 mets/@OBJID always fires
#79 opened by carlwilson - 3
Parsing of paths from the root METS is faulty
#80 opened by carlwilson - 1
- 1
CSIPSTR13: Detection fault
#76 opened by carlwilson - 3
CSIPSTR15: Schema folder detection
#77 opened by carlwilson - 1
CSIPSTR16: Detection of documentation folder.
#78 opened by carlwilson - 1
CSIPSTR11: Detection seems faulty
#75 opened by carlwilson - 0
CSIP23 always fires
#81 opened by carlwilson - 4
- 1
- 0
CSIP60 - All documentation pertaining to the transferred content is placed in one or more file group elements with mets/fileSec/fileGrp/@USE attribute value “Documentation”.
#46 opened by JoaoGomes2110 - 0
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 opened by JoaoGomes2110 - 1
- 0
- 0
CSIP64 - The value in the mets/fileSec/fileGrp/@USE is the name of the whole folder structure to the data
#50 opened by JoaoGomes2110 - 0
CSIP107 - The package’s representation division <div> 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 opened by JoaoGomes2110 - 0
CSIP95 - The documentation division <div> element in the package uses the value “Documentation” from the vocabulary as the value for the @LABEL attribute.
#55 opened by JoaoGomes2110 - 0
CSIP99 -The schema division <div> element’s @LABEL attribute has the value “Schemas” from the vocabulary.
#56 opened by JoaoGomes2110 - 0
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 opened by JoaoGomes2110 - 0
CSIP80 Requirement - The structural map <structMap> element is the only mandatory element in the METS. The <structMap> in the CSIP describes the highest logical structure of the IP.
#45 opened by JoaoGomes2110 - 0
CSIPSTR5 - The Information Package root folder SHOULD include a folder named metadata, which SHOULD include metadata relevant to the whole package.
#57 opened by JoaoGomes2110 - 0
CSIP1 - The mets/@OBJID attribute is mandatory, its value is a string identifier for the METS document. For the package METS document, this should be the name/ID of the package, i.e. the name of the package root folder. For a representation level METS document this value records the name/ID of the representation, i.e. the name of the top-level representation folder.
#48 opened by JoaoGomes2110 - 0
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 opened by JoaoGomes2110 - 0
CSIPSTR9 - The Information Package folder SHOULD include a folder named representations.
#58 opened by JoaoGomes2110 - 0
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 opened by JoaoGomes2110 - 0
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 opened by JoaoGomes2110 - 2
Class not found when running with Java 11
#37 opened by luis100 - 0
METS.xml file format
#36 opened by MChatzakis